To play Project Zomboid Build 42, install the game in Steam, open Project Zomboid → Properties → Game Versions & Betas (called Betas in older Steam instructions), and choose Unstable. Let Steam finish downloading the branch before launching. The official site currently lists both Stable 42.21 and Unstable 42.21, so choose the branch that matches whether you want a relatively settled game or the newest test updates.
Godlike.Host offers hosted Project Zomboid servers with its own game panel, SFTP access and free DDoS protection, if you would rather not host it yourself.
Back up every save before changing branches. Build 41 saves and mods are not compatible with Build 42, and later Unstable updates can invalidate Build 42 saves, including multiplayer games.
As an Amazon Associate I earn from qualifying purchases.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Which Build 42 branch should you choose?
Build 42 is a version family rather than a single permanent download. Steam lets you select the branch that supplies the game files. Your best choice depends on whether you are starting fresh or protecting an existing game.
| Branch | Use it when | Main trade-off |
|---|---|---|
| Stable 42.21 | You want the least-changing current Build 42 experience. | It may receive changes later than Unstable. |
| Unstable 42.21 | You deliberately want the newest fixes and gameplay improvements while testing Build 42. | It is unfinished; bugs, balance changes, interface changes, mod failures and save disruption are possible. |
| legacy41 | You need to continue a compatible Build 41 game. | You remain on Build 41 rather than gaining Build 42 content. |
| 42.19 (where available) | You are finishing a game created on the 42.19 Unstable branch. | You do not receive the newer branch’s changes. |
The Indie Stone describes Unstable players as playing “a work in progress.” Select it intentionally, not because the word sounds like a special edition or a required upgrade. If you simply want to begin Build 42 today, Stable 42.21 is the conservative choice; if you want the current test fixes and accept disruption, use Unstable.
#1 Best Overall
- UPDATED CLASSIC: Dive into Zombicide: 2nd Edition, the thrilling update to the classic zombie-slaying game. Experience enhanced gameplay and new challenges in the zombie apocalypse.
- COOPERATIVE SURVIVAL: Join forces as Survivors in a world overrun by zombies. Work together to navigate through missions, complete objectives, and fight for survival.
- ADRENALINE-POWERED ACTION: With each zombie kill, increase your Adrenaline Points. Gain strength and skills but attract more zombies with your actions – a double-edged sword.
- INTENSE MISSIONS: Face a series of challenging missions, each requiring strategic planning, teamwork, and bravery. Can you accomplish your objectives while fending off the undead?
- SURVIVE OR BECOME ZOMBIE PREY: The stakes are high - will you emerge as a triumphant survivor or fall victim to the relentless zombie hordes?
How to install Build 42 through Steam
- Install or update Project Zomboid. In Steam, make sure the base game has finished installing and that any pending update has completed.
- Open the game’s properties. Go to your Steam Library, right-click Project Zomboid, and select Properties.
- Open the branch selector. Select Game Versions & Betas. Older instructions may call this tab Betas.
- Choose a branch. Select Unstable for the current Unstable Build 42 client. If you want the current settled Build 42 files, select the Stable installation instead of opting into an older beta. To preserve a Build 41 game, select legacy41; to finish a compatible 42.19 Unstable game, select 42.19 if Steam still lists it.
- Wait for Steam to patch. Steam may download a substantial update and may verify files. Do not launch until the download and disk activity have completed.
- Launch normally. Start Project Zomboid from Steam. The selected branch supplies the client you play; you do not need a separate Build 42 executable.
- Back up before loading a save. Make a manual copy of the relevant Project Zomboid save folder before opening an existing game, especially on Unstable. Keep the copy outside the live save location and label it with the branch and version.
If the game still reports Build 41 after selecting Unstable, close the game, return to the branch selector, confirm that Unstable is actually selected, and wait for Steam to finish its download. A branch change that is still queued or paused has not taken effect. Launching an old shortcut before patching can also make it appear that nothing changed.
Why your old save or mods may not work
Build 41 saves
Build 41 saves are not compatible with Build 42. The Indie Stone states this directly: “Build 41 saves and mods are NOT compatible with Build 42.” Do not overwrite your only Build 41 copy by switching branches and attempting to load it. Select legacy41 when you want to keep playing that world, and maintain a separate Build 42 game for new characters.
Recommended Free Tools
Build 42 saves across Unstable updates
Compatibility can also change within Build 42. The 42.20 release made 42.19 saves incompatible because it added map content. That means a save that worked on one Unstable build is not guaranteed to work after the next update. Before every Unstable update, make a fresh manual backup. If a newer update breaks a continuing game, select the matching older beta, such as 42.19 when it remains available, and restore the backup rather than repeatedly opening the original file.
Mods
Build 41 mods are not compatible with Build 42, and Build 42 updates can require authors to revise their work. Disable all mods before diagnosing a crash, a missing item, a failed load, or a multiplayer connection problem. Re-enable only mods explicitly updated for your exact Build 42 branch, one group at a time, after confirming that an unmodded game loads.
What a safe migration looks like
- Leave the original Build 41 save untouched.
- Copy any important Build 42 save before changing from Stable to Unstable or between Unstable builds.
- Record the branch and version associated with each backup.
- Test a new, disposable character before risking a long-running world.
- Keep a separate mod profile, or remove mods entirely, while testing updates.
What Build 42 adds
Build 42 is a substantial content and systems update rather than a small patch. The launch announcement highlights an expanded map, animals, overhauled crafting and building, new lighting, and expanded lore. Those systems change the way a new game unfolds: exploration has more territory and wildlife, construction and production offer more options, lighting affects how locations feel and function, and the world contains additional narrative context.
Expanded map
Additional map content increases the amount of territory to explore and is one reason saves can become version-specific. Map additions are not merely cosmetic data; when the world layout changes, an older save may not be safe to open on a newer build.
Animals
Animals add another part of the survival environment beyond zombies and human supplies. Treat them as a Build 42 system to learn in a fresh game rather than assuming a Build 41 routine or mod will account for them.
Crafting and building
The crafting and building systems have been overhauled. Recipes, materials and construction decisions should therefore be learned from the Build 42 interface and current in-game information, not from an old Build 41 mod list or guide.
Lighting and lore
New lighting changes the presentation and atmosphere of locations, while expanded lore adds more world context. The Unstable launch notes also warn that balance and interface work remain in progress, so numbers, menus and presentation can change between updates.
Continuing development
The Stable-release notice says post-launch work continues on optimization, additional modding support, multiplayer, controller improvements and player-requested polish. The roadmap explains that moving to Stable is intended to give mod authors a less changeable platform while that support work continues. Stable therefore means a more dependable target, not that every planned Build 42 system is finished.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Playing Build 42 alone or with other players
Build 42 multiplayer is available as work in progress for stress testing. The official multiplayer notice strongly advises Steam co-op or whitelisted servers for the best experience, recommends no more than 20 players, asks players to disable all mods, and warns that future Unstable updates will disrupt ongoing multiplayer games.
| Mode | Best fit | What to expect |
|---|---|---|
| Solo | Learning Build 42 systems or protecting a long-term save. | Few connection variables, but branch updates can still affect saves and mods. |
| Steam co-op | A small group testing the current multiplayer build. | Officially recommended for the best experience; keep the group at 20 players or fewer and disable mods. |
| Whitelisted server | A controlled group that can restrict access. | Also strongly advised by The Indie Stone for the test release; plan for disruption after Unstable updates. |
| Open or larger server | Only when you accept the test status and additional variables. | Not the recommended path for this work-in-progress multiplayer release; more than 20 players is specifically discouraged. |
Starting a Steam co-op test
- Ensure every player selects the same Build 42 branch and waits for Steam to finish updating.
- Disable all mods for every participant.
- Have the host create or load a test world only after backing it up.
- Invite a small group through Steam co-op.
- Keep the session at 20 players or fewer, and expect an Unstable update to require a new or restored game.
Do not treat a successful first session as a compatibility guarantee. The official warning is explicit that future Unstable updates will disrupt ongoing multiplayer games.
Troubleshooting common Build 42 problems
Steam shows only Build 41
- Reopen Properties → Game Versions & Betas and check that Unstable, not legacy41, is selected.
- Wait for Steam’s download, patching and file verification to finish.
- Restart Steam if the branch selector changed but the download did not begin.
- Launch from the Steam Library after patching rather than an outdated shortcut.
A save refuses to load
- Stop trying to open the original and preserve it.
- Confirm which branch and version created the save.
- Return to legacy41 for a Build 41 save, or to the matching 42.x beta for a version-specific Build 42 save when that beta remains available.
- Restore the manual backup if an update changed the world or corrupted the working copy.
The game crashes or behaves strangely
- Disable every mod and test a new world.
- Confirm that all players use the same branch in multiplayer.
- Check whether the problem appeared immediately after an Unstable update; if so, use the backed-up compatible branch rather than overwriting the save.
- Remember that Unstable includes unfinished balance and interface work, so a reproducible issue may be a branch bug rather than a setup mistake.
Multiplayer disconnects or fails to start
- Use Steam co-op or a whitelisted server, the routes officially recommended for the test release.
- Disable mods on the host and every client.
- Keep the group to 20 players or fewer.
- Verify that everyone has the same Build 42 branch and current files.
- Do not continue an important multiplayer world through an Unstable update without a backup; future updates may disrupt it.
A practical first-session plan
- Choose Stable 42.21 unless you specifically want Unstable testing.
- Start a new, unmodded world so you can learn the revised crafting, building, lighting and animal systems without legacy assumptions.
- Use the first session to confirm that the map, controls and save process work on your machine.
- Only after that, add Build 42-compatible mods or invite friends to a small Steam co-op test.
- Before every branch change or Unstable update, make and label a separate save backup.
This approach keeps an established Build 41 world safe, gives a new Build 42 character a compatible environment, and makes it clear which version produced each save.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallQuick Recap
Build 42 decision checklist
- Want the current, least-changing Build 42? Use Stable 42.21.
- Want the newest test fixes and gameplay improvements? Use Unstable 42.21, with backups and no assumption of save or mod compatibility.
- Need your Build 41 world? Select legacy41 and do not load that save in Build 42.
- Finishing a 42.19 Unstable world? Select 42.19 if Steam still offers it.
- Playing multiplayer? Prefer Steam co-op or a whitelisted server, disable mods, stay at 20 players or fewer, and expect future Unstable updates to disrupt the game.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
