How to Update a Palworld Dedicated Server Without Breaking It

A how to update a Palworld dedicated server search usually starts with a friend who sees a version error after patch day. Use the same install method that already runs your world: check the current patch notes, warn the group, save and stop cleanly, make a backup, update, then inspect the server before you invite anyone back. The steps below cover Steam’s Dedicated Server tool, SteamCMD, and Pocketpair’s official Docker image. They do not assume your settings or mods will survive every game patch unchanged.

Check the patch and prepare a backup before changing server files#

Start by checking whether an update is actually available for the server build and whether the platforms your group uses have a current compatibility note. Palworld’s official notices are dated by patch; a note about one release does not promise the same cross-play behavior for the next one. Write down the source version and the version you intend to install so you can tell whether Steam or Docker updated the expected build.

Before changing any server program files, decide where the backup will live and what it must contain. The dedicated server world is under Pal/Saved/SaveGames/0/<WorldGUID>/; the Windows configuration is under Pal/Saved/Config/WindowsServer/, and Linux uses Pal/Saved/Config/LinuxServer/. Keep the whole world directory, the active PalWorldSettings.ini, and any mod files or configuration your server uses. The official Docker image stores the game data in its Saved directory and the sample Compose file mounts ./Saved into the container, so preserve that same host folder when you update the image.

A copy of only the game executable folder is not a world backup. A Steam file validation checks installed program files; it does not restore Level.sav, test an archive, or repair a world. Keep one copy outside the install directory so a reinstall or container replacement cannot remove both copies together. If you use a panel, confirm which files its backup includes before relying on it for configuration and mods as well as the save.

Warn players, save the world, and stop the server cleanly#

Tell the group when the server will go down, and ask players to leave before the update starts. With the Palworld admin password configured, an authorized player can save the world and schedule a timed shutdown from chat. The official command list documents /Save and /Shutdown [Seconds] [MessageText]; /DoExit force-stops the server, so it is not the graceful option for a routine update.

1. Announce the window

   Post the planned downtime and ask players to log out. If someone is in a boss fight or building, give them time to finish before you start the countdown.

2. Save and schedule the shutdown

   Run /AdminPassword <your-admin-password> if you are not already authenticated, then run /Save. Give players a short warning with /Shutdown 30 Server update starts in 30 seconds and wait for the process to exit.

3. Finish the offline copy

   Once the server has stopped writing to the world, copy the complete world folder, active INI, and mod files to the separate backup destination you prepared. Check that the copied folders and files have non-zero sizes before replacing server files.

official Palworld command list lists the available admin commands and their arguments. If the game never reaches a clean stopped state, investigate that shutdown first; don’t update files underneath a process that may still be saving. Keep your players’ world identifier with the backup so you can distinguish it from an older world folder if more than one save exists.

Update a Palworld dedicated server through Steam, SteamCMD, or Docker#

Use the path that owns the running server files. A fresh install in a different folder is not an update to the server your friends use.

Steam Dedicated Server tool

If you installed Palworld Dedicated Server from Steam’s Library under Tools, let Steam finish that tool’s pending download in its Download Manager before you start the server again. The generic Steam update setting can keep an item updated automatically, update only when launched, or give it higher download priority. Those are Steam client choices; they do not show that the Palworld server can update safely while its process is running. Stop it first, let the tool finish, and check the installed server before reopening it. B18 explains where the Steam tool lives and how to run it.

SteamCMD

Pocketpair documents the anonymous server App ID 2394010 and this command for its documented SteamCMD install path:

steamcmd +login anonymous +app_update 2394010 validate +quit

Run the update against the same SteamCMD installation that contains your active PalServer files. If you installed to a custom directory, follow the existing path and command-order details in the SteamCMD guide; don’t paste a default-path command into a new empty directory. Pocketpair’s example includes validate to check the installed files. It is not a world backup or save-repair command.

Pocketpair’s official Docker image

Pocketpair’s official Compose example pins a game-version tag and keeps Saved mounted outside the container. After the offline backup is in place, stop the existing Compose project, change the image tag to the version you intend to run, and start the same project again:

