Nothing feels worse than losing hours of progress because you didn’t know how saving actually worked. It’s worse when you have caught a pal, and you lose it because of a glitch. When I first started playing Palworld, I was dumbfounded about saving too. And I have noticed this to be a common question on the game forums and threads. If you are not sure if the game has a manual save button or if your progress is saved in the background, this guide will help you a lot. So, let’s look at exactly how saving works, plus the backup habits that’ll actually protect you when things go wrong.
Note: Most of the information in this guide is based on my gameplay experience of the Early Access version. But, I will be updating this guide soon when I have played the full release enough to know better.
Does Palworld Auto-Save?
Yes, and this is the most important thing to know upfront. Palworld automatically saves your progress when you return to the title screen. So if you’re playing solo and just want to stop for the day, simply backing out to the main menu triggers a save behind the scenes. You don’t need to hunt for a manual save option buried in a menu somewhere; exiting properly to the title screen handles it for you.
Now, you might think, why am I contradicting myself in the intro? Well, that’s because relying purely on this single auto-save trigger isn’t the best option, especially once you start caring about protecting hours of base-building and Pal breeding work. Let’s get into the more advanced saving options.
How To Manually Save If You’re Running A Dedicated Server
If you’ve moved past solo play and you’re running your own dedicated server, either self-hosted or through a managed provider, saving works differently and actually gives you more direct control.
First, you’ll need admin privileges. Once you’re logged into your server, press Enter to open the chat box and type:
/AdminPassword YOURPASSWORD
You should get a confirmation message that you’re now an admin. From there, you can trigger a manual save at any time by typing:
/Save
This immediately writes your world state to disk rather than waiting for anyone to return to the title screen. This is especially useful if you’re about to attempt something risky, a big base rebuild, an experimental breeding session, or heading into a tough boss fight, and want a safety checkpoint before things potentially go wrong.
When you’re ready to properly shut the server down, don’t just close the command window. Instead, save first with /Save, then close things down cleanly with:
/DoExit
Closing the server window directly without doing this risks losing progress, since the game may not have finished writing everything to disk yet.
Why is manual saving better than auto-save?
While the game has auto-save, it is not the most reliable feature (About Early Access, I have not played version 1.0 enough to comment about it right now). Palworld has a documented history of save corruption. This is particularly tied to unexpected shutdowns like crashes, power loss, or force-closing the game. This isn’t some rare edge case either; entire Steam community threads exist specifically about lost saves, with titles as blunt as “my save is gone.”
Because of this, getting into the habit of manual saves before ending a session, rather than just trusting the title-screen auto-save alone, gives you a meaningful extra layer of protection. You can think of it less as a “just in case” step and more as standard practice if you’ve put real hours into your Pals and base. I just hope this issue doesn’t happen in the 1.0 version.
Where Are Your Save Files
If you ever want to back things up manually, knowing the location of your saved game is a must. Also remember that the location of these files varies depending on how you’re playing.
So, if you’re playing solo or hosting co-op through Steam:
%LOCALAPPDATA%\Pal\Saved\SaveGames\<your-steamid>\<world-guid>\
But if you’re running a self-hosted dedicated server:
<server-root>\Pal\Saved\SaveGames\0\<world-guid>\
You will notice that the dedicated server path uses a literal 0 in place of a Steam ID, that’s simply how dedicated servers are structured internally.
Inside that world folder, a few files matter more than others:
| File/Folder | What It Contains | What Breaks If Missing |
| Level.sav | The world itself, terrain, bases, objects | Everything, the world won’t load |
| LevelMeta.sav | World name and creation settings | May not appear correctly in server browser |
| WorldOption.sav | In-world setting overrides | Settings may reset to default |
| Players/ | One file per player, character data and inventory | Any missing player file forces that player to start a new character |
That Players/ folder needs your special attention. Each file inside represents one player’s actual character, their Pals, inventory, and progress. If you’re ever backing up or moving a save, skipping this folder means whoever’s file is missing effectively loses their character permanently and has to start fresh.
The process for manual saving is the same for players across the globe. So, whether you are playing from the UK or the US or any other region, it’s going to be the same for you.
How To Back Up Your Save Manually
Take it from me, backing up your save periodically is genuinely worth the two minutes it takes. Here’s how to do it based on your platform:
PC (Steam): Your save files live at %LOCALAPPDATA%\Pal\Saved\SaveGames. Copy the entire folder somewhere safe, your desktop, an external drive, or cloud storage. To restore later, just paste the folder back into place.
PS5: If you have PlayStation Plus, your saves back up automatically to cloud storage. You can also manually copy saves to a USB drive through Settings → Saved Data and Game/App Settings → Saved Data (PS5) → Console Storage → Upload/Copy.
Xbox Series X|S / Game Pass: Xbox automatically syncs saves to the cloud when you’re connected. It’s still worth confirming that sync has actually completed before doing anything risky, like a major update or a fresh reinstall.
When Should You Actually Back Up?
There is no point in backing up your game when nothing special is happening. I suggest you do it when:
- Before any major game update. Big patches sometimes shift how save files are structured, and having a pre-update backup gives you a safety net if something behaves unexpectedly afterward
- Before experimenting with mods, since heavily modded saves are far more prone to conflicts, and a bad mod interaction can leave a save in a broken state
- Before migrating to a dedicated server, if you’re moving from local co-op hosting to your own server setup
- Periodically, just as good practice, especially once you’ve sunk serious hours into base building or a particularly good Pal collection
What Happens To Your Save Across Big Updates?
If you’re worried about losing everything to a major content patch, the good news is Pocketpair has consistently avoided forcing save wipes across its update history, including big content drops. Existing saves and characters have reliably carried forward through major updates without deletion.
That said, it’s still smart to back up beforehand regardless of what’s officially promised, since “no wipe planned” and “zero risk of any issue” aren’t quite the same guarantee. A two-minute backup costs you nothing and protects against the rare edge case where something does go wrong during a big transition.
That’s it; now you know all the basics of saving your game progress in Palworld. I hope you are enjoying the full version of the game. I know I will be glued to my screen for the entire weekend. You know what that means? More Palworld guides for you!! So, I will see you soon. Till then, Happy Gaming!!
Leave a Reply