Verified for current Java versions

Minecraft Locator Bar Color Checker

Enter a Java username or UUID. Get the exact visible marker color, HEX and RGB, current rarity odds, the 1.21.6 legacy difference, party clashes, and a copy-ready command.

  • Defaults to 1.21.7–26.2
  • UUID math runs locally
  • No account or upload
  • Bedrock limits stated honestly

Step 1 — identify the player

Find the default dot color

Online mode looks up a public Java profile. Offline mode reproduces the server UUID made from OfflinePlayer:<name>.

Account mode

UUIDs stay in this browser. An online username is sent through this site to PlayerDB's public Minecraft profile resolver and is never included in analytics events.

Try:
Java only: vanilla Bedrock colors are not derived from a Java UUID, so a gamertag cannot predict the session color. See the edition table.

Your marker is waiting

Enter a username or UUID. The result will show the visible dot, base hash, exact odds, and version difference.

What “rare” really means

A raw hash can be 1 in 16.7 million. A visible dot usually is not.

Current Java versions force HSV brightness to 0.9. That maps many different 24-bit hash colors onto the same rendered dot. We enumerated every possible input using the current client operation, then stored the exact reverse count for instant lookup.

16,777,216 possible raw 24-bit hash colors
159,391 distinct visible colors in 1.21.7+
26 fewest raw values behind a visible color
256 most raw values behind a visible color
The “1 in 16,777,216 visible color” claim needs context.

Each exact raw hash color is one of 16,777,216 values. But in Java 1.21.7+, even the least common rendered colors each have 26 raw preimages—about 1 in 645,278 under an even hash distribution. The checker reports both the raw and visible values so those two ideas do not get mixed together.

Party color comparison

Find the teammates whose dots will clash

Check up to ten players at once. Exact duplicates are flagged, and an OKLab distance heuristic identifies colors that may be difficult to distinguish as tiny HUD markers.

Players to compare

One username or UUID per line. Public online usernames are resolved through PlayerDB; UUIDs and offline names calculate locally.

Your party palette and closest color pairs will appear here.

Copy-ready server action

Change or reset a Locator Bar color

Generate the vanilla Java command without guessing where the hash symbol goes. Commands need cheats or operator permission; the target must resolve to a transmitting waypoint.

Command settings

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

Generated command

Paste this in chat or the server console

/waypoint modify @s color hex E66185

An explicit waypoint color takes priority over a team color and the automatic UUID fallback. Use reset to return to the normal precedence chain.

Version-correct methodology

Why two checkers can return different HEX values

The Locator Bar launched in Java 1.21.6, but its automatic brightness operation changed immediately in 1.21.7. This page defaults to the current behavior and keeps 1.21.6 as an explicit one-release option.

01

Normalize the UUID

Hyphens and letter case do not affect the 128-bit value. Online usernames resolve to the account UUID; offline names use the server-style version 3 UUID.

02

Reproduce UUID.hashCode()

Java folds the UUID's two 64-bit halves into a signed 32-bit hash. The low three bytes form the raw red, green, and blue channels.

03

Apply the correct renderer step

Current versions preserve hue and saturation and set HSV brightness to 0.9. Only 1.21.6 scales every RGB channel by 0.9.

Java version Visible color operation What it means
1.21.6 only scaleRGB(raw, 0.9f) Each channel is multiplied and truncated. This usually makes the raw color darker.
1.21.7 through current 26.2 setBrightness(raw, 0.9f) Hue and saturation are retained while value/brightness is fixed at 90%, so one channel reaches 230.
Independent check:

The implementation was verified against Mojang's official client artifacts for 1.21.6, 1.21.7, 1.21.8, 1.21.9, 1.21.10, 1.21.11, 26.1, and 26.2. The rarity table is generated deterministically from every possible 24-bit raw color using the same float-rounding sequence. Last checked July 29, 2026.

Edition and override limits

What this result can—and cannot—predict

The result is the automatic Java fallback. A server can draw a different color without changing the player's UUID, and Bedrock follows a different assignment system.

