Guide contents
For Steam Windows, begin with the common LocalAppData Pal Saved SaveGames location, close the game, and back up the whole relevant directory. Do not reuse it for Xbox App or server saves.
This page keeps platform, version, dependency, and source boundaries visible so a safe test has a clear result.
Follow the smallest useful path.
Confirm the platform scope
Use the Steam Windows branch and keep Xbox App, dedicated server, and cloud saves separate.
The backup note names Steam Windows and does not claim a universal path.
Copy the save directory
Copy the relevant Pal Saved SaveGames directory while the game is closed.
The backup contains the complete directory and a date in its name.
Test the backup boundary
Keep the original untouched and document which copy would be restored if a Mod test fails.
You can identify the backup without overwriting the live save.
Use the symptom to choose the next check.
| Symptom | Check | Recovery |
|---|---|---|
| The expected folder is empty or missing. | Confirm the platform, hidden AppData visibility, and whether the save is cloud/server-managed. | Do not create a replacement folder or overwrite another platform's save. |
| A cloud save conflicts with a local copy. | Compare the Steam Cloud file types and local backup dates. | Keep both copies and verify the intended restore path before changing cloud state. EvidenceBNeeds source review |
Questions this source set can answer.
Is this path valid for every Palworld version?
It is scoped to the common Steam Windows case; Xbox App, dedicated server, and cloud paths need separate verification.
Should I back up before Mod changes?
Yes. Close the game and copy the complete relevant directory before testing a Mod.
If the current source disagrees with an older tutorial, pause the change and re-check the release, platform, and original Mod page before continuing.