A Zomboid world is a directory tree. Copy the entire selected save folder plus a record of the game build and mod list before updating a server/world or moving it to another machine.
Start with the least destructive explanation
When Project Zomboid progress appears missing, first verify the active PC location: Windows: %USERPROFILE%ZomboidSaves. Expected files/folders: mode/world folders containing map data, player data, and world database files. Many apparent save failures are actually profile, storefront, path-redirection, or cloud-selection problems rather than damaged game data.
Preserve every surviving copy
Close Project Zomboid, let the launcher finish any synchronization, then copy the complete documented save directory to a dated folder outside the live path. Preserve companion files rather than selecting only the newest-looking record. Before renaming, moving, replacing, or opening candidate backups, copy them outside the live directory. Do not use the only surviving file as the test specimen for repair or editing.
Check launcher and cloud state
Storefront context: Steam, GOG. The active Steam, GOG installation determines which local profile and cloud copy can overwrite the save. Identify the storefront and account before restoring files. Cloud notes: Steam Workshop/mod state is separate from the local world folder; cloud is not a substitute for a complete manual world backup. A sync client can reintroduce an older or newer version after a manual restore, so recovery work should keep local and cloud copies conceptually separate until the wanted progress is confirmed.
Use format and compatibility clues
Project Zomboid saves are directories containing many world/player files rather than one portable save. Mods and game build can materially affect world compatibility. Treat saves as version-, storefront-, account-, and mod-sensitive unless the game or a separately verified migration workflow proves otherwise. A similar filename or extension is not evidence that two releases are interchangeable. If the file exists but is ignored, compare the complete directory structure, slot/profile naming, game edition, mods/DLC, and any companion metadata. Do not assume an extension change or generic checksum tool can repair a game-specific container.
Game-specific troubleshooting
If progress is missing after a restore, confirm the active Windows account, storefront/profile, cloud state, and exact directory first. Restore the untouched backup before experimenting with individual files or older autosaves. If a known-good backup works, preserve it and create a fresh in-game save before further experiments. If no copy works, prefer read-only inspection and source-backed game-specific tooling over repeated writes.
Verification context: Windows save location, file-boundary, launcher/cloud, and backup notes were reviewed against the linked game-specific references for Project Zomboid. This Game Hub is documentation only and does not claim a new game-specific Save Editor.
Recorded Phase 40 evidence boundary
This Phase 40 entry is grounded in the researched PC save boundary for Project Zomboid: Windows: %USERPROFILE%ZomboidSaves The recorded file or folder pattern is mode/world folders containing map data, player data, and world database files. These concrete identifiers are retained so backup, transfer, recovery, and editing preparation remain tied to the documented game/storefront context instead of a generic extension guess.