How to Restore a Project Zomboid Server Backup Safely

To restore a Project Zomboid server, stop every process that can write to the save, preserve the current Zomboid directory as a rollback copy, and then put the backup into the matching profile and build. A multiplayer world normally lives in Zomboid/Saves/Multiplayer/<servername>; server settings are under Zomboid/Server. A save-only archive replaces the matching world folder, while a complete server backup may also require db and Server. Keep the same profile name, game/server build, and Workshop mod list whenever possible, then test with one client before reopening the server.

Prefer not to run the server on your own PC? Godlike.Host offers hosted Project Zomboid servers with free DDoS protection and up to three free backups a day.

What you need before touching the files

Write down the server or profile name exactly as it appears in the host configuration, the game and dedicated-server build, and every Workshop or mod identifier enabled on that profile. The current procedure is labeled for Build 42.21 Stable (updated September 30, 2026), but your backup must match the build that created it. No compatibility guarantee is established for restoring a world across different builds or mod sets, so treat a version or mod change as a possible cause of a failed load rather than assuming the files are damaged.

#	Preview	Product	Price
1		Zombicide 2nd Edition Strategy Board Game | Cooperative Game for Teens and Adults | Zombie Board...		Buy on Amazon

As an Amazon Associate I earn from qualifying purchases.

• Profile identity: Restore to the original profile name when you can. Hosted tools may use that name as part of the hosted identity; copying files to a newly named profile can detach client-local state.
• Access: You need permission to stop the dedicated server or hosting container and to read and write its data directory.
• Backup media: Have an external drive or cloud destination ready for a copy of the current data. This copy is your way back if the selected archive is wrong.
• Test account: Plan to join with one administrator or test client before allowing the rest of the players back in.

Choose the restore scope

First determine what is actually inside the archive. Restoring only a world folder over a full installation can leave old settings or database state in place; restoring an entire configuration when you only meant to roll back the map can overwrite passwords, whitelist entries, or other server settings.

Where Project Zomboid stores a multiplayer world

On Windows, the common data root is C:Users<username>Zomboid. On Linux it is ~/Zomboid/. Within that root:

#1 Best Overall

Zombicide 2nd Edition Strategy Board Game | Cooperative Game for Teens and Adults | Zombie Board Game | Ages 14+ | 1-6 Players | Avg. Playtime 1 Hour | Made by CMON

• UPDATED CLASSIC: Dive into Zombicide: 2nd Edition, the thrilling update to the classic zombie-slaying game. Experience enhanced gameplay and new challenges in the zombie apocalypse.
• COOPERATIVE SURVIVAL: Join forces as Survivors in a world overrun by zombies. Work together to navigate through missions, complete objectives, and fight for survival.
• ADRENALINE-POWERED ACTION: With each zombie kill, increase your Adrenaline Points. Gain strength and skills but attract more zombies with your actions – a double-edged sword.
• INTENSE MISSIONS: Face a series of challenging missions, each requiring strategic planning, teamwork, and bravery. Can you accomplish your objectives while fending off the undead?
• SURVIVE OR BECOME ZOMBIE PREY: The stakes are high - will you emerge as a triumphant survivor or fall victim to the relentless zombie hordes?

Buy on Amazon

• Saves/Multiplayer/<servername> contains the multiplayer world: map and chunk data, vehicles, containers, and the persistent world state.
• Server/ contains profile configuration used by the dedicated server.
• db, when present in a complete backup, is part of the server’s persistent database state and should be restored with the matching profile rather than mixed casually with an unrelated save.

Folder names are case-sensitive on Linux. Do not rename the restored world to make it look tidy; use the name the server is configured to load. If you must experiment with another name, do it on a disposable copy, not on the production profile that players use.

Safe restore procedure for a local or dedicated server

1. Record the profile and stop writes

Confirm the profile name, build, and mod list from the server configuration and your backup notes. Shut down the dedicated server cleanly before replacing anything. A running process can keep files open or write a newer world state over the files you just copied. Never overwrite a save while the server is online.

2. Make a rollback copy

Close the server and copy or rename the entire current Zomboid data directory to a separate location. An external hard drive or cloud destination is suitable. Give the copy a date and a clear label such as Zomboid-before-restore-2026-10-15. Do not delete this copy until the restored world has passed your checks and at least one test player has joined successfully.

3. Inspect the archive before extraction

List the archive’s top-level folders without extracting over production data. Decide whether it is save-only or complete. If it contains a single server folder, identify its exact name and compare it with Saves/Multiplayer/<servername>. If it contains db, Saves, and Server, plan a complete restore only if that is the scope you want.

4. Replace a save-only world

1. Inside Zomboid/Saves/Multiplayer, rename the current matching world folder to a dated rollback name, for example servertest.old-2026-10-15. Renaming is safer than deleting because it leaves an immediate fallback.
2. Copy the archived world folder into Saves/Multiplayer so its final path exactly matches the configured profile, such as Zomboid/Saves/Multiplayer/servertest.
3. Check ownership and permissions on Linux or a container host. The account that runs the server must be able to read and write every restored file.

5. Replace a complete profile

