How to back up a Palworld save before updates or mods

Safety

Back up while the world is not being written

Close a local session or stop a dedicated server cleanly before copying its world data. A folder copied during active writes may look complete while containing inconsistent files.

Name the backup with the date, game version and reason, such as before-1.0.3 or before-mod-update. Keep at least one copy outside the live game directory.

Safety

Verify the backup instead of trusting the copy dialog

1. Confirm that the backup contains files and is not unexpectedly small.
2. Record the original path and the exact restore destination.
3. Keep the previous known-good backup when creating a new one.
4. Test the restore workflow on a separate copy when the world is important.
5. Do not overwrite the live world until the test copy loads correctly.

Safety

Use a new checkpoint before every mod change

Pocketpair warned that incompatible pre-1.0 mods and loaders can cause crashes, corrupted saves and broken quest or event progression. Removing the visible mod files may still leave a loader or altered data behind.

Make one change, start the game, inspect the world and only then install the next 1.0-compatible mod. This makes the cause identifiable and gives each step a clean rollback point.