How Much RAM Does a Project Zomboid Server Actually Need?
Most hosts publish a recommended RAM figure with no measurement behind it. We run PZ servers ourselves, so when we found and fixed a memory bug affecting our own fleet, we kept the real numbers from testing it. This page is those numbers: boot-time and idle memory snapshots, not guesses.
A real crash, fixed: 100% → 0%
We found a memory-handling issue causing clean, unmodded PZ boots to fail outright at one of our RAM tiers. Tested five separate clean boots before the fix: all five hit an out-of-memory kill during startup, every time, before the server finished loading. Tested five more after the fix: all five completed a normal boot, zero crashes.
5/5
boots crashed, before fix
0/5
boots crashed, after fix
We're not publishing the internal mechanism of the fix here. The before/after outcome is what we're standing behind.
What a clean, idle boot actually uses
Measured on a real starter-tier allocation, unmodded, no players connected: five separate clean boots.
~1.6 GB
real memory used (anon + shmem)
That leaves roughly 20.8% headroom on that tier at idle, with no world activity, no active players, and no mods loaded. This is a floor, not a target: it tells you the minimum a PZ server ever needs, not what it needs once people are actually playing on it.
How memory moves as real Workshop mods are added
Same starter-tier allocation, tested at 1, 4, 7, 8, and 9 real Workshop mods (not a continuous sweep of every possible count, five specific tiers, two boots each). Every one of those boots completed normally, zero out-of-memory kills across the whole modded range we tested.
about 1.4 – 1.8 GB
Headroom across that range worked out to 14.0%–29.4%, and it wasn't a straight line: the worst headroom we measured wasn't at the highest mod count we tested, it was in the middle of the range. Mod RAM impact depends on what each mod actually does, not just how many you've installed. Treat any single "X mods = Y RAM" rule of thumb, including this one, as a rough signal, not a formula.
What this data doesn't cover
Every figure here is a boot-time or idle snapshot, not a loaded, actively-played session with real players. Real play adds load these numbers don't capture: more entities tracked, more zombies simulated, more player state synced. And memory headroom is a separate question from mod-list validity: a single invalid or removed Workshop mod ID can still crash a server outright regardless of how much RAM it has. For general sizing guidance across every game we host, see our RAM requirements guide.
Want to see it for yourself?
Start a free Project Zomboid trial on Zeros Host: no credit card required. Your panel shows live memory usage from the moment your server boots.
Start your free Project Zomboid server →Frequently asked questions
Is this RAM usage from a server with real players connected?
No, and we want to be upfront about that rather than let the numbers imply more than they show. Every figure on this page is a boot-time or idle measurement: the server starting cleanly, or sitting idle with zero players connected, not a live session with people actually playing. Real play sessions add load these numbers don't capture. We're publishing what we've actually measured, not extrapolating to a scenario we haven't tested yet.
Why did the server crash 100% of the time before the fix?
At the 8GB tier we tested, every single clean boot (5 out of 5 test runs) hit an out-of-memory kill during startup, before the server ever finished loading. After the fix, 5 out of 5 boots completed normally with no crash. We're not publishing the specific mechanism here, but the before/after outcome itself, 100% failure to 0% failure, is real and repeatable.
Does more Workshop mods always mean more RAM?
Not in a straight line. In our testing, memory usage didn't scale smoothly with mod count. It's a real, if imprecise, signal that mod RAM impact depends heavily on what each individual mod actually does, not just how many you've installed.
Is a heavily modded Project Zomboid server safe to run?
These figures show that the mod loads we tested didn't run out of memory at the RAM levels we tested them at. That's a memory-usage answer, not a general safety guarantee: a completely separate issue exists where a single invalid or removed Workshop mod ID can still crash a server outright, independent of how much RAM it has. Memory headroom and mod-list validity are two different problems.