Why host a dedicated Project Zomboid server?
You can host PZ from your own PC, and for a three-person Saturday night it's fine. The moment you want the world to keep ticking while you're at work, or you want more than five or six people in it, the home-hosted route runs out of road. A dedicated box sidesteps the obvious stuff — your PC sleeping, Windows Update rebooting mid-raid, your upstream choking when someone else in the house starts streaming — but the real reason we push people toward dedicated hosting is consistency. PZ's world state is fragile. A server that crashes hard mid-save can corrupt chunks, and we've seen groups lose weeks of progress to a single bad shutdown on a home machine with no backup discipline.
A proper host gives you 24/7 uptime, automated backups you don't have to think about, and hardware that isn't fighting your game client for RAM.
What actually matters when you're picking a host
PZ is one of the more demanding survival servers to run well, and the specs that matter aren't the ones most hosts put on the front of the box.
RAM is the number that decides everything
The Zomboid server loads a huge amount of map data, tracks every zombie as an individual entity, and on Build 42 layers animal simulation, crafting stations and multi-level basements on top. Rough working numbers we use internally:
| Group size | Build 41 | Build 42 |
|---|---|---|
| 2-5 vanilla | 4 GB min, 6-8 GB comfy | 6 GB min, 8 GB comfy |
| 10-20 with light mods | 8 GB min, 10-12 GB comfy | 10-12 GB min, 12-16 GB comfy |
| 20+ with heavy mods | 12-16 GB | 16 GB+ |
If you take one thing from this post: 8-10 GB is the real floor for a healthy multiplayer Zomboid server, and moving from B41 to B42 realistically adds 2-4 GB on top of whatever you're running today.
The pricing models you'll run into
Every host sells PZ slightly differently, and the headline price almost never tells you what you're actually getting. In broad strokes there are three models out there:
Slot-based plans bundle RAM into tiers — you pick how many player slots you want and the RAM comes with it. This is how LOW.MS and Host Havoc sell PZ, and it's the easiest model to reason about because your "is there enough memory?" question is answered at purchase.
RAM-based or cloud plans (G-Portal is the obvious example) sell you GB of memory and leave slots flexible or effectively unlimited. These can work out well if you know exactly how much RAM you need and don't mind doing the maths.
Hybrid slot plans — Nitrado and Shockbyte sit here — advertise a cheap per-slot headline but ship with 2-4 GB of RAM, then sell memory as a paid add-on. The sticker price looks great until you read the upgrade page.
The only honest yardstick is PZ's actual appetite. If a plan can't comfortably sit at 8-10 GB of RAM for a real multiplayer session, the per-slot price on the front page isn't the number you should be looking at.
Single-thread CPU performance
PZ's server loop is largely single-threaded, so raw clock speed and IPC matter far more than core count. A modern AMD Ryzen part will walk all over older Xeon hardware for this one specific workload. At LOW.MS we offer a latest-generation AMD Ryzen upgrade for groups that want the fastest single-thread performance we can give them — it's the upgrade we'd actually recommend before more RAM for smaller, mod-heavy groups.
NVMe storage and DDoS protection
PZ reads and writes world chunks constantly as players explore. NVMe is effectively table stakes in 2026 — if a host is still quoting SATA SSDs, keep walking. DDoS protection matters the moment your server is public; game servers get poked at far more than people realise.
A mod manager you'll actually use
This is the bit we'd push on. PZ lives and dies by its Steam Workshop mods, and editing Mods= and WorkshopItems= lines by hand in two separate config files is the single most common way new admins break their server. The LOW.MS panel ships a Mod Manager that browses Workshop, installs mods with one click and keeps both lists in sync. Whatever host you end up on, check that mod management isn't a text-editing exercise.
Project Zomboid hosting at LOW.MS
Our PZ plans are slot-based with RAM bundled per tier, NVMe storage, automatic Cloud Backup, DDoS protection and multi-region deployment as standard. Every server runs on the TCAdmin-based LOW.MS control panel — Web Console, File Manager, Configuration Files, Commandline Manager, Mod Manager, Steam Update, Scheduled Tasks, Cloud Backup and Cloud Restore are all in the sidebar, not behind a support ticket.
Full configuration options, current pricing and regions are on the Project Zomboid server hosting page.
Build 42: where it actually stands
Build 42 is the update people keep asking us about, so let's be straight about what it is and isn't in April 2026.
B42 adds animal husbandry, the crafting discipline overhaul, basements, taller buildings and a chunk of new map content. It's a genuinely large update and most of it shipped to the single-player unstable branch a while back. Multiplayer is the piece that matters for hosting, and B42 multiplayer went to the unstable branch in December 2025 (build 42.13, Indie Stone's announcement). It is not on the default branch, it is not stable, and Indie Stone have not announced a stable B42 MP date.
Indie Stone's current public guidance is to keep B42 MP sessions at or below 20 players while it's in stress-test. We'd go further and say treat anything above 10-15 players as experimental until a few more patches land. If you want a large public server today, B41 is still the sensible branch. If you want to dig into what B42 actually changes for multiplayer groups, our Build 42 multiplayer survival guide walks through it.
The other thing worth flagging: B42 is not a drop-in replacement for B41 in resource terms. Expect the 8-10 GB you were comfortable with on B41 to climb toward 10-12 GB on B42 for the same group, and plan RAM headroom accordingly.
Running the thing well
A few beats we'd give any new PZ admin.
Start with sensible defaults and resist the urge to tune everything on day one. Zomboid has something like 200 server settings and it's genuinely tempting to spend an evening turning every dial. Don't. Ship the defaults, play three sessions, then change the two or three things your group actually complains about. Our best settings for 2026 post covers the handful that actually matter.
Enable the in-game backup belt-and-braces. Even with Cloud Backup running at the host level, turn on BackupsOnStart=true and set BackupsPeriod=60 in your servertest.ini. Two backup systems running independently is the only configuration we fully trust for a world people care about.
Restart daily during off-peak. PZ's memory use drifts upward over long uptimes. A scheduled restart at 4am clears it cheaply — TCAdmin's Scheduled Tasks in the panel handles this in about thirty seconds of setup.
Watch your resource graphs, not your crash logs. The LOW.MS panel surfaces live RAM and CPU under Current Activity & Stats. If you're consistently sitting above 85% RAM, upgrade before something goes wrong rather than after. When something does go sideways — a save that won't load, a mod that won't initialise, a server that refuses to start after a Steam Update — our Project Zomboid troubleshooting guide covers the issues we see support tickets for most often.
Be honest with your players about branches and mods. Pin your game branch, pin your mod list, and tell people before you change either. More community servers die from an unannounced mod swap than from any technical fault we've ever debugged.
For the click-by-click setup walkthrough, the Project Zomboid getting started guide and the server configuration reference are the two KB articles to bookmark.