Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →A Minecraft whitelist limits a server to an approved player list. The setup depends on the edition: Java Edition uses /whitelist commands and whitelist.json, while Bedrock Dedicated Server calls the feature an allowlist, uses /allowlist, stores entries in allowlist.json, and must have allow-list=true in server.properties.
The server must be installed and running from its server directory before you can use administration commands. Follow the section for your edition, then use the troubleshooting checks if a player is still refused or a file edit appears to do nothing.
As an Amazon Associate I earn from qualifying purchases.
What a Minecraft whitelist does
A whitelist is an access-control list for a private server. When it is enabled, only the player names (Java) or GamerTags (Bedrock Dedicated Server) on the approved list can join. Everyone else is rejected even if they know the server address.
Free tools Windows power users keep installed
One-click scans. No signup required.
It is not the same as making someone an operator. An operator can receive administrative permissions; a whitelisted player is simply allowed to connect. Grant operator status separately and only to people who need it.
#1 Best Overall
- Play and share with friends on console, mobile and Windows 10
- discover community creations in the new in-game store
- access new mini games and game modes through servers
Identify your edition before changing anything
| Server | Enable setting | Command family | Access file | Important reload detail |
|---|---|---|---|---|
| Java Edition dedicated server | Java whitelist setting controlled by the server commands | /whitelist |
whitelist.json |
Reload after a direct file edit with the Java server’s whitelist reload command. |
| Bedrock Dedicated Server | allow-list=true in server.properties |
/allowlist (Microsoft also documents /whitelist as an alias) |
allowlist.json |
Run /allowlist reload after an outside edit. |
A hosting control panel or cross-play proxy may present different buttons and may translate commands. The procedures below describe the official dedicated-server interfaces; use the host’s current documentation when its panel hides the console or changes the file layout.
Before you start
- Have a working dedicated server. The server software must already be installed, and you need its server directory and console. Minecraft’s official Java setup documentation explains that the Java server is launched from that directory and that server settings are kept in
server.properties: Minecraft Java Edition server setup. - Know which edition is running. Java commands and files do not substitute for Bedrock commands and files.
- Have administrative permission. On Java, command access depends on your operator status and server configuration. On Bedrock Dedicated Server, Microsoft documents the allowlist command as requiring owner permission with cheats enabled.
- Record the exact account identifier. Use the Java player name exactly as it appears, or the Bedrock GamerTag exactly as it is spelled. Do not substitute an Xbox/Microsoft account email address for a GamerTag.
- Make a backup before manual file work. Stop the server before copying or editing its JSON files so that the running process cannot overwrite your changes during shutdown.
Set up a whitelist on a Java Edition server
Use the dedicated Java server console, or an in-game account that has permission to run server commands. The commands below are shown with the leading slash used in chat and command documentation.
1. Start the server and open an administrative interface
Launch the Java server from its server directory using the server JAR, then leave its console available. If you administer from inside the game, connect with an operator account. A command entered on a client without the required permission will not change the server’s list.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
2. Turn the whitelist on
Run:
/whitelist onThis activates the list. Enabling it before adding names can immediately prevent unlisted players from joining, so tell current players what you are doing if the server is already in use.
3. Add each approved player
Run the command once for every player:
/whitelist add <playername>For example, replace <playername> with the player’s Java in-game name. Keep the spelling and capitalization consistent with the account that will connect. Add new players before their first connection if you want the server to remain closed to everyone outside the list.
4. Check the current list
Use:
/whitelist listConfirm that every expected name appears. This is the quickest way to distinguish a rejected connection caused by a missing entry from a network, version, or authentication problem.
5. Remove a player when access should end
Run:
/whitelist remove <playername>Then run /whitelist list again to verify the entry is gone. Removing someone from the whitelist does not by itself revoke operator status; if that person is also an operator, manage that separate permission through your normal operator controls.
Recommended Free Tools
6. Reload after editing whitelist.json manually
The Java server keeps its access entries in whitelist.json in the server directory. Manual editing is more error-prone than using commands, so stop the server and make a backup first. After an outside edit, use the server implementation’s whitelist reload command before expecting a running process to use the new contents. The exact command behavior can vary with the server implementation and version; use that implementation’s current command reference.
If you edited the file while the server was stopped and then started it, check the list in the console with /whitelist list. If the expected names are not shown, stop the process, restore the backup, and make the change through /whitelist add instead.
Set up an allowlist on Bedrock Dedicated Server
Bedrock Dedicated Server uses the term allowlist in its files and primary commands. Microsoft documents /whitelist as an alias, but using /allowlist makes it clear that you are following the Bedrock command family.
1. Stop the server and back up its files
Stop the Bedrock process cleanly before editing server.properties or allowlist.json. Copy the server directory, or at minimum those two files, to a safe backup location. This gives you a recovery point if a syntax error or an accidental overwrite prevents the server from reading the settings.
2. Enable the feature in server.properties
Open the server.properties file in the Bedrock server directory and set this exact property:
allow-list=trueSave the file without changing the hyphen or the value. This setting is what tells Bedrock Dedicated Server to enforce the entries in allowlist.json. A correctly populated file has no effect while the allowlist setting is disabled.
3. Start the server
Start Bedrock Dedicated Server again from its server directory. Wait until the server is ready for commands, then use its console or an account with the documented owner permission and cheats enabled.
4. Add approved GamerTags
Run:
/allowlist add <GamerTag>Use the player’s Bedrock GamerTag, not a Java name. If the GamerTag contains spaces, enclose the complete value in quotation marks:
/allowlist add "Example GamerTag"Repeat the command for every person who should be able to join.
5. Review the entries
Run:
/allowlist listCheck the result for spelling, spaces, and accidental omissions. If a player cannot join, verify this output before changing unrelated network or firewall settings.
6. Remove an entry
Run:
/allowlist remove <GamerTag>For a GamerTag with spaces, retain the quotation marks:
Rank #4
- Play and share with friends on console, mobile and Windows 10
- discover community creations in the new in-game store
- access new mini games and game modes through servers
/allowlist remove "Example GamerTag"7. Reload an edited allowlist.json
Bedrock Dedicated Server does not automatically apply an outside edit to the running list. Microsoft states: “If you make modifications outside Minecraft, you’ll need to run the command /allowlist reload so the server reads the changes.” After saving allowlist.json, run:
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11/allowlist reloadThen confirm the result with:
/allowlist listIf you changed the file while the server was stopped, start the server and still use /allowlist list to verify that the entries were parsed. If the list is wrong, stop the server, restore the backup, and add players with commands rather than continuing to edit JSON blindly.
Bedrock allowlist actions at a glance
| Action | Command | Use it when |
|---|---|---|
| Enable | /allowlist on |
You want Bedrock to enforce the approved list. |
| Disable | /allowlist off |
You need a temporary open server; entries remain available for later use. |
| Add | /allowlist add <GamerTag> |
You are approving a player. |
| List | /allowlist list |
You are checking who is currently approved. |
| Remove | /allowlist remove <GamerTag> |
You are ending a player’s allowlisted access. |
| Reload | /allowlist reload |
You edited allowlist.json outside the game and need the running server to reread it. |
Microsoft’s Bedrock command reference lists these actions and identifies /whitelist as an alias. Use the form that matches the interface and documentation for your Bedrock server version.
Why a whitelist or allowlist appears not to work
You used the other edition’s command or file
Java reads whitelist.json and responds to /whitelist. Bedrock Dedicated Server reads allowlist.json, requires allow-list=true, and responds to /allowlist (with /whitelist documented as an alias). Putting a name in the Java file on a Bedrock server, or vice versa, changes nothing.
The feature is disabled
On Bedrock, inspect server.properties and confirm the value is exactly allow-list=true. On Java, run /whitelist list and then /whitelist on if enforcement was turned off. A list can contain the right names and still allow everyone through when enforcement is disabled.
You edited the file but did not reload it
This is especially common on Bedrock. After an outside edit, run /allowlist reload, then /allowlist list. On Java, use the whitelist reload command appropriate to the server implementation and version, then verify with /whitelist list.
The account identifier does not match
Check every character. Java requires the player’s Java name; Bedrock requires the GamerTag. A GamerTag containing spaces must be quoted in the command. Do not rely on a nickname, display label, or a different account’s name.
The command was rejected for lack of permission
Java command access depends on the account’s operator status and the server setup. Bedrock’s documented allowlist command requires owner permission and cheats. If you cannot run the command, use the server console or ask the server owner to perform the change; repeatedly editing files will not bypass command permissions safely.
You changed the wrong server directory
Dedicated servers may have several folders after backups, upgrades, or multiple worlds. The correct directory is the one from which the running server process was launched and where its active server.properties and access JSON file reside. Stop the process, identify that directory, and make a dated backup before editing.
A hosting panel hides or rewrites the command
Some panels expose a whitelist toggle instead of a console, while others use provider-specific labels. Do not assume that a panel, proxy, or cross-play layer uses the same command or file as the underlying dedicated server. Follow the provider’s current documentation, and use the official Java or Bedrock procedure when you have direct console access.
Operating a private list safely
- Prefer commands for routine changes. They reduce the chance of malformed JSON and make the result immediately checkable with
list. - Back up before manual edits. Keep the previous file until every approved player has successfully connected.
- Verify after every change. Run the relevant
listcommand rather than assuming a successful command prompt means the intended name was entered. - Keep operator access separate. Whitelisting controls entry; it does not grant moderation or administration powers.
- Document temporary changes. If you run
/allowlist offor/whitelist offfor an event, turn enforcement back on afterward and verify the state. - Plan for account changes. When a player changes the account they use, remove the old identifier and add the new one rather than leaving an obsolete entry indefinitely.
Choosing between direct self-hosting and a control panel
Running the dedicated server yourself gives you direct access to the console, server.properties, and the edition-specific JSON file. A managed Minecraft server host can be more convenient when you need persistent uptime, automated backups, or a web control panel, but its buttons and command handling vary by provider. Confirm that the service supports the edition you run and exposes the allowlist or whitelist controls you need. Regardless of the interface, the underlying distinction remains: Java uses /whitelist and whitelist.json; Bedrock Dedicated Server uses allow-list=true, /allowlist, and allowlist.json.
If you would rather not run the machine yourself, Godlike.Host offers Minecraft Java and Bedrock servers with a Pterodactyl-based panel, SFTP access for file edits and up to three free backups a day with restore, which suits the backup-before-editing advice above. See the current plans for details.
Quick Recap
Quick verification checklist
- Identify whether the server is Java Edition or Bedrock Dedicated Server.
- Confirm the server is running from the directory whose files you are changing.
- Use the matching command family and exact player identifier.
- Enable enforcement:
/whitelist onfor Java, orallow-list=trueand the Bedrock allowlist controls. - Run
listand confirm the player appears. - After a Bedrock file edit, run
/allowlist reload; after a Java file edit, run the reload command supported by that server implementation and version. - Test with one approved account and, if appropriate, one unlisted account to confirm that enforcement—not just the file contents—is working.
