Palworld

Palworld guides

By the New Games Guide team · Last updated 2026-08-02

Palworld is a survival-crafting game wrapped around a creature-collection loop: you catch Pals with spheres, put them to work on a base, and use them as mounts, weapons and factory labour. That mix is exactly why it breaks in interesting ways. A Pal is simultaneously a creature, a worker, an item in your storage and a record in your save file — and when one of those four copies falls out of sync, you get the bugs this section exists to fix.

The three failure modes almost every Palworld bug falls into#

Once you have debugged enough Palworld saves, the reports stop looking varied. Nearly everything lands in one of these buckets, and knowing which bucket you are in tells you which fix to try first.

1. World-state desync (multiplayer). In co-op and dedicated-server play, the host owns the world and clients own their character. When those disagree — because of packet loss, a mid-session patch, or a mod on one side only — you get rubber-banding, Pals that vanish on reload, chests that show empty, and hard disconnects at a specific trigger. The fix is almost never on the client.

2. Quest-flag corruption (softlocks). Palworld's quests set flags on your save. If the game saves between a flag being set and the object that flag refers to being spawned — which is what an autosave during a cutscene or a crash mid-dialogue does — the quest is now waiting for something the world will never produce. You are not stuck because you missed a step. You are stuck because the save is internally inconsistent, and no amount of replaying will clear it.

3. Cache and shader staleness (visuals and crashes). Palworld ships compiled shader caches that get invalidated on patch day and on GPU-driver updates. A stale cache is the single most common cause of "it worked yesterday, today it crashes on load" and of the texture and lighting artifacts people report after an update.

Where to start#

If you are here with a specific problem, jump straight to it:

• Kicked out of a friend's world, or dropped at the same point every time — Panthalus disconnect fix
• A quest NPC or objective will not advance — First Islander softlock · Captured Adventurer softlock
• A Pal you definitely caught is gone from the box — Victor / Shadowbeak disappearing
• An achievement did not pop even though you met the condition — Predator Hunter achievement fix
• Flickering, black textures or broken lighting near the World Tree — World Tree graphics fix

How Palworld saves actually work#

Understanding this makes every recovery guide on this site make sense.

A Palworld world is not one file. It is a folder containing Level.sav (the world: bases, containers, Pals in the world, quest flags), LevelMeta.sav (the world's metadata), and one .sav per player under Players/. Your character — inventory, level, tech points, captured Pals — lives in the player file. The world lives in Level.sav.

That split is why two things are true that surprise people:

• You can rescue a character from a broken world. Copy your player .sav into a fresh world folder and you keep your level and gear, losing only base construction.
• You cannot fix a broken character by resetting the world. If the corruption is in your player file, a new world inherits it the moment you copy the file across.

Back up the whole folder, not one file. The game rewrites several of them together, and a mismatched set is worse than either save alone.

Multiplayer: co-op world vs dedicated server#

Most disconnect reports come down to people not realising which of these they are on.

Invite co-op runs the world on the host's machine and routes traffic through the platform's relay. It needs no port forwarding, caps out around four players, and dies the moment the host alt-tabs into a heavy application. Stability is bounded by the host's upload bandwidth and CPU.

Dedicated server runs the world as its own process, with its own save folder, and stays up when nobody is online. It is dramatically more stable for four-plus players and for anyone building large bases, because base simulation is the single heaviest thing in the game and it is no longer competing with someone's render thread.

If your group has more than three people or more than two bases, moving to a dedicated server solves a whole category of problems permanently. It is the recommendation we end up giving in almost every multiplayer troubleshooting thread.

Patch-day routine#

When a Palworld update lands, do these four things before you report a bug — they clear the majority of post-patch reports on their own:

1. Let the update finish on every machine. In co-op, a host on 1.0.2 and a client still on 1.0.1 will connect and then fail in confusing ways rather than refusing outright.
2. Delete the shader cache. Remove %LOCALAPPDATA%\Pal\Saved\Shaders and let it rebuild. Expect one stuttery session afterwards; that is the rebuild, not a new bug.
3. Disable mods and Pal-editing tools. Save editors in particular write fields the new version may read differently. Re-enable them one at a time after you confirm a clean load.
4. Load the save once solo before inviting anyone. If it loads solo and fails in co-op, the problem is network or version, not your save — which cuts your search space in half.

FAQ#

Does verifying game files delete my Palworld save?#

No. Verification only compares and repairs installed game files. Saves live in %LOCALAPPDATA%\Pal\ on Windows, which the installer does not touch. It is one of the safest troubleshooting steps available, which is why it appears early in most of our checklists.

Will rolling back to an older Palworld version fix a broken save?#

Rarely, and it can make things worse. Saves written by a newer build may not load correctly on an older one, and some updates migrate save structures irreversibly. Restore a backup from before the patch instead — that is a supported path, and a version rollback is not.

Can I move a co-op world to a dedicated server?#

Yes. Copy the world folder from the host's SaveGames directory into the server's save location and point the server config at it. Player files come across too, so everyone keeps their character. Do it with the server stopped, and keep the original folder untouched until you have confirmed the server world loads.

Why do my Pals stop working at base when I walk away?#

Bases only simulate fully while a player is inside their radius. Away from base, work is approximated and some tasks pause entirely. Pals standing idle when you return usually means a work suitability mismatch or a full storage container, not a bug — check the container first.

All Palworld guides