Project Zomboid: Whitelist & Private Server Configuration
Quick answer: Set Open=false in server_settings.ini, restart, then run adduser "Username" "Password" in the server console for each player. They log in with those credentials at the in-game join screen.
Project Zomboid uses a robust whitelisting system that prevents anyone from joining your server unless you have specifically created a "Player Account" for them. This is the gold standard for dedicated roleplay (RP) servers and private groups who want to avoid the "hit and run" griefers common on open servers.
1. The "Open" Variable
By default, servers are "Open," meaning anyone with the IP and Port can create an account as they join. Setting Open=false locks the door, allowing only existing accounts in the database to connect.
2. Database Persistence
Whitelisted accounts are stored in the server's .db file. Even if you restart or update the server, the whitelist remains intact until you manually delete an entry.
3. Admin Bypass
The server owner (Admin) is automatically whitelisted. You can always join to manage the server even if the Open setting is toggled to false.
Step 1: Enabling the Whitelist Lock
- Navigate to your Supercraft Panel and go to the File Manager.
- Open the directory
/Zomboid/Server/. - Edit your
server_settings.ini(the name matches your server profile). - Find the line
Open=trueand change it toOpen=false. - Click Save and Restart the server.
Step 2: Adding Players via the Console
Since the server is now locked, you must manually grant access to your players.
- Open the Console (Terminal) tab in your panel.
- Type the following command:
adduser "Username" "Password" - Share the exact username and password with the player. They must enter these in the "Join" menu to authenticate.
Advanced Whitelist Commands
| Command | Action |
|---|---|
/showoptions | Checks the current status of the "Open" variable. |
/removeuserfromwhitelist "Name" | Removes a player from the whitelist. They can no longer authenticate until re-added. |
/grantadmin "Name" | Gives a whitelisted player administrative powers. |
Note for Build 42: Whitelisted players in Build 42 can be assigned specific "Starter Packs" if you configure the `SpawnItems` setting in the INI. This allows you to give your community a head-start once they are added.
Lock down your apocalypse without the stress. Host your Project Zomboid server with Supercraft and manage your player database with our integrated console and lightning-fast file editor.
Frequently asked questions
How do I add a player to the Project Zomboid whitelist?
Run adduser "Username" "Password" in the server console. The player must enter the same credentials in the in-game Join menu to connect.
How do I remove a player from the whitelist?
Run /removeuserfromwhitelist "Username" in the server console. The account is removed from the whitelist and can no longer authenticate.
Does the whitelist persist after a server restart?
Yes. Whitelisted accounts are stored in the server's .db file and survive restarts and updates until you manually delete an entry.
Can the admin still join when Open=false?
Yes. The server owner / admin account is automatically whitelisted, so you can always reconnect to manage the server even with Open=false.
Does the whitelist work in Build 42?
Yes. Build 42 keeps the same Open=false + adduser whitelist flow as Build 41, and adds the SpawnItems setting so whitelisted players can be given a starter loadout when they first spawn.