Situation Predictable here? Reason
Java online-mode default Yes Stable account UUID → deterministic fallback color.
Java offline-mode default Yes, from the exact server name The server derives a version 3 UUID from OfflinePlayer:<name>.
Java team member Not from UUID alone A scoreboard team color overrides the UUID fallback.
Java explicit waypoint color Not from UUID alone A /waypoint modify … color value takes priority.
Vanilla Bedrock session No The displayed session color is not calculated from a Java UUID or a predictable gamertag hash.
Geyser/Floodgate on a Java server Depends on proxy configuration Use the exact virtual UUID reported by that Java server rather than guessing from an Xbox gamertag.
A

Bar not showing?

Another visible player must be present. The marker only appears inside the front 120° view, and the XP bar can temporarily occupy the same HUD area.

B

Player intentionally hidden?

Sneaking, invisibility, a carved pumpkin or mob head, and spectator rules can remove a player from another player's Locator Bar.

C

Game rule or range changed?

Check locatorBar on 1.21.6–1.21.10 and locator_bar on 1.21.11+. Receive/transmit range attributes can also suppress waypoints.

Short, exact answers

Minecraft Locator Bar color FAQ

How do I know my Locator Bar color?

Enter your Java username or UUID above. Use the default 1.21.7+ mode for current Minecraft. The result is the automatic UUID fallback—not a server's team or explicit waypoint override.

Is my color really 1 in 16,777,216?

The raw 24-bit hash value is one of 16,777,216 values. Current Java rendering collapses those into 159,391 visible colors. Each visible color corresponds to 26–256 raw values, and the result card gives the exact count for yours.

What is the rarest Locator Bar color?

There is not one unique rarest visible color in current Java. The exhaustive mapping contains 294 visible colors tied for the minimum of 26 raw preimages each—about 1 in 645,278 under an even hash distribution. Rarity does not grant an in-game benefit.

Can I change the color in Java Edition?

An operator can use /waypoint modify <target> color hex RRGGBB or one of the named colors. A team color can also replace the UUID fallback. The command generator above handles the syntax and reset action.

Why does another color checker disagree?

It may still apply the 1.21.6 launch algorithm. Starting with 1.21.7, Minecraft changed from scaling RGB channels to setting HSV brightness. Also confirm that both tools use the same UUID and that you are not comparing a team or custom server color.

Does changing a Java username change the color?

Not for an online-mode account because the account UUID does not change. On an offline-mode server the UUID is derived from the exact username, so a renamed offline player can get a different UUID and color.

Can this predict a Bedrock player's color?

No. Vanilla Bedrock does not use the Java UUID algorithm for its session colors. A page that promises a stable vanilla Bedrock result from a gamertag is answering a different question. On a Java server with Geyser/Floodgate, use the exact virtual UUID the server reports.

Why is my marker missing even when the color is valid?

Color validity does not control visibility. Check for another player, front-facing range, the Locator Bar game rule, waypoint receive/transmit attributes, sneaking, invisibility, worn heads or pumpkins, spectator state, and the XP bar temporarily taking over the HUD slot.

Primary references and reproducibility

Privacy and analytics notice

Inputs are kept out of analytics

This site uses GA4 without a consent pop-up so product usage can be measured fully. The boundaries below explain what is and is not collected.

Calculator inputs

UUID calculations and offline-name UUID generation happen in your browser. Username, UUID, HEX, RGB, and result values are never attached to GA4 events. Online lookup sends only the public Java username through this site's endpoint to PlayerDB; this application does not store it.

GA4 measurement

GA4 may use cookies or similar identifiers and receives standard usage information such as page views, tool success or error category, input type—not input value—theme choice, copy actions, party size, browser/device data, referrer, and approximate geography. Cloudflare Web Analytics also measures page delivery and performance without receiving calculator input or result values.

Local preferences and providers

The chosen dark, warm white, or warm yellow theme is stored in local storage. Hosting and security are provided by Cloudflare; public online profile resolution is provided by PlayerDB using Minecraft account data. Cloudflare, Google, and PlayerDB may process ordinary request or measurement data under their own policies.