Run these from an operator’s chat, a command block, or a function file. Stopwatch and Fetchprofile are newer commands — check availability on your Minecraft version.

How to Use the Fetchprofile Command Generator

  1. Pick a lookup mode: Player name, UUID, or Entity/target selector (to read the profile off something already in the world, like @s).
  2. Type the player’s name, their UUID, or a target selector, depending on the mode.
  3. Copy the generated /fetchprofile command into the console or an operator’s chat.
  4. Run it, then click any value it prints in chat to copy that exact piece (name, UUID, or signed skin/cape property) for pasting elsewhere.

/fetchprofile is a newer command – verify it exists on your Minecraft version before relying on it.

Command Syntax Reference

/fetchprofile name <player>
/fetchprofile id <uuid>
/fetchprofile entity <target>

/fetchprofile looks up a full game profile – the player’s name, UUID, and their signed skin/cape texture properties – and prints each piece to chat individually, click-to-copy. /fetchprofile name Steve looks the profile up by username, /fetchprofile id 069a79f4-44e9-4726-a5be-fca90e38aaf5 looks it up directly by UUID, and /fetchprofile entity @s reads the profile straight off a target selector matching an entity already in the world (typically a player). The point of all three is the same: getting a correctly signed profile you can paste into a minecraft:profile component – most commonly to set a custom player head’s skin via /give @s player_head[profile={...}] or a similar item component – without needing an external tool to fetch the signed texture data.

Frequently Asked Questions

Why do I need the “signed” skin/cape data instead of just a texture URL?

Minecraft verifies the authenticity of skin/cape textures via a cryptographic signature from Mojang’s session servers. A raw texture URL without that signature won’t render on a player head profile component in recent versions – /fetchprofile gets you the properly signed value directly from the game’s own session handling.

What’s the difference between the three lookup modes?

They’re just three ways to identify the same kind of profile: by exact username, by exact UUID, or by pointing at an entity/target selector already present in the world (like @s for yourself) so you don’t have to type a name or UUID at all.

What do I actually do with the output after running it?

Each printed value – name, UUID, and the signed texture property – is click-to-copy in chat. You paste the relevant piece into a minecraft:profile item component, most commonly to set a player head’s skin without needing a third-party skin/UUID lookup site.

Does /fetchprofile require the player to be online?

Looking up by name or UUID queries the profile service and doesn’t require the player to be online or nearby; looking up by entity/target selector does require a matching entity to actually be present for the selector to resolve.

Related Tools