Back up and restore a Palworld dedicated server

Define the backup contents

For a manual dedicated-server backup, archive Pal/Saved with its directory structure. Retain startup arguments and mod versions separately. This captures saves and configuration belonging to that installation.

Inside SaveGames, retain the entire active world directory, including Level.sav and Players where present. Do not construct an archive from selected files with unrelated timestamps. Record the world selected in the panel to avoid restoring an unused older session.

Create a consistent copy

Announce maintenance, have players leave and stop the server properly. Wait until the process exits before downloading through the file manager or SFTP. Confirm transfer completion and inspect the archive's contents.

Keep a copy outside hosting, dated and labeled with the game version. If the provider documents a managed backup process without downtime, follow that procedure. A manual copy during active writes does not offer the same assurances.

Combine automatic saves and exports

bIsUseBackupSaveData enables the game's backup snapshots under a backup subdirectory. Pocketpair notes that this adds disk workload. Check free space and verify that new snapshots actually appear.

Ask the provider about backup retention and restoration too. Automatic copies stored on the same server do not replace an independent export.

Restore and verify player data

Archive the current state, stop the server and restore a consistent snapshot. Select the correct world and use compatible game and mod versions. Test with a few players first: characters, guilds, Pals, inventory, storage and bases.

If character creation appears unexpectedly, avoid further actions that could overwrite data and investigate identifiers. Moving from cooperative play can require player mapping; that differs from restoring a backup on the original dedicated server.

Frequently asked questions