Project Zomboid 42.22 Pre-Release: Protect a Long-Term Save Before Switching

Decide whether this is a test world or the only copy

The developer describes Pre-Release as a testing branch and recommends the default Stable branch for average players while the new build is vetted. It specifically warns against moving a long-term singleplayer save without a backup and does not guarantee that the save will work in the final release. Treat your own save's value—not curiosity about a new feature—as the first decision.

References: The Indie Stone: Moving on Up — 42.22 Pre-Release · The Indie Stone: 42.21 Stable Released

Make a backup that is separate from the live save

The publisher says to back up saves before testing 42.22 but does not prescribe a file-level method on this page. As a conservative workflow, close the game cleanly, use your operating system's file manager to copy the relevant world data to a clearly separate location, and leave the original untouched. Check that the copied folder is present and non-empty before changing branches; GamerWin does not inspect its contents or certify that it is restorable.

1. Exit the game before making a manual copy so the save is not being written while you copy it.
2. Use the current official support instructions or the game's own save location for your platform; do not copy a folder path from an unrelated Build 41 guide without checking it.
3. Copy the relevant world data to a separate location that is not the live save folder, and label it with the build you are leaving.
4. Before switching, confirm you can identify both the original and the separate copy. If unsure, stop and ask on the publisher's support forum before opening the world on another branch.

References: The Indie Stone: Moving on Up — 42.22 Pre-Release · The Indie Stone: Project Zomboid status and build history · The Indie Stone Forums: Project Zomboid

Switch only after the backup gate is satisfied

The 42.22 announcement gives a Steam-specific path: right-click the game in Library, open Properties, then select Pre-Release under Game Versions & Betas. The same announcement says the developer expects to vet a Pre-Release build before moving it to Stable; that interval and the final contents can change.

1. Keep your long-term original closed; launch the separate test copy only if you deliberately accept the pre-release risk.
2. On Steam, verify the selected branch reads Pre-Release before downloading or launching; Stable is the default recommended for ordinary play.
3. After launch, confirm the in-game build shown on the title screen before loading the test copy.
4. If you later return to Stable, keep the untouched backup until you have independently confirmed the intended world opens correctly. Do not assume branch changes merge or roll back save data.

References: The Indie Stone: Moving on Up — 42.22 Pre-Release · The Indie Stone: 42.21 Stable Released

Limits and where to get help

This guide is about the specific Steam branch process for the publisher-listed 42.21 Stable / 42.22 Pre-Release state checked on November 5, 2026. The publisher says the Stable build is recommended for average players and does not guarantee long-term-save compatibility with the final release. The interactive check records only your selections; it cannot see, copy or restore a save.

References: The Indie Stone: Moving on Up — 42.22 Pre-Release · The Indie Stone: Project Zomboid status and build history · The Indie Stone Forums: Project Zomboid

Before you play

• I know whether this is the only copy of a world I care about.
• A separate manual copy exists outside the live save location before I test Pre-Release.
• I verified the Steam branch and the build displayed by the running game.
• I will keep the original backup until the desired Stable build opens the intended world.

Frequently asked questions

Sources & revision notes

Editorial revision: November 5, 2026; not a gameplay test date. The reference notes identify source limits and version differences.

1. The Indie Stone: Moving on Up — 42.22 Pre-Release (Official)

   Publisher instructions checked November 5, 2026. The page identifies Stable 42.21 and Pre-Release 42.22, recommends Stable for average players, explains the Steam branch path, and warns that a long-term save should be backed up before testing Pre-Release. It does not promise save compatibility with the final release.

2. The Indie Stone: 42.21 Stable Released (Official)

   Publisher release context checked November 5, 2026. It describes the path from Unstable to Stable and the 42.21 changes; use the live game title screen to confirm the build installed on a particular client.

3. The Indie Stone: Project Zomboid status and build history (Official)

   Publisher status page checked November 5, 2026; it lists Build 42 stable history and points readers to the community-maintained wiki for full changelists.

4. The Indie Stone Forums: Project Zomboid (Official)

   Publisher-hosted community forum checked November 5, 2026. It separates general discussions, support, bug reports, updates and multiplayer. Posts are user submissions, not GamerWin testing or endorsements; follow the relevant forum rules and remove private data.