Keeping your Project Zomboid server updated is important whenever a new patch or Build 42 update is released. If the server is running a different game version from the players trying to connect, you may encounter version mismatch errors or be unable to join altogether.
The update process depends heavily on how your server is hosted. A self-hosted server usually requires SteamCMD commands, manual file management, and backups, while dedicated Project Zomboid hosting can automate much of the process through a server panel.
How To Update A Self-Hosted Project Zomboid Server
If you manage the server yourself, you will need to stop the server, back up your files, open SteamCMD, target the correct installation directory, and manually run the update.
Back Up Your Project Zomboid Server
Before updating, create a backup in case the update causes problems with your world, configuration, or mods.
On Windows, Project Zomboid commonly stores server data under:
C:\Users\YourUsername\Zomboid\
Your multiplayer saves are typically located in:
C:\Users\YourUsername\Zomboid\Saves\Multiplayer\
Server configuration files can be found under:
C:\Users\YourUsername\Zomboid\Server\
Copy the files you want to preserve somewhere outside the active server directories before updating.
With a self-hosted server, this backup process is generally something you need to manage yourself. Creating regular copies before updates is especially useful if you are running a larger world or a heavily modded server.
A backup does not guarantee that an older save will work with every major game version. It simply gives you a copy of your previous server data if something goes wrong.
Stop Your Project Zomboid Server
Your Project Zomboid dedicated server should be completely offline before updating its installation.
If the server console is currently open, shut the server down normally and wait until the process has fully closed.
Avoid updating server files while the server is still running. Once everything is offline, you can open SteamCMD.
Open SteamCMD And Log In
SteamCMD is Valve's command-line tool for installing and updating dedicated servers.
If your Project Zomboid server was originally installed through SteamCMD, locate the folder containing:
steamcmd.exe
Open it and wait for the SteamCMD console to appear.
Enter:
login anonymous
Project Zomboid Dedicated Server supports anonymous SteamCMD access, so you do not need to sign into your personal Steam account to update it.
Set Your Server Installation Directory
Before running the update, make sure SteamCMD is targeting the correct Project Zomboid installation.
For example, if your server is installed under:
C:\PZServer
enter:
force_install_dir C:\PZServer
Replace this path with the actual location of your server.
If you are unsure where it is installed, look for the folder containing server files such as:
StartServer64.bat
Getting this path right is important. Otherwise, SteamCMD could download the server files into another directory instead of updating the installation you actually use.
Update Your Project Zomboid Server
Project Zomboid Dedicated Server uses Steam App ID:
380870
To update an existing server running on the current public Stable branch, enter:
app_update 380870
SteamCMD will check the dedicated server installation and download any newer files that are available.
Once SteamCMD reports that the update has completed successfully, enter:
quit
You can then close SteamCMD.
If your server intentionally runs a beta branch instead of Stable, your update command will need to continue specifying that branch. Do not remove an existing beta branch unless you actually want to change which version of Project Zomboid the server runs.
When Should You Use Validate?
You may also see Project Zomboid server guides using:
app_update 380870 validate
The validate option checks the installed server files against the files available through Steam and replaces files that do not match.
You do not necessarily need to validate the entire installation every time you perform a normal update.
However, it can be useful if an update has failed, server files may be corrupted, or the server refuses to start correctly after updating.
If you are troubleshooting one of these situations, run:
app_update 380870 validate
and allow SteamCMD to complete the verification before starting the server again.
Start The Server And Check The Update
Return to your Project Zomboid server installation after SteamCMD finishes.
On Windows, you will commonly start the dedicated server using:
StartServer64.bat
Allow the server to finish loading and check the console for errors.
Try connecting with an updated Project Zomboid client afterward. If the client and server are running different versions, update both before troubleshooting other connection problems.
You should also pay attention to mods after larger updates. A Project Zomboid update can sometimes require Workshop mods to be updated as well.
If the server worked before updating but fails afterward, checking recently installed or outdated mods can help narrow down the cause.
How To Update With Dedicated Project Zomboid Hosting
Using dedicated Project Zomboid hosting makes regular updates much easier because you do not need to manage SteamCMD commands, installation directories, or server App IDs yourself.
With Pine Hosting, updates can be handled automatically whenever the server restarts.
Enable Auto Update On Restart
Open your Project Zomboid server and go to the Startup page.
Find:
Auto Update on Restart
Make sure this slider is enabled.
Once it is active, the server will check for available game updates whenever it restarts and install them before starting again.
To manually trigger an update, the process is simply:
- Open your Project Zomboid server panel.
- Go to the Startup page.
- Make sure Auto Update on Restart is enabled.
- Restart the server.
- Allow the update and restart process to complete.
There is no need to open SteamCMD, use force_install_dir, remember App ID 380870, or manually run an app_update command.
Automate Future Project Zomboid Updates
You can also leave Auto Update on Restart enabled indefinitely.
If your server already has a restart schedule, this means future updates can be installed automatically whenever the scheduled restart occurs. You do not need to manually check for updates and run commands every time a new patch is released.
This is particularly useful for servers that already restart on a regular schedule for maintenance.
Instead of manually:
- Stopping the server
- Opening SteamCMD
- Setting the installation directory
- Running the update command
- Starting the server again
The hosting panel can handle the update as part of the normal restart process.
Schedule Automatic Backups
Dedicated Project Zomboid hosting can also make backups easier to manage.
Rather than manually copying your Zomboid save and configuration folders before every update, you can create a backup schedule so server files are backed up automatically.
This gives you a recent copy of your server data if an update, mod change, or unexpected file problem causes an issue.
Combining scheduled backups with scheduled restarts and Auto Update on Restart means much of the normal Project Zomboid server maintenance process can run without you needing to manually manage files or commands.
Keep Your Project Zomboid Server Updated With Pine Hosting
Keeping a Project Zomboid server updated manually is not especially difficult once you understand SteamCMD, but it does require several steps every time a new version is released.
With Pine Hosting's Project Zomboid hosting, updates can be installed automatically during restarts, backups can be scheduled, and regular server maintenance can be handled directly through the game panel.
Whether you are running a private Build 42 world with friends or managing a larger modded community, choosing the best Project Zomboid hosting provider can save you from repeatedly managing SteamCMD, server directories, and manual backups.
Start your Project Zomboid server hosting journey with Pine Hosting and make updates and server maintenance easier to manage.
