Project Zomboid Server sizing & resource guide
This guide lets you figure out how much RAM and CPU power your Project Zomboid server will likely need.
TL;DR - Standard RAM sizes for common scenarios
The following table contains some of the most common Project Zomboid server scenarios if you just want to get a rough idea:
| Use case | RAM (est.) | CPUs | Notes |
|---|---|---|---|
| Small vanilla world, 2–4 players | ~4–6 GB | 2–3 Cores | Base game, low zombie pop, limited map exploration |
| Modded friends server, 5–10 players | ~8–10 GB | 3–4 Cores | Map mods, custom cars, moderate zombie hordes |
| Community server, 10–20 players | ~10–16 GB | 4–6 Cores | Heavy mods (Brita's, map expansions), high zombie density |
| Large public world, 32+ players | ~12–16+ GB | 6–8 Cores | Massive map exploration, huge hordes, heavy vehicle use |
How Project Zomboid uses resources
Project Zomboid runs a continuous server-side simulation: thousands of zombie positions, item states in every container, blood splatters, and weather events all happen on the server.
Because the map is massive and highly persistent, proper sizing is critical for a smooth survival experience.
RAM usage patterns
Project Zomboid keeps loaded map chunks, zombie AI states, and mod assets in memory.
More players exploring, higher zombie multipliers, and heavy Steam Workshop mods directly increase memory usage.
| Workload type | Description | Typical RAM behaviour |
|---|---|---|
| Vanilla / Base Game | Few players, mostly staying in one town | Memory sits at a stable baseline (~2-4 GB) |
| Active exploration | Players driving cars across the map | RAM spikes as new map cells and zombies are loaded |
| Mods & custom maps | Raven Creek, Brita's Weapons, custom vehicles | Each mod significantly increases the baseline memory usage |
| Large community | Many players spread across multiple towns | Memory scales heavily with loaded chunks and active zombies |
CPU resources
Project Zomboid uses CPU for:
- Zombie AI and horde pathfinding
- Vehicle physics and collision
- Combat sync (preventing phantom bites)
- Map chunk generation and saving
- Mod scripts
Because of this:
- High single-core speed is crucial for zombie pathfinding and preventing combat desync.
- Extra cores help handle the massive background tasks like saving chunk data to the disk and network routing.
HypeServ’s Ryzen 9 CPUs are tuned for exactly this kind of real-time simulation workload. Giving you the best of both single-core speed and multi-core handling for other server tasks.
(This is what all HypeServ packages follow by default.)
Putting it all together
Here’s a practical sizing reference combining RAM and CPU expectations:
| Use case | RAM (est.) | CPUs | Notes |
|---|---|---|---|
| Small vanilla world, 2–4 players | ~4–6 GB | 2–3 Cores | Base game, low zombie pop, limited map exploration |
| Modded friends server, 5–10 players | ~8–10 GB | 3–4 Cores | Map mods, custom cars, moderate zombie hordes |
| Community server, 10–20 players | ~10–16 GB | 4–6 Cores | Heavy mods (Brita's, map expansions), high zombie density |
| Large public world, 32+ players | ~12–16+ GB | 6–8 Cores | Massive map exploration, huge hordes, heavy vehicle use |
Common pitfalls & how to avoid them
Allocating too little RAM
If allocated memory is too low, the Project Zomboid server will struggle to load map chunks and keep track of mods.
Typical console errors include:
java.lang.OutOfMemoryError: Java heap space
This usually leads to the server suddenly stopping, players dropping, or chunks failing to save.
What you can do to avoid this: Increase RAM allocation so the server has enough memory to cache the map and heavy mods.
Allocating too little CPU
When the server can’t keep up with the simulation, you will encounter the most dangerous issues in Project Zomboid: combat desync. Zombies might teleport, hits might not register, and players driving cars might rubber-band or hit invisible walls.
What you can do to avoid this: Increase CPU cores or move to a higher-performance plan, and consider lowering the zombie population multiplier in your sandbox settings.
Summary
Jokes on you, this is not actually the summary! We’ve put it at the top so most people get to the important bits immediately.