How to Update a Project Zomboid Dedicated Server Safely

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

Playing with friends? Godlike.Host runs hosted Project Zomboid servers from 10 data-center locations, with free DDoS protection.

Update a Project Zomboid dedicated server with a controlled stop → backup → SteamCMD update → restart → compatibility check workflow. The update command is steamcmd +force_install_dir <server-folder> +login anonymous +app_update 380870 validate +quit. Keep the server, saved world, clients, and Workshop mods on compatible branches: a Build 41 save cannot be loaded by Build 42.

What a server update actually changes

A dedicated-server update replaces the server program files and may also change the game branch, bundled files, or the behavior expected by clients and mods. SteamCMD can download the correct binaries again, but it cannot recreate a deleted world, server configuration, player database, or custom settings. Those files must be protected separately.

#	Preview	Product	Price
1		Zombicide 2nd Edition Strategy Board Game | Cooperative Game for Teens and Adults | Zombie Board...		Buy on Amazon

There are two different maintenance cases:

• Patch update within the same major branch: this is normally the intended in-place workflow. You still need a backup because mods or a patch can change save behavior.
• Major-branch change: Build 41 and Build 42 require separate planning. The Indie Stone’s July 2026 Build 42 Checklist states: “Build 41 savegames clearly will not be compatible with Build 42.” Do not point a Build 41 world at a Build 42 server and expect it to load.

The current material treats Build 42 as the default branch, but branch names and patch numbers can change. Read the branch and build shown by Steam or in the startup log at the time you update instead of copying an old build number from an evergreen guide.

Before taking the server offline

Do the preparation while the server is still running, but do not copy live save files. A save can be changing while the server writes it, producing an incomplete or inconsistent backup.

#1 Best Overall

Zombicide 2nd Edition Strategy Board Game | Cooperative Game for Teens and Adults | Zombie Board Game | Ages 14+ | 1-6 Players | Avg. Playtime 1 Hour | Made by CMON

• UPDATED CLASSIC: Dive into Zombicide: 2nd Edition, the thrilling update to the classic zombie-slaying game. Experience enhanced gameplay and new challenges in the zombie apocalypse.
• COOPERATIVE SURVIVAL: Join forces as Survivors in a world overrun by zombies. Work together to navigate through missions, complete objectives, and fight for survival.
• ADRENALINE-POWERED ACTION: With each zombie kill, increase your Adrenaline Points. Gain strength and skills but attract more zombies with your actions – a double-edged sword.
• INTENSE MISSIONS: Face a series of challenging missions, each requiring strategic planning, teamwork, and bravery. Can you accomplish your objectives while fending off the undead?
• SURVIVE OR BECOME ZOMBIE PREY: The stakes are high - will you emerge as a triumphant survivor or fall victim to the relentless zombie hordes?

Buy on Amazon

1. Announce a maintenance window. Tell players when the server will stop and when they should reconnect. Include the branch you intend to run after the update.
2. Record the current branch and build. Note whether the installation uses the default branch or a pinned legacy branch, and capture the build shown in the server startup output.
3. Record mod settings. Copy the existing Mods and WorkshopItems values from the server configuration. Do not use the update as an opportunity to edit several mod lists at once; preserving a known-good list makes a failure diagnosable.
4. Warn players about client updates. Everyone must use the same game branch and compatible mod versions after the server returns.
5. Stop the server cleanly. From the server console, enter quit, or use the stop action supplied by the service manager. Wait for the process to exit before touching any files.

Back up the world, configuration, and player data

Make a dated copy on storage that is not overwritten by the update. Keep the original until players have successfully joined and you have confirmed that the world is healthy.

Files to preserve

• Zomboid/Server/ — server configuration, settings, and the recorded mod lists.
• Zomboid/Saves/Multiplayer/<servername> — the multiplayer world and its save data.
• Player database on Linux, when used. Preserve the database file or directory used by your installation so player identities, permissions, and related records can be restored.

Use a name that records the date, branch, and purpose, such as pz-backup-2026-10-15-build41-before-update. Back up the folders rather than attempting to export individual map files. Do not edit a live save directory or replace files while the server process is still running.

Why server binaries are not the important backup

SteamCMD can redownload the dedicated-server program files. It cannot regenerate your world, settings, or player records. Prioritize the save and configuration folders, then retain the backup until the new build and its mods have passed a join test.

Choose the update method

