Project Zomboid server lag after Build 42

Is it the client, the network or the Project Zomboid server?

Start by asking who is affected and since when, because each layer has a different fix. This split follows Connect Hosting's lag article (dated 28 Aug 2026 on the page, which also describes events in October 2026), a seller's triage with no data behind it, and the fan-run pzfans troubleshooting guide for Build 42.19.

The ping column arrived in The Indie Stone's 42.20.0 notes ("Added ping values for each player in the Players and Users List tabs"). Failure to connect is a separate problem from lag: the community-written PZwiki lists UDP 16261 and 16262 as the default ports.

What should you check first on a Build 42 server?

Check the free and certain things before anything that costs money or changes the world. The order is this page's synthesis of its sources.

1. Build. Put the server and every client on the same branch and version, then update.
2. Console. Search console.txt for java.lang.OutOfMemoryError: Java heap space. pzfans gives the path as ~/Zomboid/console.txt on Linux and %UserProfile%\Zomboid\console.txt on Windows.
3. Heap. Find the -Xmx your launch method really reads (see the fix list below).
4. Memory over time. Log the process every minute through a full session and a restart. Confirm the process name with ps first, because it varies by launch method.

while true; do
  echo "$(date -Is),$(ps -o rss= -p "$(pgrep -f ProjectZomboid | head -n1)")" >> pz-rss-kb.csv
  sleep 60
done

1. Pauses. On Java 9 or later, add -Xlog:gc*:file=gc.log to the launch options and see whether pauses line up with the freezes.
2. Timing. Note when lag happens, who is online, where they are and what changed since the last good day.

Change one thing, then log again.

Has a Build 42 patch already fixed your lag?

It may have, because several hotfixes target server lag directly. The wording below is The Indie Stone's, from the Steam news feed read on 8 Nov 2026. None of these notes gives a before-and-after figure, and "should fix" is the studio's expectation.

On 27 Oct the default Stable branch was 42.21, with 42.22 on a new Pre-Release branch replacing Unstable; hotfixes followed on 4 and 6 Nov. The post invites server admins to opt in for testing. This page suggests keeping a live world on Stable unless you have a backup and every player can move with you.

Hotfix posts ask players to reproduce bugs "on a fresh save with no mods installed", so a fresh no-mod save is a cheap test before blaming hardware. The 42.20.1 and 42.20.3 posts ask anyone still hitting out-of-memory errors in a new save to file logs and a debug profiler video. Posts on 9 and 24 Jul 2026 promise a "Build 42 Support Update that focuses on optimization" during the rest of 2026.

What does each kind of lag look like?

Memory, load and scheduled work look alike to players and separate in a log. Most rows are Connect Hosting's descriptions, so use them to organise your log and do not treat them as findings.

Which fix should you try first?

Try them in this order. No source read for this page publishes how much any of these reduces lag or memory use.

1. Update the server and clients.
2. Correct the heap. Connect Hosting says ProjectZomboid64.json has its own -Xmx in vmArgs (-Xmx8g on servers it checked in October 2026), and reports one 16 GB server whose startup line asked for about 13 GB while the JSON said 8 GB, which died with the heap error. PZwiki says StartServer64 "specifies 16GB of starting memory" by default; pzfans gives 4096 MB as the Host Server default. Connect Hosting advises leaving about 3 GB for the JVM, the operating system and non-heap memory. PZwiki's example launch line uses -XX:+UseZGC, so check your collector before copying Minecraft G1 advice.
3. Bisect the mods. Remove the newest batch, restart and retest. On 21 Oct 2026 The Indie Stone said Java-based mods "are not officially supported" and "will be fundamentally broken by those updates, without warning", so Connect Hosting's advice to suspect them first after a game update is reasonable.
4. Bound world build-up. In servertest_SandboxVars.lua, Connect Hosting points to HoursForCorpseRemoval, HoursForWorldItemRemoval and WorldItemRemovalList. It quotes the game's description that items are removed "the next time that part of the map is loaded", so one restart will not clear a world. Stop the server and back up before editing.
5. Step population down with PopulationMultiplier, if lag tracks busy areas. Connect Hosting says fewer zombies "won't touch" rhythmic, all-at-once freezing. It also blames Build 42 animals for part of the load, with no data, so log before changing animal settings.
6. Schedule restarts as a bridge. WinterNode's RAM guide (18 Mar 2026) suggests every 6-12 hours without giving a method. PZwiki's admin commands include servermsg to warn players, save, and quit. A restart clears growth over uptime and leaves world, mods and population as they were.

What is not worth your time?

Skip these until a log points at them.

• Swap. Connect Hosting says a Java server touching swapped-out heap during collection turns short pauses into long freezes (RAM post).
• Setting -Xmx to the full plan. Connect Hosting warns the operating system may kill the process. The Build 42 RAM figures cover the gap.
• Keys you cannot find in your own file. Connect Hosting says it knows of no developer documentation for a network setting that fixes lag. Supercraft (updated 2 Nov 2026) recommends LightingUpdateInterval and a "Z-Net" mod, with no link to it. LOW.MS (25 Aug 2026, still calling Build 42 unstable) recommends ZombieUpdateDelta. Both sell hosting, and neither key appears in PZwiki's server settings list read on 8 Nov 2026.

When is the answer a bigger plan or a different host?

A bigger plan is the answer when your log, on a current build with mods checked, shows the process near the plan's limit in normal play, or OutOfMemoryError keeps returning. Size it with the Build 42 RAM figures and sanity-check it in the server RAM calculator.

More RAM will not help when memory is flat and lag still follows load. Pine Hosting and Supercraft both point to CPU speed for simulation and publish no numbers. Ask your host which CPU the plan uses and whether it is shared.

A different host makes sense for reasons you can check first: no region near your players, no access to console logs, or no control of launch settings. LOW.MS says RAM on its plans is tied to the tier and you do not hand-edit Xmx values there, so ask before you buy. Plan structures are compared on the Project Zomboid hosting hub.

What GameServerBench plans to record

GameServerBench holds no Project Zomboid lag data. The planned protocol would run fixed worlds with different animal densities and mod lists on one setup, logging heap, process memory and server responsiveness over time, and publish the raw logs with dates. Hosts' terms may restrict automated load; see independence and host terms. For keeping your own runs comparable, read how to benchmark your game server.

If your log points at memory, go next to the Build 42 RAM requirements.