Skip to main content
PalMods

Updated

Guides/Player Essentials/Servers, Wipes & Save Transfers
Server & savesPalworld 1.0Intermediate

Servers, Wipes & Save Transfers

Set up and back up a Palworld 1.0 dedicated server, understand official-server wipes and the Global Palbox, and avoid unsafe character-save transfers.

14 min read Researched for 1.0 Sources included

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.

01Host model

Choose the right way to host

All three can run the same world settings, but ownership and uptime are different.

Host typeBest forMain tradeoff
Invite-code co-opA small group that always plays with one hostThe host owns the world and must be online.
Steam dedicated-server toolA persistent Windows world with the easiest setupSteam and the server tool share the host machine.
SteamCMD on Windows or LinuxA headless server, rented host, or automated updatesYou manage the process, firewall, backups, and updates yourself.
Official Docker imageExperienced Linux operators using ComposePocketpair discourages Docker Desktop because storage I/O can raise save-corruption risk.
02Requirements

Official dedicated-server baseline

ResourcePocketpair guidancePractical note
CPU4 cores recommendedFast per-core performance helps busy bases and many players.
Memory16 GB recommended; more than 32 GB for larger servers8 GB can boot but has a higher out-of-memory crash risk.
StorageFast SSD recommendedSlow storage increases save-corruption risk.
NetworkUDP 8211 by defaultAllow it in the host firewall and forward it when players connect over the internet.
PlatformsSteam,Xbox,PS5,Mac by defaultUse CrossplayPlatforms to narrow the allowed platforms if needed.
03SteamCMD

Set up a clean Palworld 1.0 dedicated server

  1. 01

    Prepare the host

    Use a 64-bit Windows or Linux host, reserve SSD space, and confirm that UDP 8211 can reach the machine.

  2. 02

    Install or update the server

    Run steamcmd +login anonymous +app_update 2394010 validate +quit. App 2394010 is the official Palworld Dedicated Server package.

  3. 03

    Launch once, then stop

    Start PalServer.exe on Windows or ./PalServer.sh on Linux. The first run creates the save and configuration directories that do not exist beforehand.

  4. 04

    Copy the default settings file

    Copy DefaultPalWorldSettings.ini into the live WindowsServer or LinuxServer configuration directory. Editing the default file itself has no effect.

  5. 05

    Set identity and access

    Configure ServerName, ServerDescription, ServerPassword, AdminPassword, ServerPlayerMaxNum, and CrossplayPlatforms in the copied file.

  6. 06

    Enable backups before inviting players

    Set bIsUseBackupSaveData=True, start the server, and confirm a backup directory appears in the save-data directory.

  7. 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.

04Command line

SteamCMD install and update command

Stop the live server and create an offline backup before running the same command for an update.

Windows or Linux shelltext
steamcmd +login anonymous +app_update 2394010 validate +quit
05File paths

Use the live configuration file

These directories appear only after the server has been started once.

HostLive PalWorldSettings.ini path
Windowssteamapps\common\PalServer\Pal\Saved\Config\WindowsServer\PalWorldSettings.ini
Linuxsteamapps/common/PalServer/Pal/Saved/Config/LinuxServer/PalWorldSettings.ini
06Operations

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.sav is 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 -UseMultithreadForDS unset 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.

07Decision table

What survives each kind of move or wipe?

ScenarioSafe expectationRecommended action
Official server wipeThe 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 exportSelected 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 hostA 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 multiplayerPocketpair 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 hostCopying 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.
08Save ownership

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.

09Continue

Finish the setup

10Verification

Research sources

The claims in this guide were checked against these current references. Primary sources are marked first.

FAQ

Frequently asked questions

Does the Global Palbox survive an official server wipe?

The Global Palbox is separate from the current server world, and current 1.0 players report that exported Pals remain after official-server wipes. Treat that as observed behavior rather than a guaranteed backup contract: export before the deadline, confirm the target server permits imports, and never assume it also saves your character, inventory, base, or world progress.

Can a server disable the Global Palbox?

Yes. Dedicated-server operators can control saving and loading separately with `bAllowGlobalPalboxExport` and `bAllowGlobalPalboxImport`. Check both before planning a move.

Can I transfer a single-player character to a multiplayer server?

There is no officially documented character-import or ID-remapping workflow. The supported clean path is a new character plus Global Palbox transfer for selected Pals when allowed. Community save editors are unsupported and should only be tested on copies.

How do I install a Palworld 1.0 dedicated server with SteamCMD?

Install SteamCMD, then run `steamcmd +login anonymous +app_update 2394010 validate +quit`. Start `PalServer.exe` on Windows or `./PalServer.sh` on Linux once to create directories, stop it, copy the default settings file to the live config path, configure it, enable backups, and restart.

Which port does a Palworld dedicated server use?

UDP 8211 by default. Allow it through the host firewall and forward it on the router when players connect over the public internet. A custom listen port can be set with the official `-port=` argument.

How much memory does a Palworld server need?

Pocketpair recommends 16 GB and more than 32 GB for larger servers. An 8 GB host can boot but has a higher risk of out-of-memory crashes. Use fast SSD storage because slow storage can increase save-corruption risk.