docker compose down

docker compose up -d

Do not remove or rename the host-side Saved folder while replacing the container. docker compose down followed by up replaces the stopped service with the image named in that Compose project; it does not promise to migrate a world between unrelated mounts. Pocketpair’s official Docker repository recommends backing up first and says Docker Desktop on Windows or macOS is not recommended because of storage I/O limits. Its instructions are separate from community images: for Thijsvanloef-specific environment variables or scheduled updates, use the image-specific guide.

Check the world, settings, mods, and logs after startup#

Start the server and wait for its normal ready message before you test it. Read the latest log for startup errors, confirm the expected server build, and check that the intended world loaded. If you run more than one server, confirm you started the one whose save and configuration you backed up.

Open the active PalWorldSettings.ini and compare it with your backup. Pocketpair’s update instructions do not guarantee that every INI value will be preserved across every update route, so don’t assume the defaults or your custom settings stayed the same. Check the settings that matter to your group, such as the server name, password, cross-play platforms, player limit, and the rates you deliberately changed. If a setting differs, restore only the value you intended after checking the current configuration documentation; don’t replace a new file wholesale with an old template.

Mods need their own compatibility check. Pocketpair’s current mod documentation warns that incompatible mods can crash the server or corrupt saves, and a game update may require a mod update too. Leave a mod disabled if its author has not confirmed support for the new game build. Check the server log before re-enabling it, and keep the pre-update mod files with the backup so you can identify what changed. This article does not establish that a particular mod, loader, or modded save is safe on today’s build.

Pocketpair’s mod documentation describes supported server-side mods and their risks. If the server fails only after a mod loads, use the UE4SS installation guide for the mod-specific recovery path; don’t delete mod files from the only save copy.

Check the current platform notes before troubleshooting a version mismatch#

A version message means you need to check whether the server build and the player’s current build are compatible; it does not prove that all version strings must always be identical. Look at the dated Palworld notice for the server patch, then check the update status on each player’s store. If a console player is on a different build, find an official note about that specific patch before you decide whether to wait, update the server, or ask the player to update their game.

Do not assume that Game Pass or PS5 always updates later than Steam, and do not attribute a delay to certification without a source for that release. Pocketpair’s July 29, 2026 PC hotfix notice explicitly said that cross-play with other platform versions would not be affected by that hotfix. That’s useful for that notice only; it does not prove that another patch will have the same compatibility. Check the official Palworld announcement list and the relevant platform’s own update page each time.

If the official note says the build remains compatible, use that guidance rather than comparing numbers by instinct. If it does not address your platform pairing, say so and wait for a current compatibility statement or update both sides when their stores offer the compatible release. For a player-facing checklist once the current note is clear, link to the platform-specific version-mismatch guide; do not treat updating the server as a fix for an official platform rollout delay.

Choose an update schedule you can verify#

Manual updates give you a chance to wait until your group is ready, back up the world, and read the release notes before changing the server. That matters for a shared world: an automatic update that happens before a console player’s store offers a compatible build can leave the group waiting even when nothing is wrong with the save. Use Steam’s per-item setting or a method-specific scheduled job only when you know how it stops the server, preserves the existing data path, takes a backup, and reports whether the update completed.

Keep the job’s steps visible. A scheduled update should announce downtime when possible, stop gracefully, protect the save and configuration, update the existing install, then start and check the logs. If your method cannot safely do those actions in order, run the update manually. The official Docker image uses a pinned version tag, so changing that tag is an explicit choice; an image pull alone is not a replacement for following its versioned Compose procedure. The third-party Thijsvanloef image has separate boot and cron options, documented in its own update and restart notes. Don’t copy its variables into Pocketpair’s image.

After you have checked the running world, configuration, mods, and patch compatibility, tell the group the server is ready to test. If you’d rather have the backup, player warning, and update-and-restart control together, Game Hosting’s Palworld panel documents that sequence on its Palworld hosting page. A managed panel can handle the server-side update flow; it cannot make incompatible client builds compatible.