Build 42 reference · Not current-build play-tested
Paths are cross-checked against a current Build 42.19 community save guide, an independent save-format reference, and a Build 42 Steam discussion. The official site currently lists Stable 42.20.4; custom installs, Steam Deck/Proton, and dedicated servers can use different roots. This page has not been tested against the user’s machine.
Start in Zomboid/Saves, not the Steam install
Close Project Zomboid before inspecting or copying anything. A normal user save is under the profile’s Zomboid/Saves folder, not under steamapps/common/ProjectZomboid.
- Windows: open File Explorer and paste
%UserProfile%\Zomboid\Savesinto the address bar. - macOS: in Finder choose Go → Go to Folder… and enter
~/Zomboid/Saves. - Linux: open the file manager’s location field and enter
~/Zomboid/Saves.
The tilde means your current home folder. It is not the game’s installation directory.
Match the mode and world shown by Load Game
ZomboidSaves<mode><world>The usual shape is Zomboid/Saves/<game mode>/<world folder>. The middle folder may be named Sandbox, Apocalypse, or another mode named by your client. A locally hosted multiplayer world can use a multiplayer mode folder.
- Open Load in the game and note the world name and mode.
- In
Saves, open the matching mode folder and compare the candidate world folder names. - If several folders look date-like, use the world you recognise and its modification time as clues; do not rename files just to make one appear.
A typical world folder contains multiple map and metadata files. Do not pick a single .bin file as “the save”; the world is the folder and its contents together.
If the normal path is empty
First check that the game has been launched under the same operating-system user and branch that created the world. Custom launch options, a portable install, and compatibility layers can change where user data is written.
- Search the user’s storage for a folder named
Zomboid. - Prefer the candidate that contains both
Savesand the game’s other user-data files, such asconsole.txt. - Do not merge two candidate folders. Record which branch and launcher produced each one, then use Load to identify the live world.
Steam Deck/Proton is not the same as native Linux: use its compatibility-data location only after checking the device’s own setup. This guide does not invent a universal Deck path.
A remote server save is not your client save
For solo and local hosted co-op, the host machine’s user-data folder is the useful starting point. For a remote multiplayer server, the authoritative world belongs to the host or server administrator; a client’s local folder is not a complete server backup.
Ask the host which build, save name, and backup policy the server uses. Dedicated-server paths depend on the host’s install and cache configuration, so this page intentionally does not prescribe a server restore path. Do not upload a client folder and assume it can replace the live server world.
Locate first, copy second
Before editing anything, note the displayed Build 42 version, the game mode, the world name, and whether mods are enabled. The developer recommends backing up existing saves before version changes because unstable-build conversions can have issues.
Once the correct folder is identified, continue to Back up a save safely ↗. This page only locates the data; it does not convert Build 41 and Build 42 worlds, repair corruption, or restore a dead character.
Sources & version notes
Research-based; not independently play-tested on 42.20.4. Core advice cross-checked against the references below.
- PZFans: Build 42.19 save paths and mode/world folder shape ↗
- GitHub pz-save-manager: independent save-format research and Windows/macOS/Linux paths ↗
- Steam Build 42 discussion: Windows save path confirmed by the accepted reply ↗
- The Indie Stone forum: Windows and macOS backup locations ↗
- The Indie Stone: Build 42.20 game modes and current client naming ↗
- The Indie Stone: backup before unstable-build save conversion ↗