Server & Files

whitelist.json Generator

Build Java Edition whitelist.json as an array of name + uuid objects. Online mode can resolve Mojang UUIDs; offline mode uses the official OfflinePlayer UUID algorithm.

Players

Usernames (one per line or comma-separated)Prefer Mojang online UUIDs (needs network; rate-limited)

Enable with white-list=true (or whitelist=true on older jars) in server.properties, put whitelist.json in the server root, then restart or run /whitelist reload. Format: JSON array of objects with uuid and name fields.

Generated whitelist.json

[
  {
    "name": "Steve",
    "uuid": "5627dd98-e6be-3c21-b8a8-e92344183641"
  },
  {
    "name": "Alex",
    "uuid": "36532b5e-c442-3dbb-a24c-c7e55d0f979a"
  },
  {
    "name": "Notch",
    "uuid": "b50ad385-829d-3141-a216-7e7d7539ba7f"
  }
]

Server & Files

Minecraft whitelist.json Generator

whitelist.json is the list of allowed players for a Java dedicated server when white-list is enabled. Paste names, choose offline or online UUID handling, and download a file the server understands. Wrong UUID mode is the usual reason a name is “on the list” but still cannot join.

What this tool does

Enter one name per line (or comma-separated lists). The generator builds JSON entries with name and uuid. Offline mode uses the same OfflinePlayer UUID math Java uses. Online mode can resolve Mojang profile UUIDs when the lookup succeeds.

Offline vs online mode

offline-mode servers care about offline UUIDs. online-mode servers expect Mojang UUIDs. Mixing them means a player can be listed by name and still rejected. Match the generator mode to server.properties online-mode before you publish the file.

server.properties still matters

The JSON file alone does nothing. Set white-list (or whitelist on older versions) to true, place whitelist.json in the server root, then restart or use the whitelist reload flow your software supports.

Failed Mojang lookups

If a name cannot be resolved online, the tool can fall back to an offline UUID and flag it. Fix those entries before opening an online-mode server to the public, or the wrong identity will be stored.

Ops and bans are separate

ops.json and banned-players.json are different files. Whitelist only answers “may this account join at all?” Admin powers and bans still need their own lists and permission plugins.

Quick questions

Is the file enough?

No. Enable white-list in server.properties and reload or restart.

Are offline UUIDs fake?

No. They follow the same version-3 style hash Java uses for offline mode.

Lookup failed for a name?

We can fall back to offline UUID with a note. Correct those before online-mode production.

Bedrock players?

This JSON is for Java whitelist entries. Bedrock and Geyser setups need their own identity rules.

Can I edit the JSON by hand later?

Yes, but keep valid UUID strings. Regenerating from names is safer than guessing UUIDs.

What do you think about this tool?

If something feels wrong, a Minecraft version is missing, the wording is confusing, or you have a better workflow idea, send it over. Real player feedback is how these tools get sharper.

Send feedback