How to Play Project Zomboid Build 42 on Steam

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

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.

To play Project Zomboid Build 42, install the game in Steam, open Properties → Game Versions & Betas (called Betas in older Steam instructions), and select Unstable. Steam will download the Build 42 branch; launch the game normally after the update finishes. As of October 15, 2026, The Indie Stone lists both Stable and Unstable as Build 42.21.

Build 42 is a major, still-evolving version. Back up your saves before changing branches, because Build 41 saves and mods do not work with Build 42, and later Unstable updates can make earlier Build 42 saves unusable. Multiplayer is available as a work in progress for stress testing, but the developer recommends Steam co-op or whitelisted servers, no more than 20 players, and no mods.

#	Preview	Product	Price
1		Zombicide 2nd Edition Strategy Board Game | Cooperative Game for Teens and Adults | Zombie Board...		Buy on Amazon

What you need before installing Build 42

• A copy of Project Zomboid installed through Steam.
• Enough free storage and time for Steam to download the branch and apply its patch.
• A backup of any save you care about before switching from another branch.
• A plan for your mods: Build 41 mods are not compatible with Build 42, and the multiplayer stress-test release should be run with all mods disabled.

The current official version labels are Stable 42.21 and Unstable 42.21. Stable is the less-changing choice for a new long-term game. Unstable receives the newest test fixes and gameplay changes first, but it is unfinished and can introduce bugs or break saves between updates.

How to install and launch Build 42

1. Open Steam and install or update Project Zomboid from your Library.
2. In the Library, right-click Project Zomboid and choose Properties.
3. Open Game Versions & Betas. Older Steam instructions may call this tab Betas.
4. Open the branch selector and choose Unstable.
5. Close the Properties window and wait for Steam to finish downloading and patching the game. Do not launch while the update is still queued or incomplete.
6. Start Project Zomboid from Steam. The game should now load the Build 42 client.
7. Before opening an existing game, make a manual copy of its save folder. The Indie Stone specifically recommends backing up when testing an Unstable update.

You do not need a separate launcher or a special executable. The Steam beta branch controls which Build 42 files are installed, and you launch the game the same way as any other Steam game.

#1 Best Overall

Zombicide 2nd Edition Strategy Board Game | Cooperative Game for Teens and Adults | Zombie Board Game | Ages 14+ | 1-6 Players | Avg. Playtime 1 Hour | Made by CMON

• 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?

Buy on Amazon

Which Build 42 branch should you choose?

Your correct branch depends on whether you are starting fresh or preserving an existing game. Switching simply to obtain new features can make an old save impossible to load, so decide before you click the branch selector.

Choose Stable when you want a dependable Build 42 foundation. Choose Unstable only when you intentionally accept testing conditions. Choose legacy41 or a version-specific branch to finish an existing compatible game, not as a general way to obtain the newest content.

Save and mod compatibility

Build 41 saves

Build 41 saves cannot be used in Build 42. The developer’s warning is explicit: “Build 41 saves and mods are NOT compatible with Build 42.” Copy your old save before experimenting, then keep playing it on the legacy41 branch if you want to preserve that campaign.

Build 42 saves across updates

Compatibility is not guaranteed even within Build 42. The 42.20 release made 42.19 saves incompatible because it added map content. This is why a save that worked on an earlier Unstable build may fail after Steam updates to a newer one. Keep a separate backup for each important version and avoid opening the only copy of a campaign after an update.

Mods

Build 41 mods do not carry over to Build 42. Build 42 itself is still receiving changes to modding support, so a mod that works on one Build 42 revision may fail on another. Remove or disable mods before diagnosing a crash or a save-loading error. For the current multiplayer stress-test release, The Indie Stone asks players to disable all mods.

A practical backup routine

1. Exit Project Zomboid completely before copying anything.
2. Use your operating system’s file manager to copy the Project Zomboid save folder to a separate location, such as an external drive or another folder clearly labeled with the branch and version.
3. Record which branch produced the backup, for example “Build 41,” “42.19,” or “42.21 Unstable.”
4. Switch branches only after the copy is complete.
5. If the new branch cannot load the game, return to the matching branch and restore the backup rather than repeatedly opening the original save.

A backup protects the files you already have; it does not make an incompatible save portable between branches.

What is new in Build 42?

Build 42 is more than a routine patch. The launch announcement highlights an expanded map, animals, overhauled crafting and building, new lighting, and expanded lore. Those systems change exploration, resource planning and how you develop a safe base, so existing guides written for Build 41 may describe menus or mechanics that no longer match your game.

Expanded map

Additional map content is one reason version changes can affect saves. The 42.20 update’s added map content made 42.19 saves incompatible, demonstrating that a map expansion is not always a harmless, backward-compatible download.

Animals

Animals add another survival consideration to the world. Their inclusion is part of Build 42’s feature set, but the Unstable branch remains subject to balance changes while the developers continue refining the release.

Crafting and building

Crafting and construction were overhauled. Expect older recipes, production routes or building assumptions to require adjustment, particularly when following a Build 41 guide.

Lighting and lore

New lighting changes the visual and atmospheric presentation, while expanded lore adds more context to the setting. The launch notes also caution that balance and interface work were still in progress on Unstable, so labels and behavior can change as testing continues.

Ongoing polish

