Palworld's Level.sav only gets bigger as your world ages, and a crash or a bad shutdown mid-save is one of the most commonly reported ways it ends up corrupted. Checkpoint64 backs up the whole world folder automatically and keeps every version, so a bad save means restoring the last healthy one, not starting over.
Where Palworld saves live
%LOCALAPPDATA%\Pal\Saved\SaveGamesInside that folder, saves nest under your Steam ID and then the world itself. Level.sav holds the world — bases, Pals, everything you've built — plus LevelMeta.sav and WorldOption.sav for settings, and a .sav per player under Players. Worlds usually carry a .png thumbnail too, which is why Palworld's preset backs up both .sav and .png files. Palworld writes only to Windows in the app's game catalog, so this folder is the whole picture.
Why big worlds get slow — and more crash-prone
Level.sav just keeps growing the longer a world runs: more bases, more Pals, more of the map explored. It's well documented in the community that an old, large world takes noticeably longer to save and load, and can crash outright on weaker hardware or a dedicated server running short on memory. That doesn't make the save file smaller, but it does mean the odds of a bad save climb the longer a world lives — exactly when a recent backup matters most.
Surviving a crash or a bad shutdown
Palworld — or a dedicated server running it — crashing, losing power, or getting force-closed mid-save is one of the most commonly reported ways Level.sav ends up unreadable; the write just never finishes. Checkpoint64 keeps every version it backed up, so recovering from a bad shutdown means restoring the last healthy version from before the crash, not losing the world.
Sharing one world without a rented server
Palworld has exactly one live world file at a time, same as Valheim or Factorio — whoever's hosting holds the only copy, and a rented dedicated server is the usual answer for keeping it online without leaving one PC running. Checkpoint64 covers most of the same need for a small group with version history plus a lock, so only one person saves over the world at a time. The dedicated server alternative guide covers the trade-off in depth.
How Checkpoint64 backs up Palworld
- Pick Palworld. The SaveGames path is already known.
- Turn on auto-backup. Every 30 seconds it checks for a changed world and uploads a new version, sending only what changed.
- Restore in one click. Open Versions, pick a healthy version from before the crash, and Restore.