How to Reduce Lag on a 7 Days to Die Server
7 Days to Die server lag spikes hardest on blood-moon night, because every alive zombie is AI on the CPU. The fix: cap the zombie counts, trim the horde size, lower view distance, keep mods sane, and put it on a fast CPU with enough RAM. Here's how to keep it smooth even on horde night.
7DtD is heavier than it looks — every alive zombie is AI the CPU has to run, so lag peaks when hordes are largest (blood-moon night). The main levers are the zombie counts, view distance and mods, on top of enough RAM and a fast CPU.
Below is the fix. For the settings context see our best 7 Days to Die server settings; if the CPU is the wall, our 7DtD hosting runs fast cores.
What you'll need
A quick checklist before you begin — have these ready and the rest is easy.
- Access to serverconfig.xml (zombie caps, view distance).
- Sensible MaxSpawnedZombies and BloodMoonEnemyCount.
- A view distance of 8-10 on a busy server.
- Enough RAM (6-8 GB vanilla, 12 GB+ modded) and a fast CPU.
- A scheduled restart to clear entity state.
Fix 7 Days to Die server lag, step by step
Cap MaxSpawnedZombies
This is a server-wide cap (not per player) — every extra zombie is CPU load. Default 64 suits small groups; drop to 40-50 on a bigger server to keep it smooth.
<property name="MaxSpawnedZombies" value="50"/>
Lower the blood-moon horde
BloodMoonEnemyCount is the max alive zombies per player during a horde — so it multiplies fast on a full server. Drop it from 8 to 6 so horde night doesn't melt performance for everyone.
<property name="BloodMoonEnemyCount" value="6"/>
Reduce view distance
After zombie caps, ServerMaxAllowedViewDistance is the biggest performance lever. Dropping it from 12 to 8-10 noticeably improves a busy server, at the cost of shorter draw distance.
<property name="ServerMaxAllowedViewDistance" value="8"/>
Trim heavy mods
Big overhaul packs (Darkness Falls, Undead Legacy) add significant load. If lag started after a modpack, that's the cause — run a lighter set, or make sure the hardware is sized for it (12 GB+).
Give it RAM and a fast CPU
6-8 GB suits vanilla; a modded server wants 12 GB+. And because zombie AI is CPU-bound, a fast high-clock core is what keeps a full horde smooth. If the config is tuned and it still lags on horde night, the CPU is the wall.
Restart on a schedule
7DtD accumulates entity state over long uptimes. A scheduled restart every several hours clears it and keeps performance steady — set it and forget it.
Where the lag comes from
Blood moon is the spike
BloodMoonEnemyCount is per player, so it multiplies on a full server. Drop it to 6 so horde night stays playable for everyone.
Zombies are CPU load
Every alive zombie is AI on the CPU. Cap MaxSpawnedZombies sensibly and run a fast high-clock core — that's what holds up under a horde.
View distance is a big lever
After zombie caps, dropping ServerMaxAllowedViewDistance to 8-10 is the biggest single performance gain on a busy server.
Mods drive the RAM need
Overhaul packs need 12 GB+. If lag started with a modpack, either size the RAM for it or run a lighter set.
Common problems & fixes
Hit a snag? These are the issues people run into most — and how to solve them.
It only lags on horde night
BloodMoonEnemyCount multiplies per player. Lower it to 6, and cap MaxSpawnedZombies to 40-50.
Lag started after adding a modpack
Overhaul packs are heavy. Run a lighter set, or give the server 12 GB+ RAM and a fast CPU.
The whole server lags with players spread out
Drop ServerMaxAllowedViewDistance to 8-10 — it's the biggest lever after zombie caps.
Config tuned but still lags under a horde
The CPU is the wall — zombie AI is CPU-bound. Move to a fast high-clock core.
Skip the setup — host it with ESAGAMES
Config tuned but horde night still crawls? Our 7 Days to Die hosting runs fast high-clock CPUs on NVMe with DDoS protection and easy config — the hardware side of a smooth blood moon, in Frankfurt.
Frequently asked questions
Why does my 7 Days to Die server lag on blood-moon night?
Because every alive zombie is AI the CPU must run, and blood-moon hordes are the largest counts of the week. BloodMoonEnemyCount is per player, so it multiplies on a full server. Lower it (to 6), cap MaxSpawnedZombies, and run a fast CPU.
How do I reduce zombie lag on a 7 Days to Die server?
Cap MaxSpawnedZombies (a server-wide limit) to 40-50, and lower BloodMoonEnemyCount to 6 for horde night. Both directly cut the AI load on the CPU, which is where 7DtD lag comes from.
What server settings most affect 7 Days to Die performance?
The two biggest are MaxSpawnedZombies (server-wide zombie cap) and ServerMaxAllowedViewDistance — dropping view distance from 12 to 8-10 noticeably improves a busy server. BloodMoonEnemyCount matters most for horde night.
Do mods cause 7 Days to Die server lag?
Big overhaul packs like Darkness Falls or Undead Legacy add significant load. If lag started after installing a modpack, that's the cause — run a lighter set or make sure the server has 12 GB+ RAM and a fast CPU for it.
How much RAM and CPU does a smooth 7 Days to Die server need?
6-8 GB for vanilla and 12 GB+ for a modded server, plus a fast high-clock CPU — zombie AI is CPU-bound, so the core speed is what holds a full horde together. A scheduled restart every few hours keeps performance steady.
Keep reading
7 Days to Die is a trademark of The Fun Pimps. ESAGAMES is an independent hosting provider, not affiliated with or endorsed by The Fun Pimps. You must own a legitimate copy of the game to play.