Fetchprofile Command - Player Profile Lookup

What the /fetchprofile Command Does

/fetchprofile asks Mojang's account servers for a player's game profile and prints it in chat: the exact name, the account UUID and the signed skin textures. Nothing in the world changes; it is a pure lookup that puts copy-ready profile data one click away.

Minecraft added /fetchprofile to Java Edition in 26.1. A game profile is the account record behind every player: the current name, the permanent UUID and a signed textures property that tells the game which skin and cape to render. Until this command existed, getting that data meant third-party websites or digging through server logs; now one chat command prints it all, and every value in the output is click-to-copy.

The command has three forms. The name and id branches resolve the profile online through Mojang's servers, so they work for any account that exists, whether or not that player has ever joined your world. The entity branch instead reads the profile of one entity that is already in the world, which makes @s the quickest way to fetch your own data. Lookups run in the background, so the result can take a moment to appear.

/fetchprofile requires permission level 2 (the gamemasters level): operators, the server console and command blocks can run it, and in singleplayer the world needs cheats enabled.

Fetchprofile Syntax Reference

The full command tree is three branches, each taking a single argument. This is the complete syntax as defined by the game:

Because the name argument is greedy, nothing can follow it; the entire rest of the line is treated as the player name. The entity argument accepts exactly one target, so @a and @e are only valid with limit=1.

Example Commands

Copy any of these straight into chat (as an operator) or into a command block:

Player Heads and the profile Component

The main reason mapmakers reach for /fetchprofile is player heads. A head stores its owner in the minecraft:profile item component, which accepts a name, an id and a properties list. The simplest form only names the player:

A name-only head makes the game resolve the skin itself when the head loads, which needs a working connection to Mojang's servers and silently changes if the account ever renames or swaps skins. For adventure maps that should look the same forever, fetch the profile first, click the id and textures values in the chat output to copy them, and bake them into the component:

Replace the two placeholders with the copied values. A head built this way renders instantly, works on offline-mode servers and keeps the exact skin it was created with. The same trick applies anywhere the profile component appears, including heads placed by /setblock and items created with /item or loot tables.