Web Analytics Made Easy - Statcounter
Server Tools

Project Zomboid: World Recovery

A save that will not load is usually one broken cell file, not a dead world. This finds the damaged files you can safely delete, and checks which of your backups is actually complete.

Everything runs in your browser. It reads names, sizes and modified times, and for backup zips only the archive index. Your save is never uploaded and never modified by this page.

1. Point it at your save folder

Windows: %USERPROFILE%\Zomboid\Saves\<Mode>\<SaveName>. Linux: ~/Zomboid/Saves/<Mode>/<SaveName>. On a dedicated server it is the same layout under the account running it. Stop the server or close the game first so nothing is mid-write.

Want this on a real server? Supercraft hosts Project Zomboid →

How a PZ save is put together, and how it breaks

A Project Zomboid world is not a single save file. It is a folder of many small files, and that is the good news when something goes wrong:

  • Cell files - map_x_y.bin, chunkdata_x_y.bin and zpop_x_y.bin each hold one square of the map. Damage is usually confined to one or two of them, typically the area you were standing in when the game or server died.
  • Shared files - players.db holds your characters, vehicles.db the cars, and map_t.bin / map_meta.bin / map_sand.bin the global state and sandbox settings. Damage here affects the whole save, so this is the case where you restore a backup.

The classic failure signature is a zero-byte or stub-sized file: the game was killed mid-write, or the folder was copied while the server was running. That is exactly what this page looks for, because those files are both easy to spot and safe to remove.

Server logs pointing at a specific error instead? Use the log analyzer. Rebuilding sandbox settings is the settings generator. Want it hosted with backups taken for you? Run a Project Zomboid server with Supercraft.

Manual recovery (no JavaScript needed)

  1. Stop the server or close the game. Nothing below is safe while it is writing.
  2. Copy the whole save folder somewhere else first. Every step after this is reversible only if you did this one.
  3. Sort the folder by size and look for .bin files at 0 bytes or a few dozen bytes. Those are your damaged cells.
  4. Delete only those files. Start the game; it regenerates those cells. Anything you built in that specific area is gone, everything else is not.
  5. If players.db or a map_*.bin shared file is the empty one, do not bother with cells: restore the newest complete zip from Zomboid/backups instead, keeping your current folder aside.
  6. Load in, verify your character and a couple of bases, and only then delete the copy you made in step 2.

FAQ

Will deleting a cell file wipe my character?

No. Characters live in players.db, which is a separate file. Removing a cell file affects that square of the map only, so you keep your character, skills and everything you built elsewhere.

My world loads but crashes when I walk to one area.

That is the textbook single-corrupt-cell symptom. The cell for that area is damaged in a way that does not show up as a zero byte count, so this page may report the folder as clean. Note roughly where it happens, and delete that cell file, or restore just that file from a backup.

There is nothing in my backups folder.

Automatic backups are a game option and can be turned off, and they are only written on certain events. If it is empty, this is the moment to turn them on for next time, and to check whether your host takes its own snapshots.

Is my save really not uploaded?

Really. There is no upload endpoint on this page. File inspection and zip index reading both happen locally in your browser.

This tool: v1.2 · updated 26 Jul 2026