What this tool does
One name per line (or commas). Hit generate, download the JSON. Each entry is name + uuid, which is what the server expects.
Server & Files
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.
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.
[
{
"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
Paste a list of names, get a whitelist.json. Offline mode uses the real Offline-player UUID math Java uses. Online mode can ask Mojang for profile UUIDs when the lookup works.
One name per line (or commas). Hit generate, download the JSON. Each entry is name + uuid, which is what the server expects.
Offline servers care about OfflinePlayer UUIDs. Online-mode servers want Mojang UUIDs. Mix them up and someone will sit in “not whitelisted” forever even though their name is in the file.
File alone does nothing. Turn on white-list (or whitelist on older jars), put the file in the server root, then reload or restart.
No. Enable white-list in server.properties too.
No. Same MD5 version-3 style Java uses for offline mode. Not random junk.
We fall back to offline UUID and show a note. Fix those before you go live if you run online-mode.
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.
Server & Files
Paste a list of names, get a whitelist.json. Offline mode uses the real Offline-player UUID math Java uses. Online mode can ask Mojang for profile UUIDs when the lookup works.
One name per line (or commas). Hit generate, download the JSON. Each entry is name + uuid, which is what the server expects.
Offline servers care about OfflinePlayer UUIDs. Online-mode servers want Mojang UUIDs. Mix them up and someone will sit in “not whitelisted” forever even though their name is in the file.
File alone does nothing. Turn on white-list (or whitelist on older jars), put the file in the server root, then reload or restart.
No. Enable white-list in server.properties too.
No. Same MD5 version-3 style Java uses for offline mode. Not random junk.
We fall back to offline UUID and show a note. Fix those before you go live if you run online-mode.
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.