Project Zomboid Server Requirements Calculator

Project Zomboid dedicated server requirements

The Project Zomboid server is a Java application. You launch it with one of three scripts: StartServer64 (Steam, 64-bit), StartServer64_nosteam, or the legacy StartServer32. Always use the 64-bit version. The 32-bit build caps usable memory at roughly 1.5-2GB and manages it inefficiently, which is a common cause of out-of-memory crashes on older setups.

RAM

A reliable real-world rule is ~2GB base + ~0.5GB per player for a vanilla server. So a 6-player game uses around 5GB, an 8-player around 6GB, and a vanilla 10-player around 7-8GB. The dedicated server ships with a fairly modest default heap - around -Xmx3072m (3GB) in ProjectZomboid64.json / the start script. That is fine for a small vanilla game but too low for modded or Build 42 servers, where the JVM hits the ceiling during chunk load and crashes. Edit the -Xms/-Xmx values to match your actual hardware and player count; just don't set -Xmx higher than the machine has, or the server will fail to start.

Leave headroom for the operating system: don't hand more than ~80% of physical RAM to the Java heap. On a 4GB box, cap the heap around 3GB.

CPU

This is where Project Zomboid is demanding. The core game loop is essentially single-threaded, so a fast modern core at 3.5GHz+ will comfortably outperform a slow 16-core chip. For small servers a good dual-core is enough; 4 fast cores is the sweet spot for 8-16 players and leaves room for mod processing and the OS. Adding more cores past that delivers diminishing returns.

Storage

The install itself is small (roughly 2-5GB). Save files grow with how much of the map players explore, but the world is chunked, so growth is gradual and rarely exceeds a few GB even on long-running servers. The important point is disk speed, not size. As players move into fresh territory the server streams and writes thousands of map chunks; on a mechanical HDD or a slow SATA SSD this can stutter, and Build 42's heavier world makes it worse. An SSD is strongly recommended, and NVMe is worth it for busy or Build 42 servers.

Network / bandwidth

Bandwidth needs are modest by modern standards - actual per-player traffic is only about 5-50 KB/s. A stable connection with around 10 Mbps upload covers a typical small-to-medium server; aim for 20-30 Mbps up for 16+ players, and 30-50 Mbps for a busy 32-player server, to avoid desync during chaotic moments. Far more important than headline speed is low, stable latency and no packet loss, since PZ multiplayer is sensitive to jitter. The default port is UDP 16261 (plus 16262); forward both.

Vanilla vs modded

Mods are the biggest variable. A heavily modded server typically needs an extra 1-2GB beyond the formula, and large mod packs can push real usage well past 16GB (a ~50-mod, 2-player server has been measured using over 5GB on its own). A poorly behaved or broken mod can leak memory indefinitely, consuming whatever you give it. Mods also extend startup time and load on the CPU during world generation. Budget conservatively and watch actual usage after adding a mod list.

Build 41 vs Build 42

Build 42 does not raise baseline hardware requirements; its optimizations actually improved multiplayer synchronization and performance over Build 41. However, its richer world simulation (crafting chains, item processing, more world-state tracking) and more granular map streaming make fast storage and a fast CPU more valuable than before.

Performance and config tips

Right-size the Java heap. The dedicated server ships with a modest default heap (about -Xmx3072m, ~3GB) in ProjectZomboid64.json / the start script. That is fine for a tiny vanilla game but too low for modded or Build 42 servers, where it causes out-of-memory crashes during chunk load. Open StartServer64.bat (or the Linux start-server.sh) and raise -Xmx to fit your player count and mods - for example -Xmx5g for a 6-player vanilla server. Setting -Xms equal to -Xmx is optional for PZ; some operators prefer leaving -Xms lower so the JVM does not grab all the RAM up front and starve the OS during heavy chunk streaming. Note: on some Linux/LinuxGSM setups the JVM flags in the start script and ProjectZomboid64.json are not always honored, so confirm which file your launcher actually reads and verify the change took effect.

