Lag, crashes and scheduled restarts
A Palworld server that lags more and more over the hours, or that crashes after a long session, is a known behavior of the game itself — not an infrastructure problem. This page explains the cause and the recommended fix.
Palworld's memory leak
The Palworld dedicated server suffers from a documented memory leak: its RAM usage grows steadily with uptime and player count. After several hours:
- The server becomes slower and slower (lag, latency, rubber-banding)
- It may eventually crash or be killed for lack of memory
- Performance returns to normal after a restart
This memory leak is a game-side problem, present on every host and even in self-hosting. Upgrading your plan pushes the deadline back but doesn't fix the cause: the server will always degrade eventually without a restart. The real solution is a regular automatic restart.
The fix: a daily automatic restart
Restarting the server once a day (e.g. at night, during low traffic) clears the memory and resets performance. This is the recommended practice for any Palworld server.
The Game Panel includes a scheduler (Schedules) to automate this:
- Log in to your Game Panel:
- Select your Palworld server
- Go to Schedules → Create Schedule
- Configure a daily restart, for example at 5:00 AM:
- Minute:
0 - Hour:
5 - Day of Month:
* - Month:
* - Day of Week:
*
- Minute:
- Add a task: New Task → Action Send power action → Payload restart
- Save
The full scheduler configuration procedure is described in Configure automatic restart. Pick an off-peak time (night) so you don't disturb players.
For a very busy server, two restarts a day (e.g. 5 AM and 5 PM) may make sense.
Is it a game or infrastructure problem?
Before opening a ticket, a few pointers to tell a game-side issue from an infrastructure-side one:
| Symptom | Likely origin |
|---|---|
| Lag that worsens over several hours, gone after a restart | Game (memory leak) — automatic restart |
| Crash after a long session | Game (memory exhausted) |
| Identical lag right from startup, continuously | To investigate (mods, plan, network) |
| Server unreachable, panel inaccessible | Infrastructure — open a ticket |
Heavy .pak or UE4SS mods worsen memory usage. If the problem appeared after adding a mod, disable it to check — see Install PAK mods.
When to contact support
If, despite a daily automatic restart, the server stays unstable within the first few minutes, or if the panel is inaccessible, it may be an infrastructure problem. In that case open a ticket from your client area, specifying:
- The time of the incidents
- Whether an automatic restart is configured
- Any installed mods