Whichever method you choose, update the same installation directory that your start script or service actually uses. Updating a second SteamCMD directory does not update the server that players connect to.

Update with SteamCMD

The dedicated-server Steam application ID is 380870. Run the command only after the server has stopped and the backup is complete.

Default current branch

Replace <server-folder> with the absolute directory used by your server. Keep the directory path quoted when it contains spaces.

steamcmd +force_install_dir <server-folder> +login anonymous +app_update 380870 validate +quit

+force_install_dir selects the destination, +login anonymous uses the public dedicated-server login, +app_update 380870 downloads or updates the server, validate checks downloaded files, and +quit exits SteamCMD when it finishes.

Windows Steam client installation

1. Open Steam and go to Library → Tools.
2. Locate the Project Zomboid dedicated server tool and confirm its installation folder.
3. Close the server if it is running, then allow Steam to finish the tool’s update.
4. Launch the server script from that same folder after the update. A 64-bit Windows installation normally uses StartServer64.bat.

If you use SteamCMD on Windows instead, point +force_install_dir at the folder containing the script you intend to launch. Do not mix a Steam client installation and a SteamCMD installation without deliberately choosing which one is authoritative.

Linux or headless Windows

1. Run SteamCMD under the service account that will own and start the server, or correct the ownership after the update.
2. Use the controlled install directory in the command above.
3. Wait for SteamCMD to report completion and validation before starting the service.
4. Start the existing Linux service or start script, rather than creating a second process from another directory.

Keep the install path, service account, backup location, and branch choice documented so a later administrator can reproduce the update.

Updating a pinned or legacy branch

If the world is intentionally kept on an older branch, do not run a default-branch update by habit. Include the branch argument documented for that server. For example, the Build 41 legacy branch uses:

steamcmd +force_install_dir <server-folder> +login anonymous +app_update 380870 -beta legacy41 validate +quit

Use the exact branch identifier supplied for your installation. Branch names are not interchangeable, and a branch argument that was valid for one release can be retired or renamed. Players must select the same game branch in their own installation.

When to stay on the old branch

• The existing save is Build 41 and you need to keep using it.
• Your required mods have not been updated for the newer branch.
• Your players have not yet migrated their clients and you have a tested transition plan.

Do not convert a production world merely to obtain a newer server binary. Make a separate test copy if you need to evaluate a major-branch change.

Start the server and verify the result

1. Confirm that the backup is complete and the update command has exited successfully.
2. Start the server with StartServer64.bat on Windows, or the established Linux service/start script.
3. Watch the startup log until the server reports that it is ready. Check the displayed branch and build against the version you intended to install.
4. Check that the expected server name, world, settings, and player data are present before inviting everyone back.
5. Join with an administrator account first. Move, interact with the world, and verify that the expected characters and permissions are available.

If the process starts but the expected world is missing, stop immediately. A common cause is starting a different install directory or using a different server name, not a destroyed save. Stop the process, identify the configured save path, and compare it with the dated backup before making changes.

Keep Workshop mods synchronized

At startup, the server checks each ID listed in WorkshopItems and downloads newer versions. The Mods value controls which downloaded mods are enabled. A server update does not guarantee that every mod is compatible with the new branch.

Safe mod-update sequence

1. Before the update, record the complete Mods and WorkshopItems values.
2. Update the server branch and start it once with the known list.
3. Read the startup log while Workshop items download or update.
4. Wait for the server to report ready, then test a client join.
5. Update or remove a mod deliberately, one change at a time, if the log identifies a compatibility problem.
6. Tell players to let Steam finish downloading the same Workshop revisions before they connect.

The error workshop item version is different than the server means the client and server have different downloaded revisions. It is not fixed by repeatedly changing unrelated server settings. Stop, establish which revision the server has downloaded, allow the client to update to that revision, and test again. If the Workshop item itself is incompatible with the selected branch, pin the server and clients to a compatible combination or remove the mod after making a backup.

Make clients match the server

A successful server process is not enough: joining requires agreement on the game branch, server build, enabled mods, and Workshop versions.

• Have every player select the same branch as the server; a Build 41 client cannot join a Build 42-only setup.
• Have players wait for their game and Workshop downloads to finish before launching.
• Give players the exact server name and connection details after the test join succeeds.
• Do not ask players to delete saves or configuration folders as a first response. Preserve evidence and resolve the branch or mod mismatch first.

Check firewall and ports after an update

