To transfer a Palworld save to a dedicated server, copy the world folder into the server’s Pal/Saved/SaveGames/0/, point the server at it in GameUserSettings.ini, and delete WorldOption.sav. Everyone’s characters come with the world, with one catch: in a co-op world the host’s character is saved under a fixed placeholder ID, not their real player ID, so on the server the host starts from scratch until you run a host save fix. On a Linux server, GameTeam’s included, the fix’s author reports that every player starts from scratch, so each character needs it. Below is the whole move, the fix, and the tools people use for it.
Before you start
A save transfer is a file copy, so most of the risk is copying the wrong folder or copying while something is writing to it. Close Palworld on the PC that hosted the co-op world, stop the dedicated server, and make two backups: one of the co-op world, one of the server’s Pal/Saved folder. Every tool below edits save files directly, and their authors all say the same thing: back up first.
- Both sides on the same game version. Update the server before you move the world, so it loads a save from the version your players are on. (How: updating a Palworld server.)
- Start the server once first. Pocketpair notes the config folders only appear after the first start, and you need
GameUserSettings.inito exist. - Co-op host: hand over the guild. If the host leads a guild, move ownership to another player and have the host leave the guild before the move. The host save fix has a known guild bug, and this is its author’s workaround. It only helps when the other players keep their characters, as on a Windows server.
Where is the Palworld save file location?
On Windows, a co-op world (one you host from your own PC) lives in %localappdata%\Pal\Saved\SaveGames\<your ID>\<world ID>\. Paste %localappdata%\Pal\Saved\SaveGames into the File Explorer address bar to jump there. On a dedicated server, worlds live in Pal/Saved/SaveGames/0/<world ID>/ inside the server folder. The world ID is a long random string; each world gets its own folder.
| In the world folder | What it is |
|---|---|
Level.sav |
The world itself: map, bases, guilds, Pals |
Players/ |
One .sav per character, named after that player’s ID. The co-op host’s is 00000000000000000000000000000001.sav |
WorldOption.sav |
The co-op world’s settings. Overrides PalWorldSettings.ini while it exists |
backup/ |
Rolling backups, if the server has bIsUseBackupSaveData turned on |
Played through Xbox / PC Game Pass? Those saves aren’t in this folder and need converting to the Steam format before a server can load them. PalworldSaveTools has a Game Pass to Steam converter.
How to move a Palworld save to a dedicated server
Copy the world folder in, tell the server which folder to load, remove the co-op settings file, then start it. These steps work for any dedicated server; the GameTeam file-manager version is in the next section. Do every step with the server stopped, because Palworld writes to the save constantly and a half-copied world can corrupt.
- Copy the whole
<world ID>folder from your co-op save location into the server’sPal/Saved/SaveGames/0/. - Open
Pal/Saved/Config/LinuxServer/GameUserSettings.ini(WindowsServeron a Windows server) and setDedicatedServerNameto the world folder’s name, so the line readsDedicatedServerName=<world ID>. - Delete
WorldOption.savfrom the world folder. Without this, the server keeps the co-op world’s settings and ignores yourPalWorldSettings.ini. Players will pick their respawn point again on first join. - Start the server and join with a player who wasn’t the host. If the bases and Pals are there, the world loaded correctly. On a Linux server, expect that player to see character creation too: that’s the ID problem below, not a wrong world.
Edit only the DedicatedServerName line and leave the rest of the file as it is. If the server ever loads a fresh world instead of yours, this line is the first thing to check, which is also the fix in server update wipes player progress.
Uploading your world to a GameTeam server
On GameTeam you do the same move through the panel’s file manager, no FTP client needed for a normal-sized world. Stop the server first, upload the world as a .zip, unpack it in the right folder, then point the server at it. For big worlds, SFTP is the better route, and support can do the migration for you if you’d rather not touch files at all.
- On your PC, zip the
<world ID>folder. - In the GameTeam panel, stop the server and open the file manager. Go to
Pal/Saved/SaveGames/0/. - Drag the .zip in (or use Upload), then choose Unarchive from the three-dots menu next to it. Check the world folder is listed, then delete the .zip.
- Large world, or the upload keeps failing? Use SFTP instead with the login details from the panel.
- Set
DedicatedServerNameinPal/Saved/Config/LinuxServer/GameUserSettings.iniand deleteWorldOption.sav, as above. - Start the server and join with a non-host character to check the world.
Moving a world off a GameTeam server works the other way round: in the file manager, pick Archive on the world folder, then download the .zip. Taking a backup from the Backups tab first never hurts.
The co-op host save fix
Palworld matches each player to their character by a player ID (a GUID). In co-op, the host’s character is stored under the placeholder 00000000000000000000000000000001. On a dedicated server the host joins with their real player ID, the server finds no save under it, and hands them a new character. A host save fix moves the old character onto the host’s new ID. Moving a Windows co-op world to a Linux server gives every player a new ID, so there you repeat the steps below for each player.
- With the world already running on the server, have the co-op host join and create a throwaway character.
- Stop the server. In the world’s
Playersfolder, a new.savhas appeared. Its file name is the host’s new player ID. Note it. - Copy the whole world folder off the server to a working folder on your PC, and keep a second untouched backup.
- Run a host save fix tool on the working copy, with the old ID
00000000000000000000000000000001and the host’s new ID (tools below). - Copy the fixed folder back to
Pal/Saved/SaveGames/0/, replacing the one there, and start the server. - The host joins and finds their character. If their Pals stand idle at the base after about five minutes, have them drop and re-pick every Pal they own from the Party menu, base workers included. That’s the documented workaround for the tool’s “Pal bug”.
Palworld host save fix tools
Three community tools do the conversion. None is made by Pocketpair, all edit save files directly, and every author says to back up first. Pick one and follow its own README; the steps above are the same for all three.
| Tool | How you run it | Notes |
|---|---|---|
| xNul’s palworld-host-save-fix | Python 3.10+ script, with a small GUI (gui.py) |
The original fix. Marked experimental with known bugs (guild, Pal, Viewing Cage). Needs palworld-save-tools 0.17.1 |
| Palworld Save Pal | Desktop app for Windows, Mac and Linux | “Player UID Swap” is meant for co-op to dedicated server moves; also has Player Transfer between saves |
| PalworldSaveTools | Prebuilt .exe, no Python | “Fix Host Save” swaps the IDs of two players. Its developers have stopped updating it (2.4.5 is the final release) and no longer recommend it |
With xNul’s script, clone the repository, then from its folder run:
python -m pip install palworld-save-tools==0.17.1
python fix_host_save.py "C:\work\<world ID>" <host's new ID> 00000000000000000000000000000001 False
The last argument is the guild fix. For a co-op move to a Windows server it stays False; you handed the guild over before the move instead. When every player needs the fix, nobody is left to hold the guild, and xNul’s README sets it to True.
Moving between two dedicated servers
Between two servers of the same kind, the move is just the folder copy and DedicatedServerName: everyone keeps their character. Between a Windows and a Linux dedicated server, xNul’s README reports that no player can use their old character, host or not. Every player then creates a new character, you note each old and new ID, and run the fix once per player with the guild fix set to True.
GameTeam’s standard Palworld server runs the Linux build, and xNul’s README lists a Windows co-op save moved to a Linux dedicated server among the cases where every player loses their character. So whether you bring a co-op world or a world from your own Windows dedicated server, plan on one fix per player, with the guild fix set to True. Want to check whose ID is whose? With admin rights, /ShowPlayers lists every player online with their ID (see Palworld admin commands).
Can you transfer Pals between servers?
Yes, through the Global Palbox, without touching save files. A player stores Pals in the Global Palbox on one world and takes them out on another, as long as both servers allow it. On a dedicated server that’s two settings in PalWorldSettings.ini, bAllowGlobalPalboxExport and bAllowGlobalPalboxImport. Characters themselves don’t travel this way; for a whole character, use a save tool’s player transfer. Editing the file safely: Palworld server settings.
Troubleshooting a Palworld save transfer
| What you see | Likely cause | Fix |
|---|---|---|
| Server starts a brand-new world | DedicatedServerName doesn’t match the folder name, or the folder isn’t directly under SaveGames/0/ |
Copy the folder name exactly; check you didn’t unzip into an extra subfolder |
| Host has a new character, everyone else is fine | Host’s save is still under the co-op host ID | Run the host save fix |
| Everyone has new characters | Moved to a Linux server from a Windows co-op world or Windows server, or the wrong world loaded | Check the world first, then fix each player |
Your PalWorldSettings.ini changes do nothing |
WorldOption.sav is still in the world folder |
Stop the server and delete it |
| Host’s Pals don’t work at the base | Pal bug after the fix | Drop and re-pick every Pal from the Party menu |
| Host can’t use guild features | Guild bug after the fix | Restore the backup, hand over the guild first, redo the fix |
| World won’t load or is missing recent progress | Copied while the game or server was running | Restore a backup and copy again with both stopped |
FAQ
Can I transfer my Palworld save to a dedicated server?
Yes. The world and bases move with the folder copy. On a Windows server the other players’ characters come along too and only the co-op host’s needs the host save fix; on a Linux server like GameTeam’s, every player’s character needs it.
Does player progress transfer?
Yes, once each character is matched to the player’s new ID. On a Windows server that’s only the co-op host; on a Linux server it’s everyone. Older guides, including an earlier version of this one, said progress was lost; that’s only true if you skip the fix.
Do my co-op world settings come with the save?
They do, inside WorldOption.sav, and they override the server’s own settings while that file exists. Delete it and set the rules you want in PalWorldSettings.ini.
Can I move a dedicated server world back to co-op?
Yes, but the host’s character has the same problem in reverse. xNul’s README has a section for moving a Windows dedicated server save back to co-op; follow it step by step, with a backup.
How much RAM does the server need for my old world?
Size for the world you bring, not a fresh one. A world with many bases and working Pals already needs the top of the 8–16 GB range. More in Palworld server requirements.
Can GameTeam move the save for me?
Yes. Open a ticket with support and they’ll handle the migration; have your world folder ready.
Skip the file juggling
Moving a world is a lot of small steps where one wrong folder name gives you a fresh map. On GameTeam’s Palworld server hosting, you upload the world and let the AI copilot handle the server side. Tell it “back up the server, then load the world I just uploaded” and it makes the backup, sets DedicatedServerName in GameUserSettings.ini, restarts the server and reads the log to confirm your world loaded. You pay per GB of RAM, from $0.49/GB a week, with unlimited slots (Palworld itself caps a server at 32). Starting from zero instead? The Palworld dedicated server guide covers everything, and joining your Palworld server gets everyone back in.

It is a pity, that now I can not express – it is compelled to leave. But I will return – I will necessarily write that I think on this question.