Project Zomboid B42 Dedicated Server Guide

Install Project Zomboid Build 42.21 stable server with SteamCMD 380870, configure Windows, open UDP 16261 and 16262, add mods and protect savegames.

project-zomboid game artwork for dedicated server instructions
Source: coop-legends.de

Overview

The Indie Stone moved Build 42.20 to the public stable branch on July 29 and released 42.21 on September 28, 2026. Dedicated servers and participating clients need a mutually compatible stable build.

Important: Build 41 saves do not work with Build 42. Use the Steam branch legacy41 on both server and clients to retain a Build 41 world. The developer also says Unstable 42.19 saves are not compatible with 42.20; it provides a 42.19 branch for those worlds.

Platform scope: The installation below covers Windows, using the current multiplayer technical guide. Linux dedicated servers also exist, but the available Linux-specific guide had not been updated to the same stable Build 42 release, so unverified Linux steps are not included.

Build 42 stable or legacy41?

For a new Build 42 world, select NONE under Steam's Betas for both the game and server tool. The older unstable branch is no longer necessary to run stable B42. If continuing a B41 world, keep everyone on legacy41. Make an external copy of saves, settings and mod lists before any branch switch.

Self-hosting versus renting

Self-hosting gives direct access to world saves, settings, mods and backup tools but requires internet reachability, firewall/router control and adequate resources. Rental can reduce operational work for an always-on world. The current multiplayer guide estimates 2 GB of server RAM plus roughly 500 MB per player, and recommends an SSD; this is a technical guideline, not a guaranteed requirement for every mod configuration.

When comparing hosts, check allocated memory and CPU, external backups, file access, mod management and delivery of Build 42 hotfixes.

Install the dedicated server via Steam

  1. Open Steam Library and display Tools.
  2. Install Project Zomboid Dedicated Server.
  3. Open its Properties and set Betas → NONE for Build 42 stable.

A typical tool directory is SteamLibrary\steamapps\common\Project Zomboid Dedicated Server.

Install with SteamCMD instead

App ID: 380870. Run the following in a Windows terminal after installing SteamCMD:

steamcmd +force_install_dir "C:\PZServer" +login anonymous +app_update 380870 validate +quit

The stable build no longer needs -beta unstable. Stop the server and back up important files before updating; use the relevant legacy branch when maintaining an old world.

Start the server and set an administrator password

Run StartServer64.bat. On first startup, set a password for the generated administrator account. Leave the console running. The technical guide gives *** SERVER STARTED **** as the successful start message. Only then attempt to join.

Where are server configuration files?

Windows server configuration is stored under %UserProfile%\Zomboid\Server. For the usual servertest server name, files include servertest.ini and servertest_SandboxVars.lua. Different server names produce corresponding filename changes. Stop the server and back up settings before editing.

Project Zomboid Build 42 ports

The multiplayer guide revised on July 29, 2026 identifies UDP 16261 and UDP 16262. Port 16261 is the default direct-join port. Allow these through Windows Firewall and forward them to your server PC's internal IP if hosting behind a router. A connection without a publicly reachable IPv4 address may not work with traditional router forwarding, even if the rules appear correct.

Adjust server RAM

The Windows launcher StartServer64.bat allows changing maximum Java heap through -Xmx. Do not allocate every gigabyte to the server: Windows and any local game client also need memory.

Launch without mods first

  1. Install the same stable branch across server and clients.
  2. Start a vanilla server without Workshop mods.
  3. Verify it starts and connections succeed.
  4. Back up the working server.
  5. Add only mods that specifically confirm Build 42 support, testing them one at a time.

This separates version and network problems from mod failures.

Missing from the browser or stuck at Getting server info?

Verify branch and version, running server status, UDP 16261/16262, local firewall, router forwarding and mod list, in that order. Do not replace working world files with unverified community patches. Reproduce the problem without mods before applying speculative fixes.

Migrating a Build 41 world

Do not launch Build 41 saves under Build 42. The Indie Stone states they are incompatible. Use legacy41 to retain an existing world, or start a new B42 world. A move between machines within a compatible build can be performed by backing up and transferring the world and settings; this is different from upgrading the save format.

Backups for permanent servers

Make independent backups before updates, beta-branch changes, mods and major configuration edits. For rented servers, retain copies outside the provider's panel. After restoring, verify the world and build match before enabling mods.

Yes. Build 42.20 entered stable on July 29, 2026, and 42.21 was the current stable update on September 28, 2026 at the source review.

380870. Build 42 stable uses the public stable branch, rather than the old unstable beta.

The updated multiplayer technical guide specifies UDP 16261 and UDP 16262. Port 16261 is the default direct connection port.

No. The Indie Stone declares B41 saves incompatible; use legacy41 to maintain them.

Under %UserProfile%\Zomboid\Server; with the default name, servertest.ini is one of the files.