Palworld server troubleshooting: saves, crashes, lag

Fix common Palworld server problems: the 1.0 save crash, version-mismatch timeouts, corrupted saves after patches, servers that won't start, Pal AI lag, and players who can't connect.

Palworld servers hit a fairly small set of problems, and most have a quick fix once you know which one you are looking at. This page covers what tends to go wrong, starting with the two issues people are hitting most in the days after the 1.0 update.

"Failed to save, failed copy from backup" and players getting dropped

This one arrived with 1.0 and caught a lot of servers, managed hosts and self-hosted boxes alike. The tell is players dropping after a few minutes with "lost connection to host", a black screen if they try to rejoin, and the server log mentioning a failed save or a failed copy from backup. It is the server failing to write its own save file.

On Hostd: restart the server once from the dashboard. That applies the fix on our side and the crashing stops.
Self-hosted: it is a permissions problem. The server process needs write access to its save folder, so run it as the right user rather than as root on Linux, or fix the folder permissions on Windows. Widening the autosave interval reduces how often it trips while you sort it out.

"Connection timed out" or "incompatible version" after an update

Almost always a version gap. Steam updates the game the instant a patch drops, so players jump to the new version while a server that has not restarted is still on the old build, and a new client cannot join an old server. Get the server onto the current version (on Hostd, one restart) and make sure everyone's own game has finished updating. If a self-hosted server still reports the old version after a SteamCMD update, re-run app_update 2394010 validate and check it wrote to the folder the server actually launches from. The full 1.0 update walkthrough is in Updating your Palworld server to 1.0 safely.

Save corruption or world reset after a patch

Easily the most common Palworld server problem, and almost always tied to a Steam patch. Symptom: your world loads but progress is missing, or the server starts on a fresh world.

What to do:

Open your dashboard and head to the Backups tab.
Find the most recent backup taken before the patch landed.
Restore it.

We take daily backups automatically, so there's almost always a good copy. If you know a patch is coming, hit Manual backup beforehand; see Manual backups.

Server won't start after a Steam patch

The Palworld dedicated server's binary version has to match what the client expects. After a patch, our image refetches on restart, but occasionally a node sticks on an older binary.

If your server keeps trying and failing to start after a patch:

Try one full restart from the dashboard.
If it still won't come up, raise a ticket with your server name. We'll force a refresh on our side.

You won't be charged downtime on a patch-related fix.

Lag, stutters, and TPS dips

Palworld lag almost always comes from three places, in this order of likelihood:

Pal AI: every working pal at every base is running pathfinding and task logic. A base with 30 pals on conveyor belts is doing a lot of thinking. Trim the headcount or split work across bases.
Too many bases: each player can have several bases, and each base ticks independently. Communities with a dozen active builders can swamp the CPU.
Save bloat: long-running worlds accumulate drops, structures, and history. Lower DropItemMaxNum in PalWorldSettings.ini and consider an occasional cleanup pass.

Palworld is CPU-thirsty more than RAM-thirsty. If the CPU panel in your dashboard is sitting near the ceiling, you're CPU-bound, and the Elite tier (with priority CPU scheduling) is the lever that helps.

REST API actions stopped working

If the dashboard's announce, save, kick, or ban buttons return an error, it's usually a transient auth issue with the in-container REST endpoint. The fix is almost always a restart:

Restart the server from the dashboard.
Wait for the Ready badge.
Try the action again.

If it persists past one restart, raise a ticket.

Players can't connect

Run through this list in order:

Is the server actually ready? The dashboard status badge shows Ready when the REST endpoint responds, which is the same moment players can actually join. If it shows Starting, wait.
Right address and port? The full join string lives on the dashboard; copy it from there rather than typing from memory.
Password? If you set a ServerPassword in PalWorldSettings.ini, players need it. Share it carefully.
Joining the right way for their platform? Steam and Mac connect with the address; Xbox, PlayStation and Game Pass players join through the in-game community server browser and search for the server by name. See Connecting across Steam, Xbox and PlayStation.
Firewall on their end? Rare, but if one specific player keeps timing out and others connect fine, it's almost certainly local to them.

Full connection walkthrough in Connecting to your Palworld server.

Asking about mods

Palworld does have Workshop and pak-based mods, but they are rough on servers: they break every time the game version bumps, and Pocketpair warned that leftover mod files crash 1.0 servers and can corrupt saves. Our managed image does not run them, on purpose, so your server rides through patches like 1.0 without a mod-shaped outage. PalWorldSettings.ini is your customisation lever, and it covers most of what people reach for mods to do.

Still stuck

Open a ticket from your dashboard with the server name and a rough timestamp of when the problem started. We'll dig into the logs from our side. For console-related questions (Palworld doesn't have a traditional console, but the question still gets asked), see Why is the console blocked on some games?.

Last updated 2026-07-10. Notice a mistake? Tell us.