Project Zomboid Build 42: Stable Migration Guide for Server Admins
Build 42.20 went stable on 29 July 2026. B42 is no longer a beta branch you opt into, it is the supported build, and Project Zomboid passed its all-time peak player count the day it landed. If anything below describes B42 as unstable or upcoming, read it as history: the branch it refers to is now the default. The one live caveat is mods, since a lot of Workshop items have not been republished for stable yet, so a list that worked last week can fail today.
Build 42 sat on the unstable branch from December 2024, gained multiplayer in December 2025, and went stable as 42.20 on 29 July 2026 - a 19-month cycle. This guide covers the transition for server admins, whether you are moving a Build 41 server across or were already running B42 from the beta branch.
Important: Build 42 stable has not been released yet. The Indie Stone has not announced a specific date. This guide helps you prepare in advance so the transition is smooth when the day comes.
Current Status (April 2026)
| Branch | Version | Multiplayer | Status |
|---|---|---|---|
| Stable | Build 41.78 | Full support | Current default |
| Unstable (B42) | Build 42.x | Supported (20 players recommended max) | Active development, frequent patches |
Save Compatibility: The Hard Truth
Save files are NOT compatible between Build 41 and Build 42. This applies to both single-player saves and dedicated server worlds. When you switch to Build 42 stable, you will need to start a fresh world.
Why? Build 42 overhauled the crafting system, terrain generation, item databases, and zombie behavior. The internal data structures changed fundamentally. There is no migration path for existing worlds.
What to Do Before the Switch
- Back up everything — your entire
Zomboid/directory (saves, mods, server settings) - Communicate the wipe to your community well in advance
- Consider running a "farewell event" on your Build 41 world before switching
- Export your
servertest.iniand sandbox settings for reference (many settings changed names or defaults)
Migration Path: Build 41 Stable → Build 42 Stable
Step 1: Back Up Your Server
# Back up the entire Zomboid directory
cp -r ~/Zomboid ~/Zomboid-b41-backup
# Back up server configuration specifically
cp ~/Zomboid/Server/servertest.ini ~/servertest-b41-backup.ini
cp ~/Zomboid/Server/servertest_SandboxVars.lua ~/sandbox-b41-backup.luaStep 2: Update the Server
Once Build 42 hits stable, SteamCMD will pull it automatically on the default branch:
# Standard SteamCMD update (will pull B42 once it's on stable)
steamcmd +login anonymous +app_update 380870 validate +quitTip: B42 is the default branch now, so a plain +app_update 380870 validate installs it - no -beta flag. If you would rather finish an existing Build 41 world than migrate it, pin the server to the legacy41 branch: +app_update 380870 -beta legacy41 validate.
Step 3: Rebuild Your Configuration
Many sandbox variables have been renamed, merged, or replaced in Build 42. Start fresh with the default servertest.ini and adjust from there, using your backed-up Build 41 config as a reference.
Step 4: Audit Your Mods
Not all Build 41 mods are compatible with Build 42. Before the switch:
- Check each mod's Workshop page for Build 42 compatibility notes
- Remove incompatible mods from your server's mod list
- Test with a minimal mod set first, then add mods one at a time
Migration Path: Build 42 Unstable → Build 42 Stable
If you have been running Build 42 unstable multiplayer, the transition should be smoother but is not guaranteed to be save-compatible:
- The final unstable build before the stable release may be save-compatible, but The Indie Stone has not guaranteed this
- Back up your unstable world before switching branches
- Switch from the unstable beta branch back to the default (stable) branch in SteamCMD
Build 42 Server Requirements
Build 42 is more demanding than Build 41 due to expanded simulation systems (animals, advanced crafting, terrain detail):
| Spec | Build 41 | Build 42 (Recommended) |
|---|---|---|
| RAM | 4 GB | 6–8 GB |
| CPU | 2 cores | 4 cores |
Java heap (-Xmx) |
2–4 GB | 4–6 GB |
| Max players (stable experience) | 32+ | ~20 (unstable), expected higher on stable |
Java tuning: Build 42's animal system and expanded crafting create more GC pressure. Use G1GC with increased heap: -Xmx6G -XX:+UseG1GC -XX:MaxGCPauseMillis=50. See our Build 42 Performance Tuning guide for details.
Key Differences for Server Admins
New Systems to Configure
- Animals & Farming — livestock density, breeding rates, and feed requirements are now sandbox variables
- Crafting overhaul — recipe progression changed dramatically; affects server economy and loot balance
- Terrain detail — higher fidelity terrain increases world save sizes
Multiplayer Stability
Build 42 multiplayer is playable but still being polished. Current recommendations:
- Use whitelisted servers or Steam co-op for the best experience
- Keep player count at or below 20 until stable release
- Run frequent automatic backups — unstable patches can occasionally corrupt saves
Pre-Migration Checklist
- Back up your entire
Zomboid/directory - Export and save your current server configuration
- Audit mod compatibility for Build 42
- Verify your server meets Build 42 hardware requirements (more RAM, more CPU)
- Communicate the upcoming world wipe to your community
- Plan a fresh world launch event to drive player engagement
- Subscribe to The Indie Stone blog for the stable release announcement
Looking for managed Project Zomboid server hosting? Supercraft runs Project Zomboid dedicated servers with daily backups, instant setup, and 5 region options. Plans from $5.99/mo.