Update the installation that actually runs your Palworld server, after explicitly saving, stopping it and protecting its persistent data. Then check the running version, the existing world and an established player's character. A completed download is only the middle of the maintenance.
This guide covers an existing Windows or Linux dedicated server on its normal public release. SteamCMD, the Steam desktop tool and Pocketpair's official Docker image use different update paths. Pick the one that created your instance; do not run a second updater against files managed by a panel or container.
Record what is running before changing it#
Find the executable or container, installation directory, operating-system account, effective persistent-data directory and service or launcher. Record the running server version and the clients' versions. If an already configured private REST connection is available, its info response supplies version and worldguid; otherwise retain the available server information and a known in-world checkpoint.
Note the players' platforms, launch arguments, mods and any custom loader. Current Palworld server documentation supports Steam, Xbox/Microsoft Store, Mac and PS5 crossplay, but Xbox and PS5 players need community-server listing. Preserve that startup mode and the configured CrossplayPlatforms list. An update is not a reason to replace these with defaults.
Check the relevant release notes and whether the required client update is available to every platform in your group. When a client cannot join because of a version mismatch, compare the actual installed builds instead of assuming every storefront released the patch simultaneously.
Save, stop and protect the entire persistent tree#
Schedule downtime and temporarily suspend jobs that can restart or update this instance. Ask players to finish actions and disconnect. Use explicit /Save followed by the normal shutdown procedure described in saving before shutdown. Confirm the game process has exited before copying its data or downloading replacement files.
For a direct installation, protect the complete Pal/Saved directory beneath the actual server installation. This retains the save tree and effective configuration together. Preserve custom startup scripts, service definitions, environment settings and mods stored outside it too. Keep a recoverable copy of the previous server release when rollback matters; having an old save without a compatible executable is an incomplete rollback plan.
Copy the backup outside the installation and keep an off-host copy. Check that the archive can be read or extracted into a separate directory. Reserve enough free space for both that copy and the update. Do not remove your only older known-good backup to make room for the new one.
For Docker, locate the host directory or volume mapped to the game's Saved directory. Pocketpair's sample maps ./Saved into /pal/Package/Pal/Saved. A different Compose working directory can resolve that relative host path elsewhere and present an empty save tree to an otherwise healthy new container.
Update through the existing installation method#
SteamCMD installation#
Run the installed SteamCMD as the account that owns the server files. These are interactive SteamCMD commands, not shell commands. Replace the example path with the verified existing installation:
force_install_dir /srv/palworld/server
login anonymous
app_update 2394010
quit
2394010 is the dedicated-server application. Wait for SteamCMD to finish and check its result before starting the game. If you intentionally use another branch, follow that branch's current developer instructions and confirm the clients use a compatible release; do not silently move a test server to public.
The example performs an update without an extra validate pass. Pocketpair also documents validation for installation. File repair does not restore a missing world, and protected local settings remain necessary whichever update or repair operation you choose.
Steam desktop tool#
Stop Palworld Dedicated Server, update that Tools-library entry and launch the intended instance again. Updating the Palworld client alone does not update a separate dedicated-server installation. Retain your chosen launch options rather than starting an unrelated shortcut.
Official Pocketpair Docker image#
Follow the official image workflow: preserve Saved, stop the deployment, change the image tag to the intended game release and start it again with the same persistent mapping. Use an explicit published tag and ensure that image is actually available locally. Do not expect restarting an unchanged tag to select a new release, or run SteamCMD inside the official image as though it were a community image with an update-on-start script.
Check the new process and the old progress#
Start through the original service or launcher. Confirm it runs the intended release and retains its working directory, account, port and community-listing options. Compare the effective PalWorldSettings.ini with your protected copy; the configuration lives under Pal/Saved/Config/WindowsServer or LinuxServer. Editing DefaultPalWorldSettings.ini does not change the running world's settings.
Join with an established player. Verify the expected base, character, inventory and a recent recognizable change. Then make a small reversible change, save, perform one controlled restart and confirm it persists. A live process, an open port or a server name appearing in the list does not establish this.
If the server still reports its old version, inspect the executable path or image actually launched. If players see character creation or a different world, stop and preserve that state before selecting or restoring data. If the process crashes during startup, retain logs and check the release compatibility of mods and loaders. Repeated updates or deleting saves will not distinguish these causes.
Keep the pre-update archive intact while investigating. Restoring an earlier release may also require its matching pre-update save; never assume a save already opened by a newer version can be downgraded safely.
When the server runs on your own VPS, Nexardo can provide a shared administration interface for your infrastructure. The update window still needs an identified instance, a verified backup and a check that the expected progress survives.
