PalworldPalworld Server Requirements: RAM, CPU and Disk (2026)
Palworld server requirements: Pocketpair recommends 16 GB RAM and 4+ CPU cores. RAM by player count, why memory grows over time, CPU and SSD needs.
Updated Oct 3, 2026 · 6 min read
On this page
- What are the official Palworld server requirements?
- How much RAM does a Palworld server need by player count?
- Why does Palworld server memory keep growing?
- What CPU does a Palworld server need?
- How much disk space does a Palworld server need?
- How much bandwidth does a Palworld server need?
- Which settings change the requirements most?
- Can you run a Palworld server on your gaming PC?
- FAQ
- The easy option
Pocketpair recommends 16 GB of RAM and a CPU with 4 or more cores for a Palworld dedicated server, on fast SSD storage, with UDP port 8211 open. A server boots on 8 GB, but Pocketpair warns that raises the risk of out of memory crashes. In practice, plan on 12 GB for up to 8 players, 16 GB for up to 16, and 24 GB or more for a busy 32 player world.
What are the official Palworld server requirements?
From Pocketpair's dedicated server requirements:
| Part | Requirement |
|---|---|
| CPU | 4 cores or more recommended |
| Memory | 16 GB recommended. 8 GB boots but makes out of memory crashes more likely. 32 GB or more for large setups |
| Storage | A fast SSD. Pocketpair warns slow storage can corrupt save data |
| OS | Windows 64 bit or Linux 64 bit (Ubuntu, AlmaLinux and others) |
| Network | UDP 8211 by default, port forwarded on a home router |
The server is PalServer, a free program from Pocketpair installed through SteamCMD. It runs without a graphics card.
How much RAM does a Palworld server need by player count?
| Players | RAM | Notes |
|---|---|---|
| 2 to 4 | 8 to 12 GB | 8 GB boots, 12 GB gives room for bases and a day of uptime |
| Up to 8 | 12 GB | Small group with a few bases |
| Up to 16 | 16 GB | Pocketpair's recommended size, right for most worlds |
| Up to 32 | 24 GB and up | Full server or late game bases everywhere |
Player count is only part of it. Palworld memory grows with:
- Working base Pals. Every Pal in a base is simulated: pathing, hunger, sanity and work. With the default 15 workers per base (
BaseCampWorkerMaxNum) and up to 4 bases per guild, a single guild can have 60 Pals working around the clock. - Spread out players. Each player loads the world around them, and wild Pals spawn near each one. Ten players in ten corners of the map cost far more than ten in one base.
- Structures and dropped items. Big builds and floors of dropped loot all stay in memory.
- Raids. Invader raids (
bEnableInvaderEnemy) spawn extra enemies near bases. - Uptime. Memory use climbs the longer the server runs.
Why does Palworld server memory keep growing?
The dedicated server has a long known memory leak: memory use climbs with uptime and only comes back down when the process restarts. Pocketpair's 1.0 release fixed some memory leaks and crashes on dedicated servers, but memory still grows over time, so scheduled restarts remain the standard advice.
What that means for sizing:
- Size for the peak, not the start. A server that uses 8 GB right after a restart might sit at 12 GB or more a few hours later on a busy world.
- Restart on a schedule. Every 6 to 8 hours suits most servers. Busy 32 player worlds may want every 4 hours.
- Watch the trend. If memory reaches the limit before the next restart, the world has outgrown the machine.
Running out of memory is not a slow decline. The server crashes and rolls back to the last save. Our Palworld lag and memory fix covers restart commands and the settings that cut memory use.
What CPU does a Palworld server need?
Pocketpair recommends 4 or more cores, and Palworld does use more than one. But a few busy threads still do most of the work, so single core speed matters as much as core count. A recent desktop CPU with strong per core performance handles a busy server better than an older many core server chip at low clocks.
CPU becomes the bottleneck when:
- Lots of Pals work in many bases at once.
PalSpawnNumRateis raised above 1.0, which adds wild Pals around every player.- Players spread out across the map, so many areas are active at once.
Signs of a CPU limit are base Pals freezing or teleporting, and rubber banding when several players are in different places, even when memory looks fine.
On a self hosted server, the classic tuning flags are -useperfthreads -NoAsyncLoadingThread -UseMultithreadForDS. Pocketpair's current docs suggest leaving them unset may perform better on 1.0 and later, so test with and without.
How much disk space does a Palworld server need?
The server install takes several gigabytes, and the save grows as the world fills up. More important than size is speed: Pocketpair specifically recommends an SSD and warns that slow storage can corrupt saves. The server writes the world regularly, and with bIsUseBackupSaveData=True (the default) it also keeps its own backups, which adds disk writes. Pocketpair also discourages running the server under Docker Desktop for the same storage performance reason.
Leave a healthy margin for backups. A good rule is enough free space for several full copies of your save folder.
How much bandwidth does a Palworld server need?
Each player needs a steady connection rather than a fast one. For a self hosted server, the upload matters most: if it is saturated by streaming or cloud backups, every player rubber bands. ServerReplicatePawnCullDistance controls how far away Pals are synced to players. Lowering it from the default 15000 to around 10000 cuts network and CPU load, at the cost of Pals appearing closer.
Which settings change the requirements most?
| Setting | Default | Effect on load |
|---|---|---|
BaseCampWorkerMaxNum |
15 | More workers per base means more memory and CPU |
BaseCampMaxNumInGuild |
4 | More bases per guild multiplies everything above |
PalSpawnNumRate |
1.0 | More wild Pals around every player |
bEnableInvaderEnemy |
True | Raids spawn extra enemies near bases |
DropItemAliveMaxHours |
1.0 | Shorter means dropped items vanish sooner |
Keeping base limits sensible from day one is much easier than taking Pals away from players later. Our best Palworld server settings has values that hold up on bigger servers.
Can you run a Palworld server on your gaming PC?
You can, but the numbers add up fast. The game itself wants plenty of memory, and the server wants 16 GB on top for a comfortable world. A PC with 32 GB can host a small group while you play. With 16 GB total, expect stutter and crashes as the world grows. The world is also only online while that PC is on. If that is a problem, see how to play Palworld with friends for the alternatives.
FAQ
How much RAM does a Palworld server need?
Pocketpair recommends 16 GB. 8 GB boots but is prone to out of memory crashes, and busy 32 player worlds do better with 24 GB or more.
Can a Palworld server run on 8 GB of RAM?
It can start, but Pocketpair warns it makes out of memory crashes more likely. It only suits a couple of players with frequent restarts.
How many CPU cores does a Palworld server need?
Pocketpair recommends 4 or more. Single core speed matters too, because a few busy threads do most of the work.
Why does my Palworld server use more RAM over time?
The server's memory use grows with uptime and with the number of working Pals and structures. A scheduled restart every 6 to 8 hours clears it.
Does a Palworld server need an SSD?
Yes. Pocketpair recommends a fast SSD and warns that slow storage can corrupt save data.
The easy option
Our Palworld plans follow the same sizing: Starter is 12 GB for up to 8 players at 29.99 USD a month, Standard is 16 GB for up to 16 at 39.99 USD, and Pro is 24 GB for up to 32 at 59.99 USD. Each server saves and restarts itself with a two minute warning every 8 hours by default, and early if memory reaches 90%, so the leak never catches you out. You can upgrade later without losing the world.
Skip the setup. Your own Palworld server.
Then $29.99/mo. Just trying it? $7.50 for 3 days