Project Zomboid Server Lag and Rubberbanding Fix (Build 42)

Project Zomboid rubberbanding usually means the server cannot keep up: it is short on Java memory, its CPU is maxed by zombies and players spread across the map, or a heavy mod list is dragging it down. Start by giving the Java heap enough RAM (about 75 to 80% of the machine's memory), restart the server daily, keep zombie population near Normal, and update to the latest stable patch. If only one player rubber bands, the problem is their connection, not the server.

Quick fix

1. Restart the server. If lag goes away for a while, it was memory or a mod update.
2. Check the Java heap (-Xmx) is set to most of the server's RAM, not a small default.
3. Make sure the server and players are on the newest stable Build 42 patch.
4. Lower Zombies one step in the sandbox if you raised it above Normal.
5. Remove the most recently added mods and test again.

Server lag or player lag?

Figure this out first, because the fixes are different.

Fix 1: Give Java enough memory

The server runs on Java, and Java only uses the memory you allow it with the -Xmx setting. Too low and it stutters as it constantly cleans up memory. Higher than the machine has and the system kills it.

• Windows: edit -Xmx in StartServer64.bat in the server folder.
• Linux: edit the -Xmx value in ProjectZomboid64.json in the server folder.

Set it to roughly 75 to 80% of the RAM the machine has free for the server, and leave the rest for the operating system. Build 42 needs noticeably more than Build 41, and mods and map mods add to it:

A SteamCMD update can overwrite these files, so check the value again after updating.

Fix 2: Zombies, spread and driving

Zombie simulation is the server's biggest CPU cost. Each player loads the area around them, so four players in four towns cost far more than four players in one base.

• Zombie population. Zombies = 4 (Normal) in SandboxVars.lua is a good ceiling for most servers. Insane (1) on a busy server is asking for rubberbanding.
• Respawn. ZombieConfig.RespawnHours set low keeps refilling cleared areas. Fine for challenge, but costs CPU on busy servers.
• Driving. Fast driving forces the server to load new map chunks quickly. If lag only happens in cars, slow down on the highways and check the server's disk speed.
• Corpses. Big fights leave hundreds of bodies. HoursForCorpseRemoval in the sandbox clears them over time. Do not set it so high that bodies never go.

Changes to zombie population mostly show in areas that load after the change.

Fix 3: Mods and map mods

Every mod runs code on the server, and some run it constantly. Map mods add a lot of world to load. If lag started after adding mods:

1. Back up.
2. Remove the most recent mods from Mods= (keep WorkshopItems= for now).
3. Restart and test.
4. Add them back one at a time.

Mods that spawn extra zombies, add lots of vehicles or rewrite loot tend to cost the most. A Workshop update can also change a mod's performance overnight, so a daily restart that pulls updates is good practice. See how to add mods to a Project Zomboid server for load order.

Fix 4: Restart daily and save sensibly

Long uptimes slowly build up memory use and pending Workshop updates. Restart once a day at a quiet hour:

servermsg "Restart in 5 minutes"
save
quit

quit saves and stops the server. Then start it again from your service or script.

For autosaves, SaveWorldEveryMinutes=15 in the ini is a sensible middle ground. Saving every minute on a big world causes regular hitches, especially on hard drives. Use an SSD for the server if you can.

Fix 5: Keep the build current

Build 42 multiplayer is still being polished. The 42.2x patches after the stable release in July 2026 have focused on multiplayer issues such as desync, teleporting passengers and stutter. Running an old patch means living with bugs that are already fixed. The server only updates when SteamCMD runs, so restart or update it after every game patch, and make sure every player has updated too.

Fix 6: Network and connection

For a home hosted server:

• Upload bandwidth matters more than download. Each player costs upload.
• Forward UDP 16261 and 16262 to the server PC, so players connect directly.
• Do not host on Wi-Fi.

For a single lagging player: check their ping, close downloads and streams, and verify game files in Steam. The PingLimit setting in the ini kicks players over a certain ping. If friends far away keep getting kicked, check that value and raise it.

Fix 7: The server is simply too small

If the heap is right, mods are sane and it still lags with your normal group, the hardware is the limit. Project Zomboid uses a few busy threads, so fast cores help more than many slow ones.

On GamezServers, we size the Java heap to your plan on every start, so Fix 1 is done for you, and the server updates itself on each restart. If you outgrow your plan, upgrade from Settings. It is prorated and keeps your world. The Check mod updates button tells you when a Workshop update is waiting. Plans are 6, 8 and 12 GB on Project Zomboid server hosting. The general checklist in why is my game server lagging applies too.

FAQ

Why do zombies teleport on my Project Zomboid server?

The server is falling behind on simulation, so positions jump when it catches up. Usually too many zombies, players spread over the map, or not enough Java memory.

Does Build 42 lag more than Build 41?

Build 42 uses more RAM and CPU than Build 41 for the same group, and its multiplayer is newer. Give it more memory than you would have for Build 41.

How much RAM should I give Project Zomboid's server?

About 75 to 80% of what the machine has free for it. 6 GB total suits a small vanilla group, 8 to 12 GB a modded or bigger one.

Why does my car rubber band when driving?

The server has to load map chunks as fast as you drive. Slow down, check the server disk is an SSD, and make sure the server is not short on CPU.

Does PauseEmpty help with lag?

Not while people play. It only stops time when nobody is online, which saves resources overnight.