LearnDocsLog in
Deploy a serverDeploy

Palworld server requirements

What a Palworld server needs in CPU, memory, disk and bandwidth, by player count. Change the numbers for your own server; the sources are listed below.

Mods (UE4SS)
Assumptions

What it needs

CPU
5 coresSingle-thread heavy: clock speed matters more than core count.
Memory
18.5 GB
NVMe storage
60 GB
Traffic per month
181 GB
Busiest upload
1.6 Mbit/s

On Clouduxe

Room to grow

VDS PrimeCore

8 dedicated cores, 32 GB DDR5, 800 GB NVMe, 16 TB traffic

₹19,880$209.49/mo

  • 2 more dedicated cores, 8 GB more memory, 300 GB more NVMe.
  • Headroom for busy evenings, more players, and the mods and updates you add later.
Deploy PrimeCoreAbout PrimeCore

By player count. Without mods (ue4ss); each step up in the calculator adds memory, disk and sometimes a core.

PlayersCPUMemoryNVMeTraffic a monthFits your loadRoom to grow
44 cores8 GB60 GB45 GBVPS GrowthVDS FusionCore
105 cores13 GB60 GB113 GBVDS OmniCoreVDS PrimeCore
165 cores18.5 GB60 GB181 GBVDS OmniCoreVDS PrimeCore
246 cores25.5 GB60 GB272 GBVDS PrimeCoreVDS TitanCore
327 cores32.5 GB60 GB363 GBVDS TitanCoreVDS UltraCore

Traffic assumes 35% of the player cap online on average across the month; change it under Assumptions in the calculator.

Where the numbers come from. Published figures first, then how the calculator turns them into a model.

Published requirements

How the model is built

Memory
4 GB plus 900 MB per player. Pocketpair's official docs give one blanket figure (16GB standard, 32GB+ recommended, 8GB usable but crash-prone) regardless of player count. xgamingserver's tiered guidance scales with players: 8GB for up to 4, 12GB for 5-10, 16GB for 10-16, 32GB for 16-32. baseGB=4 plus 900MB per player reproduces roughly 8GB at 4 players and 32GB at 32 players, the two ends of that tiered range.
CPU
4 cores, one more for every 8 players. Official docs call for 4+ cores. Hosting guides note CPU single-thread speed is the real bottleneck once bases and pal automation get busy, so clock speed matters more than raw core count; extra cores still help at higher player counts with more concurrent bases.
Disk
15 GB for the server plus 45 GB for saves and backups, on SSD or NVMe. Initial server download is roughly 12-15GB. Small private servers (up to about 8 players) need 40-60GB total for saves and backups as bases grow; busy community servers can need 100GB+. installGB=15 plus growthGB=45 lands near the middle of the small-server range; scale up for large populations. Official docs warn slow storage risks save data corruption, so SSD/NVMe is treated as required.
Bandwidth
100 kbit/s of upload per player. Derived from a hosting guide's rule of thumb: 10 Mbps upstream per 10 concurrent players, which is 100kbps per player. Pocketpair's official docs give no bandwidth figure.
Mods (UE4SS)
Memory times 1.3 for some and 1.7 for heavy; a heavy load also adds a core.

Pocketpair's official docs state one flat requirement (4+ cores, 16GB RAM standard, 32GB+ recommended) rather than a table by player count; the player-count breakdown here comes from a hosting guide. Modded servers using UE4SS can vary widely in resource use; the mods multipliers are an estimate since no source gives modded-vs-vanilla figures.

Before you set it up. The ports it listens on and what the guides say drives its load.

Ports

PortProtocolUsed for
8211UDPgame
25575TCPRCON (optional, deprecated)
8212TCPREST API (optional)

Game server hosting: every game we size, the protection each one gets, and the plan for it.

DDoS protection is on every Clouduxe plan. How Prism handles game traffic.

What drives the load

  • Pocketpair's own docs recommend 16GB RAM as standard for any dedicated server and warn that 8GB risks out-of-memory crashes; scale toward 32GB+ for a full 32-player server.
  • CPU single-thread clock speed matters more than core count once pal automation and base-building activity ramp up.
  • Use SSD or NVMe storage; the official docs warn that slow storage can corrupt save data.
  • Default max players on a dedicated server is 32 (ServerPlayerMaxNum), separate from the 4-player co-op party size setting (CoopPlayerMaxNum).

Palworld server questions

Talk to us
How much RAM does a Palworld server need?

About 8 GB for 4 players and 32.5 GB for 32, before mods (ue4ss). Pocketpair's official docs give one blanket figure (16GB standard, 32GB+ recommended, 8GB usable but crash-prone) regardless of player count. xgamingserver's tiered guidance scales with players: 8GB for up to 4, 12GB for 5-10, 16GB for 10-16, 32GB for 16-32. baseGB=4 plus 900MB per player reproduces roughly 8GB at 4 players and 32GB at 32 players, the two ends of that tiered range.

How many CPU cores does a Palworld server need?

4 for 4 players, 7 for 32. The server is single-thread heavy, so the clock speed of one core matters more than how many cores it has. Official docs call for 4+ cores. Hosting guides note CPU single-thread speed is the real bottleneck once bases and pal automation get busy, so clock speed matters more than raw core count; extra cores still help at higher player counts with more concurrent bases.

How much bandwidth does a Palworld server use?

About 100 kbit/s of upload per connected player, so 1.6 Mbit/s with 16 players online and about 181 GB a month if 35% of that cap is online on average. Derived from a hosting guide's rule of thumb: 10 Mbps upstream per 10 concurrent players, which is 100kbps per player. Pocketpair's official docs give no bandwidth figure.

Which Clouduxe plan should I pick for Palworld?

For 16 players, VDS OmniCore fits the load and VDS PrimeCore leaves room to grow. Every plan includes DDoS protection: 17 Tbps of upstream mitigation plus Clouduxe Prism on the server.

Other games. The same calculator, sized from each game's own documentation.

All calculators

Host Palworld on VDS OmniCore.

Sized for 16 players, with DDoS protection included. Or talk to us about a bigger server.

See VDS OmniCoreSize another server