Project Zomboid Server Requirements: Players, RAM and World Size

For a Project Zomboid server, 4 players need at least 2 vCPU and 6 GB RAM, while 16 players need 4 vCPU and 16 GB RAM; when players actively explore the map, spare memory matters more than the configured slot limit.

You cannot size project zomboid server requirements by connection count alone. The game continuously stores the state of loaded cells: zombies, containers, destruction, dropped items, vehicles, fires, corpses, and modded objects. The farther players spread across the map, the more data remains in memory and the heavier the load on the main CPU thread becomes.

Project Zomboid server requirements for 4–32 players

Why player count is not the only metric

The question project zomboid how many players is not answered by the MaxPlayers limit alone. Eight survivors living at one base in Muldraugh can put less load on a VPS than four players simultaneously exploring Louisville, Riverside, industrial zones, and modded maps.

The server activates world chunks around characters. When players are spread out, more cells are loaded at the same time, zombie simulation grows, and read/write activity increases. This is why an 8-slot server is not always lighter than a 16-slot server: player behavior and world density are the deciding factors.

For a broader overview of game server sizing, see our guide to game server requirements and calculating player capacity by configuration: Project Zomboid is particularly sensitive to single-core CPU performance and available RAM.

Load scale → recommended specs

For 4/8/16/32 Project Zomboid players, allow 2/2/4/6 vCPU, 6/8/16/32 GB RAM, and 40/60/100/160 GB NVMe storage respectively, provided old saves are cleaned up regularly.

Prices in the table are general market estimates for February 2026, not offers from a third-party provider. For a public server, choose a Valebyte VPS that lets you increase RAM quickly: explored-world data grows gradually, but memory usage can spike after a single game night in a new city.

Why Project Zomboid server requirements depend on the map

World cells, zombies, and saved state

Project Zomboid server requirements change as players uncover new areas. The game does not keep the entire state of Kentucky in RAM, but the server saves and processes visited areas: modified buildings, loot, broken windows, barricades, vehicles, blood, corpses, and traces of player activity.

On a fresh world, 8 GB RAM may be enough for 10–12 players. After several weeks of regular trips through cities, base building, and mod use, actual consumption can rise to 12–14 GB. If a VPS has exactly 8 GB with no reserve, Linux starts using swap and the server will stutter during autosaves.

What increases memory usage the most

• Players spreading across the map. Four groups in different cities keep more active zones loaded than 16 players in one neighborhood.
• Louisville and dense urban areas. More objects, zombies, vehicles, and containers require more resources.
• Map and vehicle mods. New tiles, cars, items, and scripts increase RAM use and save size.
• A long season without a wipe. A world with thousands of buildings and abandoned items needs more NVMe storage and save time.
• High zombie population. Raising Population Multiplier from 1.0 to 2.0–3.0 has a more noticeable CPU impact than disk impact.

The same pattern applies to other games with persistent worlds: our guide to 7 Days to Die server requirements also shows that world size and accumulated changes matter, not just online player count.

How much Project Zomboid server RAM do you need?

Calculating project zomboid server ram

To determine how much RAM a Project Zomboid server needs, use this formula: base server memory + memory for active cells + a 25–35% reserve for peaks. For a vanilla server, assume a 3–4 GB base, then add 0.4–0.8 GB for every 4 active players and another 2–8 GB for the explored world, mods, and headroom.

The practical minimum of 4 GB is only suitable for 1–3 players on a fresh world without heavy mods. For a persistent server for 4–8 players, choosing 6–8 GB from the start is more sensible. A 16 GB configuration becomes the working standard for 12–16 players, while 32 GB is justified for a large modded community or a long-running map without wipes.

How to identify insufficient RAM

Do not rely only on the “used memory” line: Linux file cache also uses memory and is normally released when needed. Available memory, swap, and kernel OOM messages are the critical metrics. If swap rises above 256–512 MB during peak hours and TPS or player responsiveness drops, the server needs more RAM or world optimization.

