Locator Bar Color Finder
Type a Java Edition username or a UUID. We reproduce Minecraft's own UUID hash to get the exact marker color your Locator Bar shows — no guessing, no screenshots.
Nothing to show yet
Enter a username or UUID above and the exact marker color appears here.
How this color is decided
Java Edition takes UUID.hashCode(), keeps the low three bytes as red, green and blue, then shades every channel to 90% before drawing the marker. Same UUID, same color, every single world.
What this Minecraft Locator Bar color checker actually calculates
Nothing here is a lookup table, a screenshot match or a guess. In Java Edition a player's marker color is a pure function of their UUID, and this Minecraft Locator Bar color checker runs the same function the game runs.
Three steps. The client calls java.util.UUID.hashCode(), which XORs the UUID's two 64-bit halves together and then XORs the top and bottom halves of that result — 128 bits folded down to one signed 32-bit integer. It reads the low three bytes as red, green and blue. Then it multiplies every channel by 0.9 before drawing, which is why the dot on the bar is always a little darker than the raw hash bytes.
Notch's UUID 069a79f4-44e9-4726-a5be-fca90e38aaf5 hashes to 0xE9F5688E; the low bytes are F5 68 8E, and 90% of those is #DC5D7F. The Minecraft UUID color algorithm page walks the arithmetic step by step. Because no randomness and no server state enters that chain anywhere, the answer is stable: same UUID, same color, every world, every server, every reinstall.
Username or UUID, and why a lookup comes back empty
Both inputs work. A UUID is hashed instantly in your browser; a username has to be resolved to a UUID through Mojang's public profile API first, which is the only network request this page makes. Three input problems cover almost every failure.
The account is not online-mode.
On a cracked or offline-mode server nobody asks Mojang anything — the server invents a UUID from the name itself: version 3, the MD5 of
OfflinePlayer:<username>. Mojang has never heard of it, so a name lookup returns nothing. The color still exists and is still stable; paste the offline UUID in directly. The split is explained in what a Minecraft UUID is.The username was recycled.
Names can be released and claimed by somebody else; UUIDs never are. If the profile that comes back is not the player you meant, look them up by UUID instead.
The player is on Bedrock.
Bedrock accounts have no Java UUID at all, and Bedrock does not derive marker colors from one — which is its own section below.
Bedrock has no UUID color to look up
This is worth being blunt about, because plenty of pages get it wrong. On Bedrock Edition the Locator Bar assigns each player a color at random, per session. Rejoin the world and it can change. It is not derived from a UUID, an XUID, a gamertag or anything else you can type into a box, so no Minecraft Locator Bar color checker — this one included — can predict a Bedrock color before you join.
If a stable, predictable color matters on your server, you need Java Edition. The Bedrock Locator Bar page covers what Bedrock offers instead: a game rule, a world-creation toggle, and, from 26.30, a scripting API that lets add-on authors set waypoint colors themselves.
What to do once you have the color
A hex value on its own is not worth much. Two follow-ups make it useful.
Check the whole party, not one player.
One color tells you nothing about whether it is distinguishable. Feed every player on your team into the locator bar color checker and it flags the pairs that read the same at a glance on a marker a few pixels wide.
Override it if you do not like it.
/waypoint modify <target> color <name>replaces the UUID default for everyone in the world. The waypoint command generator builds that command for your exact version, and how to change your Locator Bar color compares all three routes — waypoint override, team color and NBT.
Two version facts before you type anything. The Locator Bar landed in Java Edition 1.21.6, and since Java 26.2 the color argument accepts only lowercase names with underscores, so dark_purple is valid and DarkPurple is rejected. Separately, the game rule that switches the bar off was renamed from locatorBar to locator_bar in snapshot 25w44a, shipped in 1.21.11; the Locator Bar gamerule page lists the right name for every version.
Locator Bar color questions people actually ask
Does my Locator Bar color ever change?
Not by itself. The UUID of an online-mode account never changes, so neither does the default color — renaming your account does not touch it. Three things can draw over it: a team color, an explicit /waypoint modify … color, and a resource pack that restyles the icon. Undo an override with color reset. On an offline-mode server the UUID is derived from the name, so renaming there does give you a new color.
Why do a teammate and I have almost the same color?
Chance. There are 16,777,216 possible values, but you are telling apart small dots in peripheral vision rather than reading hex strings, so visually similar pairs turn up at ordinary party sizes. Run everyone through the locator bar color checker to see which pairs actually clash, then override one of them.
Can I check a Bedrock player here?
No, and neither can anything else. Bedrock colors are random per session rather than derived from an identifier, so there is nothing to compute. This Minecraft Locator Bar color checker is Java Edition only.
Do I need to be an operator to change a color?
To change one, yes: /waypoint needs permission level 2 and cheats enabled, or a server console, command block or function. Reading a color needs nothing — that is what this page is for.
Which versions does this apply to?
Java Edition 1.21.6 and later, where the Locator Bar was introduced. The UUID-to-color derivation has not changed since; what changed later is command syntax and the game rule name.