For a complete backup, restore the matching db, Saves, and Server directories into the Zomboid root. Preserve the same profile name and directory layout. Do not merge similarly named files from two different backups unless you know which snapshot is authoritative; a mixed database, save, and configuration set can produce confusing joins or missing state.

6. Match the runtime before starting

Install or select the same game/server build used by the backup and enable the same Workshop and mod identifiers. A world can appear to load while still failing to stream map chunks when its mod list differs. If you intentionally need to change versions or mods, duplicate the restored files into a lab profile and test there first.

Docker restore sequence

For a Docker deployment, the container must be stopped before the mounted data is changed. The documented sequence is:

1. From the directory containing the Compose file, run docker compose down.
2. Rename the current save directory, for example change data/Saves/Multiplayer/servertest to a dated path such as data/Saves/Multiplayer/servertest.old-2026-10-15.
3. Extract the archive into the matching data/Saves/Multiplayer/servertest directory. Use the archive tool’s documented strip-components setting so the archive’s enclosing directory is not duplicated (avoid ending up with a path such as servertest/servertest/...).
4. Restore Docker-side configuration separately if the archive contains only saves. Do not assume a save archive includes Compose files, environment variables, server settings, or the db directory.
5. Run docker compose up -d and wait for the server to finish starting before allowing players to connect.

The project-zomboid-server-docker documentation describes asking the server to save through RCON before every scheduled backup so the archive is a consistent snapshot rather than a collection of mid-write files. Apply the same principle when creating any manual archive: issue a save command through RCON, wait for it to complete, and only then copy the files.

Hosted and co-op restores: the local-cache trap

Native hosted auto-backups restore server-side profile and save state. They do not automatically replace the local client cache at Saves/Multiplayer/<profile>_player. After a healthy server restore, a client can therefore retain stale map data.

If the server starts normally but logs or the client show map or chunk download errors, CRC mismatches, or repeated attempts to download the same area, do not immediately overwrite the server files again. Use the host tool’s preview and confirm workflow to reset that client’s local cache, then reconnect. Perform this only for the affected client unless the host specifically instructs otherwise; deleting server-side saves is a different operation.

First-start verification checklist

Start the server with its normal password and whitelist settings, then join with one test client. Check the following before announcing the restore complete:

• The server loads the intended profile name and reaches a healthy, joinable state without repeated errors.
• The in-game world date and time correspond to the selected backup.
• Your expected player character is present, with the appropriate inventory, skills, and location.
• Vehicles, containers, safehouses, doors, generators, and other persistent world changes are present where expected.
• The active Workshop and mod list matches the backup’s recorded list.
• A test client can move through previously visited areas without map or chunk errors.
• Passwords, whitelist entries, and administrator settings are correct if you performed a complete restore.

Keep the pre-restore copy until these checks pass. If the world opens but one check fails, stop again and investigate while the old files are still available.

Troubleshooting by symptom

The server loads a new world instead of the backup

Usually the restored folder is in the wrong path or has the wrong name. Verify that the final directory is exactly Zomboid/Saves/Multiplayer/<servername> for the profile the server starts. Check for an extra archive directory level and confirm capitalization on Linux. Also verify that the server is using the intended data root rather than a different user’s home directory or Docker volume.

The server fails during startup after a full restore

Stop it and compare the build and mod list with the backup. A complete restore can also bring back configuration that expects a different port, password, or mod identifier. Restore the pre-restore copy if you need the server online, then test the archived files in a disposable profile while you reconcile configuration.

Characters or server settings are missing

Determine the archive scope. A save-only archive may not include db or Server, so it cannot roll back data stored there. Conversely, restoring only the world folder will not return configuration from a complete snapshot. Use the matching scope rather than combining files from unrelated dates.

The map shows CRC or chunk errors after a successful start

Inspect server logs first. If the server-side world and mod list are correct, reset the affected hosted/co-op client’s <profile>_player cache through the host’s preview/confirm workflow. A client-cache reset is not a substitute for restoring a missing world folder.

Players cannot connect after the restore

Check that the server is listening with the expected password and whitelist, that the profile name was preserved, and that clients have the required Workshop content. Do not conclude that the save is corrupt until a clean test client has tried the same build and mod set.

How to make the next backup easier to restore

• Keep a manifest with the profile name, game/server build, Workshop IDs, backup date, and whether the archive is save-only or complete.
• Prefer a graceful shutdown or an RCON save before copying. A live copy can capture files during a write.
• Store at least one rollback copy outside the machine that runs the server. An external drive protects against local disk failure; an off-site copy protects against loss of the host itself.
• Retain the original directory name in the archive and document any required archive extraction setting, including how many enclosing path components must be stripped.
• Periodically perform a test restore on a disposable profile. This verifies that the archive is readable without risking the live world.

The reliable pattern is simple: identify the exact profile and build, stop writes, preserve the current files, restore only the scope contained in the archive, and verify with one client before reopening. Keeping those boundaries prevents most accidental overwrites and makes a failed restore reversible.

Quick Recap

Bestseller No. 1

Zombicide 2nd Edition Strategy Board Game | Cooperative Game for Teens and Adults | Zombie Board Game | Ages 14+ | 1-6 Players | Avg. Playtime 1 Hour | Made by CMON

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.