Free tools Windows power users keep installed
One-click scans. No signup required.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
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.
The reliable way to back up a Project Zomboid server is to stop it before copying anything, then archive three pieces together: the active multiplayer world, the matching server profile, and the Workshop/mod records. Save the archive with the server name, UTC timestamp, and game build; keep a copy on an independently managed drive; and test the archive on a separate profile or staging host before replacing the live save.
What a complete Project Zomboid backup contains
A server save is more than the map data. The world, server settings, and mod manifest must remain consistent. Copying only the world directory can produce a server that starts with default settings, generates a new map, or fails when clients have a different mod set.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →| Component | Typical location | Purpose |
|---|---|---|
| Multiplayer world | Zomboid/Saves/Multiplayer/<server> |
Characters, chunks, vehicles, containers, buildings, zombies, and the current world state. |
| Server profile | Zomboid/Server |
The server INI and, when present, *_SandboxVars.lua, spawn-points, and spawn-regions files that define how the world runs. |
| Mod and Workshop records | Fields in the server profile, including WorkshopItems and Mods |
Recreates the same Workshop items, mods, maps, and dependencies during a restore. |
| Build and branch note | Write beside the archive name or in a text file inside it | Identifies the Project Zomboid/server build used to create the backup, which matters when branches or updates change compatibility. |
These files normally live outside the Steam installation directory. Backing up the game binaries alone does not preserve the multiplayer world.
Find the active data directory
Windows desktop or dedicated server
Windows user data is commonly under %UserProfile%Zomboid. Open File Explorer, enter that path in the address bar, and look for the Saves and Server directories. The multiplayer world should be below SavesMultiplayer, with one folder for each server name.
#1 Best Overall
- 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?
Do not assume the copy inside the Steam installation is the live save. If the server was launched under a different Windows account, as a service, or by a hosting panel, the active profile may belong to that account instead.
Linux self-hosted installation
Desktop installations commonly use ~/.local/share/Zomboid. A dedicated server may instead use ~/Zomboid, depending on how it was installed and which account launches it. Check the account that owns the running server process and inspect its home directory before copying.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Docker and managed hosting
Containers and managed hosts can relocate the data directory with the Java option -Duser.home. In that case, the visible host home directory may not contain the live files. Use the provider’s file manager or inspect the container’s mounted volume, then identify the volume containing Zomboid/Saves/Multiplayer and Zomboid/Server.
A control-panel “backup” is not automatically equivalent to a self-hosted backup. Confirm that it includes the mounted world directory, the server profile, and the mod records rather than only configuration exported by the panel.
Prepare a consistent backup
Project Zomboid writes to the world while players are online. Copying during active writes can leave an archive with mismatched or incomplete files. Schedule a maintenance window and tell players when the server will be unavailable.
- Save and quiesce the server. For an automated Docker workflow, request a save through RCON first. Then stop the dedicated server or otherwise prevent further writes.
- Wait for the process to exit. Confirm that the server process and container have stopped before opening the files for copying. A panel showing “stopping” is not the same as a completed stop.
- Copy from the active data path. Use the path belonging to the account or mounted volume that actually runs the server, not a similarly named test directory.
Never overwrite the only known-good archive while creating a new one. Create a new dated directory or archive first, then leave the previous restore point untouched until the new copy has been checked.
Step-by-step backup procedure
1. Copy the multiplayer world
From the active Zomboid data directory, copy the entire Saves/Multiplayer/<server> folder. Keep its internal structure intact. The folder name identifies the server profile; changing it casually can make the server look for a different world.
Copying the complete folder is safer than selecting individual map or character files. The world contains many related files, and a partial selection may omit recent changes.
2. Copy the matching server profile
Copy the profile files in Zomboid/Server that correspond to the same server name. Include the server INI and, where used, the matching *_SandboxVars.lua, spawn-points, and spawn-regions files. These files preserve rules, sandbox settings, spawn behavior, and the profile’s relationship to the world.
If several servers share the same installation, match the profile to the world folder you copied. Do not combine a configuration from one server with another server’s world unless you intentionally want different settings and have tested the result.
3. Preserve the mod manifest
Record the values for WorkshopItems and Mods from the server profile. Also preserve map and dependency fields when they are present. The records tell a restore which Workshop content and load order the server expects.
Keeping the records is important even if the host currently has the mod files cached. A fresh machine, a rebuilt container, or a cleaned Workshop cache may need to download the same items again. The archive should make the expected mod set unambiguous.
4. Build a dated archive
Place the world folder, server profile, and mod records together in a backup directory. Use a name that identifies both the world and the creation time in UTC, for example:
rosewood-2026-10-15T121504Z
Keep the original folder hierarchy inside the archive or include a short README stating where each item belongs. Record the Project Zomboid build and branch beside the archive name or in that README. A useful entry includes the server name, UTC creation time, build, branch, and whether the point was taken before an update.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →5. Make an independent copy
Store one copy on a second physical or independently managed location: an external hard drive, external SSD, NAS, or another storage system that is not the same disk used by the server. A disk failure, accidental deletion, or filesystem problem should not destroy both the live server and its only backup.
Keep a short retention set instead of one constantly overwritten file. Daily points and a point taken immediately before a game or mod update are practical examples. Prune older archives only after a newer archive has been opened and checked.
6. Record the backup as unverified until restoration
Successful copying proves only that files were read and written. Treat the archive as a candidate backup until it has passed a restore test. Keep the source archive and the live server unchanged while performing that test.
How to restore a Project Zomboid server safely
Restore into a separate profile, directory, container, or staging host first. Testing in place risks replacing the only usable world with an archive that has a path, build, or mod problem.
- Prepare an empty staging location. Use the same operating system or host type when possible. Confirm which home directory or mounted volume the staging server will use.
- Extract the archive without flattening it. Put the multiplayer world under the staging location’s
Zomboid/Saves/Multiplayerdirectory and place the matching profile files underZomboid/Server. Preserve the server folder name. - Use the recorded build and branch. Start the staging server on the build noted with the archive. If the archive predates a major update, test it on the previous known-good build before attempting an upgrade.
- Recreate the mod set. Use the saved
WorkshopItems,Mods, map, and dependency values. Allow required Workshop content to install, then check that the server’s load list matches the archive. - Start the server and inspect the result. Confirm that it starts without generating a new world or reporting missing profile files. Check that the expected map, sandbox rules, spawn regions, and other settings are present.
- Join as a client. Connect with a test client using the expected mod list. Verify that the world opens, a character can load, and important areas such as bases, vehicles, containers, and map additions appear as expected.
- Promote only a verified restore. Stop both staging and live instances. Make a fresh backup of the current live data, then replace the live world and profile with the tested copy. Keep the previous live backup available for rollback.
If the staging test fails, do not delete the archive. Correct the path, build, or mod mismatch and test again. A restore that has not loaded successfully should not be treated as a recovery point.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Troubleshoot common restore problems
The server starts a new world
This usually indicates that the server cannot find the copied world under the profile name it is using. Stop the server and check that the folder is directly below Saves/Multiplayer, that its name matches the configured server profile, and that the staging process is using the intended home directory. On a managed host, verify the mounted volume and any -Duser.home setting.
The server starts but settings are wrong
Check that the server INI and any *_SandboxVars.lua, spawn-points, and spawn-regions files came from the same profile as the world. Copying only the world can leave the server using newly generated defaults.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsPlayers receive missing-mod or map errors
Compare the restored WorkshopItems, Mods, map, and dependency fields with the archive. Install the required Workshop items and confirm the load order. A client must also use the expected mod set; a world can load on the server while a client is rejected for a mismatch.
The archive works on one machine but not another
Check the Project Zomboid build and branch first. Then compare the operating system’s data path and the account running the server. Linux, Windows, containers, and managed hosts can place the same logical Zomboid directories in different physical locations.
A provider’s backup appears complete but cannot restore the world
Inspect what the provider actually captured. Some panels export service settings without including the mounted Saves/Multiplayer directory or the server profile. Create an independent file-level archive from the mounted data path and validate it on a staging instance.
Handle updates and branch changes deliberately
Project Zomboid builds and branches can change paths, compatibility, and mod behavior. Before a major update, create a fresh archive while the old server is still on its known-good build. Retain that previous point instead of converting it in place.
Write the build and branch beside every archive, not only in a separate spreadsheet. When a rollback is necessary, the label should tell you which server files, game version, and mod assumptions belong together.
After updating, perform another staging restore. Confirm that the world loads and a client can join before allowing players onto the upgraded live server. If the update changes mod compatibility, keep the pre-update archive as the rollback source and create a new backup after the upgraded server has been proven stable.
Quick Recap
A practical backup checklist
- The maintenance window was announced.
- The server was saved, stopped, and no process is still writing to the world.
- The entire
Saves/Multiplayer/<server>directory was copied. - The matching server INI and applicable sandbox, spawn-points, and spawn-regions files were copied.
WorkshopItems,Mods, and any map/dependency fields were preserved.- The archive name includes the server/world name and a UTC timestamp.
- The Project Zomboid build and branch are recorded with the archive.
- At least one copy is stored on an independent drive or location.
- A staging restore starts the server and allows a client to join with the expected mods.
- Older restore points are kept until a newer archive has passed that check.
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.
