Project Zomboid Dedicated Server Hosting: The 2026 Buyer's Checklist
"Looking to host a server for me and a few friends — any good hosts?" is the most-asked question on r/projectzomboid. The honest answer depends on your build (41 vs 42), modding intent, group size, and tolerance for self-management. This page is a vendor-neutral checklist of the 8 specs that actually matter for Project Zomboid in 2026. Bring it when you compare quotes.
1. Single-thread CPU clock speed
Project Zomboid's main simulation runs heavily on one core. Zombie pathfinding, weather, vehicle physics, and chunk updates all share the per-tick budget. Hosts with high core counts but low boost clocks (e.g., 32 cores @ 2.5GHz) run a small PZ server WORSE than a host with 6 cores @ 4.5GHz.
| Server scenario | Required single-thread clock |
|---|---|
| 2-4 players, vanilla B42 | 3.5 GHz+ |
| 5-10 players, light mods | 4.0 GHz+ |
| 10-20 players, heavy mod load | 4.5 GHz+ (Ryzen 7/i7) |
| 32+ player public server | 4.5-5.0 GHz, Ryzen 9 / i9 |
If a host advertises only "modern Xeon/Ryzen" without naming the model, ask. CPU model tells you the boost clock; core count tells you almost nothing for PZ.
2. RAM headroom (chunks are the killer)
PZ memory usage grows with explored chunks. A 4-player group that explores aggressively can have 5,000+ chunks loaded after a month. Each chunk has zombies, items, building data, environmental state.
| Setup | Recommended RAM |
|---|---|
| 2-4 players, B42 vanilla, modest map exploration | 4-6 GB |
| 5-10 players, B42, light mods | 8-12 GB |
| 10-20 players, B42, heavy mods (Britas, Common Sense, etc.) | 16-24 GB |
| 32+ players, public server | 32 GB+ |
Mid-tier hosts often cap RAM at the entry plan. PZ servers grow — make sure you can upgrade in-place without rebuild.
3. Build 41 vs Build 42 (and how the host handles the switch)
Build 42 was stable-promoted in early 2026, but many groups still run B41 for mod stability. A good host should support BOTH:
- Build version selector in the panel (not buried under support tickets).
- Per-deployment version pin (so different servers can run different builds).
- Documentation for the B41 → B42 migration path. See our B42 stable migration guide.
- Hot-rollback ability if a B42 patch breaks something.
If a host only supports the latest build with no rollback, that's a flag for modded groups.
4. Mod hot-load and pin-and-update workflow
PZ modding is Steam Workshop driven. Server admins need to:
- Sync Workshop mods to the server (Mods= and WorkshopItems= lines in INI).
- Update mods when authors push patches.
- Roll back mods that break on a B42 patch.
- Pin specific mod versions during unstable Workshop changes.
Demand from the host:
- 1-click "Update Workshop Mods" button in the panel.
- FTP/SFTP access to
Mods/folder for manual control. - Auto-restart after mod sync (or warn the player).
- Ability to set
SafeHouseAllowFire=false, sandbox settings, and mod-specific config via panel.
5. Anticheat sanity (B42 specifically)
B42's anticheat has been notably aggressive — kicking players for legitimate mod actions. A host should:
- Expose AntiCheatType1-24 toggles in the panel (or via INI edit).
- Document common AC kick patterns and which to disable for modded play.
- Not block your ability to disable anticheat layers (some hosts try to enforce them).
If you're running heavy mods, expect to disable several AC layers. See our recommended server settings guide.
6. Save backup retention
PZ saves include map state, player progress, zombie population, vehicle positions, base modifications. A 200-hour group server is irreplaceable. Demand:
- 14-day retention minimum. 7-day is too short.
- Hourly auto-backups during sessions. Daily-only loses too much.
- Self-service restore via panel. Not 24-hour ticket queue.
- Download backup via FTP. Off-host copy protects against host-side disasters.
- Map reset bug protection. The reported "map resets every time we play" issue is a save-cycle problem — good hosts handle it transparently.
7. Region selection
PZ is forgiving on latency compared to FPS games but unforgiving past 200ms.
| Player majority | Optimal datacenter region |
|---|---|
| US East | Virginia / Toronto |
| US West | Oregon / California |
| UK / Western EU | Paris / London / Frankfurt |
| Eastern EU | Warsaw / Frankfurt |
| Australia | Sydney / Melbourne |
| Mixed group | US East |
8. Refund + plan flex
- 2-day refund minimum if performance doesn't match the spec sheet.
- In-place plan upgrades (no server rebuild for bigger RAM).
- No 12-month contract lock-in (1-month minimum is standard).
- Static IP or stable DDNS hostname.
Red flags during vendor evaluation
- "Per-slot" pricing. PZ doesn't have hard player slots like CS2 — it has RAM and CPU. Per-slot pricing is a marketing leftover.
- Build version stuck at one release. If a host can't switch you between B41 and B42, walk away.
- Vague CPU specs. "Modern Xeon" tells you nothing. Demand the model.
- No mod auto-update. Manual mod updates are a recurring time sink. Modern hosts automate this.
- Aggressive contract lock-in. 12-month commitments for a niche game = predatory.
- Anticheat lockdown. Some hosts force AC settings you can't override. Bad for modded groups.
The self-hosted alternative
PZ self-hosting on a spare PC or VPS is feasible. The trade-offs:
- You handle port forwarding (16261 UDP for PZ, 16262 for Steam).
- Your home upload speed limits player capacity (20+ Mbps for 8+ players).
- You're the one diagnosing "server terminated" at 2 AM.
- CGNAT users can't expose the server without a tunnel.
For 2-4 close friends and patient debugging, self-hosting works. For 8+ players and scheduled play sessions, managed hosting wins on availability.
Common buyer questions
Should I get a Nitrado / generic provider, or a PZ-specialist host?
Generic providers (Nitrado, OVH, etc.) usually work fine for vanilla but can be clunky for modded play (auto-update flows, version pinning). PZ-specialist hosts (Supercraft, similar) handle the mod ecosystem and build-switching more elegantly. For modded groups, the specialist option is usually worth a 10-20% premium.
Is dedicated hardware required, or is a VPS okay?
For 2-6 players, a properly-spec'd VPS is fine. For 10+ players or heavy modded, dedicated hardware (bare metal) avoids "noisy neighbor" CPU contention that VPS plans suffer from during peak hours.
What about pay-per-hour or pay-as-you-go pricing?
A few hosts offer this. It works for groups that play in bursts (weekend sessions only). For continuous always-on servers, monthly flat pricing is usually cheaper.
Related guides
- Dedicated server setup
- B42 dedicated server setup
- B41 to B42 migration
- Recommended multiplayer settings
- Docker self-hosting
Supercraft Project Zomboid hosting checks every box: Ryzen 7/9 X3D hardware, build version selector (B41/B42) in the panel, 1-click Workshop mod sync, hourly backups with 14-day retention, 5 regions, in-place plan upgrades, and a 2-day refund policy. From $5.99/mo, no contract.