How to make a Project Zomboid server: ports, mods, admins

Updated 2 November 2026 · 7 minute read · Project Zomboid (PC), your own PC or a rented server · By Exclsv Support

Project Zomboid’s dedicated server is a free Steam download (SteamCMD app 380870) for Windows or Linux. Open UDP ports 16261 and 16262, set an admin password on the first start, and add mods with the Mods= and WorkshopItems= lines in servertest.ini.

What you need

• A Windows or Linux computer that stays on. Hosting from the game’s own Host menu works for an evening, but the world stops when you do.
• SteamCMD. The server downloads without a Steam login; players need their own copy of the game.
• Memory: about 4 GB for a few players with light mods. Long Workshop lists need more than the player count suggests.
• The same build as your players: Build 42 is Steam’s public branch, Build 41 the legacy41 branch.

Install and start it

1. In SteamCMD, type force_install_dir ./pzserver, then login anonymous, then app_update 380870 validate. For Build 41, add the legacy41 branch to that app_update line with SteamCMD’s branch option (Valve’s SteamCMD page shows how).
2. Start start-server.sh on Linux or StartServer64.bat on Windows.
3. On the first start the server asks you to choose an admin password. Pick a long one: it’s the password for the admin account.
4. The server is ready when the console says SERVER STARTED.

The server’s memory is the -Xmx value in ProjectZomboid64.json (Linux) or in StartServer64.bat (Windows). Raise it if the server runs out, but leave room for the system.

Ports to open

Settings files

The server keeps its files in a Zomboid folder in your user folder (your home folder on Linux). For a server called servertest:

• Server/servertest.ini: the public name, password, player limit, PvP, whether it’s listed (Public=true), mods and more.
• Server/servertest_SandboxVars.lua: the world itself: zombie numbers and speed, loot, how long the power and water last.
• Server/servertest_spawnregions.lua: where players can spawn.

Edit them with the server stopped. Changes made while it runs can be overwritten when it saves or shuts down.

Workshop mods

Two lines in servertest.ini work together, each a list separated by semicolons:

• WorkshopItems=: the Workshop item numbers, from each mod’s Workshop address. The server downloads these.
• Mods=: the Mod IDs listed on each Workshop page, which switch the mods on. One item can hold several Mod IDs.

Map mods also need their map folder in the Map= line. Build 42 mods use a different format from Build 41, and many mods support only one build, so check each mod’s page before adding it. Players download the mods when they join.

Admins and players

Sign in with the admin account and the password you chose, or type commands in the server console without the slash. Useful ones:

• /setaccesslevel "Name" admin: make someone an admin (or moderator, none).
• /kickuser "Name" and /banuser "Name": remove a player.
• Open=false in servertest.ini, then /adduser "Name" "password": a whitelisted server.

The easy way: on Exclsv

On an Exclsv server both ports are open already and the admin account is made for you. Paste a Workshop collection link and HQ writes the Mods= and WorkshopItems= lines in the right format for your build, and flags mods that only support Build 41. Choose Build 41 or 42 under Settings, Updates; switching takes a backup first. HQ writes your settings while the server is stopped, so they stick.

Project Zomboid plans and what each includes ›

If it doesn’t work

Run this on Exclsv: Project Zomboid server hosting, from £9.99 a month ›

Project Zomboid server settings explained ›