We are your new 5-Star Hosting Company. At least according to ★ Trustpilot

Following along with a Palworld server? Deploy yours in minutes.

All servers come with a 24-Hour Trial, Free Backups, and 40Gbps DDoS Protection included!

Use code SAVE15 to take 15% OFF Your First Invoice with ChicagoServers! Limited Time!
Palworld guide

Palworld Server Lag and Crashes: How to Fix Them

By the ChicagoServers team · Updated · 6 min read

Most Palworld server lag and crashes come down to three things: not enough memory, memory that keeps growing until the process dies, and load from too many bases, Pals and workers. Check RAM first, watch whether it climbs over time, then reduce load with the settings Pocketpair documents. A scheduled restart is the standard practical safeguard, and on ChicagoServers it is a task on the Schedules tab.

Facts below come from the official Palworld server documentation (version 1.0.4 when checked in November 2026). Where something is community knowledge rather than official guidance, this guide says so.

Quick answer
  • Pocketpair lists 16 GB RAM as the requirement and says 8 GB can boot the server but raises the chance of out-of-memory crashes. Your RAM comes from your plan; watch Memory at the top of your server page.
  • Admins widely report that memory climbs the longer the server runs. There is no official restart interval, so use the live Memory reading to pick one.
  • Warn players, then restart on a schedule from the Schedules tab. A restart from the panel saves the world first.
  • Load settings to lower, in World settings (PalWorldSettings.ini) on the Configs tab: bases per guild, workers per base, Pal spawn rate and the Pal sync distance.
  • Keep client and server on the same game version (Update now on the Steam update bar), and check the Troubleshoot tab after a crash.
On this page
  1. Step 1: check you have enough hardware
  2. Step 2: memory growth and scheduled restarts
  3. Step 3: reduce the load the world creates
  4. Step 4: startup arguments
  5. Step 5: keep versions in step
  6. Step 6: reading what the server tells you
  7. If the save is damaged
  8. Frequently asked questions

Step 1: check you have enough hardware

The official requirements page recommends 4 or more CPU cores and lists 16 GB of RAM, noting that 8 GB can start the server but raises the possibility of out-of-memory crashes. It recommends a fast SSD and warns that slow storage may corrupt save data. The server listens on UDP port 8211 by default; on ChicagoServers the panel assigns your port, shows the address at the top of the page and under Network on the Startup tab, and there is nothing for you to open. CPU is shown in cores (1.00 means one full core busy) next to Memory and Players at the top of your server page, and the Analytics tab charts players and CPU from 24 hours to 90 days.

  • If the process disappears with no clear error as memory approaches the limit, that pattern points to an out-of-memory kill. The Troubleshoot tab lists crashes and failed starts from the last 14 days with the likely cause.
  • If the server is smooth empty but laggy with players, suspect CPU load from bases, Pals and workers.

Hosting with ChicagoServers? The Palworld server hosting page lists what is included, such as free server backups and SFTP file access.

Step 2: memory growth and scheduled restarts

Many admins report that Palworld server memory usage rises steadily over hours of uptime rather than leveling off. Pocketpair's documentation does not publish a restart interval or describe the cause, so treat the following as community practice, not an official rule.

  • Watch Memory at the top of your server page across a busy session. A steady climb toward the ceiling means you need regular restarts.
  • Choose a restart schedule that keeps the server well below the ceiling, with a margin, at off-peak hours. Intervals admins report range from a few hours to daily, depending on RAM and the size of the world.
  • Always warn players first.

To set up the restart on ChicagoServers, open the Schedules tab and follow these steps:

  1. Name the task and pick the time

    Under Add a scheduled task, name it and choose When (every day, days of the week, every few hours and so on). Times are Chicago time.

  2. Warn players

    Click Add a step, choose Send console commands and enter the broadcast below.

  3. Wait

    Add a step, Wait 5 minutes.

  4. Restart

    Add a step, Restart the server. Restarting from the panel saves the world first and starts the server again.

  5. Save the task

    Click Add task. Use Run now on the task list to test it.

Admin command from the official docs, for the Send console commands step or the Console tab. /Shutdown and /Save also exist in game, but the Restart the server step is the panel's way
/Broadcast Restarting in 5 minutes

The game's REST API, when enabled with RESTAPIEnabled=True, also has save and shutdown endpoints and uses HTTP basic authentication. The docs say it is not designed to be exposed to the internet. On ChicagoServers you do not need it for restarts; use the Schedules and Console tabs.

Step 3: reduce the load the world creates

