How do I find my Minecraft Locator Bar color?

Enter your Java Edition username or UUID. A username is resolved to its public UUID, then the default Locator Bar fallback color is calculated in your browser.

Is a Minecraft Locator Bar color random?

The default color looks random but is deterministic. Current Java clients derive the fallback color from the waypoint UUID, so the same UUID produces the same result.

Why is my in-game Locator Bar color different?

A team color, a /waypoint color override, a plugin, a proxy, an offline-mode UUID, or a modded client can replace or change the default UUID-derived fallback color.

Does this checker work for Minecraft Bedrock Edition?

The deterministic checker is for vanilla Java Edition UUID waypoints. Bedrock and Geyser or Floodgate identifiers follow different paths, so a Java username result should not be treated as authoritative for them.

How do I change a Locator Bar color?

With operator permission, use /waypoint modify followed by one target and either a named color, color hex RRGGBB, or color reset. The command generator on this page formats it for you.

A pasted UUID is calculated locally. A username must be sent to a public profile lookup service to obtain its UUID, and a player head image is loaded from an external avatar service after a successful result.

Free Java Edition tool

Minecraft Locator Bar Color Checker

Enter a Java username or UUID to calculate the player's default Locator Bar marker color. Then compare a whole group and copy the exact command needed to change a confusing color.

UUID input works locally Current brightness logic No sign-in or download

What this result means: it is the vanilla UUID-derived fallback color. A team, a /waypoint override, a plugin, or a different server UUID can take priority in-game.

Find a player's default color

Java username, dashed UUID, or 32-character UUID

JAVA

Your marker color appears here

Paste a UUID for an instant local result, or enter a username and the checker will resolve its public Java UUID first.

Player

—

#84D26A default color

WNE

HUD-style color preview Marker shape and background vary with client/resource pack

Rendered default

#84D26A

RGB

132, 210, 106

HSL

105°, 53%, 62%

Nearest Minecraft name

green

Raw UUID hash RGB

#84D26A

Java UUID hash

0

Verified calculation path: Java UUID.hashCode() → lower 24-bit RGB seed → ARGB.setBrightness(..., 0.9F). This sets HSV brightness to 90%; it does not simply multiply every RGB channel by 0.9.

Multiplayer readability

Check whether player colors are too similar

One color alone cannot tell you whether a group is readable. Add checked players or custom Hex colors; the tool finds the closest pair using perceptual Lab distance and suggests more distinct replacements.

Add a custom or server color

Use this for a team color, an existing waypoint override, or a player you already checked.

Practical guide: ΔE below 3 is extremely close, below 10 is easy to confuse at small HUD sizes, and above 20 is usually more distinct. This is a usability heuristic, not a medical accessibility test.

Group color check

0/10 colors added

Add at least two colors

No colors added yet
Check a player above and select “Add to comparison,” or add a custom Hex color here.

Distinct replacement ideas

Chosen to maximize distance from the colors currently in the list.

Operator utility

Minecraft Locator Bar command generator

Choose a target and color. The generator formats the exact Hex command, reset command, and the version-appropriate Locator Bar gamerule.

Command settings

Commands require cheats or suitable operator/function permission.

Single target

Use @s, a player name, UUID, or a selector that resolves to one waypoint.

Java version

Named color

Exact Hex color

Ready-to-copy commands

Valid target and color.

Set exact Hex color

/waypoint modify @s color hex 84D26A

Set named color

/waypoint modify @s color red

Return to automatic color

/waypoint modify @s color reset

Disable Locator Bar globally

/gamerule minecraft:locator_bar false

Before running the command

Use one transmitting target. A broad selector can fail when the command expects one waypoint. Narrow it with selector arguments when needed.
Omit the # inside the command. The valid Hex form is six digits such as 6495ED.
For Java 26.2+, named colors use lowercase names with underscores. Use dark_purple, not DarkPurple or darkpurple.
Reset removes the explicit waypoint color. A team color can still override the UUID-derived fallback.

Gamerule syntax changed in Java 1.21.11 when game rules moved to namespaced snake_case IDs. Select the server version above before copying it.

Calculation methodology

How a UUID becomes a Locator Bar color

The result is reproducible. The checker mirrors the current Java fallback path and exposes the intermediate seed and signed hash so you can verify the output rather than trust a mystery lookup table.

Normalize the UUID

Uppercase, lowercase, dashed, and undashed forms are converted to the same 128-bit UUID.

Run Java UUID.hashCode()

The two 64-bit halves are folded into the same signed 32-bit hash Java produces.

Take the RGB seed

The lower 24 bits become the raw red, green, and blue seed shown in the result details.

Set brightness to 0.9

