Switch a Steam beta branch with a save rollback plan
Check branch notes, preserve the stable version’s saves and test beta compatibility before continuing your main campaign.
In brief
A Steam beta branch can deliver experimental or alternate game builds. A save created in a newer build may not load in the stable build, so changing back in the menu is not always a complete rollback.
A separate test save lets you try the build without staking your only campaign on compatibility that has not been established.
Know what you are testing
Identify whether the branch is a public test, an older build or a preview for a particular feature. Check mods and multiplayer version requirements. Do not join just because it sounds newer; have a specific issue or feature you want to evaluate.
Isolate progress before switching
Copy the documented save folder after closing the game and label it with the stable version. Use the game’s supported separate profile or slot where possible. Understand how its cloud save setting behaves, and avoid testing on one device while another continues the main campaign.
Roll back both build and data
To return, choose the normal non-beta option and let Steam complete the download. Follow the developer’s compatible restore procedure for the stable save. Do not open a beta-written save and repeatedly overwrite it while expecting the old build to convert it safely.
Before you act
Branch availability and password access are controlled by the developer. A beta label is not a promise of stability, and automatic cloud sync can carry its changed saves to another device.
What to do next
- Read the developer’s beta notes and save compatibility instructions.
- Back up the stable saves, then open Properties → Betas and select the intended branch.
- Wait for the update and test a separate save; keep the stable backup untouched for rollback.
