Project Zomboid

How Much RAM Does a Project Zomboid Server Need?

Plan Project Zomboid server memory around your build, players, mods, and save, with practical starting guidance and room for the operating system.

For a small friends-only Project Zomboid server, consider 6–8 GB assigned to the server as a starting test, with additional memory left for the host. This is practical planning guidance, not a universal minimum. Indie Stone support has suggested that range in a co-op memory-allocation case. It doesn't establish a player capacity for every build or mod list.

Older support advice mentions 4 GB as a starting minimum. Don't turn that historical number into a promise for a newer build, a long-running save, or a large set of mods.

Match the advice to your build

Check the game version and branch first. Build 41 advice is not automatically a benchmark for Build 42. Server and clients need compatible versions, and mods must support the build you're running.

Before choosing capacity, write down your expected simultaneous players, the server build, and the mods you want. “Ten friends in our Discord” could mean three online most nights or ten exploring at once. Those are different tests.

SituationSensible next step
Small group, new save, little or no moddingTest the starting allocation during actual play
An existing save with map and content modsLoad a copy with the full mod list before settling on capacity
More players or increased zombie activityWatch both memory and processing load during a busy session
Playing and hosting on the same PCBudget separately for the client, server, and operating system

Assigned RAM is not all the RAM you need

Zomboid uses Java. Its memory allocation doesn't include every byte used by Java or the rest of the machine. Giving the server all available memory can cause the very crashes you're trying to prevent.

In a Build 41 support case, support identified an 8 GB allocation on an 8 GB host as a problem and suggested leaving room for the operating system. The general lesson is to keep headroom, rather than copying those exact numbers for every setup.

For managed hosting, distinguish the plan's total resources from the game's allocation. Ask support to help interpret memory readings if you're unsure what the panel includes.

When adding RAM won't solve it

A failure during startup may be a mod conflict, a missing dependency, or a version mismatch. A server that starts but struggles during a large horde may need its settings or processing load investigated. “NormalTermination” by itself doesn't identify the cause.

Keep a backup, record the error and time, and try a separate unmodded test world if the problem began after adding mods. Don't strip mods out of your only save just to experiment. Check free disk space too; world saves and backups need somewhere to go.

Watch a normal evening's peak usage, then repeat after a major build or mod change. Save age is a reason to retest, not a fixed multiplier for buying RAM.

When you're ready, prepare your server name and administrator details. The Project Zomboid page shows the current Jovian configurations if you'd prefer managed infrastructure.