How Much Server Memory Does A Project Zomboid Server Need?

The short answer to how much server memory Project Zomboid needs: 4 GB for a small vanilla group, 8 GB as the minimum for modded play, and 12 GB or more for a busy community with heavy mods. The exact amount depends on player count, mods and how much of the map players explore. This page shows you how much RAM your own Project Zomboid server needs and how to confirm it in Apollo Panel.

How much RAM does a Project Zomboid server need?

Most community servers need 4 to 12 GB. A vanilla Project Zomboid server needs 2 to 3 GB just to start; each concurrent player adds roughly 0.5 to 1 GB, and heavily modded servers can need 12 to 32 GB depending on player count and mod types.

Project Zomboid server RAM by server size

What does server memory do in Project Zomboid?

Server memory holds everything the game simulates in real time: loaded map cells, zombies, vehicles, loot and inventories. The world is persistent, so the server side also tracks what changed around players’ previous positions, not just where they stand now.

That work happens on the server side only. A game client with 32 GB of RAM won’t help if the Zomboid server itself runs out of memory.

What drives RAM usage on a Zomboid server?

Four things drive RAM usage: how many players are online, which mods are loaded, the zombie population and how long the server runs between restarts.

Player count

Each player keeps the map cells around them loaded. Two players in one town share that data; in different cities, they double it. As a rule, plan for 0.5 GB per player, closer to 1 GB if your group splits up.

Mods and map areas

Mods are the biggest variable. Light mods that add a few items barely register, but 50+ mods can need several gigabytes more than vanilla gameplay. Large map overhauls add new map areas the server has to load and save, often around 1.5 GB extra.

Zombie population

Every nearby zombie is an entity the Zomboid server tracks, so more zombies means more memory, especially in cities. Lowering it frees server RAM without changing your plan.

Memory leaks over long uptime

Java servers accumulate memory usage over time, and some mods cause memory leaks. The longer the server runs, the more it grows, which is why a restart schedule matters as much as the RAM amount.

Build 41 vs Build 42 RAM requirements

Build 42 needs noticeably more memory than Build 41 for the same group. The Indie Stone moved Project Zomboid Build 42.20 to the stable branch on July 29, 2026, and it roughly doubled Knox Country, so more world gets generated, loaded and saved.

Treat RAM requirements from Build 41 guides as a floor. Build 41 remains on a legacy Steam branch, but its saves don’t load in Build 42: switching means a fresh world.

Calculate how much RAM your Zomboid server needs

Use this rule of thumb: base RAM, plus RAM per player, plus mods, plus 20–25% headroom for activity spikes.

1. Start with 3 GB as the vanilla base.

2. Add 0.5–1 GB per player for your peak: how many players are online at once, not the whitelist.

3. Add about 1 GB for a handful of light mods, several gigabytes for 50+ mods and around 1.5 GB per large map.

4. Multiply the total by 1.25.

Example: if you host 4 friends with 20 light mods, that’s 3 + 2 + 1 = 6 GB, plus 25% = 7.5 GB. An 8 GB plan fits that setup; more players push you to the next tier.

Apollo Panel server list showing the RAM assigned to each Project Zomboid server

RAM isn’t the only thing to compare when choosing a host. For a public server, check that the host offers full mod support, instant setup and DDoS protection.

Set the JVM heap in Apollo Panel

The JVM heap is the memory Java can use. Set it lower than your plan, and the extra RAM sits idle; set it equal to it, and the server crashes at the limit.

Important: stop the server first. A wrong value can keep the server from starting.

1. Open your Project Zomboid server in Apollo Panel and click Stop.

2. Go to Files and open ProjectZomboid64.json in the root folder.

3. In vmArgs, set -Xmx to about 75–80% of your plan (a safe rule for any size). For 8 GB, use -Xmx6g:

json

"vmArgs": [
    "-Djava.awt.headless=true",
    "-Xmx6g",

1. Click Save Content, then Start.

Apollo Panel file editor with ProjectZomboid64.json open and the -Xmx value highlighted

Note: on some setups, the startup script sets the JVM heap from a memory variable under Startup on every boot. If you see one, change it there or ask your host. Our related guides cover Files and SFTP if you’re new to the panel.

Set a restart schedule in Apollo Panel

Restarts clear memory and keep performance steady. No matter the size, restart at least once a day. If your server runs 50+ mods or a busy community, restart every 6–12 hours.

1. Go to Schedules and click Create Schedule.

2. Set Minute to 0, Hour to*/6 and fill* in the other fields.

3. Enable Only When Server Is Online and save.

4. Add a Send command task: servermsg "Server restart in 5 minutes". Players see it as an in-game message.

5. Add a Send command task with save and a 270-second time offset.

6. Add a Send power action task set to Restart with a 30-second offset.

7. Click Run Now to test it; no extra script needed.

Apollo Panel Schedules page with a 6-hour restart schedule and three tasks

Reduce Project Zomboid server RAM without upgrading

Before paying for more resources, find out what’s using them.

Audit your mods

Remove mods one at a time on a test copy and compare after an hour of play. Mods that add hundreds of items, vehicles or whole towns are the usual suspects. Every client downloads the same list, so a shorter one also helps players join faster. Keep what your community actually uses.

Check that it worked

Open Console and watch the memory card for a few days. Healthy RAM usage climbs after startup, levels off and drops after each restart. Above 90% of your plan at peak hours, move up a plan. If usage never passes 50%, you’re paying for too much RAM.

Apollo Panel memory graph dropping after a scheduled restart

Frequently asked questions

How much RAM should I give my Project Zomboid server?

For most people, 8 GB is the practical minimum for a small group with light mods plus headroom. A vanilla duo runs on 4 GB; a large modded community needs 12 GB or more.

How much memory should a server have?

Enough for peak players plus 20–25% headroom. The rule: 3 GB base, 0.5–1 GB per player, extra for mods. More players means more memory.

Does Project Zomboid use a lot of RAM?

Yes. A Project Zomboid server tracks a persistent world with loot, zombies and every player change, all kept in memory while cells are loaded.

Does more RAM fix lag?

Only if memory is the bottleneck. Zombie AI leans on the CPU, so free RAM with a maxed CPU needs more CPU speed instead. Lag can also come from a player’s own client or connection. Pick a host with SSD storage too, since the world saves constantly.

If something goes wrong

The server crashes with an OutOfMemory error → the heap is too small → raise -Xmx within your plan or upgrade.

Memory climbs until the server crashes → a mod is leaking → restart every 6 hours and audit your mods.

Players can’t join after you changed -Xmx → the heap is at or above your plan’s RAM → set it to 75–80%.

RAM looks fine, but the game lags → CPU or disk bottleneck → check the CPU graph and send your host’s support the Settings → Debug Information details so they can check node performance and resources.

Updated on: 04/11/2026