Dedicated Project Zomboid server for zombie survival and base building with friends
Grab the automated bash script from GitHub to follow along with the video.
wget https://raw.githubusercontent.com/mhmdali94/Docker/main/gaming/project-zomboid/project-zomboid-ubuntu.sh
chmod +x project-zomboid-ubuntu.sh
sudo bash project-zomboid-ubuntu.shThe script installs Docker, pulls the Project Zomboid dedicated server image, and starts the container. The server downloads ~3 GB of game files and runs on ports 16261 and 16262 UDP.
wget https://raw.githubusercontent.com/mhmdali94/Docker/main/gaming/project-zomboid/project-zomboid-ubuntu.sh
chmod +x project-zomboid-ubuntu.sh
sudo bash project-zomboid-ubuntu.shEdit server.ini to configure server name, password, max players, and Workshop mod IDs. Configure sandbox settings for zombie density, loot rarity, and survival difficulty.
# Edit server configuration
nano /opt/project-zomboid/data/Server/servertest.ini
# Key settings:
# ServerName=My Zomboid Server
# Password=yourpassword
# MaxPlayers=20
# Public=true
# WorkshopItems=2392709732;2699172477
# Mods=MoreBuilds;BetterSortingB41Open Project Zomboid, click Join Server, enter your server host IP and port 16261. If the server has a password, enter it when prompted. Ensure Workshop mods are subscribed and synced before joining.
# Connection details
Host IP: <your-server-ip>
Port: 16261Use the in-game admin chat or server console to manage players. Grant admin access, kick or ban disruptive players, and monitor server activity with live logs.
# In-game admin commands (chat or server console):
# /setaccesslevel <username> admin
# /kickuser <username>
# /banuser <username>
# /teleport <username>
# /save
# View live server logs
docker logs -f project-zomboid-server| Port | Purpose |
|---|---|
| 16261 UDP | Game traffic |
| 16262 UDP | Direct UDP connection |
Project Zomboid is a hardcore zombie survival RPG set in Knox County, Kentucky. A dedicated server allows a persistent multiplayer world where players survive together, build bases, and manage character skills and traits — all while managing the encroaching zombie horde.
A dedicated Project Zomboid server keeps the survival world running 24/7, allows your survivor group to join at different times, and gives full control over sandbox settings — zombie count, infection rules, helicopter events, water shutoff timing, and much more.
Project Zomboid uses UDP port 16261 for the main game connection and UDP port 16262 for direct connection. Open both UDP ports. Steam query uses additional ports for server browser listing. All ports should be UDP.
Alternatives include peer-to-peer hosting via Steam Remote Play, co-op hosting from within the game, and commercial game server hosts. Self-hosting provides a persistent world without requiring any player to stay online.
Avoid self-hosting if you only play occasional 2-player sessions — the built-in co-op hosting works fine. Also avoid if your server has less than 4 GB RAM; Project Zomboid is surprisingly memory-intensive with large zombie populations.
PrismaTechWork provides end-to-end infrastructure services — from initial deployment and security hardening to ongoing monitoring, automated backups, and dedicated support. Whether you need a single-server setup or a multi-site network, our team ensures your infrastructure is built right, secured properly, and maintained reliably.
Yes. Player characters are saved on the server and persist between sessions. Your character's inventory, skills, traits, and position in the world are saved. If you die, you respawn as a new character (configured based on sandbox settings — some servers use permadeath).
Find the mod IDs from the Steam Workshop page for each mod. Add the IDs to the Mods= and WorkshopItems= lines in your server INI configuration file. On next server start, SteamCMD downloads the workshop items. Clients must also subscribe to the same mods on Steam.
Project Zomboid dedicated servers can theoretically support hundreds of players, but performance depends heavily on player density and zombie population. For 10 to 30 players with moderate zombie counts, 4 cores and 8 GB RAM works well. Very large servers with 100+ players need powerful dedicated hardware.
Yes — extensively. The sandbox settings control zombie population density, speed (walker, sprinter, shuffler), strength, sight, hearing, memory, and behavior. You can create a horror experience with fast-moving, hearing-sensitive zombies or a slower survival experience with shambling walkers.
Sandbox settings are set once at server creation and cannot be changed after the world is generated. They control everything from zombie count and loot rarity to electricity and water shutoff timing, helicopter events, and character starting conditions. Plan your sandbox settings carefully before launching.
Yes. Configure friendly fire settings, PvP rules, and use admin tools to enforce roleplay guidelines. Many PZ community servers run dedicated roleplay communities with custom whitelists, Discord-based applications, and custom lore. The extensive sandbox settings support many different roleplay scenarios.
Set an admin password in the server INI file. Players with admin access can log in by typing /setaccesslevel USERNAME admin in the server console, or you can use the in-game admin panel accessible via Esc then Manage Players. Admins can teleport, spawn items, kick and ban players.
Project Zomboid updates via Steam. The Docker-based setup uses SteamCMD to update server files. Configure the container to check for updates on restart, or run steamcmd +app_update 380870 manually. Ensure clients are on the same build number — clients cannot connect to mismatched server versions.