Back up a Project Zomboid world before you touch it

Close the game before copying

Exit Project Zomboid normally and confirm it is no longer running. Open world files can still change while the process is open, so a live copy may be incomplete.

1. For solo or local hosted co-op, close the game on the world-owning machine.
2. For a dedicated or remote server, the host/admin must stop the server; a client cannot create a complete server backup.
3. Keep the Build 42 version, mode, world name, and mod list beside the backup.

Copy the whole world folder

From Zomboid/Saves/<game mode>/, copy the complete world folder—not one map file or database. To protect every local world, copy the entire Saves directory.

1. Paste the copy outside the live Zomboid tree, preferably on another drive or controlled cloud location.
2. Add a timestamp and world name, such as pz_backup_20260911_MyWorld.
3. With mods, preserve the enabled-mod list and version notes; a copy cannot supply a mod later removed or changed.

Do not leave ambiguous copies beside the live world under Saves; they are easy to load by mistake and do not protect against disk failure.

↑ Back to contents

Restore onto the live path without destroying the backup

1. Quit the game completely and move the live world to a holding folder such as MyWorld_before_restore. Do not delete it.
2. Copy the dated backup into the original Saves/<mode>/<world> location. If testing mods or branches, work from a duplicate of the backup.
3. Launch the same Build 42 branch, choose Load, and check the map, survivor, inventory, and world state.
4. If it fails, quit and move the holding folder back. Keep the dated backup unchanged.

Never overwrite your only backup with a newer live folder. The safe pattern is move aside, copy in, verify, and keep both copies until the test passes.

What a backup can and cannot bring back

A backup returns the world to the moment it was copied. Progress made after that moment is not in it, and there is no guarantee that a backup taken after a death can resurrect the earlier survivor or recover items already lost. It is not an in-game “Save As” slot.

Branch changes, missing mods, changed mod versions, or a genuinely corrupted snapshot can still prevent loading. Do not delete files, edit binary data, or call a failed restore proof that the backup is bad. Keep the original and collect the exact error before trying one controlled change.

Single-player and multiplayer are different backups

In single-player or local co-op, a clean copy of the host’s world folder is a rollback point for that local world. It cannot recover state that was never captured.

In remote multiplayer, the host/server owns the authoritative world, inventory, and shared map. A client’s local data is not a complete server snapshot. Ask the host/admin for the server-side backup and restore procedure; do not substitute a client path or upload a local folder to a live server. For a crash or mod failure, keep the backup and use the error-log guide ↗.