Fix Common Palworld Dedicated Server Problems

Most Palworld server problems fall into a short list: players locked out after a patch, settings that do not stick, a server running out of memory, a world that did not move across properly, and the occasional bug Pocketpair has since patched. This page names each one, says what is known about the cause, and points to the guide that has the full steps. Where the cause is a game bug, the fix is Pocketpair's own, and we say so rather than invent a workaround.

Checked against Palworld 1.0.5 (15 September 2026) and Pocketpair's server guide for 1.0.4, October 2026.

Players cannot join after an update

When Pocketpair releases a patch, players on the new build usually cannot join a server still on the old one. Take a backup from the Backups tab, then press Restart so the server installs the current build. The Console prints a [PYW] Running SteamCMD update line while it works. Palworld getting started walks through comparing versions with the Info command.

The server is missing from the community list

Check the status reads Running and search for the exact Server Name from the Startup tab. Xbox and PS5 players find the server only through the community list, so Crossplay Platforms needs those platforms ticked. Steam players can join by address meanwhile.

A setting will not stick

The usual causes are saving while the server runs, a key that Startup manages, or a WorldOption.sav file overriding the settings file. Fix Palworld settings not applying works through them in order.

The server crashes or restarts on its own

Pocketpair says 8 GB "is also bootable, but increases the possibility of server crashes due to out of memory", and lists memory as "16GB" with the note "Recommended for larger than 32GB." Watch RAM in the left rail. If it sits near the limit, the world has outgrown the plan. Fix Palworld server lag and memory growth covers the nightly restart and the settings that cost the most.

Some crashes are Pocketpair bugs it has patched. Its notes list a fix for players being disconnected, and for crashes, during the Panthalus battle on dedicated servers (v1.0.2), and a fix for a server crash when sorting Pals (v1.0.4). Run the newest build, which a restart installs. If a crash repeats on the current build, copy the last lines of the Console and send them to support with the time it happened.

The update did not finish

On start the server checks Steam for a new build. If Steam did not finish, the Console prints [PYW] Steam did not finish updating the game, clears its update record and tries once. If it still fails, it prints a line saying the server is starting on the version it already has. Your world and settings are not touched. Restart once more to try again. If players then cannot join, contact support.

Characters or progress missing

• After moving a co-op world, the host usually loses their character: Fix a missing Palworld character after a move.
• Pocketpair's 1.0.1 notes fixed "an issue where save data could be unintentionally discarded after certain operations", and v0.5.3 fixed dedicated server save data rolling back under certain settings. Run the current build, and press Create backup before big changes.
• To go back to an earlier state, use Restore backup on the Backups tab. A restore overwrites all current server files, stops the server first and starts it again afterwards.

Players with mods cannot join

The server must allow client mods through bAllowClientMod. Palworld 1.0 mods: what works on a server shows where to set it and why server-side mods do not run here.

Lag for one player

If only one player lags, Why is my server lagging? helps you tell a server problem from a connection problem.