Moving a Palworld save to a dedicated server

Plenty of groups start in four-player co-op from the game, then want to move to a dedicated server keeping their world. It is doable, but not in the way people picture: the world moves, the characters much less well.

What carries over

The world itself — terrain, built bases, chests, assigned Pals — lives in the save files and transfers correctly to a dedicated server.

That is the bulk of what a run represents: the hours of building and breeding are preserved.

Where it breaks

Player characters are identified differently in single player and on a dedicated server. The result after a transfer is usually the same for everyone: the world is there, the bases are there, and each person restarts with an empty character.

This is not a bug but a consequence of how identities are assigned. Community tools exist to re-link characters, with results that vary by game version.

The cautious method

1. Shut the source game down cleanly. Copying files mid-write is the fastest way to corrupt them.
2. Copy the whole save folder, not just the files that look useful. The metadata is part of it.
3. Keep the original untouched. It is your way back, and you will probably need it on the first attempt.
4. Test on the server before announcing the migration. Connect alone, check the world loads and the bases are there.

Whether to do it at all

Worth asking honestly. If your run is a few hours old, starting fresh on the server costs less in time and frustration than the migration. If it is a hundred hours old, the transfer is worth it even at the price of rebuilt characters.

In between, the deciding factor is what you have built: that is the part that cannot be redone in an evening.

After the move

Once the world sits on the server, the save no longer depends on one personal PC. That is the most concrete gain. Our Palworld hosting gives full file access, which makes the transfer possible in both directions and the backups schedulable.