PALWORLD · BACKUP, RESTORE AND TRANSFER · NOVEMBER 2026

How to Back Up, Restore and Transfer a Palworld World

Which files make up a Palworld world, how far back the server’s own backups reach, how to take and restore a backup safely, and how to move a co-op world to a dedicated server without losing the host’s character.

What a Palworld world is made of

Every world is one folder with a 32-character name, such as 535B53F9492B47B2255A4CB90C5C5CB9. On a dedicated server it sits in Pal/Saved/SaveGames/0/. On your own PC, a co-op world you host through Steam sits in %LOCALAPPDATA%\Pal\Saved\SaveGames\<your SteamID64>\ instead. The files inside are the same either way, but they do not all belong on a server.

Which files to copy for each job
In the world folderYour own backupRestore a snapshotCo-op world to a server
Level.sav (the world)YesYesYes
LevelMeta.sav (world details)YesYesYes
Players/ (one file per character)YesPartlyYes
WorldOption.sav (co-op world settings)YesNoNo
LocalData.sav (your PC only)NoNoNo
backup/ (Palworld’s own copies)PartlyNoNo
Partly for Players = only if characters should go back too. Partly for backup = useful, but large. WorldOption.sav only exists in some worlds, mostly ones that started as co-op.
Level.sav and LevelMeta.sav always travel together. WorldOption.sav must not come along to a server.

Two settings files outside the world folder matter too. GameUserSettings.ini in Pal/Saved/Config/WindowsServer/ (or LinuxServer/ on Linux) has a DedicatedServerName= line naming the world folder the server loads. If that line names a folder that is not there, the server quietly creates a brand-new world under that name, which is the most common reason an upload “did nothing”. PalWorldSettings.ini in the same folder holds your rates and rules.

The backups Palworld already makes

When bIsUseBackupSaveData is True in PalWorldSettings.ini, the server creates a backup folder inside the world folder and fills it on a fixed schedule. Pocketpair’s server documentation gives the schedule, and notes that the feature adds disk load. Each copy is a folder named with its date and time, such as 2026.11.11-23.19.54, holding its own Level.sav, LevelMeta.sav and Players.

How far back Palworld’s own backups reach
With bIsUseBackupSaveData=True, from Pocketpair’s server documentation
Every 30 seconds
5 copies kept
about the last 2½ minutes
Every 10 minutes
6 copies kept
about the last hour
Every hour
12 copies kept
about the last 12 hours
Every day
7 copies kept
about the last week
Recent copies are close together, older ones a day apart. Nothing reaches back further than about a week.

In practice that means you can usually go back a few minutes, an hour, half a day or up to a week, with fewer choices the further back you go. It is the fastest fix for a griefed base or a bad admin command. It is not a backup plan on its own: the copies live on the same disk as the world, and they go when the server does. Keep the setting on, and still take your own copies.

Take a backup you can restore

  1. Get admin rights in game with /AdminPassword <your password>.
  2. Save and shut down with a warning. /Save writes the world to disk. /Shutdown 60 Backup in one minute stops the server after 60 seconds and shows the message to everyone online. Keep /DoExit, which force-stops the server, for when nothing else works.
  3. Copy the whole world folder from Pal/Saved/SaveGames/0/, plus PalWorldSettings.ini and GameUserSettings.ini if you want your settings back too. Level.sav can run to hundreds of MB, so use SFTP rather than a browser upload for big worlds.
  4. Store it off the server, in a folder named with the date and the reason, such as 2026-11-18 before update.
  5. Start the server again.

Do this before every game update and before adding mods. A running server holds the world in memory and writes it over the files on its next save, so never copy into, or out of, a world folder while the server is up. Our game server backups explainer covers how often to schedule copies.

Roll the world back

Choose how far back you need to go, then pick the matching route.

Which restore do you need?
The world needs to go back to an earlier state
Is the moment you need within the last week?
Yes
Palworld’s own backupCopy Level.sav and LevelMeta.sav from a dated folder in backup/world/. Add Players to roll characters back too.
No
Do you have your own copy from that time?
Yes
Your own backupRename the world folder with -old, put your copy back under the original name.
No
Ask your host whether its panel backups go back further, before you change anything.
Whichever route you take, shut the server down and copy the current world folder first.

