Palworld Server Updates: Handling Breaking Patches

Pocketpair ships updates fast. That’s mostly good news, but it comes with a real operational cost: some patches silently reset your server config, and the bigger ones can break save compatibility entirely. If you’ve been running a Palworld dedicated server for a while, you’ve probably already felt this.

This guide covers the full update workflow: what to back up, where those files live, how to spot save incompatibility before it ruins a session, and how to recover when a patch goes sideways. We’ve run Palworld servers through multiple breaking patch cycles at WinterNode, and this is the process that works.

What Save Files to Back Up (and Where They Are)

The most common mistake is backing up only Level.sav. That file holds world data, but it’s not the whole picture. A complete backup means copying the entire WorldGUID folder.

Your saves live here:

• Linux: Pal/Saved/SaveGames/0/{WorldGUID}/
• Windows: Pal\Saved\SaveGames\0\{WorldGUID}\

To find your WorldGUID, list the contents of Pal/Saved/SaveGames/0/. There will be one folder with a long alphanumeric name — that’s it.

Here’s what’s inside that folder and why each file matters:

Which Config Fields Get Reset by Major Patches

Palworld patches — particularly major version bumps — have a documented pattern of overwriting PalWorldSettings.ini with defaults or blanking specific fields. You need to know which ones to check after every update.

Config file locations:

• Linux: Pal/Saved/Config/LinuxServer/PalWorldSettings.ini
• Windows: Pal\Saved\Config\WindowsServer\PalWorldSettings.ini

These are the fields most commonly reset:

; Server identity - frequently blanked on major patches
ServerName=
AdminPassword=
ServerPassword=

; Network/RCON - often reverted to defaults
RCONEnabled=False
RCONPort=25575
MaxPlayers=32

; Balance multipliers - silently reset on schema-changing patches
ExpRate=1.000000
PalCaptureRate=1.000000
DeathPenalty=All
WorkSpeedRate=1.000000
PalStomachDecreaceRate=1.000000
PlayerStomachDecreaceRate=1.000000
PalEggDefaultHatchingTime=72.000000
bEnableInvaderEnemy=True
bEnablePlayerToPlayerDamage=False

Keep a text file with your working config saved somewhere outside the server directory. After any update, diff it against the current INI. The two minutes this takes has saved us from multiple headaches.

For a full walkthrough of each setting, see the Palworld configuration guide.

Pre-Update Checklist

Do these steps in order, every time, before applying a Palworld patch:

1. Read the patch notes. Pocketpair’s patch notes call out save migration warnings when they exist. Look for mentions of “save compatibility,” “migration,” or “schema changes” before doing anything else.
2. Announce downtime. If other players are on the server, give them warning. A save that’s flushed mid-session can corrupt.
3. Perform a clean shutdown. Use RCON or your panel’s stop button — not a kill or force stop. Palworld needs to flush saves to disk properly. A hard kill can leave Level.sav in a partial write state.
4. Verify save flush timestamps. After the server stops, check the last-modified timestamps on Level.sav and the files in Players/. They should match your shutdown time. If they don’t, wait or restart cleanly before proceeding.
5. Copy your backup. Copy the entire Pal/Saved/SaveGames/0/{WorldGUID}/ folder to a dated location outside the server directory. Example: palworld-backup-2026-04-15-pre-update/.
6. Note your current server version. Check Pal/Saved/Logs/PalServer.log or your panel for the current build number. You’ll need this if you have to roll back via a Steam beta branch.
7. Copy your config. Save a copy of PalWorldSettings.ini to the same backup location.

If you’re on WinterNode, the backups guide covers the automatic backup system and how to trigger manual backups before major patches. One-click backups from the control panel cover most of this in one step.

If you’d rather not manage pre-patch backup routines manually, WinterNode’s Palworld hosting includes built-in backups.

How to Identify Save Incompatibility Before It Ruins a Session

When Palworld loads a save, the startup logs tell you what’s happening. The log file is at:

Pal/Saved/Logs/PalServer.log

Watch for these strings during startup after a major patch:

• SaveGame — general save loading activity, normal on its own
• migration — the server is attempting to migrate save data from an older schema to the new one
• incompatible — the save schema cannot be migrated; this is the bad one
• LevelMeta — version mismatch messages often reference this file specifically

If you see migration messages but the server loads successfully and gameplay looks normal, the migration worked. If you see incompatible or the server crashes during world load, the save cannot be read by the current binary.

Before letting players connect after a major update:

• Check the log for the strings above
• Connect with a secondary account before sharing the IP
• Confirm structures, Pals, and inventory are present before giving the all-clear

Player .sav files and the world file can be independently incompatible. A world that loads fine can still spawn players with blank characters if the player save schema changed. Test both.

Post-Update Verification Steps

Once the server is running and the logs look clean:

1. Connect and confirm the world loads at the correct state — structures intact, Pals in bases, no terrain resets.
2. Check your PalWorldSettings.ini against your saved config copy. Look for every field listed in the section above.
3. Verify AdminPassword is set. Test it with an RCON connection or in-game admin command before assuming it works.
4. Confirm MaxPlayers is correct — a reset here lets more players in than your server is sized for.
5. If bEnableInvaderEnemy was set to False for performance reasons, confirm it’s still False. This setting can materially affect server performance, so verify it after updates if you changed it intentionally.
6. Check ServerName and ServerPassword — a blank server password means your server is publicly accessible.

For help applying the update itself on WinterNode, see how to update your Palworld server.

Recovery Procedure When Saves Break

If you’ve confirmed save incompatibility and the server cannot load your world, you have two paths.

Option 1: Restore from backup and roll back the server version

This is the cleanest recovery if you need the server back up immediately.

1. Stop the server completely.
2. Copy your pre-update backup back to Pal/Saved/SaveGames/0/{WorldGUID}/, overwriting the current files.
3. Roll back the server binary to the previous version. On Steam: right-click Palworld Dedicated Server, select Properties, then Betas, and choose the previous version from the dropdown. On WinterNode, contact support — we can assist with version pinning and rollback.
4. Restore your pre-update PalWorldSettings.ini.
5. Start the server and verify the save loads on the old binary.

This keeps your world intact while you wait for Pocketpair to ship a hotfix or migration tool.

Option 2: Wait for the hotfix

Pocketpair often follows major breaking patches with hotfixes fairly quickly. If your backup is intact and the rollback process feels risky, waiting is a valid option. Check the Palworld Steam news hub and the known issues page for migration tool announcements.

Do not attempt to manually edit .sav files to force compatibility. Palworld’s save format is binary, and manual edits will corrupt the data further.

Keeping a Palworld server stable through Pocketpair’s update cadence is mostly about having a repeatable process before each patch, not firefighting after. Get the backup habit in place and you’ll survive any patch cycle.

On WinterNode, backups are built into the control panel with one-click access to your backup history. If something goes wrong, restoring to a clean pre-update state takes under a minute. At $1.99/GB, a 4GB Palworld server runs $7.96/month.

Get your Palworld server →