The client keeps hue and saturation, then sets HSV brightness/value to 90% with Java-style rounding.

defaultColor = ARGB.setBrightness(ARGB.color(255, UUID.hashCode()), 0.9F)

The 0.9F operation is a brightness replacement, not a channel multiplier. For example, multiplying every channel by 0.9 produces a darker, different Hex value.

✓ What this checker does

Ports the current ARGB.setBrightness behavior, including hue/saturation preservation and Java float-style rounding. The main result is the color the current fallback render path produces.

✕ Common shortcut

Taking the raw UUID RGB and multiplying each channel by 0.9 is not equivalent. The result can differ visibly and should not be described as the current client calculation.

Troubleshooting

Why the in-game color or bar may look different

This checker calculates the default fallback. Live server state and visibility rules can override it or prevent the marker from appearing at all.

Color mismatch

The player belongs to a team

Team color takes priority over the automatic UUID-derived color. Check the scoreboard team configuration before assuming the calculation is wrong.

Color mismatch

A waypoint override is active

An operator, data pack, or plugin may have set an explicit color. Use the reset command above to remove the waypoint-level override.

Different identity

Offline mode, proxy, or Geyser

The server may identify the player with an offline, proxy, or Floodgate UUID rather than the public Java account UUID. Ask the server for the UUID it actually broadcasts.

Marker hidden

Sneaking, invisibility, headwear, or spectator rules

Crouching, invisibility, a mob head or carved pumpkin, and spectator behavior can hide players under vanilla Locator Bar rules.

Bar missing

No visible waypoints or XP is being shown

The Locator Bar shares space with the experience bar. It appears when relevant waypoints are available; gaining experience temporarily brings the XP bar forward.

Server setting

The gamerule or ranges disable tracking

The Locator Bar gamerule, waypoint transmit range, or receive range can remove waypoints globally or for individual entities and viewers.

FAQ

Minecraft Locator Bar color questions

How do I check my own Locator Bar color if I cannot see my own marker?

Enter your Java username here. The tool resolves your public account UUID and calculates the same default fallback used for the waypoint marker. It does not need to connect to your world or server.

Is my default color permanently tied to my username?

It is tied to the UUID, not the visible username. A normal Java account name change keeps the same UUID and therefore the same fallback color. A server using a different UUID scheme can produce a different result.

Can two players receive the same or nearly identical color?

Yes. The fallback is derived from a 24-bit color space, so exact collisions are possible, and perceptually similar colors are much more common. Add the whole group to the comparison tool to find the closest pair.

Why does another color checker give me a darker answer?

Some calculators multiply each raw RGB channel by 0.9. The current Java renderer instead calls ARGB.setBrightness(..., 0.9F), which preserves hue and saturation while setting HSV brightness/value to 90%. Those operations are not equivalent.

Does the tool read the color currently configured on my server?

No. A static webpage cannot see your scoreboard teams, waypoint packets, plugins, or command history. It calculates the automatic UUID fallback and helps you produce a replacement command.

Does this work for Bedrock Edition or Geyser players?

The authoritative calculator is for Java UUID waypoints. Bedrock uses different identifiers, and Geyser/Floodgate servers may broadcast virtual UUIDs. Paste the exact UUID used by the Java server if you need to test a cross-play player.

What information leaves my browser?

A valid UUID is calculated locally. A username is sent to public profile lookup services to obtain a UUID, and a player-head image is requested from MC Heads after a result. Google Analytics also measures visits and interactions using cookies and similar identifiers. The checker does not intentionally send the username, UUID, copied value, or command target you enter to Google Analytics. See the Privacy Notice for the full disclosure.

Transparency

Version notes, sources, and privacy

Mechanics and commands can change. These links make the page's assumptions auditable and give server owners the official version context.

Primary references

Minecraft Java Edition 1.21.6 release notes — Locator Bar behavior and original commands.
Minecraft Java Edition 1.21.11 release notes — namespaced snake_case gamerules.
Minecraft Java Edition 26.2 release notes — current command-name formatting.
26.2 client fallback path and ARGB brightness implementation.

Network and privacy behavior

UUID inputNormalized and calculated locally in JavaScript.

UsernameResolved through PlayerDB, with MCState as a fallback.

AvatarLoaded after a result from MC Heads.

AnalyticsGoogle Analytics 4 loads when the page opens and measures visits, device and referral information, scrolls, outbound links, forms, downloads, and tool actions. No consent banner is shown.

StorageAnalytics may set first-party cookies. The selected color theme is stored locally in your browser; the tool has no login, application database, or localStorage-based profile.

DetailsRead the complete Privacy Notice, including retention and browser controls.