From Palworld’s own backups

  1. Shut the server down and copy the current world folder somewhere safe, so you can undo this.
  2. Open backup/world/ inside the world folder and pick the dated folder from before the problem.
  3. Copy its Level.sav and LevelMeta.sav into the world folder, two levels up, replacing the ones there.
  4. To put characters back to that moment too, copy its Players files over the world’s Players folder. Leave this step out and the world goes back while everyone keeps the character they have now.
  5. Leave the backup folder and the world folder’s name as they are, then start the server and check before letting everyone in.

From your own backup

Shut the server down, rename the current world folder by adding -old to its name, then put your copy back under the original name. Restoring over a live folder leaves today’s files mixed in with the old ones. Because the name is unchanged, DedicatedServerName still matches. Start the server, check, and delete the -old folder once you are happy.

Move a co-op world to a dedicated server

This is the move most groups make once the host gets tired of leaving their PC on. The world transfers cleanly. The host’s character is the one thing that does not.

Moving a co-op world to a dedicated server
The world
%LOCALAPPDATA%\Pal\Saved\SaveGames\<SteamID64>\<World ID>
upload, delete WorldOption.sav
Pal/Saved/SaveGames/0/<World ID>
DedicatedServerName=
World loads
The host’s character
Co-op ID ending in 0001
not matched
New Steam-based ID on the server
host fix
Original character back
Other players are matched by the same ID on both sides, so their characters are waiting for them.
The world moves with three steps. Only the host’s character needs the extra host fix.
  1. Start the new server once so it creates its folders, then shut it down.
  2. On the host’s PC, open %LOCALAPPDATA%\Pal\Saved\SaveGames\, then the folder named after their SteamID64, and find the world folder. If there are several, the one changed most recently is usually the world you played last.
  3. Upload that whole folder, under its own name, into Pal/Saved/SaveGames/0/ on the server. You can leave its backup folder behind; the server makes its own.
  4. Delete WorldOption.sav from the uploaded folder. While it is there, the co-op world’s settings can override your PalWorldSettings.ini. Players will choose their respawn point again on first join.
  5. Set DedicatedServerName= in GameUserSettings.ini to the uploaded folder’s name, exactly.
  6. Start the server and have a player who was not the host join first. If their character, bases and Pals are there, the world loaded correctly.

Why the host starts as a new character

Palworld matches each player to their save by an ID. In co-op, the host’s character is stored under a fixed ID ending in 0001, while a dedicated server gives the host an ID based on their Steam account like everyone else. The server does not connect the two, so the host is asked to create a new character and their old one sits unused in Players.

The fix is what hosts call a “host fix”. The host joins the new server once and plays far enough to save a placeholder character (Indifferent Broccoli suggests reaching level 2). You then stop the server, download the world folder, use a community save tool’s host-fix option to move the original character into the placeholder’s slot, upload the folder again and start the server. Palworld does not include this tool itself, so take a full copy of the world before you try it.

Moving between two dedicated servers is simpler: copy the world folder across, keep the same folder name or update DedicatedServerName, and run the same game version on both. Our guide to moving to a new host covers the rest of the switch.

Want backups and transfers handled for you?

Many Palworld hosts run scheduled backups, restore from the panel and help with save uploads. Compare UK hosts, and what each one includes, in our roundup.

Compare the best Palworld server hosts

Palworld backup and transfer FAQ

Where are Palworld dedicated server save files?

In Pal/Saved/SaveGames/0/, one folder per world with a 32-character name. DedicatedServerName in GameUserSettings.ini tells you which one the server loads.

Does a Palworld server back itself up?

Yes, when bIsUseBackupSaveData is True. It keeps 5 copies every 30 seconds, 6 every 10 minutes, 12 every hour and 7 every day in the world’s backup/world/ folder.

Why did my uploaded Palworld world not load?

Usually because DedicatedServerName does not match the uploaded folder’s name, so the server made a new world. Check the name, and that the folder sits directly in SaveGames/0/.

Why do my server settings not apply after moving a co-op world?

The world still has its WorldOption.sav, which carries the co-op settings. Delete it from the world folder with the server stopped, then set your rates in PalWorldSettings.ini.

Can the co-op host keep their character on a dedicated server?

Yes, with a host fix. The host creates a placeholder character on the server, then a community save tool moves the original character into that slot.

More Palworld server guides

Compare hosts, tune settings and fix problems.

Palworld updates and host panels change. Where your server or your host’s panel works differently from what is described here, follow what you see on your server.

Similar Posts