Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →A Minecraft whitelist (called an allowlist on Bedrock Dedicated Server) limits logins to named players. On Java Edition, enable it with /whitelist on and manage names with /whitelist add. On Bedrock Dedicated Server, set allow-list=true in server.properties, then use /allowlist commands. The two editions use different command families and JSON files, so use the procedure for your server software.
Playing with friends? Godlike.Host runs hosted Minecraft Java servers from 10 data-center locations, with free DDoS protection.
Your dedicated server must already be installed and running from its server directory. Java’s official setup documentation explains launching the server JAR from that directory and using server.properties for server settings: Minecraft Java Edition server setup.
As an Amazon Associate I earn from qualifying purchases.
Recommended Free Tools
What a Minecraft whitelist does
A whitelist is an access-control list. When it is enabled, the server checks an incoming player against the approved names and refuses players who are not listed. This is useful for private survival worlds, family servers, classroom sessions, and invitation-only communities because the server address alone is no longer sufficient for joining.
Whitelisting does not replace other security measures. Keep operator privileges limited, protect the server console, and use the access controls provided by your hosting provider or network setup. The steps below cover a self-hosted Java server and the official Bedrock Dedicated Server.
#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 server edition before changing anything
| Server type | Term used in commands | Access file | Enablement | Command family |
|---|---|---|---|---|
| Java Edition dedicated server | Whitelist | whitelist.json |
Enable with /whitelist on |
/whitelist ... |
| Bedrock Dedicated Server | Allowlist (Microsoft also documents /whitelist as an alias) |
allowlist.json |
Set allow-list=true in server.properties, then turn it on |
/allowlist ... |
These instructions are for the dedicated server programs themselves. A third-party control panel, cross-play proxy, or managed host may present different buttons or command syntax. If the panel hides the server console, use that provider’s current documentation rather than assuming its interface is identical to vanilla Java or Bedrock.
Prepare the server and your permissions
Start in the correct server directory
Locate the directory that contains the running server software and its configuration files. For Java, this is the directory from which the server JAR is launched; it is also where server.properties and whitelist.json are stored. For Bedrock Dedicated Server, use the directory containing server.properties and allowlist.json. Editing a similarly named file elsewhere will not change the running instance.
Use an authorized administration account
You can run commands from the dedicated server console or from an in-game account that has the required authority. Java command permissions depend on the server’s operator and permission setup. Bedrock’s documented allowlist command requires owner permission and cheats enabled. If a command is rejected, resolve the permission issue before changing files; otherwise you may mistake an authorization error for a whitelist problem.
Make a backup before direct file changes
Before copying or editing a JSON file, stop the Bedrock server as directed below and keep a backup of the original. A backup lets you restore the previous list if a manual edit is malformed or if you edit the wrong entry. Never assume a file change is active merely because the file saved successfully; the running server must read it.
Set up a whitelist on Java Edition
1. Start the server and open its console
Launch the Java dedicated server from its server directory and wait until it is ready to accept commands. Alternatively, connect with an authorized operator account. The server must be running when you issue the commands in this section.
2. Turn the whitelist on
Run:
/whitelist onThis activates access checking. Players who are not in the list will be denied once the setting is active.
3. Add each approved player
Add one player at a time with the exact Java player name:
/whitelist add <playername>Replace <playername> with the player’s name; do not include the angle brackets. Repeat the command for every person who should be able to join. Add your own account before enabling the list if you are testing from in-game, so you do not accidentally lock yourself out.
4. Check the current entries
Display the server’s current whitelist with:
/whitelist listUse this immediately after adding names to catch spelling errors and to confirm that the server accepted each command. The list shown by the running server is the authoritative state for that session.
5. Remove a player when access should end
Remove an entry with:
/whitelist remove <playername>Then run /whitelist list again if you need to verify that the name is gone. Removing a player from the whitelist does not grant or revoke operator status; those are separate permissions.
6. Reload after editing whitelist.json directly
Java stores its entries in whitelist.json. If you modify that file outside the game, tell the running server to read the changed file by running:
/whitelist reloadWithout a reload, the server can continue using the list it already has in memory. Keep the file in the same server directory used by the running Java instance, and use the command supported by your specific server implementation and version.
Set up an allowlist on Bedrock Dedicated Server
1. Stop the server before backing up or editing
Shut down the Bedrock Dedicated Server cleanly before you make a backup or change its files. This prevents the server from writing over your edit during shutdown and gives you a stable copy of server.properties and allowlist.json.
2. Enable the setting in server.properties
Open server.properties in the Bedrock server directory and set this exact property:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
allow-list=trueSave the file, then start the server again. This property enables the allowlist feature for the Bedrock Dedicated Server; it is not the Java command or Java file name.
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
3. Add approved GamerTags
With the server running and your account authorized, add a player with:
/allowlist add <GamerTag>Microsoft documents /whitelist as an alias for the Bedrock command family, but using /allowlist makes it clear that you are following the Bedrock terminology. A GamerTag that contains spaces must be enclosed in quotation marks, for example:
/allowlist add "Player Name"Use the player’s GamerTag exactly as required by Bedrock. If the command succeeds but the player still cannot join, inspect the list and verify the spelling before changing any other setting.
4. Review the entries
Run:
/allowlist listThis shows the entries currently recognized by the running server. It is the quickest way to determine whether the add command affected the active allowlist.
5. Remove an entry
To revoke access, run:
/allowlist remove <GamerTag>Quote the GamerTag when it contains spaces, just as you did for the add command.
6. Reload a file edited outside the server
Bedrock stores the list in allowlist.json. After editing that file outside Minecraft, run:
/allowlist reloadMicrosoft’s Bedrock Dedicated Server documentation states: “If you make modifications outside Minecraft, you’ll need to run the command /allowlist reload so the server reads the changes.” The reload is therefore required even when the JSON file appears correct on disk.
7. Other Bedrock actions
The documented Bedrock action set is:
/allowlist on— enable checking./allowlist off— disable checking./allowlist add <GamerTag>— add a player./allowlist remove <GamerTag>— remove a player./allowlist list— display entries./allowlist reload— rereadallowlist.json.
The /whitelist alias refers to this Bedrock command family; the configuration key and file remain allow-list=true and allowlist.json.
Java and Bedrock differences at a glance
| Question | Java Edition | Bedrock Dedicated Server |
|---|---|---|
| What is the feature called? | Whitelist | Allowlist; /whitelist is an alias in Microsoft’s command reference |
| How is it enabled? | /whitelist on |
allow-list=true in server.properties, then the allowlist command can be enabled |
| Which file stores entries? | whitelist.json |
allowlist.json |
| Add command | /whitelist add <playername> |
/allowlist add <GamerTag> |
| List command | /whitelist list |
/allowlist list |
| Remove command | /whitelist remove <playername> |
/allowlist remove <GamerTag> |
| Reload after direct file edit | /whitelist reload |
/allowlist reload |
| Documented command authority | Depends on operator/server setup | Owner permission and cheats |
Troubleshoot a whitelist that is not working
The player was added, but still cannot join
- Run the edition-specific list command:
/whitelist liston Java or/allowlist liston Bedrock. - Compare the displayed entry with the player’s exact name or GamerTag. On Bedrock, put names containing spaces in quotation marks when adding them.
- Confirm that the feature is enabled: Java must have
/whitelist on; Bedrock must haveallow-list=trueand allowlist checking enabled. - Make sure you changed the file in the directory used by the running server, not a backup, download, or different instance.
You edited the JSON file, but nothing changed
A direct edit changes disk contents, not necessarily the server’s in-memory list. Run /whitelist reload on Java or /allowlist reload on Bedrock. Bedrock explicitly requires this reload after outside modifications. If the problem remains, stop the server, restore your backup, and repeat the edit in the active server directory.
The command is unknown or rejected
First verify that you are connected to the dedicated server software described in this guide and that it is running. Java commands require the appropriate operator authority. Bedrock commands require the documented owner permission and cheats. A host panel or proxy may expose a different command interface; consult that implementation’s current documentation instead of mixing Java and Bedrock syntax.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Everyone is locked out
This usually means access checking is enabled while the list is empty or contains a misspelled name. Use the server console or an authorized account to add the intended administrator, then check the list. If you cannot obtain an authorized session, temporarily disable the feature with the edition’s off command, correct the entries, and enable it again.
Changes disappear after a restart
Check that you edited the live instance’s files and that the server shut down cleanly before the edit. Keep one known-good backup of the JSON file and verify the active list with the list command after every restart.
Safe operating checklist
- Identify Java Edition versus Bedrock Dedicated Server before entering a command.
- Work in the server directory that contains the running configuration and access file.
- Keep a backup before manually editing JSON or
server.properties. - Add an administrator account before turning access checking on for the first time.
- Use the list command to verify every addition and removal.
- Reload after any direct JSON edit; a saved file is not automatically loaded into the running process.
- Limit operator or owner permissions to trusted people and protect console access.
- Treat hosting-panel and proxy controls as implementation-specific rather than assuming vanilla commands apply.
When a hosting panel may be easier
Self-hosting gives you direct control over the console and files. A managed Minecraft server hosting service can be more convenient when you need persistent uptime, automatic restarts, or a web control panel, but its whitelist controls may be buttons, a scheduled task, or a provider-specific command wrapper. Follow the host’s current instructions and confirm the resulting list in the actual server console when possible.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problems
