Restore Backups
Restoring a backup is a recovery operation, not a routine file copy. The goal is to get the world back to a known-good state with the least extra damage possible, which means choosing the right restore point and validating it before players pile back in.
Pick The Backup Deliberately
| Too old | You recover stability but lose unnecessary player progress. |
|---|---|
| Too recent | You may restore the same corruption or bad mod state you were trying to escape. |
| Best candidate | The last version from before the incident that still reflects most recent healthy progress. |
Restore Procedure
- Preserve the current broken state first so you can examine it later if needed.
- Restore the chosen backup into the correct world location with the server stopped.
- Confirm the config, map stack, and mod list still match that backup era.
- Join privately and inspect key bases, player characters, and any problem zone that triggered the rollback.
Common Recovery Mistakes
- Overwriting the only copy of the current world before you are sure the backup works.
- Restoring a world file but leaving mismatched live configs in place.
- Announcing success before anyone has actually checked the damaged area.
Verified 2026 Detail
The official stable and unstable split matters during recovery because a backup is only truly healthy in the environment it matches. If you restore the right files into the wrong branch context, the symptoms can look like corruption even though the recovery point itself was fine.
Current Official Note
The official Project Zomboid FAQ still treats unstable builds as a distinct opt-in track. During recovery, use a backup from the correct branch era whenever possible, because restoring a stable-era world into an unstable environment can look like data corruption even when the files are intact.
Need a stable place to test changes before you touch a live world? Launch your Project Zomboid server with Supercraft.