Quick answer
What to do first
Exit the game and stop a hosted server cleanly before copying its data. Keep an untouched, dated copy outside the active save folder, record the game build and mods, and restore only into a compatible setup. Preserve the destination's existing data too. A multiplayer client cache is not the server's authoritative world, and a backup does not convert B41 or B42.19 into current Stable.
Check your game conditions
- Current Stable
- 42.20.4 Stable
- Play mode
- Singleplayer / Multiplayer
- Vanilla / Mods
- Vanilla baseline; mods may replace rules
- Sandbox / server settings
- Same-build restoration only; server identity/configuration is separate from a single-player save.
Backup and restore checkpoints
Stop writes
Copying live world files can capture an inconsistent state
Check: Game closed; owner stopped the server normally
Safe action: Wait for the process to finish before copying.
Locate the authoritative data
Client and server data are not interchangeable
Check: Which machine/account owns the world
Safe action: Back up that data, not only a joining client's folder.
Copy, do not move
The original is the rollback path
Check: Dated destination outside the active save directory
Safe action: Keep the first copy untouched and record build/mod information.
Prepare the target
Old data must not be silently overwritten
Check: Compatible build and a separate backup of target data
Safe action: Restore into the intended profile with the game stopped.
Validate the restored copy
A successful file copy is not a successful recovery
Check: Correct world, character and expected progress
Safe action: Retain the original until the restored session is confirmed usable.
Know which folder you are protecting
On a default Windows installation, the user-data root is %USERPROFILE%\Zomboid. Singleplayer worlds are under its Saves directory, grouped by mode and world. This is separate from the Steam installation folder. Copy the whole intended save rather than guessing which individual map or character file matters.
For a self-hosted server, preserve the authoritative world together with its matching server configuration and database data. The Zomboid user-data root contains Saves, Server and db areas used for these different roles. A host may relocate them; use its actual configuration and backup facility instead of assuming the desktop path.
Restore a copy, then confirm it
Keep the current destination safe before replacing anything. With the game/server stopped, place the compatible backup in the intended data location. Do not merge random old and new files to force an incompatible world to open.
For a move to another PC, match the build and required mods and verify the selected world and character after loading. If the result is wrong, stop and return to the preserved copy. A cloud sync or a joining client's cached files should not be your only recovery plan.
Version notes & limits
Default paths can be relocated by a server host or cache-directory setting. Confirm the actual data directory and branch first; the 42.20 release explicitly separates incompatible older worlds.
Non-destructive backup, restoration and same-build transfer. No singleplayer-to-server identity conversion, cross-build converter or deletion commands.
Last verified means the linked documentation was reviewed, not that this guide was tested in-game. PZwiki is maintained by community contributors.
Version & sources
Sources & what may change
- Applies to
- 42.20.4 Stable; Singleplayer / Multiplayer; Vanilla baseline; mods may replace rules
- Last verified
- 2026-09-04
- When to check again
- A relevant Stable patch, changed world setting, mod update or correction to the cited instructions.