Restore your Project Zomboid world from a backup

Recover the progress you want to keep without treating every missing character or broken mod as a reason to reset the whole server. Check what your backup contains before replacing any live files.

What you'll do

1. 1Choose the progress to keep
2. 2Check the backup and active save
3. 3Restore only when the scope is clear
4. 4Join and verify the result

An older backup can remove newer progress.

Tell players which recovery time you are considering. Stop the server before copying or replacing files, and keep a separate copy of its current state where possible. A backup only contains the files it captured; do not assume it includes every character, setting or mod.

Decide what needs recovery

What happened	What to check before acting
One character is missing or player data looks corrupt	Confirm the player’s exact account name and server address first. Check whether the recovery point contains the relevant player data. A working login does not prove the character is present. Ask support to assess a targeted recovery if only one player is affected.
The world or bases are missing	Identify the active save name and a recovery point that contains the matching world. Check its date against the progress you want to keep.
Mods changed and the server will not load	Compare the active profile’s mod and Workshop lists with the recovery point and the mod guide. Restoring the list alone does not guarantee that the required mod versions are available or compatible with the save.
Everything needs to return to an earlier time	Check that the backup includes the matching world, player data, configuration and required mod references before considering a full rollback. All later progress in replaced files can be lost.

If you have no usable backup, stop resets, reinstalls and file deletions. Ask support to check which recovery points, if any, are available for your server. Do not assume a recovery point or retention period exists.

Restore the matching recovery point

1. Identify the active save and build

   In the game panel, record the installed Project Zomboid version or branch, the active Save/Config Name if shown, and the server’s address. In Files, compare the active profile and save names. On setups using .cache, the profile is under .cache/Server/ and the matching world is under .cache/Saves/Multiplayer/. Other data roots are possible; if the names or paths do not match, ask support to identify the active save before restoring.

2. Inspect the backup and keep the current state

   Open Backups and choose a point from before the problem. Check its date and any ignored files. Download a copy before restoring. If possible, make and download a fresh backup of the stopped server too, so you can return to its current state. Check that the chosen archive includes the matching world and the player, profile and mod information needed for your goal. If you cannot confirm its contents, pause and ask support.

   Project Zomboid Build 41 saves are not compatible with Build 42. Match the recovery point to the server build and check the mod authors’ requirements before starting it.

3. Choose the recovery scope

   A panel Restore overwrites files present in the backup; the panel backup guide explains the restore choices. Delete all files before restoring also removes files absent from that backup. Use a full rollback only when you have confirmed that the recovery point covers everything you need and that losing later progress is acceptable. For one character, one save component or a mod list, ask support to identify a safe targeted route instead of guessing which files to replace.

4. Restore and start the server

   Follow Restore a backup for the panel action after the scope is clear. Start the server and check the console for save, database and mod errors. If the backup is missing a required file or the build or mods do not match, stop; do not reset the save or keep retrying different file combinations.

5. Join and check the recovered progress

   Join with the original account name and the matching client version. Check the expected world and bases, then ask affected players to verify their own characters and inventory. Check that the server starts again after a normal stop. Keep both downloaded copies until everyone has checked the result.

Done! The recovered save is checked.

Keep the recovery point while players confirm their progress. If a character, base or mod is still missing, send support the backup time, build, save name and first relevant console error.

Download a backup before stopping or moving

1. Stop and create a panel backup

   Stop the server and wait for it to finish saving. Follow Create a backup and leave Ignored Files & Directories empty unless you know those files are unnecessary for recovery.

2. Download and check it

   Wait until the backup finishes, then use Download in its three-dot menu. Keep the downloaded archive somewhere you control and check that it contains the active world, player data and matching configuration. The backup guide has the panel steps; SFTP can also copy files from a stopped server.

3. Keep it until the move is verified

   Retain the copy until the destination server starts, players can join and the expected world and characters are present. If the archive is incomplete, do not cancel the old server or remove its files yet; ask support what must be included.

Extra tips

• Keep names together: record the backup date, server build, active save name and affected account names without sending passwords.
• Missing files matter: a world without its matching player or profile data may start but still lack characters, settings or mods.
• Avoid a reset: the reset guide starts fresh; use it only when losing the old progress is your goal.

Still stuck?

Send us your server name and the last 20 console lines. A real person reads it, usually within a few hours.

Open a ticket

Host your own Project Zomboid server

Play together on your own server

View servers