Palworld server requirements: how much RAM is enough?

The dedicated-server requirements are a better starting point than a host’s “up to 32 players” badge. Pocketpair’s current requirements list four or more CPU cores as recommended, 16 GB of memory, and a recommendation for more than 32 GB. It explicitly warns about out-of-memory crashes at 8 GB.

These are developer-published specifications, not measurements from SpawnHosts. Check the linked official page again before ordering: requirements can change with the server build.

A slot is permission for another player to join. It does not tell you how much work the server can complete while that player is there. Two plans with the same slot count can have different memory limits, CPU allocations, storage behavior, or restrictions on configuration.

Ask what the quoted resources mean. Is the memory dedicated to this instance? Is the advertised CPU a model name or an allocation? Can you see usage and logs? What happens if the process reaches its limit? A provider that answers these questions clearly is easier to evaluate than one offering a large “unlimited” label.

Keep the workload in view. A fresh test world and your group’s established save are not interchangeable. A useful trial should include the save, settings, and usual activity you expect to run, rather than a quiet server nobody has joined.

When a budget plan sits below the published baseline, treat it as a deliberate experiment with an exit plan. Confirm the refund window, how upgrades are billed, and whether you can download the complete save. Do that before the group invests another evening in the world.

During your first sessions, keep a note of memory usage alongside player count and what the group was doing. A usage snapshot without context cannot tell you whether a spike is unusual. Preserve the logs when a crash happens instead of immediately restarting and losing the evidence.

There is no defensible universal “GB per player” formula in our current evidence. We have not run a controlled load test. If a plan needs to be sized precisely, use an actual trial with your save or obtain a provider’s specific recommendation in writing.

Check backup retention and export access alongside RAM. A larger plan cannot recover a save that was never backed up. Ask whether backups remain available if the service is suspended and whether restoring one changes the running instance immediately.

Compare the price you will pay next month, the billing period, and any paid extras. Annual billing can look cheap per month while making an untested choice more expensive to reverse. For a new group, a short initial commitment is often the simpler experiment.

Once you have a workable baseline, avoid changing several settings to squeeze out more capacity at once. Make one change, keep the old configuration, and compare another normal session. The goal is a stable shared world, not a low idle-memory screenshot.