free -h
vmstat 1
journalctl -k | grep -i -E "oom|killed process"
df -h
du -sh ~/Zomboid/Saves/Multiplayer/*

A small 1–2 GB swap file is useful as emergency protection against a sudden process crash, but it is not a replacement for RAM. NVMe is faster than SATA SSD, but even fast storage cannot compensate for sustained swap use caused by insufficient memory.

Quick pick

Need a dedicated server?

Bare metal with NVMe in 70+ locations — configure and order in minutes.

Browse servers

Which Project Zomboid server hardware matters most: CPU, NVMe, or network?

CPU: high clock speed beats more slow cores

Project zomboid server hardware should provide strong single-core performance. The server uses multiple threads, but game simulation and part of its logic remain constrained by the main thread. As a result, 2 fast vCPU at around 3.5 GHz or higher are often more useful than 4 slow or oversold virtual cores.

For 4–8 players, use 2 vCPU. One vCPU can still work for a couple of friends on a fresh vanilla world, but it stops handling load reliably with 4 active players, players traveling to different areas, or autosaves. Typical symptoms are delayed actions, teleporting zombies, freezes during saves, and increasing tick time.

NVMe, IOPS, and backups

Storage affects startup time, world loading, autosaves, and recovery after a failure. For Project Zomboid, choose NVMe rather than HDD: low random-operation latency matters more than advertised sequential throughput. A reasonable baseline is 40 GB for a small world, 100 GB for a 16-player server, and from 160 GB for modded maps and backups.

Do not keep your only backup next to the live save. Configure daily backups and retain at least 7 recovery points. A complete deployment guide is available in our article on how to set up your own Project Zomboid server on a VPS or dedicated server.

#!/bin/bash
DATE=$(date +%F)
SRC="$HOME/Zomboid/Saves/Multiplayer"
DST="$HOME/backups/zomboid-$DATE.tar.gz"

tar -czf "$DST" "$SRC"
find "$HOME/backups" -type f -name "zomboid-*.tar.gz" -mtime +7 -delete

When does a 1 vCPU VPS stop being enough for Project Zomboid?

Limits of a single-vCPU configuration

A 1 vCPU VPS is acceptable for a test server, 1–2 players, or a short vanilla session on a fresh map. For a persistent world, it becomes unreliable at just 3–4 concurrent players, especially if they are more than one cell apart. Any competing process—system updates, backups, or monitoring—takes CPU time away from the game thread.

Moving to 2 vCPU is not about doubling the player limit; it is about headroom. One thread handles critical game workload, while the second handles network operations, the Java process, the file system, and background tasks. For 16+ players, you need not just extra cores but predictable CPU performance without aggressive overselling.

When you need a dedicated server

A dedicated server is justified when online activity reaches 24–32 players, the map has been developing for months, a large mod pack is used, or multiple instances must run. For one Project Zomboid server, a configuration with 6–8 physical threads, 32 GB RAM, and NVMe usually provides substantial headroom. If the same machine also hosts panels, databases, Discord bots, or other games, calculate those resources separately.

For comparison, ARK uses significantly more memory at a comparable player count, as covered in our guide on how much RAM and CPU an ARK Survival Ascended server needs. Project Zomboid is more resource-efficient, but more sensitive to a slow main CPU core.

How to set up a Project Zomboid server for 16–32 players without lag

Sandbox settings and zombie management

Even the right project zomboid dedicated server specs cannot save a server with unrestricted simulation. For 16–32 players, do not raise Population Multiplier without testing: start at 1.0–1.5, run a load test in Louisville, and check latency. Prevent pointless corpse accumulation, configure cleanup, and avoid adding dozens of vehicle mods at once.

Before a public launch, test the server using realistic scenarios: 8 players spread across four areas, two driving vehicles, several building a base, and one triggering a large horde. This is more useful than measuring an idle server at 0% CPU.

A practical administrator checklist

1. Keep 25–35% RAM free above the expected peak.
2. Choose at least 2 vCPU for 4–8 players and 4 vCPU for 16 players.
3. Use NVMe and keep at least 20% of disk capacity free.
4. Check save folder size weekly after updates and mod changes.
5. Create backups before changing a mod pack, map, or server version.
6. Monitor CPU steal time on a VPS: persistent values above 5% indicate resource contention on the host.

mpstat 1
top -H -p $(pgrep -f ProjectZomboid)
iostat -xz 1
ss -s

If the server runs alongside heavy services such as local AI models, do not share 16 GB RAM with them without a reserve. A self-hosted LLM can consume several times more memory; this is covered in detail in our guide to server requirements for self-hosted AI.

Quick pick

Need a dedicated server?

Bare metal with NVMe in 70+ locations — configure and order in minutes.

Browse servers

Frequently Asked Questions

How many players can a Project Zomboid server with 8 GB RAM handle?

With 8 GB RAM, a server typically supports 6–10 players on a vanilla or moderately modded map when it has 2 fast vCPU. After weeks of map exploration, the safe limit may fall to 6–8 active players. If players spend most of their time in cities, upgrade to 12–16 GB RAM before swap usage and stutters begin.

Is 1 vCPU enough for Project Zomboid?

1 vCPU is suitable for testing, 1–2 friends, and a fresh world without heavy mods. With 3–4 active players, travel across different areas, or large zombie hordes, one core often becomes the bottleneck. For a persistent server, use at least 2 vCPU with strong per-core performance and a clock speed around 3.5 GHz or higher.

How much disk space does a Project Zomboid world use?

A small server needs 40 GB NVMe, but this space includes the game, SteamCMD, logs, mods, and backups. For a 16-player server, allocating 100 GB NVMe is more practical. A long-running season with Workshop maps and 7 daily backups requires from 160 GB of free storage.

Do you need a 1 Gbps port for a 16-player server?

For 16 players, a 1 Gbps port provides sufficient headroom; actual Project Zomboid traffic is usually far below that throughput. A stable network, low latency to players, and a bandwidth allowance from 3 TB per month matter more. With mods, players also download additional content through Steam, but this does not always pass through the game server.

Conclusion

The right configuration without overspending

For a stable 4–8 player server, choose a Valebyte VPS with 2 vCPU, 8 GB RAM, and 60 GB NVMe; for 16 players, choose 4 vCPU, 16 GB RAM, and 100 GB NVMe. Do not plan a long-running modded world on 1 vCPU: Project Zomboid loads the server not only through player count, but also through every newly explored map cell.

SSD NVMe

Ready to launch your VPS?

NVMe VPS activation in 60 seconds: full root access, 20+ locations, and card or crypto payments.

Choose a plan