The official configuration reference flags these settings as affecting performance. Change them in World settings (PalWorldSettings.ini) on the Configs tab (Settings view or Text), click Save, then Restart. Lower them one at a time and observe.

SettingWhat the docs say
BaseCampMaxNumInGuildBases per guild; default 4, max 10. Higher values add processing load.
BaseCampWorkerMaxNumMaximum Pals per base, up to 50. Higher values add load.
BaseCampMaxNumTotal bases allowed on the server.
PalSpawnNumRatePal spawn rate. The docs note it affects performance.
ServerReplicatePawnCullDistanceDistance in cm from players at which Pals sync; range 5000 to 15000.
MaxBuildingLimitNumPer-player building cap. 0 means unlimited.
PhysicsActiveDropItemMaxNumMaximum dropped items that use physics.
bIsUseBackupSaveDataWorld backups; the docs note it increases disk load.

Some admins also report that disabling raids with bEnableInvaderEnemy=False reduces load. That is a community observation, not documented guidance, so test it on your own server.

Step 4: startup arguments

The official arguments page lists -useperfthreads -NoAsyncLoadingThread -UseMultithreadForDS as performance-related flags and states that in v1.0 and later, leaving this parameter unset may improve performance. Many older guides tell you to add them, so leaving them out is worth testing if you copied an old startup line. -NumberOfWorkerThreadsServer=X sets the worker thread count and works with those flags.

On ChicagoServers you do not edit the startup line. The Startup tab has fields for the server name, description, passwords and community listing, but no field for these flags, and Extra launch options and the command line are staff-only. If you want a flag added or removed to test performance, contact support.

Step 5: keep versions in step

Client and server need to run the same game version. After a Palworld patch, click Update now on the Steam update bar; a running server stops and starts again by itself. A server left on the old build can refuse updated clients. If something looks wrong afterwards, Validate on the same bar repairs the game files. If crashes began right after you added mods or changed versions, remove the mods first and re-test.

Step 6: reading what the server tells you

Palworld's dedicated server writes events to its console output. On ChicagoServers, read the last lines on the Console tab. The Troubleshoot tab shows what its checks found, Crashes and failed starts for the last 14 days with the likely cause, and Players leaving to show who dropped.

  • Note the last lines before a crash and compare the time with the Memory reading and the Analytics tab.
  • Crashes at the same moment every time, such as the same login or area, point to a bad save or a specific base.
  • Crashes only after hours of uptime with climbing memory point to memory pressure.
  • Crashes right after a patch point to a version mismatch or mods.

If the save is damaged

With bIsUseBackupSaveData on, the server keeps rolling backups in a backup folder inside the save data directory: 5 saves every 30 seconds, 6 every 10 minutes, 12 every hour and 7 every day. To use them, stop the server first so it doesn't write over the files you just restored, then copy files back on the Files tab.

The panel's own backups are the safer fallback. On the Backups tab, click Restore next to a backup under Your backups, choose Put it back (the server stops, its files are replaced and it starts again if it was running) and leave Save the current files as a restore point first ticked. Set up Automatic backups there too, and star a backup you want to keep. Keep a copy of important saves somewhere off the server as well.

Frequently asked questions

How much RAM does a Palworld dedicated server need?

The official requirements list 16 GB. Palworld can boot on 8 GB, but the docs warn this increases the possibility of out-of-memory crashes. Your RAM comes from your plan; watch the Memory reading at the top of your server page.

Why does my Palworld server get laggy over time?

Admins widely report memory climbing as uptime increases. Watch the Memory reading and restart on a schedule (Schedules tab) before it reaches the limit; there is no official interval.

Which settings reduce Palworld server lag?

Lowering BaseCampMaxNumInGuild, BaseCampWorkerMaxNum, PalSpawnNumRate and ServerReplicatePawnCullDistance in World settings on the Configs tab, which the official docs flag as performance-related.

Should I use -useperfthreads on a Palworld server?

The official docs say that in v1.0 and later, leaving -useperfthreads, -NoAsyncLoadingThread and -UseMultithreadForDS unset may improve performance. Customers can't edit the startup line on ChicagoServers, so contact support if you want to test with and without.

We are your new 5-Star Hosting Company. At least according to ★ Trustpilot

Following along with a Palworld server? Deploy yours in minutes.

All servers come with a 24-Hour Trial, Free Backups, and 40Gbps DDoS Protection included!

We offer quality support, a detailed knowledgebase, video tutorials on most topics, and even live support in case you prefer a live human.

Use code SAVE15 to take 15% OFF Your First Invoice with ChicagoServers! Limited Time!