Restore Server Backup
A backup restore is easiest when you already know which copy is healthy and why you are rolling back. If you are guessing, slow down. Restoring the wrong backup can compound the original problem by adding unnecessary progress loss on top of downtime.
Choose The Right Restore Point
| Before corruption | Best if the incident is clearly tied to a crash or bad shutdown. |
|---|---|
| Before a patch or mod change | Useful when the world became unstable immediately after an update. |
| Latest healthy copy | Often the best compromise between safety and lost progress. |
Recovery Workflow
- Preserve the current broken state in case you need to inspect it later.
- Restore the selected backup with the server stopped.
- Verify world load, player access, base locations, and any recently changed settings.
- Invite only a small test group first if the world matters to many players.
What Not To Do
- Overwrite the live world without keeping the failing copy.
- Restore a backup and then forget to match the corresponding config or version context.
- Assume success because the server boots. Booting is not the same as healthy gameplay.
Verified 2026 Detail
The official docs tie runtime settings, REST behavior, and file layout to specific server versions. That means backup recovery is safer when you think in terms of restoring an environment snapshot, not only a world file: version, config family, and management expectations should line up with the chosen recovery point.
Current Official Note
Palworld's official server documentation makes it clear that server configuration and operational state are closely tied to the running environment. When you restore a backup, validate the restored world against the same version and server settings family instead of looking only at the save files themselves.
Need a stable place to test changes before you touch a live world? Launch your Palworld server with Supercraft.