Palworld Backup and Restore Safety Checklist

A save backup is not glamorous, but it is the one guide you want before something breaks. The rule is simple: copy the whole save container while the game is closed, keep the copy outside the live folder, and never delete the old copy until the restore has loaded correctly.

The safe backup rule

Use this three-step rule on every platform:

1. Close the game first. Do not copy while Palworld is writing data.
2. Copy the whole save container. World files work together; partial backups are fragile.
3. Name the backup clearly. Use the date and a short note, such as before-1-0-cleanup.

For players returning to 1.0, pair this with Returning Player Guide.

Save locations and backup method

Platform	What you can do
PC Steam	Copy the full local SaveGames folder from AppData while the game is closed
PC Game Pass	Copy the whole container folder used by the Xbox app version; do not cherry-pick opaque files
PS5	Use the console’s supported saved-data and cloud controls; do not assume a raw USB copy is available for PS5 saves
Xbox	Let cloud sync protect the save, and avoid deleting cloud data by mistake
Dedicated server	Stop the server, then copy the world folder and settings file together

Save locations vary by store, account, and server setup. If you cannot identify the live container, stop and use the platform’s support flow rather than copying a plausible-looking folder.

How to restore without making things worse

Use this process for PC or server restores:

1. Close the game or stop the server.
2. Rename the current live folder instead of deleting it.
3. Copy the backup into the original location.
4. Launch and test the world.
5. Verify player, base, Palbox, inventory, and settings.
6. Only then remove the old renamed folder.

That rename step is the safety net. If the backup is wrong, you can still go back.

Modded installs: the cautious route

If the PC install used mods before 1.0, separate the world from the game files.

• Back up the save first.
• Remove old mod files and loaders from the game installation.
• Verify or repair the game files through the store client.
• Launch the clean game once.
• Load the save only after the clean game works.

Do not test a valuable world as your first proof that a mod cleanup worked.

Console recovery rules

Console saves are safer in some ways and less flexible in others.

• PS5: check the console’s supported saved-data and cloud controls before overwriting local data. Do not rely on a generic “USB backup” instruction for a PS5 game save.
• Xbox: use the console’s local-delete option carefully if cloud sync needs to pull a copy back down. Do not choose a delete option that removes the cloud copy too.
• Cross-save: treat synchronization as transfer, not as a versioned recovery backup. A bad state may sync too.

Dedicated server backups

A server save is not just the world folder. Keep the world data and the server settings together, or a restore may load with the wrong rules.

Before any manual restore:

• Stop the server.
• Copy the world folder.
• Copy the active settings file.
• Preserve timestamps or notes so you know which backup predates the problem.

For server rule changes, read World Settings Explained.

Red lines

• Do not edit .sav files with random tools.
• Do not download unknown “recovery” utilities.
• Do not copy a save while the game is running.
• Do not delete the live folder until the restored world is proven.
• Do not assume cloud sync means yesterday’s local mistake is reversible.

Bottom line

A good backup is boring, complete, and tested. Use the current platform UI and support flow for save locations and recovery options that this checklist cannot show.