When LAN players can connect but Internet players cannot, check networking before changing the save. The Linux guide’s example defaults are UDP port 16261 and UDP port 16262; your server may be configured differently, so use the ports shown in its settings.

• Allow the configured UDP ports through the host firewall.
• For Internet play, forward those UDP ports from the router to the server’s local address.
• For LAN-only play, router forwarding is normally unnecessary.
• Recheck the host address if the machine received a new local IP after a restart.

A branch or mod update does not normally change router rules, but a service restart can expose an existing firewall or port-forwarding mistake. Test locally first, then test from an external connection.

Troubleshoot common post-update failures

SteamCMD reports success, but the old version starts

• Confirm that +force_install_dir matches the folder used by the start script.
• Check that no second server process is still running from the old directory.
• Inspect the startup log for the actual branch and build.
• Stop both processes, then update and start only the intended installation.

Build 41 world will not load after moving to Build 42

This is an incompatibility, not a missing validation step. Restore the backup, return the server and clients to the matching Build 41 branch, and keep the Build 42 experiment separate. Build 41 savegames are not compatible with Build 42.

Players receive a Workshop version error

Compare the server’s downloaded Workshop revision with the client’s revision. Make the client finish its download, or return the server and clients to a known-compatible mod version. If a mod changed its data format, restore the pre-update save and mod list before testing further.

The server starts, but the world or characters appear reset

• Stop the server and do not let new play overwrite the suspected location.
• Check the server name and save path in Zomboid/Server/.
• Confirm that the service account can read the intended save directory.
• Compare the active path with Zomboid/Saves/Multiplayer/<servername> in the backup.
• Restore the dated backup only after the process is stopped and the matching branch is selected.

LAN works but remote players cannot connect

Verify the configured UDP ports, host firewall, router forwarding, and public address. The example ports 16261 and 16262 apply only when those are the ports configured by your server.

The process crashes during startup

Read the first meaningful error in the startup log rather than treating the final shutdown line as the cause. Check branch compatibility, Workshop downloads, file permissions, and recent mod changes. If the failure began with the update, stop the server, restore the dated save and configuration backup, return to the previous branch, and then test changes in isolation.

Rollback safely

Rollback is a controlled return to the last known-good branch, binaries, configuration, and save—not merely a second validation run.

1. Announce that the server is offline and stop it with quit or the service manager.
2. Keep the failed-upgrade files in a separate folder if you need logs for diagnosis.
3. Restore Zomboid/Server/, Zomboid/Saves/Multiplayer/<servername>, and the Linux player database backup where applicable.
4. Use SteamCMD with the branch that matches that backup, such as -beta legacy41 for a Build 41 installation.
5. Restore the recorded Mods and WorkshopItems values.
6. Start the server, verify the build in the log, and perform an administrator and ordinary-player join test.

Do not overwrite the only backup with files produced by the failed run. Keep at least one untouched dated copy until the rollback has been verified.

Self-hosted versus managed updates

Self-hosting gives you direct control over branch pinning, update timing, files, and rollback. It also makes you responsible for SteamCMD, service restarts, backups, permissions, firewall rules, router forwarding, and player communication. Managed hosting can outsource those operations, but you should still ask where backups are stored, whether a legacy branch can be pinned, how Workshop updates are controlled, and how a rollback is performed. A provider’s “automatic update” is not a substitute for a recoverable world backup.

Capacity and version-specific claims

Some Build 42 material cites handling for up to 254 players. Treat that figure as patch-specific rather than a permanent server guarantee: verify the capacity guidance for the exact build you install, and consider CPU, memory, network, and mod load separately. The update procedure itself does not establish a performance limit.

Quick Recap

Bestseller No. 1

Zombicide 2nd Edition Strategy Board Game | Cooperative Game for Teens and Adults | Zombie Board Game | Ages 14+ | 1-6 Players | Avg. Playtime 1 Hour | Made by CMON

Final maintenance checklist

• Players were warned and the server stopped cleanly.
• The dated copies of Zomboid/Server/, the multiplayer save, and the Linux player database were completed while the server was stopped.
• The intended branch was confirmed before running SteamCMD.
• app_update 380870 validate completed in the directory actually used by the server.
• The startup log shows the intended branch and build.
• Mods and WorkshopItems were preserved and Workshop downloads completed.
• Clients use the same branch and mod revisions.
• Configured UDP ports, firewall rules, and router forwarding were tested for the intended LAN or Internet audience.
• An administrator and at least one ordinary player completed a join test before normal play resumed.

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.