Project Zomboid Starter
€4.10 / month
- vCPU
- 2 cores
- RAM
- 4 GB
- Storage
- 60 GB NVMe SSD
- Processor
- AMD Ryzen 9 9950X3D
- Location
- Turkey
More features
- Traffic
- Unlimited
- Operating system
- Linux/Windows
SURVIVAL · PC
Project Zomboid Game Server
Project Zomboid load grows through active cells, zombie and item persistence, player bases, vehicles, and Workshop content.
AMD Ryzen 9 9950X3D
Project Zomboid Recommended · 6 GB
€5.35 / month
- vCPU
- 4 cores
- RAM
- 6 GB
- Storage
- 80 GB NVMe SSD
- Processor
- AMD Ryzen 9 9950X3D
- Location
- Turkey
More features
- Traffic
- Unlimited
- Operating system
- Linux/Windows
Project Zomboid Recommended · 8 GB
€7.14 / month
- vCPU
- 4 cores
- RAM
- 8 GB
- Storage
- 100 GB NVMe SSD
- Processor
- AMD Ryzen 9 9950X3D
- Location
- Turkey
More features
- Traffic
- Unlimited
- Operating system
- Linux/Windows
Project Zomboid Performance · 10 GB
€9.82 / month
- vCPU
- 6 cores
- RAM
- 10 GB
- Storage
- 120 GB NVMe SSD
- Processor
- AMD Ryzen 9 9950X3D
- Location
- Turkey
More features
- Traffic
- Unlimited
- Operating system
- Linux/Windows
Project Zomboid Performance · 16 GB
€17.85 / month
- vCPU
- 8 cores
- RAM
- 16 GB
- Storage
- 200 GB NVMe SSD
- Processor
- AMD Ryzen 9 9950X3D
- Location
- Turkey
More features
- Traffic
- Unlimited
- Operating system
- Linux/Windows
Resource selection
Choose Your Project Zomboid Server Plan
Dense city cells, zombie movement, loot respawn, and vehicles add simulation work; a long-running world differs from a new save.
Project Zomboid Starter
The first resource profile for a controlled launch and measurement baseline.
- Processor
- AMD Ryzen 9 9950X3D
- vCPU
- 2
- RAM
- 4 GB
- Storage
- 60 GB NVMe SSD
Project Zomboid Recommended · 8 GB
A middle profile to assess as community and content workload grows.
- Processor
- AMD Ryzen 9 9950X3D
- vCPU
- 4
- RAM
- 8 GB
- Storage
- 100 GB NVMe SSD
Project Zomboid Performance · 16 GB
A higher resource profile to compare when measured CPU, RAM or storage needs increase.
- Processor
- AMD Ryzen 9 9950X3D
- vCPU
- 8
- RAM
- 16 GB
- Storage
- 200 GB NVMe SSD
Evaluate CPU, memory, and storage options against the expected game workload.
Player load
How player count affects resources
Spread-out players keep more cells active, while a shared base defence concentrates zombies and items; observe both patterns separately.
-
Single-core strength
Measure processor peaks and game-loop response during a busy session.
-
RAM
Track peak memory use together with growth headroom.
-
NVMe storage
Measure storage behaviour across saves, logs, and backups.
-
Mod and script density
Measure actual mod, plugin, and script workload separately from extension count.
-
World / map size
Track world size, active regions, and persistent-data growth together.
-
Player scenario
Evaluate concurrent-player distribution, activity, and content workload together.
Detailed planning notes
| Scenario | Resource effect | Check |
|---|---|---|
| Concurrent players | Spread-out players keep more cells active, while a shared base defence concentrates zombies and items; observe both patterns separately. | Measure a busy session |
| Game activity | Dense city cells, zombie movement, loot respawn, and vehicles add simulation work; a long-running world differs from a new save. | Repeat the peak scenario |
| World / save growth | Explored cells, player structures, vehicles, and objects expand the database; compare startup and backup duration with world age. | Track save and restore duration |
CAPACITY ESTIMATE
Estimate Resources for Your Project Zomboid Server
Estimate starting capacity from your player and world goals.
Capacity summary
Estimated CPU, memory, storage, and a suitable resource profile appear here.
Mod / plugin level
Mods, plugins, and additional content
Workshop IDs, map order, and dependencies must match on client and server. Test map-mod changes against a save copy.
Mod compatibility can vary by game and server-software release.
Administration
Administration and server settings
Manage sandbox options, respawn behaviour, loot, zombie density, safehouses, and the mod list through planned changes.
Installation and management
After deployment, manage Project Zomboid processes, version changes, and settings that require restarts in controlled maintenance windows.
Backups
Back up Project Zomboid saves, configuration, and additional-content data as separate restore points before changes.
File access
Limit file access to Project Zomboid configuration, logs, and managed content directories; stop the relevant process before replacing active files.
Frequently asked questions
Project Zomboid
What should I measure for a long-running world?
Evaluate the existing save with its developed bases, vehicles, zombie density and loot-respawn settings. Measure CPU and memory use during busy city activity and record save size separately from a fresh-world test.
How should I test a group planning to settle in different towns?
Compare simultaneous exploration in separate areas with a shared-base defence. Active areas and zombie activity can differ, so player count should not be the only input to resource selection.
Can I keep the same mod list when changing the game branch?
Verify the target client and server branch, mod versions and dependencies separately. A mod working on the previous branch does not prove compatibility with the new one. Test the transition using a copy of the existing save.
What should I do before adding or removing a map mod?
Keep the save, map order and mod dependencies together. Open the changed copy and inspect visited areas, bases and access. Do not overwrite the working world with the first migration attempt.
Should I change settings or resources first as the server grows?
Review zombie density, loot respawn and vehicle accumulation alongside the community rules. After separating configuration-related workload, compare packages against any recurring measured CPU, memory or storage constraint.
NEXT STEP
Choose Your Project Zomboid Server Plan
Contact support for ordering details and special requirements.