Palworld Server Requirements Calculator

Palworld dedicated server requirements

Palworld (built on Unreal Engine 5) is still in Early Access, and its dedicated server reflects that: it works well but is unoptimized in ways that directly shape your hardware budget. Pocketpair's official Requirements page lists a 4 Core+ CPU, a minimum of 8GB RAM with larger than 32GB recommended for serious use, SSD storage, and UDP port 8211. It does not name a single mid-range RAM figure — the widely-quoted "16GB" is the de-facto community and host standard for small-to-mid servers, not an official number. Below is what those specs mean in practice.

RAM — the number that matters most

16GB is a sensible default for up to roughly 8-10 players. But Palworld's server has a well-documented memory leak: the process allocates RAM continuously during a session and rarely releases it. A server that starts at 2-6GB can climb to 15-20GB after several hours of active play. Community operators consistently report a 16-player server reaching ~19GB over a session, which is why Pocketpair and hosts alike recommend 32GB for anything approaching the 32-player cap.

• 8GB: the official minimum — works for 2-4 players but offers almost no leak headroom; out-of-memory crashes are likely without frequent restarts.
• 16GB: the common practical recommendation; comfortable for 8-10 players with nightly restarts.
• 24-32GB: needed for 16-32 players, primarily to absorb the leak rather than because players each cost that much.

CPU — clock speed beats core count

This is the most misunderstood part of Palworld hosting. The server is heavily single-thread bound: it effectively uses only about 2-3 cores no matter how many you provide. Community testing and the official guide agree that a few fast cores outperform many slow ones. Target a modern CPU at 3.5 GHz or higher (ideally 4 GHz+) with 4-6 cores so the OS, backups, and worker threads have room. Adding more cores past 4-6 buys you almost nothing for the simulation itself.

Storage — SSD is mandatory, not optional

The server install is roughly 8-12GB. The catch is the save data: the official docs explicitly warn that low-performance storage can corrupt your save, and the main level.sav file grows large over time (60MB+ has been reported before instability). Bases, Pals, structures, and inventories all add to it, and rotating backups can roughly double your footprint within a few weeks. Budget ~30GB on SSD or NVMe for the install, saves, backups, and logs (some hosts suggest 40GB to be safe).

Network and ports

Palworld uses UDP port 8211 by default (changeable). Bandwidth is modest compared to RAM/CPU: roughly 0.1-0.2 Mbps per active player, so ~10 Mbps upload comfortably handles a small group and 20+ Mbps suits a busy 20-32 player server. Per active player, expect on the order of 15-25GB of monthly egress depending on session length and population.

OS

A 64-bit OS is required — Windows 64-bit or Linux 64-bit (Ubuntu, AlmaLinux, etc.). Linux via SteamCMD is the common choice for headless hosting.

Vanilla vs. modded

Palworld does not officially support server-side mods, so there's no sanctioned mod loader to budget for. Heavier custom settings (higher spawn rates, larger build limits, more capture/breeding) do increase memory and CPU load, so treat the "modded" allowance as a buffer for aggressive configuration rather than true mod packs.

Optimizing your Palworld server

Because Palworld is unoptimized in predictable ways, a handful of targeted changes deliver outsized gains.

Use the multithreading startup flags

Launch the server with the performance flags the official guide recommends: -useperfthreads -NoAsyncLoadingThread -UseMultithreadForDS. These improve performance in multi-threaded CPU environments by spreading work across threads more effectively. You can cap worker threads with -NumberOfWorkerThreadsServer=X; the docs note the maximum useful value is your CPU thread count minus one.

Disable invader enemies to fight the leak

Setting bEnableInvaderEnemy=false in PalWorldSettings.ini is the single most effective mitigation for the memory leak — operators and hosts report RAM usage dropping by more than half and staying stable for hours afterward. If your players don't rely on invader events, turn it off.

Automate restarts

Until the leak is fixed upstream, scheduled restarts are the reliable fix — they are not optional for stable Palworld hosting. For a healthy 16GB server, every 8-24 hours is fine; for busy 16-32 player servers, every 3-6 hours keeps memory and rubber-banding under control. Restart during off-peak hours and always after a clean save.

Tune the settings that multiply load

ServerPlayerMaxNum, PalSpawnNumRate, base/guild build limits, and capture/breeding rates all multiply CPU, memory, and network cost. Raise them gradually and watch resource use rather than maxing everything at once.

Protect your saves

Keep saves on SSD/NVMe, enable frequent automated backups, and never store the world on slow or network-mounted storage — the docs warn this can corrupt the save. Back up before every restart so a bad shutdown can't cost you progress.

Watch the right metrics

Monitor RAM trend (not just a snapshot), single-core CPU utilization, and tick rate / server FPS. If one core is pinned at 100% while others idle, that's expected — your fix is a faster CPU or fewer simulation-heavy settings, not more cores.

What to look for in a Palworld host

Palworld's specific quirks should drive your hosting checklist more than generic marketing specs. Focus on these:

• High single-core clock speed. Because the server is single-thread bound, the CPU's per-core GHz (and generation) matters far more than the advertised core count. Look for hosts that publish their CPU models and offer modern, high-clock chips (3.5 GHz+). A plan boasting many slow vCPUs will underperform a few fast ones.
• Generous RAM headroom. Given the memory leak, choose a plan that lets you run comfortably above your expected steady-state usage — and ideally upgrade RAM without migrating. Avoid plans that hard-kill the process the instant it hits the cap.
• NVMe/SSD storage. Fast storage isn't a luxury here; slow disks can corrupt saves. Confirm the host uses SSD or NVMe, not HDD.
• Automated, frequent backups. Look for built-in scheduled backups with easy restore, since save corruption and restarts are part of normal Palworld operation.
• Scheduled restart support. The ability to set automatic restarts (and ideally pre-restart save commands) is genuinely important for this game, not a nice-to-have.
• Full file and console access. You'll need to edit PalWorldSettings.ini and set startup flags, so SFTP/FTP file access and a console or custom launch arguments are essential.
• DDoS protection and low-latency location. Pick a data-center region close to your players to minimize ping, and confirm the host includes network-level DDoS mitigation on the UDP game port.

Whether you self-host on a VPS or use a managed game host, these capabilities — not brand names — determine whether your Palworld server stays stable.

CPU note: Heavily single-thread-bound: the server effectively uses only ~2-3 cores no matter how many you give it, so prioritize high clock speed (3.5 GHz+, ideally 4 GHz+) over core count. Two fast cores beat eight slow ones. Allocate 4-6 fast cores so the OS, backups, and the worker threads have headroom.

Numbers are for vanilla early-access Palworld dedicated servers (still officially Early Access as of 2026). Pocketpair's official requirements page lists 8GB as the bootable minimum and recommends RAM 'larger than 32GB' for serious use, with no single intermediate figure; 16GB is the de-facto community/host standard for small-to-mid servers. The defining factor is NOT a fixed per-player RAM figure but a well-documented memory leak: the process allocates RAM steadily over a session and rarely frees it, so a server that idles at 2-6GB can climb to 15-20GB after hours of play. Always size RAM with generous headroom and automate restarts rather than trusting a single per-player number. Palworld does not officially support mods on dedicated servers, so the modded multiplier (~1.5x) is a rough allowance for heavier community settings/tooling, not sanctioned mod loaders. Storage figures assume SSD/NVMe (the docs explicitly warn low-performance disks can corrupt saves) and include room for the growing level.sav plus rotating backups.