Palworld server: Create and restore backups
A backup only helps if you know exactly which state was saved and how to restore it. For a Palworld server, you should therefore keep the complete save data together with the corresponding configuration. A single Level.sav is not a substitute for a full backup.
The following guide describes how to restore a complete file backup. It does not rely on any specific backup button in the customer panel. For download only, see the shorter guide at Back up Palworld save.
What belongs in a backup?
| Component | Why keep it? |
|---|---|
Complete contents of Pal/Saved/SaveGames/0/ | So that matching world and player files are preserved together |
GameUserSettings.ini | To track, among other things, which world folder was previously selected |
PalWorldSettings.ini | So you can restore or compare the server rules from that time |
| Date, game version, and reason for the backup | To make clear under which conditions the state last worked |
Create a dedicated folder on your PC, for example Palworld-before-update-2026-09-10. Do not always save into the same folder without archiving the old state separately first. Also wait until your FTP program has finished all transfers.
Create a manual backup
- Inform your fellow players. If you are connected as an admin, you can save with
/Savebefore maintenance. - Stop the server via the server management and wait until it shows Server not running.
- Download the complete save and both configuration files as described in the download guide.
- Verify in your FTP program that no files failed and nothing is still queued.
- Keep this copy unchanged and restart the server if no further work is pending.
The /Save command saves the running world but by itself does not create an independent copy on your computer. You still need to perform the download afterward.
Automatic backups in Palworld
Palworld offers an in-game backup feature with bIsUseBackupSaveData=True. It creates backups in the backup directory within the save data and causes additional write operations. The feature is described in the official parameter documentation.
A backup on the same server does not replace an additional external copy. Before maintenance, check whether a suitable restore point actually exists. Do not confuse these in-game files with any separate hosting backups that may be offered.
Restore a complete save
All progress after the chosen backup time will be lost on the restored server. Coordinate the timing with your group and inform them before you stop the server.
- Stop the server and wait until it is no longer running.
- Also back up the current state completely into a new local folder. This applies even if the current state appears faulty.
- Work with a copy of your desired backup. Identify the world folder it contains and the associated
GameUserSettings.ini. - Move any current world folder with the same name out of the active savegame directory to a separate backup location, if your FTP access allows it. If not, coordinate the swap with support. Do not mix old and new player files through a partial upload.
- Upload the complete backed-up world folder to
Pal/Saved/SaveGames/0/. The world folder must be directly under0, not under an additional copy of0. - Check in the active
GameUserSettings.inithatDedicatedServerNamepoints exactly to this folder. The upload guide contains the appropriate example. - Compare the backed-up
PalWorldSettings.iniwith your current configuration. Apply the desired rules selectively rather than blindly copying an old file over a new one after a game update. - Verify all transfers and start the server.
Verify after restoration
Let only a small group join first. Check your base, storage, Pals, and characters. A successful server start alone does not confirm that the intended state was loaded.
If everything looks correct, save with /Save and perform a controlled restart. Then check again that the same state loads. Only then should the whole group continue playing. Keep both the original backup and the copy from before the restoration.
How are in-game backup files different?
A subfolder from backup may not have the same scope as your full manual download. Check which world and player files the selected point in time contains. Do not combine data from different times, and do not copy the entire backup folder into the location of an active world.
If the mapping is unclear, give support the configuration ID, the desired time, and the existing folder structure. Have the state checked before swapping it in. This is more sensible than loading multiple different .sav files into the running server.