Palworld, three months later — what actually eats memory

Player count matters less than explored map area. Numbers from servers on our nodes, and why we set the minimum plan where we did.

Palworld launched in January and immediately produced the same support ticket from everyone: “the server uses 8 GB with six players”. That is accurate, and it is not a bug. Here is what we measured over three months on production nodes.

Memory is map, not players

A fresh world with four players settles around 4.5–5 GB after the first session. The same world with twelve players settles around 6–7 GB. The difference between four and twelve players is smaller than the difference between a world where people have explored three regions and one where they have explored twelve.

Palworld keeps world state in memory rather than streaming it from disk on demand. Every explored region, every captured Pal assigned to a base, every built structure in those regions has a representation in RAM. Players wander; the map does not shrink.

Observed ranges

World statePlayersResident memory
Fresh world, starting area2–43.5–4.5 GB
A few days of play4–85–6.5 GB
Two weeks, several bases8–167–9 GB
Long-running public server16–3210–14 GB

These are steady-state figures after a few hours, not peaks. The peak during startup is higher, which is why a server with exactly enough memory to hold the world can still fail to start after a backup restore.

What we recommend now

Community 8 (8 GB) is the smallest plan we will suggest for Palworld, and we say so even when the customer asks for Sandbox 2. It is not a sales decision: a 4 GB server will start, run for twenty minutes, and die on the first raid. Recommending a larger plan we know is required is cheaper for everyone than a refund and a support thread.

For a public server with more than sixteen slots, the dedicated node is the honest answer. Not because of CPU — Palworld is not especially CPU-heavy — but because memory grows and does not come back until the world is reset.

Things that help

  • Lower the base worker cap; each assigned Pal costs memory in the base simulation.
  • Reduce the drop rate for items on the ground — item entities are a real cost.
  • Restart on a schedule. It is not a fix, but it returns the process to a known state.
  • Reset the world when a season ends, rather than running the same map for a year.

The game will probably get better at this. Until then, memory is the number to look at, and player count is a weaker predictor than most people assume.

← All posts