Palworld Server Save Not Loading After an Update? How to Fix It

When a Palworld dedicated server will not load its save after an update, it is almost always one of three things: the server is pointing at a different world folder and quietly made a new world, an old mod is crashing the load, or the save was damaged when the server was stopped mid write. Your world is usually still on disk. Check DedicatedServerName first, then remove mods, then restore from the server's own backup folder.

What you are seeing

Match the symptom before you change anything:

Take a full copy of Pal/Saved before trying any fix. Every step below is safe if you have that copy.

Where the world lives

Pal/Saved/
  Config/LinuxServer/GameUserSettings.ini    (WindowsServer on Windows)
  Config/LinuxServer/PalWorldSettings.ini
  SaveGames/0/<world ID>/
    Level.sav            the world: bases, Pals, items, guilds
    LevelMeta.sav        world name and info
    Players/             one .sav per player character
    WorldOption.sav      optional, old settings baked into the save
    backup/              automatic backups the server writes

The world ID is a long string of letters and numbers. A server can have several world folders side by side, and only one loads.

Fix 1: Point the server back at your world

GameUserSettings.ini holds this line:

[/Script/Pal.PalGameLocalSettings]
DedicatedServerName=0A1B2C3D4E5F67890A1B2C3D4E5F6789

That value picks which folder in SaveGames/0/ loads. If it is missing, empty or changed, the server creates a new world folder and loads that instead. Updates sometimes reset this file, and it also happens when a fresh install replaces the config.

1. Stop the server.
2. Open SaveGames/0/ and list the folders. Your real world is the one with the large Level.sav and a full Players folder. The new empty world was created today and is small.
3. Copy your real folder's name into DedicatedServerName.
4. Start the server and join.

Leave the new empty folder alone until you have confirmed your world loads, then delete it.

Fix 2: Remove old mods

Big Palworld patches change the game's code, and mods built for the old version often crash the server on load. Pocketpair warned about exactly this before 1.0: old mod files can crash the game or damage saves even when switched off. On a modded Windows server:

1. Stop the server.
2. Move the mod files out of the server folders, including UE4SS and anything in the Mods or LogicMods folders under Pal/Binaries and Pal/Content/Paks.
3. Start the server without mods.

If the world loads without mods, add them back one at a time once each mod has an update for the new version. The best Palworld mods guide covers which mods are server side and how to keep them current.

Fix 3: Restore the server's own backup

Palworld dedicated servers write rolling backups of the world into the backup folder inside each world folder, with a folder per backup named by date and time. If Level.sav is damaged, the server may crash on load or load with missing bases.

1. Stop the server.
2. Open SaveGames/0/<world ID>/backup/world/ and find the newest backup from before the update.
3. Copy its Level.sav, LevelMeta.sav and Players folder.
4. Paste them into the world folder, replacing the current ones (you made a copy of Pal/Saved first).
5. Start the server.

If the newest backup also fails, step back to the one before it. A backup from a few minutes before the update loses very little.

This kind of damage usually comes from the server being killed while saving. Always save and shut down cleanly before updates: Save then Shutdown 30 Updating over RCON, or the panel's stop button.

Fix 4: Players start new characters

When the world loads but some players get character creation:

• Their file is missing. Check Players/ for their .sav. If a backup has it and the live folder does not, copy it back.
• They joined from a different platform or account. Characters are tied to the player's ID. Joining from a different account creates a new character.
• The world came from co-op or another server. The host's character in a co-op world has a special ID. Moving co-op worlds needs the steps in transferring a co-op save.

Fix 5: Settings changed after the update

If the world loads but rates, death penalty or raids feel different, the update did not touch your save. Since 1.0, the dedicated server's default world settings match single player Normal, so a server running on defaults feels different after updating. A WorldOption.sav in the world folder also overrides your ini. Both are covered in Palworld server settings not working.

Avoid it next patch

1. Save and stop the server cleanly before updating.
2. Copy Pal/Saved somewhere safe.
3. Remove mods until they are updated for the new version.
4. Update, start, and check DedicatedServerName still points at your world.

On a GamezServers Palworld server, Update on start keeps the server on the current version, the stop button saves and shuts the server down properly, one click backups cover all of Pal/Saved, and the file manager makes Fix 1 a two minute job. For a group server that just works on patch day, see the Palworld server for friends page.

FAQ

Did the Palworld update delete my world?

Almost never. Updates replace program files, not saves. Check SaveGames/0/ for your world folder and point DedicatedServerName at it.

Where are Palworld server backups?

Inside each world folder, in backup/world/, one folder per backup named by date and time. Keep your own copies too.

Why does my Palworld server crash when loading the world?

Usually an outdated mod or a damaged Level.sav. Remove mods first. If it still crashes, restore Level.sav from the newest backup.

Can I load a newer Palworld save on an older server?

No. Saves written by a newer version may not load on older servers. Update the server instead.