Palworld Server Backup Restore: Safe Step-by-Step

Restoring a Palworld server backup is the safest way to recover from corrupted worlds, failed updates, or accidental player wipes. This guide walks you through the entire process—locating your backups, stopping the server cleanly, replacing the correct files, and verifying the world loads without errors. You’ll need access to your server’s file system (via FTP, SSH, or a hosting control panel) and a recent backup archive.

What You’ll Need

• A Palworld dedicated server (official or community) that is currently stopped or can be stopped.
• File access to the server directory—usually via SSH, FTP, or your hosting provider’s file manager.
• A backup file or folder from a previous point in time. This can be a .zip, .tar.gz, or a plain folder copy.
• Basic command-line knowledge if using SSH (optional but helpful).

Step-by-Step

1. Stop the server completely. Use the game’s console command save first if it’s running, then shut down the process. If you’re using a hosting panel, click the “Stop” button. For a manual server, send Ctrl+C in the terminal or use kill with the correct PID. Do not skip this—restoring while the server is writing data will corrupt the world.
2. Locate the save directory. The default path for a Linux server is ~/Steam/steamapps/common/PalServer/Pal/Saved/SaveGames/0/. On Windows, it’s typically C:\Program Files (x86)\Steam\steamapps\common\PalServer\Pal\Saved\SaveGames\0\. Inside, you’ll see one or more folders with long numeric names—each corresponds to a world save.
3. Identify the correct world folder. If you have multiple worlds, check the WorldOption.sav file inside each folder or look at the folder’s modification date. The folder with the most recent activity is usually the one you want. If you’re unsure, back up the entire SaveGames folder first.
4. Rename the current world folder (optional but recommended). Instead of deleting it, rename it to something like 0_OLD_BROKEN. This preserves your current (possibly corrupted) data as a fallback and avoids accidental deletion.
5. Extract or copy your backup into place. If your backup is a compressed archive, extract it into the SaveGames/0/ directory. If it’s a folder, copy it there. The result should be a folder with the same numeric name as the original (e.g., 0 or ABC123). If the backup folder has a different name, rename it to match the original exactly.
6. Check file permissions (Linux only). Run chown -R steam:steam /path/to/SaveGames if your server runs as the steam user. Incorrect ownership will cause the server to fail to read the save.
7. Start the server. Launch the server normally. Watch the console output for the message “World Saved” or “Loading complete”. If it loads without errors, your restore worked.
8. Verify player data. Connect to the server and check that your character, bases, and Pals are present. If something is missing, you may have restored the wrong world folder or an older backup.

Common Mistakes

• Restoring while the server is running. This almost always corrupts the save. Always stop the process first.
• Mixing up world folders. Copying a backup into the wrong numeric folder will load a different world or fail to load entirely. Double-check the folder names.
• Forgetting to preserve the .sav file extensions. Some backup tools rename files—ensure all files end with .sav and are in the same structure as before.
• Skipping the rename step. If you delete the old folder and your backup is bad, you have no fallback. Keep the old folder until the new one is verified.
• Ignoring file permissions. On Linux, if the server can’t read the save, it will create a new world instead of loading your backup—silent data loss.

Tips

• Always take a fresh backup before restoring. Even a broken world is better than nothing if the restore goes wrong.
• Use the in-game save command. Type save in the server console before stopping to ensure all data is flushed to disk.
• Test the backup on a separate instance. If you have the resources, spin up a temporary server on a different port to verify the backup loads before touching your live server.
• Keep multiple backup generations. A backup from 2 hours ago might be better than one from 2 days ago if the world was corrupted recently. Store at least 3-5 rolling backups.
• Document your world folder name. Write down the numeric folder name for your main world—it saves time when you need to restore quickly.

Troubleshooting

Server starts but creates a new world instead of loading your backup. This usually means the save folder name doesn’t match what the server expects, or the folder is empty. Check that the folder name exactly matches the original (including case) and that it contains Level.sav and WorldOption.sav.

Server crashes on startup after restore. The backup may be corrupted or from a different game version. If you updated Palworld recently, the save format may have changed—try restoring an older backup from before the update, or check if a backup tool (like Palworld Save Tools) can convert it.

Players’ characters are missing but the world is intact. Player data is stored in the same folder, so this points to a partial backup. Restore the entire folder from a more recent backup, not just Level.sav.

File permission errors on Linux. Run chown -R steam:steam ~/Steam/steamapps/common/PalServer/Pal/Saved and restart. If that fails, check that the folder isn’t mounted with noexec or similar restrictions.

Backup won’t extract. If your archive is corrupt, try using 7z or unzip -t to test integrity. If it’s beyond repair, you’ll need to use an older backup.

Frequently Asked Questions

How often should I back up my Palworld server?

Ideally every 1-2 hours if the server is active. Many hosting panels offer automatic backups—enable them if available. For manual servers, set a cron job to copy the save folder hourly.

Can I restore a backup from a different server (e.g., from a friend’s server)?

Yes, but only if the game version matches. Copy the entire SaveGames/0/<worldID> folder to your server and rename it to your world ID. Player data and world data are portable.

Will restoring a backup affect player levels and progress?

Yes—it will revert all player data to the point of the backup. Any progress made after that backup will be lost. Make sure you communicate this to your players.

What’s the difference between a world save and a player save?

In Palworld, both are stored together in the same folder. Level.sav contains the world state, while Players/ folder contains individual player data. You must restore both together for a complete rollback.

Can I restore a backup while the server is running?

No. You risk corrupting the save file. Always stop the server first. Some hosting panels allow “hot restore” but it’s not recommended—stop the server to be safe.

How do I know which backup is the right one?

Check the modification date of the backup folder. Most backup tools timestamp them. If you have multiple, pick the one just before the issue started. If you’re unsure, restore the most recent one and check if the problem is gone.

Related

• Business Phone Systems for Remote Teams: Which Fits?
• Turn Kits Allen Key Redesign: Key Concept Changes
• Encrypted Flash Drive: What It Is & How to Choose