Palworld stores three different kinds of progress that players often call a save: the server world, the character attached to that world, and Pals deliberately exported to the Global Palbox. They do not move together. A server wipe replaces the world and its characters; a Global Palbox export is meant to carry selected Pals between worlds when both sides allow it.
This guide starts with a supported dedicated-server setup, then separates backup, wipe, and transfer scenarios so you can choose the safe path. The short rule is simple: stop the server before touching saves, copy the whole save tree rather than one file, and do not treat community character-remapping tools as an official migration feature.
Choose the right way to host
All three can run the same world settings, but ownership and uptime are different.
| Host type | Best for | Main tradeoff |
|---|---|---|
| Invite-code co-op | A small group that always plays with one host | The host owns the world and must be online. |
| Steam dedicated-server tool | A persistent Windows world with the easiest setup | Steam and the server tool share the host machine. |
| SteamCMD on Windows or Linux | A headless server, rented host, or automated updates | You manage the process, firewall, backups, and updates yourself. |
| Official Docker image | Experienced Linux operators using Compose | Pocketpair discourages Docker Desktop because storage I/O can raise save-corruption risk. |
Official dedicated-server baseline
| Resource | Pocketpair guidance | Practical note |
|---|---|---|
| CPU | 4 cores recommended | Fast per-core performance helps busy bases and many players. |
| Memory | 16 GB recommended; more than 32 GB for larger servers | 8 GB can boot but has a higher out-of-memory crash risk. |
| Storage | Fast SSD recommended | Slow storage increases save-corruption risk. |
| Network | UDP 8211 by default | Allow it in the host firewall and forward it when players connect over the internet. |
| Platforms | Steam,Xbox,PS5,Mac by default | Use CrossplayPlatforms to narrow the allowed platforms if needed. |
Set up a clean Palworld 1.0 dedicated server
- 01
Prepare the host
Use a 64-bit Windows or Linux host, reserve SSD space, and confirm that UDP 8211 can reach the machine.
- 02
Install or update the server
Run
steamcmd +login anonymous +app_update 2394010 validate +quit. App 2394010 is the official Palworld Dedicated Server package. - 03
Launch once, then stop
Start
PalServer.exeon Windows or./PalServer.shon Linux. The first run creates the save and configuration directories that do not exist beforehand. - 04
Copy the default settings file
Copy
DefaultPalWorldSettings.iniinto the live WindowsServer or LinuxServer configuration directory. Editing the default file itself has no effect. - 05
Set identity and access
Configure
ServerName,ServerDescription,ServerPassword,AdminPassword,ServerPlayerMaxNum, andCrossplayPlatformsin the copied file. - 06
Enable backups before inviting players
Set
bIsUseBackupSaveData=True, start the server, and confirm abackupdirectory appears in the save-data directory. - 07
Connect and test a full save cycle
Join, build a disposable object, log out, stop the server cleanly, restart, and confirm the world and character return before opening the server to the group.
SteamCMD install and update command
Stop the live server and create an offline backup before running the same command for an update.
steamcmd +login anonymous +app_update 2394010 validate +quitUse the live configuration file
These directories appear only after the server has been started once.
| Host | Live PalWorldSettings.ini path |
|---|---|
| Windows | steamapps\common\PalServer\Pal\Saved\Config\WindowsServer\PalWorldSettings.ini |
| Linux | steamapps/common/PalServer/Pal/Saved/Config/LinuxServer/PalWorldSettings.ini |
Back up and update without losing the world
Announce downtime
Prevent players from reconnecting while the process is stopping or files are being copied.
Stop cleanly
Use the server shutdown command or service manager and confirm the process has exited before copying saves.
Copy the entire saved tree
Keep the world, player records, local data, backups, and configuration together. A lone
Level.savis not a complete restore point.Keep one backup off the host
A second disk or remote object store protects you from drive failure and a broken in-place update.
Update with SteamCMD
Run app 2394010 with
validate, then compare the copied default settings with your live configuration for new parameters.Avoid obsolete 1.0 launch flags
Pocketpair notes that leaving
-useperfthreads -NoAsyncLoadingThread -UseMultithreadForDSunset may improve performance in 1.0 and later.Test restore, not just backup
Periodically restore a copy to a separate instance. A backup you have never loaded is only a hope.
What survives each kind of move or wipe?
| Scenario | Safe expectation | Recommended action |
|---|---|---|
| Official server wipe | The server world, bases, inventory, and world character reset. | Export important Pals to the Global Palbox before the deadline and verify that the destination allows imports. |
| Global Palbox export | Selected Pals are stored separately from the current world; world progress does not travel with them. | Confirm both bAllowGlobalPalboxExport and bAllowGlobalPalboxImport are allowed where you plan to use it. |
| Move a dedicated server to a new host | A complete stopped-server save tree can preserve the same world and character records. | Copy the whole saved directory and matching configuration, then test the clone before changing DNS or inviting players. |
| Single-player character to multiplayer | Pocketpair does not document raw character-file remapping as a supported transfer. | Start a new world character and use the Global Palbox for supported Pal movement when available. |
| Another friend becomes co-op host | Copying only the world can leave player ownership or identity mismatches. | Keep the original host or treat any community conversion workflow as unsupported and work only on duplicate saves. |
Why raw character transfers are risky
A Palworld character is not a portable profile file. It is linked to a specific world and player identity. Moving a world between hosts is different from inserting one character into another world, and a file that looks like the right player record can still point at the wrong identity after a host or platform change.
That is why the safe answer to single-player-to-multiplayer questions is conservative: there is no official character import workflow in Pocketpair's current server documentation. Community editors can rewrite identifiers, but a successful conversion depends on versions, platforms, and the exact source and destination saves. If you experiment, duplicate both saves, keep the originals untouched, and validate inventory, guild ownership, bases, quests, and Pals before anyone continues playing.
Finish the setup
Research sources
The claims in this guide were checked against these current references. Primary sources are marked first.