Palworld Dedicated Server Requirements
A Palworld dedicated server is CPU- and RAM-hungry, and its footprint grows as players build bases and capture Pals. This page covers exactly how much RAM and CPU you need for your player count, the ports you must open, and how much disk space to plan for.
How much RAM does a Palworld server need?
RAM is the most important resource for a Palworld dedicated server, and requirements went up with the 1.0 release: worlds are bigger (Sky Islands, 70+ new Pals) and Pocketpair now recommends 16GB for a full server. Real-world usage also climbs as more players join and as bases, captured Pals, and world objects accumulate, so a long-running world uses noticeably more memory than a freshly created one.
| Plan / RAM | Recommended players | Best for |
|---|---|---|
| 5GB RAM | Up to 4 players | Small co-op group, casual play |
| 8GB RAM | Up to 8 players | Friends group, regular sessions |
| 12GB RAM | Up to 16 players | Medium group, active base building |
| 16GB RAM | Up to 32 players | Full-size community server (max players) |
These tiers map directly to the Flux hosting plans. If you are self-hosting, treat them as a guide: 5GB is a practical floor for a small co-op world on 1.0, and you should provision 16GB or more before opening a public 32-player server.
CPU requirements
Palworld's server process benefits from strong single-thread performance. The simulation — Pal AI, base automation, and world physics — is sensitive to per-core speed, so a modern CPU with good single-core throughput matters more than a high core count. On a managed Flux plan the vCPU allocation scales with the plan tier, so a larger player cap comes with more CPU headroom automatically.
Which ports does a Palworld dedicated server use?
Two ports matter. Get these wrong and players cannot connect — this is the single most common reason a Palworld server does not show up.
- UDP 8211 — the game port. This is how players connect to the server. It must be open and reachable on your public IP. This is required.
- TCP 8212 — the REST admin API. Optional, used for remote administration: querying online players, saving the world, broadcasting announcements, and graceful shutdown.
On a Flux-hosted server these ports are exposed for you at deploy time, so there is no router or firewall configuration to do. If you self-host, forward UDP 8211 (and TCP 8212 if you want the admin API) on both your router and OS firewall.
Disk space and saves
The Palworld dedicated server files are a few gigabytes, and the save data grows with world size, base count, and player activity. Plan for enough SSD/NVMe headroom to hold the server build plus a growing world and a couple of backups. Managed Flux plans include SSD/NVMe storage sized to the plan, and you can take on-demand backups and restore them with one click from the dashboard.
Network and uptime
A public server needs stable bandwidth and, ideally, DDoS protection — a real concern for any exposed game server. Self-hosting from a home connection exposes your IP and offers no protection. Every Palworld server on Flux includes DDoS protection at no extra cost and runs on a distributed network for 99.9% uptime, so the world stays online without tying up your own machine.
Frequently asked questions
How much RAM do I need for a Palworld dedicated server?
Since the 1.0 update: at least 5GB for small co-op groups up to 4 players, 8GB for up to 8, 12GB for up to 16, and 16GB or more for a full 32-player server. Memory use grows as bases and captured Pals accumulate, so size up for long-running worlds.
What ports does a Palworld server need?
UDP port 8211 for game traffic (required) and TCP port 8212 for the optional REST admin API.
How many CPU cores does a Palworld server need?
Palworld favors strong single-core performance over many cores. A modern CPU with good per-core speed handles the Pal AI and base simulation best; managed plans scale vCPU with the player tier.
How much disk space does a Palworld server use?
The server build is a few gigabytes and the save grows with world size and base count. Allow headroom for the build plus a growing world and backups.