Move your Palworld co-op world to a dedicated server

Palworld co-op is how most groups start: one person hosts, friends join, everyone builds a base and it is great - right up until the host has to go to bed. A co-op world only exists while the host is playing, which means your whole group's progress runs on one person's schedule and one person's PC. Moving that world to a dedicated server fixes this for good, but thanks to a quirk in how Palworld stores saves, the move is not a simple copy-paste. Here is what is involved, and how InstantNode's Save Manager does the hard part for you.

The limits of co-op

1. The host has to be online. No host, no world. Different time zones or work schedules turn the server into a part-time one.
2. Co-op caps at four players. A dedicated server raises that ceiling dramatically.
3. Performance rides on the host's PC. The host is rendering the game and serving everyone else at the same time, on a home upload link.
4. The world lives on one machine. One failed drive, and the base you spent 200 hours on is gone.

A dedicated server runs 24/7, lets anyone drop in whenever they like, and keeps the world independent of any single player's hardware.

Why you can't just copy the save folder

Palworld stores a world as a folder: Level.sav for the world itself, plus a Players directory with one file per character, named after that player's GUID. Here is the trap: in a co-op world, the host's character is stored under a special local GUID - a string of zeros ending in 1. On a dedicated server, that same person connects over the network and is assigned a completely different, real GUID.

Copy the folder over unchanged and everyone else is fine - but the former host logs in to a brand-new character. Their pals, inventory and progress are still inside the save, stranded under the old GUID. Fixing it means remapping the host's GUID inside the save files, which historically required community-made save tools, a Python environment, and a healthy tolerance for reading GitHub issues at midnight.

The built-in way: the Save Manager

InstantNode's Palworld servers include a Save Manager in the panel that covers the whole move:

1. World upload: zip your co-op save folder and upload it straight to the server.
2. Co-op save migration: the built-in migration remaps the host GUID so the former host keeps their character, pals and progress - no external tools, no Python.
3. Backups: snapshot the world before and after, and restore any backup if something goes sideways.

Step by step

1. Find your co-op save. On Windows it lives under %LOCALAPPDATA%\Pal\Saved\SaveGames\<SteamID>\<WorldFolder> - the world folder is the one containing Level.sav.
2. Zip the world folder while Palworld is closed, so nothing is written mid-copy.
3. Deploy a Palworld server. InstantNode game servers start at €4.99/mo on Ryzen 9 5950X hardware, with free DDoS protection included.
4. Upload the zip in the Save Manager and let it replace the fresh default world.
5. Run the co-op migration from the Save Manager and follow the prompts so the former host's character is remapped to their new server identity.
6. Join and verify. Everyone connects, the ex-host checks pals and inventory, and you take a first backup as the new baseline.

Tune the world while you're at it

A dedicated server also unlocks proper server-side configuration: XP and capture rates, difficulty, day/night speed, death penalty and more, all living in PalWorldSettings.ini. InstantNode's panel includes a visual settings editor, so you are choosing options from a form instead of hand-editing INI syntax. If you want to know what each option actually does before you touch it, we broke them down in our Palworld dedicated server settings guide.

Common questions

Do the other players keep their characters?

Yes. Guests in a co-op world already have regular player GUIDs, so their files carry over as they are - only the host's identity needs remapping, which is exactly the part the migration handles.

Can we go back to co-op later?

You can download backups of the server world at any time, so your data is never locked in. Moving a dedicated save back into co-op involves the same GUID quirk in reverse, though, so treat the move as one-way unless you enjoy save surgery.

Two tips before you switch

First, match versions: update everyone's game client and migrate when the server is on the current build, not in the middle of an update week. Second, keep the original co-op save on the host's PC until the group has played a few sessions on the new server - it costs nothing and it is the ultimate fallback. After that, the Save Manager's backups take over, and "can someone host tonight?" leaves the group chat for good.