How to Back Up Save Data: Steam, Xbox, and Servers

A corrupted world file takes everything with it — the bases, the breeding lines, the Pals you spent a week perfecting — and Palworld's own safety net is quieter than most people realise. This guide covers where your save actually lives on Steam and on Xbox, how the built-in backup rotation and the auto-save timer work, how to restore an older copy without losing more than you meant to, and the server settings that decide whether a backup is being written at all.

What Palworld Actually Saves

Your "save" is not one file. Palworld writes four separate streams every time it saves, and knowing which is which explains a lot of the odd behaviour players report — like restoring an old copy and finding the world rolled back but your character's inventory didn't, or moving a save to a new PC and discovering the Global Palbox came along independently. The split that matters most is world versus local: the world holds the map, your bases and everything built on it, while local holds your character. The game's own backup folder is divided along exactly that line, so a backup entry is really a pair.

If you take one instruction from this whole page, take this one: when you copy anything by hand, copy the entire user folder, not one world inside it. It costs you a few hundred megabytes of disk and it removes every chance of pairing a world with the wrong character data later. The per-stream detail above is for diagnosing a restore that went sideways, not for cherry-picking files during a backup.

The Built-In Backup System

Palworld keeps its own rotating backups without being asked, which is why a lot of players never find out they exist until something breaks. Saves fire on a timer — the default is every 30 seconds — and the game keeps a set of older copies alongside the live world. The set is thinned as entries age, so the list you see is dense near the present and gets sparser the further back you scroll; it is a rolling window, not an archive, and it will eventually eat the copy you wanted. That is the whole reason a manual copy is still worth taking before anything risky.

In the world select menu, backups are listed with the timestamp plus the world's name, your level and the in-game day, which is usually enough to identify the right one at a glance. Level and day are the useful columns: the clock time tells you when you played, but "day 214, level 51" tells you what you are actually rolling back to.

How to Restore from Backup Data

Restoring is a menu action, not a file operation, and it is the fastest fix when a world stops loading or you want to undo something catastrophic. The catch is that it overwrites the live save with the copy you picked — everything you did after that timestamp is gone the moment you confirm. Newer backup entries usually survive the swap, so it is often recoverable if you pick wrong, but not once the auto-save timer has cycled through the list a few times.

How to Change the Auto-Save Interval

The auto-save timer is a world setting, so you can raise it from the default 30 seconds up to tens of minutes. There is a real reason to: a sprawling world with a lot of built structures takes longer to write, and on a modest machine that shows up as a rhythmic hitch every half minute. Raising the span smooths that out. The cost is exactly proportional — set it to 10 minutes and a crash can take 10 minutes of play with it, along with anything you caught or crafted in that window.

Most single-player runs are better off leaving it at 30 seconds and living with the hitch, because the failure it protects against is a hard crash and those never happen at a convenient moment. If you do raise it, raise it modestly — a couple of minutes is enough to change how the game feels on a big base without turning a crash into a lost evening. On a dedicated server the same value lives in the config file as `AutoSaveSpan=30.000000`, and the same trade-off applies with more players to annoy.

How to Back Up a Steam Save on PC

The manual copy is the only backup that survives things the in-game system cannot help with — a failing drive, a bad game update, a save that gets overwritten by newer auto-saves before you notice it broke. Palworld makes this easier than most survival games by putting a shortcut to the folder right in the world select screen, so you do not have to know the path by heart.

`AppData` is hidden by default, so typing `%localappdata%` into the address bar of a File Explorer window is faster than trying to click your way there. Do the copy with Palworld fully closed — not paused, not alt-tabbed. Copying files while the auto-save timer is mid-write is one of the few ways to produce a backup that looks fine and refuses to load.

How to Back Up an Xbox or Game Pass Save

The Game Pass version leans on cloud saves, and for most players that is the backup — if the local files and the cloud copy disagree, the game offers to pull the cloud version down, which quietly covers the reinstall and new-PC cases. What it does not cover is rolling back a bad session, because the cloud copy is simply your latest state, not a history. For that you need a local copy, and the folder layout is less friendly than Steam's.

Restoring is the same move in reverse with the game closed, and it is worth understanding the risk before you do it: because the cloud copy is authoritative, dropping older files in can result in the cloud version winning on next launch and undoing the restore. If you are deliberately rolling back on Game Pass, keep a copy of the current `wgs` folder too, so a failed rollback still leaves you where you started rather than somewhere worse.

How to Back Up a Dedicated Server World

Server worlds are the easiest to back up and the most expensive to lose, because they carry a whole group's progress rather than one player's. Two config values decide what the server does on its own, and both sit in the same settings file as the rest of your world options — on Windows that is `Pal\Saved\Config\WindowsServer\PalWorldSettings.ini`, and on Linux the `LinuxServer` folder in the same place. The full stop-copy-update procedure is in our Palworld server update guide, which is the moment you are most likely to need this.

The single-file answer for a server is to stop the process, wait for it to genuinely exit, and copy the whole `Pal\Saved\` directory off the machine. That one folder holds the world, the rotating backups, the config file and every player character, so a restore never turns into a hunt for which piece you forgot. Keeping it on the same box as the server does not count as a backup — the failure you are insuring against usually takes the whole machine.

What Can Still Eat Your Progress

Not every way to lose a world looks like corruption. Several of them are settings behaving exactly as configured, and they hit multiplayer groups far more often than they hit solo players — which is unfortunate, because those are the worlds with the most hours in them. The table below is the short list of things worth checking on any server you care about, along with what a backup does and does not do about each.

When to Take a Manual Backup

The in-game rotation handles crashes on its own, so a manual copy is not something you need nightly. It is worth the two minutes at the specific moments where the thing about to go wrong is bigger than a crash — anything that rewrites files, anything you cannot undo in-game, and anything that involves someone else's server. In practice that is a short list, and every entry on it gives you advance warning.

One more habit worth building: keep two copies, not one. A backup taken this morning and a backup taken last month cover completely different accidents, and the second one costs nothing but disk space. The failure that ruins a run is rarely the one you noticed the same day — it is the corruption or the missing base you find a week later, by which point today's copy has the same problem baked in.

Related Guides