A Project Zomboid server can feel perfect during the first hour and then start struggling once players scatter across Knox Country, drive off in different directions, build big bases and stack up Workshop mods. That is why Project Zomboid server requirements are less about a single minimum spec and more about sizing the server for the way your group actually survives.
A private vanilla world for a few friends needs very different resources from a 30-player community with persistent loot, custom sandbox rules, dozens of vehicles and regular restarts. The good news: Project Zomboid does not need extreme hardware. It does need fast CPU cores, honest RAM headroom and storage that keeps up with a growing world and its backups.
Project Zomboid server requirements at a glance
For a small vanilla server with one or two players, start with 4 GB of RAM, a fast modern CPU core and around 30 GB of NVMe storage. Up to four players without mods are comfortable on 6 GB.
Once mods enter the picture, 8 GB is a sensible starting point: enough for up to eight players and around 20 mods. Communities with large map expansions, vehicle packs, item overhauls or higher player limits should plan 10–16 GB, and big public servers 20 GB or more. What counts is the number of players online at the same time, not how many people are on the whitelist.
Storage needs are modest at launch but grow over time: the server stores player data, explored map cells, vehicles, containers, safehouses and backups. Fast NVMe storage also shortens the pauses when the server reads and writes save data.
The host itself should run a 64-bit Windows or Linux. If you self-host, remember that the world is only available while that machine is on — a dedicated server stops one player's gaming PC from being the permanent bottleneck. Our guide on how to host a Project Zomboid server walks through both options.
CPU: fast cores beat big core counts
Project Zomboid benefits most from strong per-core performance. The server does use several threads, but a processor with many slow cores is not automatically better than a modern high-frequency CPU.
CPU load climbs when players explore new areas, when zombies are active around several players at once, when vehicles are moving and when modded systems run their logic. One player speeding through unexplored towns can create more work than someone quietly sorting their base. That is why a server can feel smooth for a while and lag only at busy moments.
For a small group, a couple of fast cores is usually enough. Public servers and heavily modded worlds need more CPU capacity, especially with many players online in different parts of the map. Don't judge a server by core count alone: consistent allocation and high per-core speed matter more than an impressive but vague number of vCPUs.
How much RAM does a Project Zomboid server need?
RAM is the resource owners most often have to raise as the world grows. It holds active game data, player activity, map information, zombies and mod content. Running short leads to stutters, crashes or a server that becomes unstable after several days of uptime.
As a practical guide based on our plans:
| RAM | Players online | Mods |
|---|---|---|
| 4 GB | 1–2 | none |
| 6 GB | up to 4 | none |
| 8 GB | up to 8 | up to ~20 |
| 10–12 GB | 12–16 | 40–60 |
| 14–16 GB | 20–24 | 60–80+ |
| 20 GB and more | 32+ | large mod packs |
More RAM does not cure everything. If the CPU is overloaded, extra memory won't fix lag caused by aggressive zombie settings, too many active mods or players constantly generating new map areas. Still, headroom is smart: a server that gets exactly enough memory on day one has no room for a growing save or a new batch of mods.
If you manage the server yourself, set the Java memory limit (-Xmx) deliberately instead of handing it all of the machine's RAM — the operating system, backups and admin tools need memory too. With managed hosting, pick a plan with realistic headroom rather than the smallest possible allocation.
Storage, backups and world size
Project Zomboid servers don't need huge disks, but storage quality affects reliability. NVMe makes saves fast and keeps routine backups from disrupting play — which matters once a group has spent weeks building a base and collecting rare vehicles.
A fresh server uses little space, but the world grows as players explore, and mods and maps add to the footprint. Around 30 GB is a comfortable start for a private server, especially if you want to keep several backups. Established modded communities should plan 40–60 GB or more.
Backups are not optional for a persistent survival world. A corrupted save, a broken mod update, an accidental admin command or a griefing incident can wipe out far more progress than anyone expects. Automatic backups let you restore a working state instead of asking everyone to start over. Before changing major mods or sandbox settings, take a manual backup as well — our backup and restore guide covers a routine that works for any game server.
Look at the busiest evening of the week, not a quiet Tuesday. If eight people log in on Friday night and split up across the map, that is the load your server has to handle. Pick RAM for that peak and keep about 20% headroom for world growth and new mods.
Bandwidth and server location
A small Project Zomboid server does not need unusually fast internet, but connection quality matters. Stable upload is worth more than high download speed. If you self-host, a reliable upload of a few megabits per second is enough for a small group; more concurrent players need more.
Location matters just as much. A server close to its regular players gives lower ping and a better experience when driving, fighting and looting. If your group is split between continents, there is no perfect spot: choose the region closest to most of your active players and test it before committing to a long-running world. You can see which cities are available on our locations page.
For public servers, network protection is worth thinking about. A home connection exposed to the internet is an easy target for unwanted traffic, while a hosting provider filters attacks before they reach the server. How such attacks work and how to protect a server is covered in our server protection guide.
Mods change the hardware equation
Mods are one of Project Zomboid's best features — and the most common reason a server outgrows its original plan. A few quality-of-life mods barely register. Large map packs, vehicles, weapons, crafting overhauls and scripts that add persistent objects all raise CPU, RAM and storage needs, and the troubleshooting load too.
Don't install mods just because they are popular. Check that they support multiplayer, match your game build and are still maintained. A single outdated mod can stop everyone from connecting after an update.
Keep Workshop IDs and Mod IDs organised and test changes on a copy of the world when you can. Mods go into the server's .ini file (WorkshopItems= and Mods=), while sandbox options live in the separate _SandboxVars.lua file — mixing them up is a classic setup mistake. The full process is in our guide to Project Zomboid server mods.
When you chase lag or startup failures, remove the most recently added mods first. Check the console for errors, then add mods back in small groups. It is slower than guessing, but it finds the real conflict without risking the main save.
Match the server to your play style
A good plan matches behaviour, not just player count. Four players travelling and building in separate towns can generate more activity than eight players sharing one compound. A 20-player server that is busy only on weekends needs a different setup from a smaller community that plays every evening.
Some practical scenarios:
- Private vanilla world for two to four friends: 4–6 GB RAM, fast CPU cores, around 30 GB NVMe.
- Modded co-op world for up to eight active players: 8 GB RAM, strong per-core CPU performance, 40 GB or more storage.
- Public or heavily modded community: 12–16 GB RAM or more, extra CPU capacity, larger NVMe storage and a tested backup routine.
Start with enough room for launch, then watch how the server behaves once your group settles in: long freezes during saves, rising memory use, slow restarts and lag when players explore separately are all signs that it needs tuning or a bigger plan.
When managed hosting makes sense
Self-hosting is fine for testing or for occasional sessions with a small group. It gets less convenient when friends expect the world to stay online, your upload is limited, or you would rather play than troubleshoot ports, Java settings, backups and updates.
A good host should give you fast modern CPUs, NVMe storage, DDoS protection, automatic backups and support that helps when a mod update breaks the server at the worst possible moment. What else to look for is covered in our guide to Project Zomboid server hosting.
The best Project Zomboid server isn't the one with the biggest numbers on paper. It is the one that stays responsive when your group splits up, protects the world when something goes wrong and leaves you free to worry about zombies instead of server maintenance.
Elysium's Project Zomboid plans run on high-frequency Ryzen with NVMe storage and always-on DDoS protection. Pulse (4 GB, €10.49/month) suits one or two players, Vector (6 GB, €15.49/month) up to four, and Nexus (8 GB, €20.49/month) up to eight players with around 20 mods; larger plans go up to 36 GB for big communities. You get the Pterodactyl panel with SFTP, a nightly automatic backup and 1 to 10 manual backup slots (extra slots are a paid add-on). Compare plans on the pricing page or set up your server on the order page.