Minecraft UUID Lookup
Look up a Minecraft player's UUID from their username using the Mojang API. Get both the trimmed and dashed UUID formats.
Embed This Tool
Put the uuid lookup on your own site or server wiki.
<iframe src="https://tools.astroworldmc.com/embed/uuid-lookup" width="700" height="500" frameborder="0" style="border:none;border-radius:12px;" loading="lazy" title="UUID Lookup"></iframe>
How to find a Minecraft player UUID
Enter the username
The current name of a Java Edition account, since the lookup goes to Mojang and Mojang only knows current names.
Copy the form you need
The dashed form for whitelist.json and most plugin configs, the undashed one for API calls and some older files.
Take the skin URL
The lookup also returns the skin the account is wearing at that moment.
Store the UUID
Names change and UUIDs do not, which is why bans, permissions and player data are all kept against the UUID.
How It Works
Resolve Minecraft player UUID from username.
UUIDs straight from the Mojang profile endpointPage updated
How to Use the UUID Lookup Tool
Enter any Minecraft Java Edition username in the search field and click "Look Up UUID" or press Enter. The tool queries the official Mojang API to retrieve the player's UUID (Universally Unique Identifier). Results include the player's current username, their avatar, and the UUID in both standard dashed format and trimmed format without dashes.
Each copy button places the corresponding value directly on your clipboard, ready to paste into server configuration files, plugin configs, whitelists, or ban lists. The dashed format (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx) is used by most server software and plugins, while the trimmed format is what Mojang uses internally and in their API responses. The dashed form is the one whitelist.json expects, so for more than one player at a time the whitelist manager resolves the whole list and writes the file.
Common Use Cases
Server administrators frequently need player UUIDs for whitelist management, permission configuration, and player data lookups. Since Minecraft 1.7.6, the game uses UUIDs instead of usernames to track players. This means a player can change their username but their UUID stays the same, so server configs that reference UUIDs will always point to the correct player.
Plugin developers use UUIDs to store player data persistently. Whether you are building a custom economy system, tracking statistics, or implementing a friend list, UUIDs ensure your data stays tied to the right player even after name changes. This tool makes it simple to test and verify UUID lookups during development.
The skin URL output is a bonus for web developers building player profiles or status pages. You can embed the avatar image directly using the provided URL to display player heads on your website, forum, or Discord bot. The full skin behind that avatar turns around in the 3D skin viewer, and LuckPerms files each player under this same UUID rather than the name, so a rename never loses a group set in the permissions calculator.
What a Minecraft UUID is
| Source | The official Mojang profile API. Only an existing account comes back, a typo returns nothing rather than a guess. |
|---|---|
| Dashed form | 32 hex characters split 8-4-4-4-12. This is the form whitelist.json, ops.json and most plugins expect. |
| Trimmed form | The same 32 characters without dashes, which is how Mojang returns it and how many database columns store it. |
| Version digit | A real Mojang account is a version 4 UUID, so the 13th hex character is a 4. An offline mode UUID is version 3 and carries a 3 there. That single character tells you which world an ID came from. |
| Since when | Minecraft 1.7.6 moved player identity from the name to the UUID, which is why a rename stops breaking server data. |
| Name history | Mojang shut the name history endpoint down in 2022. No public API returns a player's previous names any more. |
Those 32 hex digits come back from Mojang itself, out of the same profile endpoint a server uses to look a player up. The dashed and the trimmed spelling are then built here in the browser from that single answer, so the two can never disagree.
How much room 32 hex digits really is
The two spellings on this page are the same 128 bits, and six of those bits are spoken for before any randomness starts. Writing that out is the fastest way to see why a server may treat the UUID as unique for ever and why the 13th character is worth checking.
32 hex digits x 4 bits = 128 bits, and the four dashes bring the written form to 36 charactersa version 4 UUID fixes 4 bits of version and 2 of variant, leaving 122 randomdistinct values = 2 to the power 122That third line is the practical one. A whitelist full of version 3 UUIDs is an offline mode server, and the moment it goes online mode every one of those entries points at nobody, because an online UUID for the same name is a different number in the same 128 bits.
Frequently Asked Questions
Questions about UUIDs
Why does a name I am sure exists return nothing?
The lookup matches the current name of an existing Java account only. A released name, a typo, or a Bedrock gamertag all come back empty. Bedrock players carry an XUID instead of a Mojang UUID and cannot be resolved here.
Which of the two formats do I paste into my config?
Dashed for whitelist.json, ops.json and most plugin configs. Trimmed where an API or a database column asks for 32 characters. Both have their own copy button so you never have to add or strip dashes by hand.
Can I look up someone's previous names?
No. Mojang removed that endpoint in 2022, so any site still showing name history is replaying a cache from before that date.
Does the UUID change when a player renames?
No, and that is the entire point of it. A config that references the UUID survives every rename, while one that references the name breaks on the first one.
