Minecraft Server Whitelist: Keep a Friends-Only World Private

A Minecraft server whitelist lets you decide who can join a private Java world. It is useful when you want a stable group of friends without publishing an open invitation to everyone who finds the server address.

The whitelist controls admission. Operator permissions control administrative power. Keep those decisions separate: a friend can play normally without permission to change the world or manage other players.

Enable the list before sharing the address

From the Java server console, use whitelist on, then whitelist add PlayerName for each invited account. Run whitelist list to review entries. Use account names, not a Discord nickname. In the in-game command window, these commands normally begin with /; panel consoles commonly omit that slash.

Paper also documents white-list and enforce-whitelist in its server properties reference. Review the distinction before changing enforcement on an occupied server: removing someone from a list and disconnecting an active session are separate concerns.

Keep the server's account authentication configured correctly. A whitelist is not a reason to disable authentication or copy an unrelated proxy configuration.

Test the invitation process

Invite one friend before adding the entire group. Ask them to connect with the exact account you approved. Then check that a non-approved test account is refused. This catches spelling mistakes and helps confirm you edited the server that actually runs your world.

If the invited player is rejected, collect the exact message and check the list in the running console. Verify the server address, edition, account name, and whether another configuration change overwrote the setting at startup.

For a Geyser server, use the bridge's documented identity format. Do not assume a Bedrock gamertag is interchangeable with a Java account name.

Keep the list useful over time

Review access when a season ends or a moderator leaves. Record who handles new invitations so multiple admins do not make conflicting changes. Keep the list with your configuration backups, because recovering the world without its access rules can accidentally reopen a private community.

Does a whitelist prevent griefing?

It reduces who can enter. It cannot prevent an invited player from breaking rules. Combine admission control with backups and a clear agreement about shared builds.

For the wider setup process, read our Minecraft Java server guide.

Choose your next step

Compare EZ Game Host Minecraft hosting for your group. Choose resources for your actual world and workload, then keep a downloadable backup before changing hosts.