Project Zomboid saves a dedicated multiplayer world on the server machine, not in a separate cloud slot. The dependable way to save it is to stop the server, copy the active multiplayer world together with its matching server profile and mod records, and restart only after the copy is complete. Loading is the reverse: stop the destination server, restore the matching files under the same profile name, verify the game branch and mods, and then start the server.
Playing with friends? Godlike.Host runs hosted Project Zomboid servers from 10 data-center locations, with free DDoS protection.
The most common failed restores copy only the world folder. That can make a server start with a new map, default settings, missing spawns, or a different mod state. Treat the world, profile, WorkshopItems list, Mods list, dependencies, and a record of the working build as one restore packet.
As an Amazon Associate I earn from qualifying purchases.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallWhere Project Zomboid server saves are stored
The exact root depends on the operating system account that runs the server. On Windows, the commonly used user-data root is %UserProfile%Zomboid. On Linux, it is commonly ~/.local/share/Zomboid. A server launched under a service account or a different user can therefore have a different Zomboid directory than the one you see in your personal account.
| Item | Windows location | Linux location | What it contains |
|---|---|---|---|
| User-data root | %UserProfile%Zomboid |
~/.local/share/Zomboid |
Project Zomboid saves, server profiles and related data |
| Dedicated multiplayer world | ZomboidSavesMultiplayer<server> below the root |
Zomboid/Saves/Multiplayer/<server> below the root |
The map and multiplayer state for the named server |
| Server profile | ZomboidServer below the root |
Zomboid/Server below the root |
The server INI, SandboxVars, spawn files and other profile data |
Replace <server> with the server/profile name in use. The profile name is significant: it selects both the configuration files and the save target. If a launch configuration points at another name, Project Zomboid can create or open another world even when the old files are still present on disk.
#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.
How the profile name selects the world
Dedicated servers use a server name/profile to associate settings with a multiplayer save. The profile includes a file such as <server>.ini, while the corresponding world is under Saves/Multiplayer/<server>. A launch setup that uses the -servername parameter must use the same value that was used when the backup was made. Changing that value is not a harmless label change; it can select a different configuration and save directory.
What a complete backup must contain
A usable backup is more than a map folder. Copy these components together so that a restore reproduces the server that created the world.
- Multiplayer world: the complete
Zomboid/Saves/Multiplayer/<server>directory, including all files and subdirectories. - Active profile: the matching
<server>.ini, SandboxVars file, spawn files and any other files used by that profile underZomboid/Server. - Workshop and mod records: the exact
WorkshopItemsandModsvalues, plus the map and dependency information used by the server. - Compatibility notes: the server/profile name, game branch or build, mod versions, and the last known good join date.
- Restore evidence: a dated directory name and, ideally, the result of loading a copy under a separate test profile.
The world and profile are separate pieces. A world copied without its profile may load with different sandbox rules, spawn settings or map definitions. A profile copied without the world can point to an empty or newly generated save. Workshop and mod records are equally important because the same world can fail to load correctly when content has been removed, changed or assigned different dependencies.
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.
How to save and back up a dedicated server safely
Use a controlled file backup rather than copying files while players are connected. The order below prevents a partially written save from being treated as a valid backup.
- Announce maintenance. Tell players that the server will be unavailable and give them time to leave safely. Record the current server/profile name and the last known good join date.
- Stop the dedicated server completely. Use the normal stop action for the process or service. Do not begin copying while the game is still writing map, player or server-state files. Wait until the process has exited and the console is no longer changing.
- Locate the active user-data root. Check the account that actually runs the server, then open the corresponding Windows or Linux Zomboid directory. Do not assume the administrator’s personal profile is the service account’s profile.
- Copy the complete multiplayer save. Copy
Zomboid/Saves/Multiplayer/<server>, preserving every file and subdirectory. Keep the folder name unchanged in the backup. - Copy the matching profile. From
Zomboid/Server, copy the profile’s INI, SandboxVars, spawn files and any other files that profile uses. Include the exactWorkshopItemsandModsrecords and the map/dependency information. - Place the files in a dated directory. A useful name includes the server name, branch/build and date, for example
Riverside-branch-build-2026-10-14. The date identifies which copy to test or restore; it does not replace the need to record the actual build and mod state. - Record the state beside the files. Write down the profile name, game branch/build, mod list and versions, map dependencies and last known good join date. These notes help you distinguish a valid old world from a copy made after a failed update.
- Optionally copy the dated directory to separate storage. An external USB hard drive can hold a physical copy. Keep the backup separate from the live server so a disk failure or an accidental replacement does not remove both.
- Restart the server only after the copy is complete. Use the same profile name and launch parameters. Watch the console for startup errors and confirm that the expected world is available before declaring maintenance finished.
Why stopping first matters
Project Zomboid may write several parts of the world and server state at different times. A live copy can contain a mixture of old and new data. That mixture may look complete in a file browser but fail during loading or roll back recent changes. A clean shutdown gives every copied file a consistent point in time.
How to load or restore a saved world
Restoration replaces the current live state, so preserve the current files before changing anything. The procedure below works for a dedicated server that uses the normal Zomboid save and profile locations.
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.
- Stop the target server. Confirm that the process has fully exited before touching the destination files.
- Make a fresh safety copy. Copy the target server’s current multiplayer world and profile to a separate dated directory. This gives you a way back if the selected backup is incomplete or incompatible.
- Prepare the destination profile. Confirm the server/profile name that the target launch configuration will use. If the launch setup uses
-servername, the value must match the backup profile name for a direct restore. - Restore the world. Put the saved multiplayer directory at
Zomboid/Saves/Multiplayer/<server>on the target machine. Preserve the directory name and the complete contents. - Restore the profile files. Put the matching INI, SandboxVars, spawn files and other profile files under
Zomboid/Server. Do not substitute a profile from another world unless you intentionally want its settings. - Restore WorkshopItems and Mods records. Reproduce the same Workshop item IDs, mod entries, map definitions and dependencies. The records should describe the content expected by the saved world, not merely the content currently installed on the target.
- Verify branch, build and mod compatibility. An older backup can be affected by a game patch, a changed mod, removed Workshop content or a dependency change. Match the server branch/build and compatible mod versions before starting.
- Test under a separate profile first. For a cautious migration, load a copy of the restored files with a separate test profile. Leave the live world untouched until the test reaches the world, accepts a player connection and shows no relevant load errors.
- Inspect the console and logs. Look for errors while the server reads the profile, world, maps and mods. If the test fails, stop the server and correct the profile, path, branch or mod mismatch rather than repeatedly starting the live copy.
- Promote the tested copy. Once the test succeeds, replace the live files with the verified world and matching profile, keep the intended profile name, and start the normal server configuration.
What “successful” means
A successful restore is not just a process that reaches a running state. Confirm that the expected map and multiplayer state appear, the server uses the intended sandbox and spawn settings, the required mods are accepted, and a test player can join. A server that starts with a fresh map or default settings has usually selected a different profile or received an incomplete restore.
Moving a hosted world to a dedicated server
The same file relationship applies when moving from in-game hosting or a managed host to a self-managed dedicated server. The host-specific download or panel controls vary, but the destination must receive the same restore packet.
Collect the source files
Stop the source session or server before exporting. Obtain the complete Saves/Multiplayer/<server> directory and the profile files under Server. If a hosting panel exposes separate downloads for saves and configuration, download both. Also record the exact WorkshopItems, Mods, map dependencies, branch/build and profile name.
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.
Prepare the dedicated server
Install or select the same game branch/build used by the source. Start the dedicated server once, if necessary, so its Zomboid directories exist, then stop it. Do not let an automatically generated profile become the replacement for the source profile; use the source name and files.
Free tools Windows power users keep installed
One-click scans. No signup required.
Copy and test
- Copy the source multiplayer world into the dedicated server’s
Zomboid/Saves/Multiplayer/<server>path. - Copy the matching INI, SandboxVars, spawn and related profile files into
Zomboid/Server. - Reproduce the WorkshopItems and Mods records and install compatible content.
- Configure the launch profile to use the same server name, including the
-servernamevalue when present. - Start a test profile or otherwise test the restored copy before directing players to the new endpoint.
Only after the test succeeds should the dedicated server become the primary instance. Keep the original host files and the pre-migration copy until players have confirmed that their expected world and characters are present.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Why a restored server opens a new or empty world
An empty world is usually evidence that the server selected a different target or could not use the intended files. Check the causes in this order.
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)
| Symptom | Likely cause | Correction |
|---|---|---|
| A brand-new map appears | The launch profile name does not match the restored folder, or -servername points elsewhere. |
Use the original profile name and confirm the world is under Saves/Multiplayer/<server>. |
| World loads but settings are wrong | The multiplayer folder was restored without its matching INI, SandboxVars or spawn files. | Restore the complete profile under Zomboid/Server. |
| Map or players fail to load after an update | The branch/build or mod content differs from the backup. | Match the game branch/build and compatible Workshop, mod and dependency records. |
| Server starts but required areas are missing | Map definitions or dependencies were not copied with the mod records. | Restore the source map/dependency information and verify the required content is available. |
| Recent progress is absent | The backup was made while the server was running or an older dated copy was selected. | Use a backup made after a clean shutdown and compare its recorded last known good join date. |
| Startup reports load errors | Files are incomplete, incompatible or assigned to the wrong profile. | Stop the server, preserve the failed attempt, inspect logs, and retry with a verified restore packet under a test profile. |
Do not fix an empty world by deleting files at random
Deleting the newly generated directory can destroy useful evidence and make it harder to determine which profile was selected. First stop the server and copy the current state. Then compare the active profile name, path and configuration with the dated backup. Restore deliberately, not by trial-and-error file removal.
Testing and maintaining backups
A backup is trustworthy only when its contents and compatibility are known. Use this checklist whenever you create or validate one:
- The server was stopped before copying.
- The complete multiplayer world folder is present.
- The matching INI, SandboxVars, spawn and related profile files are present.
- WorkshopItems, Mods, map definitions and dependencies are recorded.
- The profile/server name is written down exactly.
- The game branch/build and mod versions are recorded.
- The copy is in a dated directory separate from the live files.
- A restore was tested under a separate profile, or the reason a test was not possible is documented.
- The console and logs showed no unresolved load errors during the test.
Keep the original backup unchanged after a successful test. If you need to edit configuration for a new server, make a working copy and leave the known-good restore packet intact. This preserves a clear rollback point when a later patch or mod update changes compatibility.
Choosing a hosting arrangement for save and load control
The file workflow differs mainly in who can access and reproduce the files. Exact panel procedures vary by managed provider, but these are the practical trade-offs.
| Arrangement | Must the host machine be online? | Who controls save/profile files? | Backup and restore approach | Reproducing the same profile and mods |
|---|---|---|---|---|
| In-game hosting | Yes; the host session must be running for others to connect. | The player operating the host machine. | Stop hosting, copy the world and matching profile, and keep dated copies. | Usually straightforward on the same machine, but the host must preserve the profile and mod records. |
| Self-managed dedicated server | Yes, but it can run unattended on a separate machine while that machine is available. | The server administrator. | Use the controlled stop-and-copy procedure and test restores under a separate profile. | High control: the administrator can preserve the exact name, branch/build and mod records. |
| Managed hosting | The provider’s server normally remains online according to its service configuration. | Access depends on the provider’s file tools or export options. | Use the provider’s download/upload tools, while still preserving the complete world, profile and mod records. | Depends on whether the panel exposes all configuration and supports the same branch and mods. |
Regardless of arrangement, ownership of a backup means having the files outside the running instance and knowing which profile, branch and mod state they require. A provider-side snapshot that cannot be downloaded or matched to its configuration is not a complete migration resource.
Quick reference: save, move or restore
To create a backup
- Announce maintenance.
- Stop the server completely.
- Copy
Saves/Multiplayer/<server>. - Copy the matching
Serverprofile files. - Preserve WorkshopItems, Mods, map/dependency data and compatibility notes.
- Store the packet in a dated directory and optionally on separate physical storage.
- Restart with the same profile and inspect startup output.
To restore a backup
- Stop the target server and make a safety copy of its current files.
- Restore the world under
Saves/Multiplayer/<server>. - Restore the matching profile under
Server. - Use the same server name and
-servernamevalue when applicable. - Match branch/build, WorkshopItems, Mods, maps and dependencies.
- Test under a separate profile.
- Inspect logs, then promote the tested files to the live profile.
Final decision rule
If you remember only one rule, keep the multiplayer world and its matching server profile together, and never copy or replace them while the server is running. Stable naming, preserved WorkshopItems and Mods records, compatible branch/build versions and a separate restore test are what turn a folder copy into a recoverable Project Zomboid server.
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.
