Minecraft
Whitelist & Ops Builder
whitelist.json needs UUIDs rather than names, and looking up twenty UUIDs by hand means twenty trips to a lookup site. Paste the names and get both files back.
One name per line or comma-separated, up to 20 at once. Java Edition only; Bedrock players have no Mojang UUID.
Advertisement
How it works
Accounts are keyed by UUID, not username, which is what stops a name change from silently removing a player from the list. We resolve each name through Mojang's public profile endpoint and write the answers into whitelist.json and ops.json. The server insists on dashed UUIDs, which the API does not return, so the dashes are added for you. There is no API key involved and nothing about the accounts is saved.
Advertisement
Common mistakes
Pick operator levels deliberately. A level 1 op gains exactly one thing: permission to build within spawn protection. Level 2 unlocks most cheat commands along with command blocks, and level 3 brings kick and ban. Level 4 is the dangerous one, granting stop, op and deop, so its holders can shut the server off or lock in their own powers for good. Bedrock players, having no Mojang UUID, are whitelisted through Geyser or Floodgate instead, and will not appear in these files.