Palworld holds every base, Pal and piece of automation in memory, so size for how much your group builds rather than how many of them there are.
Pocketpair's official minimum. A small private world for a few friends.
Matches Pocketpair's recommended 16GB specification exactly.
For a long-running world, heavy bases, or a big modded server.
10GB at $20/month and 12GB at $24/month are also available — see all plans.
Most budget hosts advertise "premium hardware" and never tell you the chip. Here is ours.
192GB DDR5 per node. High-clock Zen 4, which is what a Palworld simulation tick actually wants.
Our North American fleet. Germany and the USA are the only two regions we run.
Multithreading is an opt-in flag, and the official docs say leaving it unset may improve performance in v1.0+.
Pocketpair warns that low-performance storage may corrupt saved data — not merely slow the server down.
We do not cap player slots. Palworld's own limit is a launch argument we raise on request.
Your server is live as soon as payment clears, with direct file access for mods and configs.
16GB. That is Pocketpair’s own recommendation for a dedicated Palworld server, and it is our $32/month plan.
The official documentation lists 8GB as the minimum and explicitly warns that running there raises the risk of out-of-memory crashes. It recommends larger than 32GB for big servers. In practice the number is driven less by how many people are online than by how much they have built — Palworld holds every base, every Pal and every piece of automation in memory, so a long-running world grows steadily heavier even with the same group of players.
As many as you want. We do not cap player slots, and Palworld’s own limit is a launch argument rather than a hard cap.
Pocketpair documents the player limit as -players=32, which is a default you can change, not a ceiling built into the game. Tell us the number you want and we will set it. The honest constraint is resources rather than licensing: past roughly 30 concurrent players a Palworld world needs RAM and single-thread headroom more than it needs a bigger number in a config file.
Not necessarily — but in-game co-op only stays up while the host is playing, and it holds far fewer people.
Palworld’s invite-code co-op runs on the host’s own machine. When they close the game, the world goes with them, and everyone’s performance depends on that one person’s PC and home connection. A dedicated server runs independently: it stays online whether or not you are, and players can log in on their own schedule.
| Requirement | Official value |
|---|---|
| CPU | 4 Core + |
| RAM (minimum) | 8GB — the docs note this raises out-of-memory crash risk |
| RAM (recommended) | 16GB |
| RAM (large servers) | Larger than 32GB |
| Storage | Faster SSD. Low-performance storage may corrupt saved data |
| Operating system | Windows 64bit or Linux 64bit |
| Port | UDP 8211 (default, changeable) |
| Player limit | -players=32 default, adjustable |
Source: Pocketpair’s official dedicated server requirements and server launch arguments . Quoted as published — we have not substituted our own estimates.
Common questions about running a Palworld dedicated server with us.