Draft. The sizes, prices and settings below are generated from this game's own configuration and are accurate. The wording around them is still being reviewed, so this page isn't listed in search yet.
All games / ProjectZomboid
Project Zomboid server hosting
Memory follows where you wander. Cores follow the dead.
About Project Zomboid on Instances
Project Zomboid streams the map in cells around each player. The map is enormous and players scatter, so what is loaded depends on how spread out you are far more than on how many of you there are.
Meanwhile the server ticks thousands of zombies: pathing, hordes, migration. Those two pressures pull in different directions, which is why memory and cores do not rise together on this list.
Five sizes, and why
Prices are for London; other regions differ by up to a quarter. You can change size later without starting a new world.
-
Solo · 1-2 Players
$0.14/hour
- vCPU
- 2
- Memory
- 4 GB
Solo or duo survival.
-
Small · 3-8 Players
$0.15/hour
- vCPU
- 2
- Memory
- 6 GB
A small group. More scattered players means more loaded cells.
-
Medium · 8-16 Players
$0.27/hour
- vCPU
- 4
- Memory
- 8 GB
An active server. The extra cores absorb the rising zombie simulation.
-
Large · 16-32 Players
$0.30/hour
- vCPU
- 4
- Memory
- 12 GB
A large server with players spread wide across the map.
-
Community · 32+ Players
$0.55/hour
- vCPU
- 8
- Memory
- 16 GB
A community server: heavy zombie population and wide world coverage at once.
How we picked them
- Memory demand tracks how many separate areas are loaded, not headcount. A handful of scattered survivors can load a great deal of world between them.
- Processor use is dominated by zombie simulation. Populated servers with high zombie counts are processor-bound, so cores ramp with player count and reach eight vCPU for large communities.
- It is JVM-based, so containers carry about 25% headroom over the heap. The default heap is around 3 GB and climbs with players and mods.
- The eight vCPU tier requires at least 16 GB alongside it, which is a Fargate constraint rather than a game one.
What you can change
Set from the instance's configuration page. The limits below are the ones the server actually enforces — they're read from its own schema. Plain-English descriptions are still being written.
| Setting | What it does | Accepts |
|---|---|---|
| Admin username | 4–16 characters | |
| Admin password | 8–32 characters | |
| Password | 8–32 characters | |
| Server name | 4–32 characters | |
| Default port | 1024–65535 | |
| Udp port | 1024–65535 | |
| Update on start | On or off |
Ready when you are
Pick a size, name your world, and it's running in a couple of minutes. Stop it when you're done and the billing stops with it.