Project Zomboid Build 42 Release Date: What People Mean
Project Zomboid: Build 42 Release Date
A “release date” picker + receipts hub.
What do you mean by “release date”?
First public playable Build 42 (Unstable)
2024-12-17
Build 42 becomes publicly playable via the Unstable/Beta branch.
Jump
Meaning Translator
Build 42 shipped in stages, so the “release date” depends on what milestone you care about.
| What people mean | Date | What happened | Where to verify |
|---|---|---|---|
| “B42 is out” (first playable) | 2024-12-17 | Build 42 becomes publicly playable via an unstable/beta branch | Official post / SteamDB patchnotes |
| “B42 has multiplayer” | 2025-12-11 | Multiplayer support lands in Unstable Build 42 (42.13) | Official post / SteamDB patchnotes |
| “B42 MP got a hotfix” | 2025-12-18 | 42.13.1 beta hotfix follows the MP drop | SteamDB patchnotes |
| “B42 is the default stable build” | Unannounced | No announced stable Build 42 calendar date (stable noted as 41.78.16 as of 2026-01) | Official framing |
Timeline (Key Dates)
| Date | Milestone | Build / Branch | Verify |
|---|---|---|---|
| 2024-12-17 | Build 42 becomes publicly playable | Unstable / Beta | Post / SteamDB |
| 2025-06-30 | 42.10 UNSTABLE release continues the runway | Unstable / Beta | — |
| 2025-12-11 | Multiplayer lands in Build 42 Unstable | 42.13 (Unstable) | Post / SteamDB |
| 2025-12-18 | Multiplayer hotfix | 42.13.1 beta (Unstable) | SteamDB |
Stable branch note (as of 2026-01): 41.78.16 — no announced date for stable Build 42 becoming the default branch yet.
Steam Branch Switch (Play B42 Today / Return to Stable)
Quick-Start checklist
Backup commands (copy/paste)
Use the one that matches your OS before swapping branches.
macOS / Linux (bash)
# macOS / Linux: back up saves + mods (creates a dated folder on your Desktop)
backup="$HOME/Desktop/pz-backup-$(date +%F)"
mkdir -p "$backup"
cp -a "$HOME/Zomboid/Saves" "$backup/" 2>/dev/null || true
cp -a "$HOME/Zomboid/mods" "$backup/" 2>/dev/null || true
echo "Backup created at: $backup"Windows (PowerShell)
# Windows PowerShell: back up saves + mods to a dated Desktop folder
$backup = Join-Path $env:USERPROFILE ("Desktop\\pz-backup-" + (Get-Date -Format "yyyy-MM-dd"))
New-Item -ItemType Directory -Force -Path $backup | Out-Null
Copy-Item -Recurse -Force (Join-Path $env:USERPROFILE "Zomboid\\Saves") (Join-Path $backup "Saves") -ErrorAction SilentlyContinue
Copy-Item -Recurse -Force (Join-Path $env:USERPROFILE "Zomboid\\mods") (Join-Path $backup "mods") -ErrorAction SilentlyContinue
Write-Host "Backup created at: $backup"Opt into B42 (Steam)
- Right-click Project Zomboid → Properties → Betas
- Pick the branch the patch notes are talking about (e.g., unstable or a numbered beta/hotfix like 42.13.1)
- Let Steam finish downloading, then launch once to generate fresh config files
Return to stable (Build 41)
- Set Betas back to None (Steam’s default stable branch)
- Assume you may need to swap back to older saves rather than keep playing the same file across versions
Version Checker
Paste the exact in-game version/build label to sanity-check what branch you’re actually on.
Version string
Example: 42.13.1 beta or 41.78.16
Server Move Rubric (B42 Multiplayer)
If “released” means “we can run a server without spending the night reading crash logs,” treat this as a policy decision.
Move now if…
Wait if…
Community mod-compat snapshot (starting point, not finish line):
reddit.com/r/projectzomboid…
Receipts (Links You Can Share)
These are the quick “show me the build number” links that end release-date arguments fast.
FAQ + “Stable Date” Watchlist
Is Build 42 released?
Yes — as an unstable/beta branch. First public playable drop: 2024-12-17.
When did B42 multiplayer release?
2025-12-11 (Build 42.13).
Is there a stable Build 42 release date?
Not announced. Stable branch was noted as 41.78.16 as of 2026-01.
Will Build 42 break my save?
It can. Back up and treat B42 like a separate timeline.
Watchlist signals: signs stable Build 42 is getting close
- Official messaging stops emphasizing separate stable vs beta build numbers.
- Hotfix cadence slows, shifting from crashes to balance tweaks.
- Must-have mods stop needing weekly babysitting.
- Servers can scale without “reduce slots / disable mods / cross fingers” being step one.
Patch History (collapsible)
| Date | Change Note | Impact on early-game priorities |
|---|---|---|
| 2024-12-17 | Build 42 becomes publicly playable via an unstable/beta branch. | Treat early runs as scouting: learn systems, expect bugs, keep saves disposable/backed up. |
| 2025-06-30 | 42.10 UNSTABLE release continues the numbered B42 runway. | Don’t anchor plans to a single “release date”; expect iterative changes and re-test routines. |
| 2025-12-11 | Build 42.13 adds multiplayer to Unstable Build 42. | MP priorities shift to server stability: modless baseline, smaller groups, conservative settings. |
| 2025-12-18 | 42.13.1 beta hotfix follows the MP drop. | If you host, schedule updates + restarts like maintenance windows; hotfix cadence matters. |
