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
Playing with friends? Godlike.Host runs hosted Project Zomboid servers from 10 data-center locations, with free DDoS protection.
Project Zomboid dedicated servers save their multiplayer world on the server computer. The dependable way to save one is to stop the server, copy the complete active world folder together with its matching server profile and mod records, and store that packet in a dated backup directory. Loading is the reverse: stop the target server, restore the matching files, keep the same server/profile name, confirm the same game branch and compatible mods, then start and test the server.
What “saving” means on a dedicated server
A dedicated server does not produce a single portable save file. The playable world and the instructions that define how the server starts are stored in separate locations. A usable backup therefore has to preserve both pieces.
- World data: the multiplayer map, characters, containers, discovered areas and other persistent server state.
- Server profile: the INI settings, sandbox rules, spawn settings and the profile name that tells Project Zomboid which world to open.
- Content records: the Workshop item IDs, mod list and map/dependency information required to interpret the world.
Copying only the world can leave you with missing settings or an apparently new map. Copying only the INI files does not preserve the world. Treat the world, profile and content records as one restore packet.
Where Project Zomboid server saves are stored
The exact root depends on the operating system and the account running the server. The common locations are:
#1 Best Overall
- Easily store and access 5TB of content on the go with the Seagate portable drive, a USB external hard Drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
| System | Common user-data root | Multiplayer world | Server profile files |
|---|---|---|---|
| Windows | %UserProfile%Zomboid |
%UserProfile%ZomboidSavesMultiplayer<server> |
%UserProfile%ZomboidServer |
| Linux | ~/.local/share/Zomboid |
~/.local/share/Zomboid/Saves/Multiplayer/<server> |
~/.local/share/Zomboid/Server |
Replace <server> with the profile name used by the server. In the profile directory, the important files normally include <server>.ini, the matching SandboxVars file and spawn files. Other files may be required by that profile, so copy the complete active profile rather than selecting one file by guesswork.
The profile name is significant. A launch setting such as -servername <server> selects the server profile and its save target. If the name changes during a move, Project Zomboid can read a different configuration or create a different save location, which looks like a lost or freshly generated world.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Rank #2
- Easily store and access 1TB to content on the go with the Seagate Portable Drive, a USB external hard drive.Specific uses: Personal
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop. Reformatting may be required for Mac
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Prepare the server for a safe backup
Do not copy a live world while the server is writing to it. A backup made during a save operation can contain files from different moments and may not restore cleanly.
- Tell players when maintenance will begin and ask them to leave the server.
- Record the server/profile name exactly, including capitalization where your hosting setup preserves it.
- Record the game branch or build, the active Workshop items, the Mods value and any map dependencies.
- Note the last known good join date so you can identify the correct backup later.
- Choose a destination with enough space. A dated directory on another disk, including an external USB hard drive, keeps a copy separate from the live files.
How to back up a Project Zomboid dedicated server
- Announce the maintenance window. Give players time to log out normally and make clear that the server will be unavailable while the files are copied.
- Stop the dedicated server completely. Use the service, launcher or hosting control that starts the server, and wait until its process and console have closed. Do not rely on merely closing a game window while a server process remains active.
- Copy the complete multiplayer save. Copy
Zomboid/Saves/Multiplayer/<server>from the account that runs the server. Preserve the folder structure and every file inside the active server directory. - Copy the matching profile. From
Zomboid/Server, copy<server>.ini, the corresponding SandboxVars file, spawn files and any other files used by that profile. If several profiles exist, use the one named by the server’s launch configuration. - Preserve content records. Keep the exact
WorkshopItemsandModsentries, plus map and dependency information. These records tell the restored server which content the world expects. - Put the packet in a dated directory. A name such as
pz-server-2026-10-14-last-goodmakes the capture date and purpose visible. Do not overwrite an older known-good copy until the new copy has been checked. - Write a short restore note. Include the profile name, branch/build, mod list, last known good join date and the backup destination. This prevents uncertainty months later when several copies exist.
The result should contain the world folder and the profile/configuration data that was active at the same time. If you cannot identify which profile was active, stop and resolve that before deleting or replacing anything.
Rank #3
- Easily store and access 4TB of content on the go with the Seagate Portable Drive, a USB external hard drive.Specific uses: Personal
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
How to load or restore a saved world
- Stop the target server. A restore must never replace files while the server is running.
- Create a safety copy of the current live files. Copy the current multiplayer folder and profile to a separate, dated directory before making changes. This gives you a way back if the selected backup is wrong.
- Restore the world folder. Place the saved world at the target’s
Zomboid/Saves/Multiplayer/<server>path. Keep the directory name identical to the profile name the target server will use. - Restore the profile files. Put the saved
<server>.ini, SandboxVars, spawn files and other profile files under the target’sZomboid/Serverdirectory. - Use the same profile name. Keep the launch setting and file names aligned. If the target uses a different name, change it back or deliberately migrate every reference; otherwise the server may select another save target or generate a new one.
- Restore the content records. Set
WorkshopItems,Mods, map entries and dependencies to the values used when the backup was made. - Check branch and versions. Confirm that the target is running the same game branch/build, and that required mods are present and compatible. A patch, removed mod or changed mod content can prevent an older world from loading correctly.
- Start and inspect the server. Read the console and logs for missing files, mod errors, map errors or profile-selection messages. Have an administrator join and check a familiar location, character state and a few persistent containers before announcing the restore complete.
For a cautious migration, restore the packet under a separate test profile first. Only replace the live profile after the test starts without errors and the world is demonstrably the expected one.
Moving a hosted world to a self-managed dedicated server
The same file relationship applies when changing machines or hosting arrangements. First obtain a complete backup from the existing host: the multiplayer save, the active profile and the exact Workshop and Mods records. A download of only a world directory is not enough if the host’s settings and mod list are not captured.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #4
- 【Upgraded version】 - The mirror logo strip is combined with the striped non-slip design. The rounded corners of the shell are more suitable for holding. The strips play a heat dissipation function to ensure a stable and fast transmission process.
- 【Ultra-thin and quiet】 - The motherboard adopts JMicron 578 noise-free solution, giving you a quiet working environment. Lightweight and portable size designed to fit in your pocket for easy portability.
- 【Ultra-Fast Data Transfers】 - Pairing this external hard drive with JMicron 578 solution USB 3.0 and USB 2.0 interfaces enables blazing-fast data transfer. It boasts theoretical read speeds of up to 125MB/s and write speeds of up to 103MB/s.
- 【Plug and Play】 - With no software to install, just plug it in and the drive is ready to use.The hard disk chip is wrapped with an aluminum anti-interference layer to increase heat dissipation and protect data.
- 【What You Get】 - 1 x Portable Hard Drive, 1 x USB 3.0 Cable, 1 x User Manual, Gift-type shell packaging ,Three-year manufacturer's warranty and free technical support services.
- Stop the hosted instance and create a dated export.
- Install or prepare the dedicated server on the destination machine using the same branch/build.
- Stop the new instance before copying files into it.
- Place the world under
Saves/Multiplayer/<server>and the profile underServer. - Configure the destination to use the identical profile name, including its
-servernamevalue if that parameter is used. - Reproduce the Workshop items, Mods list, maps and dependencies from the export rather than rebuilding the list from memory.
- Start under a test profile or isolated test copy, inspect logs and join the world.
- After the test succeeds, schedule the cutover and replace the live destination files with the verified packet.
Provider control panels differ in how they expose file managers, profiles and backups. The file locations and profile relationship above are the portable part; panel-specific buttons and paths must be checked against the provider’s documentation.
What must stay together in a restore packet
| Component | Why it matters | What to verify |
|---|---|---|
Zomboid/Saves/Multiplayer/<server> |
Contains the persistent multiplayer world and state. | Folder name and contents match the intended profile and backup date. |
| Active server profile | Defines server settings, sandbox rules and spawn behavior. | <server>.ini, SandboxVars, spawn files and other files used by that profile are present. |
WorkshopItems and Mods |
Tell the server which mod and Workshop content the world expects. | Entries and dependencies match the known-good state. |
| Branch/build record | Determines whether the executable can interpret the saved data and mod content. | Target branch/build is compatible with the backup. |
| Backup note and test result | Identifies the correct copy and proves it was usable. | Profile name, date, last good join and test outcome are recorded. |
Why a restored server opens a new or empty world
| Symptom | Likely cause | Fix |
|---|---|---|
| A completely fresh map appears. | The server is using a different profile or save-folder name. | Compare the launch profile, -servername value and folder name. Restore the world under the exact active name. |
| Settings look default even though the world is present. | The world was copied without its matching INI, SandboxVars or spawn files. | Restore the complete profile from the same backup date. |
| Players or areas fail to load after a move. | Workshop items, Mods, map dependencies or mod versions do not match. | Restore the recorded content lists and install compatible versions before testing again. |
| The server reports load or map errors. | The target branch/build differs, or content was removed or changed after the backup. | Use the compatible branch/build and reproduce the required mod and map set; review the console and logs for the first reported error. |
| The restored files appear incomplete or inconsistent. | The backup was copied while the server was still running. | Discard that capture and restore from a backup made after a complete shutdown. |
| The right files exist but are ignored. | The server process runs under another operating-system account and therefore reads another user-data root. | Check which account launches the service and place the files in that account’s Zomboid directory. |
Always investigate the first relevant console or log error rather than repeatedly replacing files. Repeated restores can hide whether the problem is the path, profile selection, content set or game build.
Best Value
- High capacity in a small enclosure – The small, lightweight design offers up to 6TB* capacity, making WD Elements portable hard drives the ideal companion for consumers on the go.
- Plug-and-play expandability
- Vast capacities up to 6TB[1] to store your photos, videos, music, important documents and more
- SuperSpeed USB 3.2 Gen 1 (5Gbps)
Game branch and mod compatibility checks
An older world is not independent of the executable and content that created it. Before loading a backup, compare:
- Stable or test branch selection and the exact build on the source and target machines.
- Every Workshop item ID recorded in the backup.
- The
Modsorder and names used by the profile. - Map packages and their dependencies.
- Whether any required mod was removed, renamed or substantially changed.
If compatibility is uncertain, preserve the live server, restore to a separate test profile and use the test logs to identify the first incompatibility. Do not overwrite the only known-good world while experimenting.
Choosing a hosting approach for save control
| Approach | Must the host machine stay online? | Who controls files? | Backup and restore workflow | Reproducing a profile and mod list |
|---|---|---|---|---|
| In-game hosting | Usually yes; the host’s game session provides the server. | The player operating that machine. | Depends on the host machine’s local files and shutdown process. | Convenient for a small group, but tied to that host’s setup. |
| Self-managed dedicated server | Yes, but it can run unattended as a server process. | The administrator has direct access to the Zomboid save and Server directories. | Use the controlled stop, copy, dated-directory and restore procedure in this guide. | High control: preserve the profile name, branch/build and content records directly. |
| Managed hosting | The provider normally keeps the service online. | Access depends on the provider’s panel and file tools. | Exact backup and restore buttons, paths and retention vary by provider. | Ask how the provider exports the profile, save folder, WorkshopItems and Mods records before committing to a migration. |
For a move between approaches, the most important question is not the label of the hosting model but whether you can obtain and restore the complete packet: world, profile, content records and build information.
A repeatable backup and restore checklist
Before copying
- Players have been notified.
- The server process is fully stopped.
- The active profile name and launch setting are recorded.
- Branch/build, WorkshopItems, Mods, maps and dependencies are recorded.
During the backup
- The entire multiplayer folder is copied.
- The matching Server profile is copied.
- The copy is placed in a dated directory separate from live files.
- The last known good join date and destination are written down.
Before declaring a restore successful
- The target is using the same profile name and compatible branch/build.
- Workshop and mod records match the backup.
- The console and logs show no unresolved load errors.
- An administrator can join and verify a known character, location or persistent container.
- The verified copy has been tested before the live world is replaced.
Key points
Stop the server before every copy or replacement. Back up the multiplayer world and its matching profile together, preserve the WorkshopItems and Mods records, keep the server/profile name stable, and verify branch and mod compatibility. When restoring or migrating, test the packet under a separate profile before putting it into production; this catches wrong paths, wrong profiles and incompatible content without sacrificing the current live world.
Quick Recap
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.
