How to Update a Project Zomboid Server Safely
Project Zomboid builds, especially major branch changes, can break save compatibility and Workshop mods at once. Backup first, and never assume a mod author has caught up yet.
Start with a restore point
Back up the full Saves folder before any SteamCMD update — beta branch moves can change the save format.
Update deliberately
- Run SteamCMD's app_update for 380870 only when ready.
- Check each Workshop mod's page for an explicit compatibility note for the new build before assuming it still works.
- Major branch updates, not just patch updates, are the riskiest for existing saves — read the patch notes for save-compatibility warnings specifically.
Verify before you reopen the server
Let the server fully load the existing save and check the console for mod errors before inviting survivors back.
FAQ
Can a Project Zomboid update break my save?+
Major branch updates occasionally do — always check patch notes for save-compatibility warnings before updating an active world.
Do Workshop mods update automatically with the game?+
No — mod authors update independently, sometimes with a delay. Check each mod's page before assuming compatibility.
What's the safest update order?+
Back up the Saves folder, update the server, then verify mods load cleanly before opening it back up to players.
Update Project Zomboid without losing a save
CoalHost backs up before every update and flags Workshop mods that haven't confirmed compatibility yet.
View Project Zomboid Hosting →