Graveyard Keeper 2 Save Corrupted — How to Fix & Recover

Last verified: 2026-09-25

If Graveyard Keeper 2 crashed, soft-locked, or says your save won't load, don't overwrite anything yet. Here's the exact backup file to restore, how to roll back to your last good save, and how to keep Steam Cloud from re-breaking it.

Save file

%USERPROFILE%\AppData\LocalLow\Lazy Bear Games\Graveyard Keeper 2

Graveyard Keeper 2 writes an automatic backup next to your save: for slot 1 you'll see 1.dat (the save), 1.info (its header) and rolling backups 1.dat.backup.1, 1.dat.backup.2… Close the game, back up the whole folder, then move the broken 1.dat aside and rename the newest 1.dat.backup.1 to 1.dat — keeping the matching 1.info — to roll back to your last good save.

Where the files live: see the full Graveyard Keeper 2 save file location guide for every platform path (PS5, Xbox, Steam Cloud).

How to transfer your Graveyard Keeper 2 save to a new PC

Fully close Graveyard Keeper 2 (confirm it isn't still running in Task Manager) so nothing overwrites the files while you work.
Open the save folder: press Win+R, paste %USERPROFILE%\AppData\LocalLow\Lazy Bear Games\Graveyard Keeper 2 and press Enter.
Back up EVERYTHING first: copy the whole folder to your Desktop or a USB drive. This is your undo button — do it before any rename.
Restore the game's own backup: move the corrupt save (e.g. 1.dat) out to another folder — don't delete it — then copy the newest backup 1.dat.backup.1 and rename the copy to 1.dat.
Keep the header file: the game needs BOTH 1.dat and its matching 1.info to show the slot. If 1.info is missing, copy any other .info you have and rename it to 1.info (save-slot stats may look wrong until you save once in-game, then they correct themselves).
Roll back Steam Cloud if the local files are also bad: exit the game, disable Steam Cloud for Graveyard Keeper 2 in the client, restore your known-good folder backup, then re-enable sync so the GOOD save uploads (not the corrupt one).
Verify game files (Steam: right-click the game › Properties › Installed Files › Verify integrity) to rule out a broken install rather than a broken save.
Still stuck? Right-click the folder › Properties › Previous Versions (or Windows File History) to pull an older copy from a restore point.

Does cloud sync move it for you?

The Steam version syncs through Steam Cloud, so if the cloud copy is the corrupt one it can re-overwrite a save you just fixed. When the client shows a sync conflict, read the timestamps and keep the one matching your real last session; if you already picked wrong, restore your folder backup and disable cloud until the good save is in place.

Common mistakes

It's a Unity game, so saves live in AppData\LocalLow (not Local or Roaming) under the publisher 'Lazy Bear Games' — some guides wrongly list 'tinyBuild'.
GK2 launched Sept 22, 2026 with progression bugs that can soft-lock crafting/quest menus; there's no official corruption fix yet, so a manual folder backup before New Game+, mods or risky quests is your only guaranteed rollback.
Never edit the .dat in place — always work on a copy. If both 1.dat and its backups are gone, a save slot with only 1.info (or vice-versa) simply won't appear in the menu.

FAQ

Where does Graveyard Keeper 2 keep save backups on PC?

In the same folder as your save: %USERPROFILE%\AppData\LocalLow\Lazy Bear Games\Graveyard Keeper 2. Look for 1.dat.backup.1, 1.dat.backup.2 next to 1.dat and 1.info.

How do I fix a corrupted Graveyard Keeper 2 save?

Close the game, back up the folder, move the broken 1.dat aside, then copy the newest 1.dat.backup.1 and rename it to 1.dat (keep the matching 1.info). Launch and it loads your last good save.

Is there an official fix for the Graveyard Keeper 2 soft-lock bug?

Not as of launch (Sept 2026). The reliable workaround is rolling back to a backup save from AppData\LocalLow, so keep manual folder copies before major decisions.

Other games

Need another game or a quick backup? Use the Save Location Finder — pick any game to get its exact save path plus a ready-to-run backup command.