Pick the right CPU. When choosing a host or VPS, prioritize per-core clock speed and a modern CPU generation over core count. Dedicated or "high-frequency" instances beat cheap shared cores. If you can see the CPU model, a 3.5GHz+ desktop-class chip is ideal.

Use SSD/NVMe storage. This eliminates the chunk-loading stutter that appears as players explore, and it is close to mandatory for Build 42. Avoid HDD-backed hosting for anything beyond a tiny private game.

Tune save and simulation settings. The SaveWorldEveryMinutes setting controls autosave frequency; very aggressive saving can cause periodic hitches on slow disks. Reducing zombie population multipliers and respawn rates lowers CPU load on large servers.

Add mods carefully. Install mods a few at a time, restart, and watch RAM usage before adding more. Keep WorkshopItems and Mods lists in sync, and remove any mod that causes climbing memory between restarts.

Restart on a schedule. A daily or twice-daily automated restart clears accumulated memory and keeps long-lived servers responsive, especially when running mods.

Monitor the right metric. If players report rubber-banding or slow zombie reactions, check CPU utilization on the busiest core first, then disk latency, then RAM. RAM is rarely the real bottleneck once the heap is set correctly.

What to look for in a host

Because Project Zomboid lives and dies on single-thread CPU performance, the most important thing to verify is processor speed and generation, not the number of cores or gigabytes of RAM in the marketing copy. Look for hosts that disclose the CPU model or advertise "high-frequency" or dedicated (non-shared) cores at 3.5GHz or higher. A plan with fewer fast cores will outperform one with many slow shared ones.

Fast storage is the next priority. Confirm SSD, and prefer NVMe if you plan to run Build 42 or expect players to spread across the map, since chunk streaming benefits directly from low disk latency.

Other things worth checking:

• RAM headroom and flexibility: the ability to set your own Java heap (-Xmx) and to upgrade memory later if you add mods, without migrating servers. Confirm the panel actually lets you change the heap, since the stock 3GB default is too low for modded play.
• One-click or easy mod installation and a way to edit the server config, Mods/WorkshopItems lists, and start parameters directly.
• Console and file access (FTP/SFTP): essential for editing start scripts, reading crash logs, and managing saves.
• DDoS protection appropriate for game traffic, since public servers are targets.
• Automated backups and scheduled restarts so a corrupted save or a memory leak doesn't end your world.
• Server location near your players to keep latency and jitter low, which matters more than raw bandwidth for this game.

Whether you self-host on a home PC or rent a server, the same priorities apply: fast cores, fast disk, low-latency network, and the freedom to tune memory and mods yourself.

CPU note: Heavily single-thread-bound. The main world/zombie simulation and chunk updates run on essentially one core, so prioritize high clock speed (3.0+ GHz, ideally 3.5+ GHz) over core count. A fast dual/quad-core beats a slow many-core CPU. Extra cores only help the OS, mod loading, and a few background tasks.

Vanilla figures use ~2GB base + 0.5GB per player, so ~4GB for 2-4 players, ~6GB for 8, ~7-8GB for 10, and ~8-10GB for 16-20. Mods are the biggest variable: budget an extra 1-2GB for light-to-moderate mod lists and far more for large packs (a ~50-mod 2-player server has been measured using 5GB+), and watch for memory-leaking mods. Crucially, the dedicated server ships with a modest default heap of about 3GB (-Xmx3072m) in ProjectZomboid64.json / the start script - that is too low for modded or Build 42 servers and is a common cause of out-of-memory crashes, so raise -Xmx to match your player count and mods. Keep the heap under ~80% of physical RAM, and never set -Xmx above the machine's RAM or the server won't start. Always run 64-bit (32-bit caps near 2GB usable). Build 42 needs no higher baseline than Build 41 (its optimizations slightly improved multiplayer) but benefits more from a fast CPU and NVMe storage.