Docs · Project Zomboid

Build 41 vs Build 42

If you’re standing up a Project Zomboid server in 2026, the first real decision is which build to run. Build 41 is the mature, rock-steady default; Build 42 is the big engine rewrite that’s where the game — and its player base — is heading. Here’s an honest read on the trade-offs.

What Build 42 actually changed

Build 42 is not a routine content patch — it’s a major engine rewrite. The headline changes include a new lighting and depth/rendering system, a substantial crafting overhaul, a larger map, animals and husbandry, and true vertical geometry with basements. It’s the most significant leap the game has taken in years, and it’s where new content lands from here on.

Where each build stands today

Build 42 multiplayer arrived in December 2025 with build 42.13, on Steam’s unstable branch. That made multiplayer B42 servers viable for the first time — but “unstable” is doing real work in that sentence, because the branch is still moving.

Build 41 — specifically 41.78.16 — remains Steam’s stable, default branch today. It’s the version most players still run by default, and it carries the most mature mod ecosystem: years of Workshop content built and tested against it.

That ecosystem gap matters more than it first looks. An engine rewrite the size of Build 42 means mods generally have to be ported rather than simply carried over, so the B42 Workshop is still catching up to the depth B41 accumulated. If your server’s identity is a specific, sprawling modpack, check that its mods have B42 versions before you commit — the ones that matter most to you may not have made the jump yet.

Saves don’t cross the line

This is the constraint that decides more server setups than anything else: B42 saves are not compatible with B41, and vice versa. You can’t take a beloved B41 world into B42, and you can’t fall back the other way without losing it.

It gets sharper within B42 itself. Because it’s on an actively-moving unstable branch, saves can break between major B42 versions. Concretely, the jump from 42.19 to 42.20 will not carry saves over. On B42, a world is only ever as safe as your most recent backup.

The 42.20 stable flip is coming

In the Thursdoid dev update on 2026-07-09, The Indie Stone announced that 42.20 is the stable candidate, targeted for “later this summer.” When it lands, 42.20 becomes Steam’s default branch — the point at which B42 stops being the opt-in unstable choice and becomes the version most players run.

For server owners, the flip carries two concrete consequences:

• A forced wipe on existing B42 worlds. Since 42.20 doesn’t carry saves from earlier B42 builds, current B42 worlds will not survive the transition intact.
• Mod-porting churn. As the ecosystem shifts to the new stable target, mods update to match — and updates are exactly when things break. Off-site backups plus staged mod updates (validating a new mod set in isolation before it hits your live world) are the mitigation.

So which should your server run?

Pick Build 41 if you’re running a long-persistence, heavily-modded community today and stability is the priority. The mod ecosystem is deepest here and the saves are settled — you won’t get surprised by a version bump mid-run.

Pick Build 42 if you want the current content — the crafting rework, basements, animals, the bigger map — and you want to be where the player base is heading as the stable flip approaches. The cost is living on a moving branch until 42.20 settles.

A useful tie-breaker: think about how long you expect this world to last. A drop-in server for a few weekends leans toward B42, where the current content is. A world you intend to persist for months — the kind people get attached to — leans toward B41 today, simply because it won’t be invalidated by an unstable-branch version bump underneath you.

Either way, off-site backups are non-negotiable. On B41 they protect against corruption; on B42 they’re the difference between a version bump costing you an hour or costing you the whole world.

Choosing on Forgehold

Forgehold lets you choose the build per server. The entry Outpost tier runs B41 only; the B42 tiers start at 8 GB because the newer engine needs the extra headroom (the requirements guide explains why). Switching a server from B42 down to B41 wipes the world — the saves genuinely can’t cross — so the dashboard requires you to type a confirmation before it proceeds. And when 42.20 flips to stable, the automated backups and staged mod updates are already in place to absorb the churn.