Project Zomboid in 2026 is two games sharing a store page. Build 41 — stable since the end of 2021, final form 41.78.16 — carries the mature mod Workshop and the established multiplayer scene. Build 42 — unstable since December 2024, multiplayer only since 42.13 in December 2025 — is where the future happens, complete with the instability the branch name promises: every "42.x killed my base" forum thread is a player learning that unstable means unstable. Mods split along the same line, saves don't cross it in either direction, and servers pin themselves to point versions. So "give me a different version" is practically a daily need here — and unusually, the developers mostly provide for it.
01The Zomboid folder comes first
Zomboid folder in your user directory (C:\Users\<you>\Zomboid on Windows, ~/Zomboid on Linux) — saves, sandbox presets, mod configuration, server data. B41 and b42 saves are mutually incompatible, unstable patches can break their own saves, and b42's young multiplayer makes no continuity promises at all. Copy the folder before any version move. The Indie Stone named their testing branch iwillbackupmysave back in the IWBUMS days for a reason; consider this page that tradition's continuation.
02The branch map — often all you need
Zomboid is the rare game whose developers keep the version shelf stocked. Right-click → Properties → Betas and the dropdown is a small museum:
| Branch | What it is |
|---|---|
none (default) | Current stable — build 41, 41.78.16, as of this writing. |
unstable | Build 42's testing line — crafting overhaul, the new lighting, and since 42.13 the experimental multiplayer. |
| point-version branches | Selected past versions of both builds (named like legacy_41_71) — the devs' answer to "the modpack needs 41.71 exactly". |
If the version you need is in that list, you're done — pick it, let Steam swap the files, play. No tool needed, and this site is happy to say so. Two real limits, though: the shelf holds selected versions, not all of them — and it ends at build 41. The Indie Stone have said plainly that older legacy builds will stay unavailable (patching years-old vulnerabilities in retired versions isn't where they'll spend b42-era effort, which is fair). And branch switching replaces your install — you're always on exactly one version, which is precisely the limitation the next section deals with.
03Where DepotDownloader earns its place
Three jobs the Betas dropdown can't do. First: both builds at once. Anyone modding, admining or testing across the b41/b42 line gets tired of Steam's swap-everything dance fast. Pull a branch into its own folder and keep your Steam install on the other build (no -depot needed — given a branch, the tool fetches the app's full depot set for your platform):
> .\DepotDownloader.exe -app 108600 -branch unstable -username you -dir .\pz-b42Second: versions missing from the shelf. An unstable hotfix that broke your base yesterday won't have a branch — point versions get curated in, not guaranteed. The full history sits in the manifest lists on SteamDB's app 108600 page: find the date the working version shipped, take that manifest for each depot your platform uses, and request it with -manifest as in the universal guide. Subject, as always, to Valve's mood about old manifests — recent ones are the reliable case.
Third: archiving. The pre-b41 story is this site's standing lesson told by a different narrator: those builds are gone not because Valve gated them but because the developer chose to retire them. Branches are a shelf the owner can clear at any time. If your group's b41 era matters to you, a downloaded copy in a folder you control is the only version of it that's truly yours.
04Servers: match to the digit
The dedicated server is app 380870, free and anonymous like the rest of its kind, with branches mirroring the client's:
$ ./DepotDownloader -app 380870 -branch unstable -dir ./pz-server-b42The operational rule is absolute: server and client versions must match exactly — a 41.78.16 server speaks only to 41.78.16 clients, and after every unstable patch your b42 server needs updating in step with your players (or deliberately holding back in step with them — the rollback-by-manifest move from the Rust guide works the same way here, and b42's wipe-prone testing phase makes it a frequent one). For mixed communities the side-by-side trick above is the quality-of-life win: one machine can host a stable b41 server and a b42 experiment in separate folders.
05Status in 2026
Zomboid is a happy outlier in the manifest-weather era: its versioning needs are mostly served by active branches, which don't depend on historical-manifest goodwill at all — and b42's march toward stable (multiplayer landed in unstable this past December; the full release looks close) will only add branches, not remove access. The two soft spots are the ones already named: unlisted point versions ride on old-manifest availability like every game's do, and anything pre-b41 is gone by the developer's own decision, permanently. Both point the same direction — the Betas dropdown is a service, not an archive. For the versions your community lives on, be your own.