Improve Project Zomboid server performance

Why a Project Zomboid server stutters, what zombie population and respawn settings actually cost you, and the changes that cut the load without making the game feel different to play.

6 min read · Updated Oct 21, 2026 · By GuavaHost Team

Project Zomboid is demanding to host, and not for the reason people assume. It is rarely memory and rarely network. It is one busy thread simulating zombies, streaming map cells in and out as players move, and running Lua for every mod installed. So the settings that help most reduce how much the server simulates at once.

Work out what is actually slow

Name the symptom first. They point at different causes.

• Everyone rubberbands at the same time, in bursts. The server cannot keep up with simulation. Look at zombie counts and player spread.
• It stutters briefly every few minutes. Almost always the world save, controlled by SaveWorldEveryMinutes.
• It gets worse the longer the server runs and a restart fixes it. That points at memory. See the signs a server is running out of RAM.
• Only one player lags. Their connection, not your server.
• It started the day you added mods. Always suspect the most recent change first.

The Console tab holds the evidence. Watch it with players online for warnings about tick time, long saves, or repeating Lua errors. An error firing once per tick is a performance problem even though it looks cosmetic.

Zombie population is the biggest lever

Zombies are the single largest cost, because every active zombie near a player is simulated. That is why a server fine all week falls over during a helicopter event. The settings live in the ZombieConfig section of servertest_SandboxVars.lua, which you edit on Server properties under Game tools:

• PopulationMultiplier scales the whole map's zombie count. This is the main dial. Dropping it from the default to around 0.6 is barely noticeable in play and takes real load off the server.
• PopulationStartMultiplier and PopulationPeakMultiplier set the count at the start and at the peak. Lowering the peak keeps a long running server playable at month four.
• PopulationPeakDay is the in-game day the peak is reached. Pushing it later spreads the increase out.
• RespawnHours is how many in-game hours before an emptied area refills. Raising it means cleared towns stay cleared, which players like anyway.
• RespawnUnseenHours is how long a cell must be unwatched before it repopulates.
• RespawnMultiplier is how much of the original population comes back. Set it to 0 for no respawns.

A good first pass: lower PopulationMultiplier a little, raise RespawnHours, lower RespawnMultiplier. None of that changes how a fight feels, it just stops the server maintaining zombies no player will ever meet.

Stop the server before editing the sandbox file, or your changes can be overwritten at the next save. The syntax matters too: it is a Lua table, so every line keeps its trailing comma and the SandboxVars = { wrapper stays intact. Detail in our guide to server and sandbox settings.

Players spread across the map cost more than players together

The server loads the map in cells around each player. Four friends looting the same block of Muldraugh is one patch of map loaded. Four friends in Riverside, Rosewood, West Point and a farmhouse is four patches, four sets of zombies, four streams of chunk loading.

That explains a lot. A server that handled eight players on day one can struggle with the same eight at month three, when everyone has their own base, and map mods multiply it because there is more map to spread across. PauseEmpty=true in servertest.ini helps either way: it pauses the world when nobody is connected.

So be honest about player counts. A vanilla server with a group playing together handles a dozen or so comfortably on decent hardware, while a heavily modded one with everyone in their own corner of the county can feel rough at six. No setting fixes that: the mod list is the budget you are spending your CPU headroom on.

Mods are the usual culprit

Content mods add items and recipes, mostly a mild memory cost. Anything running Lua every tick, and anything adding map regions, is a different story.

• Add mods a few at a time. Install twelve at once and you will have no idea which one slowed things down.
• Treat map packs as the expensive ones. Every extra region is more world to keep loaded, which our RAM guide goes into.
• Watch the Console for repeating Lua errors. A mod throwing an error on a timer burns CPU continuously.
• Prune honestly. Most servers carry mods nobody has used in months. Removing a content mod mid-save strips its items out of the world, so snapshot on the Backups page first, then edit the Mods= and WorkshopItems= lines as the Workshop mods guide describes.

Server settings worth adjusting

In servertest.ini, on the Server settings tab of Server properties:

• SaveWorldEveryMinutes controls the periodic world save behind that regular brief stutter. Saving less often means fewer stutters and more to lose in a crash. It is a trade, not a fix.
• MaxPlayers is worth setting honestly rather than aspirationally. A server that lets twenty in and lags for all of them is worse than one that holds twelve well.
• The ZombieUpdate options, including ZombieUpdateMaxHighPriority and the priority radius settings, decide how many zombies get full attention each tick and how far out. The defaults are sensible, so change one value in small steps, because pushing them too far makes distant zombies visibly stupid.

Do not expect a dramatic win from the ini file. Population settings and the mod list are where the real gains are.

Where hardware comes in

Project Zomboid leans on single core speed rather than core count, because the main simulation loop is one thread. That is why GuavaHost runs high clock AMD Ryzen and Intel hardware, and why single thread performance matters here.

RAM is different: it stops the server running out of room, and a server short on memory crashes or stalls rather than merely stuttering. Adding memory to a server that already has enough changes nothing. You can change RAM any time with Manage plan in the server menu, then Change plan, with billing prorated.

To tell the two apart: if performance degrades over hours and a restart fixes it, suspect memory. If it is bad immediately whenever several players are active in different places, that is simulation load on the CPU.

A sensible order to work through

1. Snapshot on the Backups page, then watch the Console with players online and name the symptom.
2. Lower PopulationMultiplier, raise RespawnHours, lower RespawnMultiplier, and set PauseEmpty=true.
3. Remove or update any mod throwing repeated Lua errors, then restart on a schedule.
4. Only then look at plan size, checking your RAM usage first.

Test between steps with the people who actually play, because one player in a field is cheap no matter how the server is configured. Commands for checking things live are in our admin commands guide.

Common questions

Will lowering the zombie population make the game too easy?

Not as much as you would think. A moderate reduction mostly removes zombies that are far from any player and were being simulated for nothing. If you want the fights to stay hard, lower the population multiplier but leave the sandbox settings for zombie strength, speed and hearing alone.

Why does my server stutter every few minutes?

That is the periodic world save, controlled by the save interval setting in your server ini file. Saving less often reduces the stutters but means losing more progress if the server crashes, so pick an interval you would be happy to lose.

Does adding more RAM fix Project Zomboid lag?

Only if you are actually short of memory, which shows up as crashes, failed startups or performance that gets worse the longer the server runs. Stutter with several players active in different places is simulation load on the CPU, and more memory does nothing for it.

How many players can a modded server really hold?

Fewer than a vanilla one, and it depends far more on your mod list and how spread out people are than on the number itself. A heavy list with map packs and players in separate bases can feel strained at six, while a lightly modded group playing together is comfortable at a dozen.

Still stuck? Jump into our Discord at discord.gg/GuavaHost and the team will help you out.

• project-zomboid
• performance
• lag
• sandbox
• mods

Host a Project Zomboid server From $5.99/mo, with instant setup and DDoS protection.

Still need help? Our team is online 24/7 to answer questions.

Contact support