The Stable-release notice describes continuing work on optimization, additional modding support, multiplayer and controller improvements, and player-requested polish. Moving a branch to Stable is intended to give mod authors a less changeable platform; it does not mean every planned improvement has finished.

Playing Build 42 alone

Solo play is the simplest way to evaluate Build 42 because it avoids server-version coordination. After selecting Stable or Unstable, create a new world if you want the cleanest compatibility. If you are opening an existing world, make the backup first and confirm that the save belongs to the selected branch.

• Use Stable 42.21 for a campaign you expect to keep through ordinary updates.
• Use Unstable 42.21 for testing the newest changes, accepting that a later update can interrupt the campaign.
• Keep mods disabled while determining whether the base game works correctly on the selected branch.
• If a save fails after a branch update, stop trying to overwrite it and return to the branch and backup that match its version.

Build 42 multiplayer: what works and what does not

Build 42 multiplayer was released as work in progress for stress testing, not as a promise of a permanently stable multiplayer environment. The Indie Stone strongly advises Steam co-op or whitelisted servers for the best experience. It advises against more than 20 players, asks participants to disable mods, and warns that future Unstable updates will disrupt ongoing multiplayer games.

Recommended multiplayer setup

1. Have every participant select the same Build 42 branch and let Steam finish updating before anyone connects.
2. Use Steam co-op or a whitelisted server, following The Indie Stone’s recommendation.
3. Keep the group at 20 players or fewer.
4. Disable every mod on the client and server for the test release.
5. Back up the multiplayer save before updates or branch changes.
6. Agree that the game may need to stop when an Unstable update arrives; the official notice says future updates will disrupt ongoing multiplayer games.

Do not treat an Unstable multiplayer world as a permanent, update-proof server. If continuity matters more than testing the newest fixes, wait for a branch that your group can keep synchronized and still make backups before every change.

Why am I still on Build 41?

If the title screen or version information still shows Build 41, Steam probably has not switched the game to the intended branch. Return to the Library, open Project Zomboid → Properties → Game Versions & Betas, and verify that Unstable is selected. Allow Steam to complete the download and patch, then launch again.

Do not select legacy41 if your goal is Build 42; that branch intentionally keeps the older game. If Steam is still downloading, the new files are not ready yet. If the branch selector uses the older Betas label, it is the same settings area.

Common problems and safe fixes

The save will not load after switching

Check the save’s original branch and version first. A Build 41 save needs legacy41, and a 42.19 Unstable save may need the 42.19 branch where available. Restore the backup that matches that version instead of converting the only copy through repeated launches.

A mod causes errors or missing content

Disable all mods and launch the unmodified Build 42 client. Build 41 mods are incompatible, and Build 42 mod support is still evolving. Re-enable nothing until the base game loads and the save is confirmed safe.

Friends cannot join the multiplayer game

Confirm that everyone is on the identical branch and revision, then disable mods on every side. Use Steam co-op or a whitelisted server, keep the group at 20 players or fewer, and remember that the multiplayer release is a stress test rather than a finished service.

The game changed after an update

That behavior is expected on Unstable. The branch is a work in progress, and later updates can alter gameplay, interface behavior, map data or save compatibility. Keep a dated backup and select the matching version-specific branch when Steam provides one.

I want to return to Build 41

Open the same Steam Properties page and select legacy41. Switch only after backing up the Build 42 files, and use the Build 41 save that belongs to that branch. Do not expect a Build 42 save to become a Build 41 save by changing the dropdown.

How to update or leave Build 42 safely

1. Finish or pause the current session and exit the game.
2. Copy the relevant save folder and label it with the current branch and version.
3. Decide whether you want Stable 42.21, the newest Unstable revision, legacy41, or a version-specific Build 42 branch.
4. Open Project Zomboid → Properties → Game Versions & Betas in Steam and select the destination branch.
5. Wait for Steam to download the complete branch before launching.
6. Open only a save known to match that branch. Keep the backup untouched until you confirm the game works.

For an existing 42.19 Unstable campaign, selecting 42.19 where available is safer than allowing the game to move to a revision that changed map data. For a Build 41 campaign, use legacy41 rather than attempting to migrate it.

Build 42 decision checklist

• Starting a new game: Select Stable 42.21 unless you specifically want to test Unstable.
• Testing the latest fixes: Select Unstable 42.21, back up first and expect bugs and save disruption.
• Keeping a Build 41 campaign: Select legacy41 and keep its mods on that branch.
• Finishing a 42.19 campaign: Select the 42.19 branch where available and do not open the only save on a newer revision.
• Playing with friends: Match branches exactly, use Steam co-op or a whitelisted server, stay at 20 players or fewer and disable mods.
• Returning to another branch: Back up before switching and use a save created for the destination version.

Bottom line

Build 42 is a Steam branch selection, not a separate game: choose Unstable under Project Zomboid → Properties → Game Versions & Betas, let Steam patch, and launch normally. Stable 42.21 is the safer starting point; Unstable 42.21 is for players willing to test unfinished work. Protect every save before switching, keep branch and mod versions aligned, and treat Build 42 multiplayer as a limited stress test rather than a guaranteed-stable long-term server.

Quick Recap

Bestseller No. 1

Zombicide 2nd Edition Strategy Board Game | Cooperative Game for Teens and Adults | Zombie Board Game | Ages 14+ | 1-6 Players | Avg. Playtime 1 Hour | Made by CMON

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.