Palworld
Palworld Server sizing & resource guide
How to pick the right RAM and CPU amounts for your Palworld server.
This guide lets you figure out how much RAM and CPU power your Palworld server will likely need.
Palworld is one of the more demanding survival games to host. Memory use grows with player count, captured Pals and the number/size of bases — and the game is known to slowly leak memory over long uptimes. Size with headroom and use scheduled restarts.
HypeServ uses high‑frequency Ryzen 9 CPUs and DDR5 RAM for all servers to maximize single‑core performance, which Palworld's world simulation benefits from significantly.
TL;DR — Standard RAM sizes for common scenarios
If you just want a rough idea, start here:
| Use case | RAM (est.) | CPUs | Notes |
|---|---|---|---|
| Small private world, 2–6 players | ~6–8 GB | 3–4 Cores | A few friends, limited bases |
| Friends / small community, 4–16 slots | ~12–16 GB | 5–6 Cores | Official recommendation is 16 GB |
| Large community, many active bases | ~16–24 GB | 6–8 Cores | Lots of Pals working across many bases |
| Full 32 slots or modded server | ~24 GB+ | 8+ Cores | Max default player cap and/or Steam Workshop mods |
Palworld's default maximum is 32 players (
ServerPlayerMaxNum). Higher player counts increase both RAM and CPU load significantly.How Palworld uses resources
Palworld runs a continuous server‑side simulation: Pals working at bases, breeding, factory logistics, wild spawns, combat and world state all happen on the server.
RAM usage patterns
| Workload type | Description | Typical RAM behaviour |
|---|---|---|
| Small private world | Few players, one or two bases | Memory grows slowly with base size |
| Active bases | Many Pals assigned to production and farming | RAM rises with working Pals and stored items |
| Large guild / public | Many players, many bases spread across the map | Memory scales with loaded areas and entities |
| Long uptime | Server running for many hours | Memory gradually creeps up (known leak) |
CPU resources
Palworld uses CPU for Pal AI and pathing, base automation, physics and combat, and networking. Because of this:
- High single‑core speed is crucial for smooth gameplay
- Extra cores help with base automation, background saves and I/O
Rule of thumb: match every ~2–3 GB of RAM with about 1 CPU Core. (This is what all HypeServ packages follow by default.)
Tips to keep it smooth
- Set
ServerPlayerMaxNumno higher than you actually need — see Configuration & Access. - Schedule an automatic restart (panel Scheduler) every few hours to reset the memory leak before it causes lag.
- Keep backups enabled so you can roll back after a bad update.
- Watch memory in the panel; if it sits near your limit for long, size up.
Not sure which plan to pick? Choose the plan that matches your group — you can always upgrade later if you need more headroom. If your projected use doesn't match a preset plan, use HypeServ's Custom option to dial in exactly the resources you need. See the general Server sizing guide for how HypeServ plans map to resources.
These figures are practical starting points and may shift as Palworld updates. If your server struggles below the suggested player count, open a ticket and we'll help you tune it.