How to Keep and Access Legacy Scrap Mechanic Saves
Steam beta rollback, backup folders, Creative compatibility, broken mods, and when Drilling Thunder needs a new world.
Why legacy saves matter in 2026
Scrap Mechanic 1.0 & Drilling Thunder (July 24, 2026) rebuilt Survival from scratch. Axolot warned before launch that existing Survival saves are not compatible with the 1.0 release. That is not a bug — quest tables, underground terrain, schematic gating and voiced NPC state all assume a post-launch world.
You are reading this guide because you have hours — maybe hundreds — invested in an Early Access factory, a Creative megabase, or a half-finished Survival run from 2024. This page explains how to back up, roll back, and decide without corrupting the only copy of a world you care about.
Step 1 — Back up everything before touching Steam
Copy the entire user folder before updating or switching betas:
%AppData%\Axolot Games\Scrap Mechanic\User\
Inside you will find world .db files, blueprint exports, and settings. Copy the whole User directory to an external drive or cloud folder with today’s date in the name — for example ScrapMechanic-Backup-2026-08-02.
Never rely on Steam Cloud alone for legacy archives. Cloud sync can overwrite a good backup if you launch the wrong client version first.
Step 2 — Steam previous-version beta rollback
Steam keeps historical client branches so you can open old saves on the engine that created them:
- Fully quit Scrap Mechanic.
- Steam library → right-click Scrap Mechanic → Properties → Betas.
- Select 0.5.1 (Previous version) or 0.3.5 (Last version before survival release) — whichever matches the era of your save.
- Wait for Steam to download the downgraded build. Launch and confirm the version string on the title screen.
- Open your legacy save only on that branch.
Rollback is one-way for story progression. You cannot migrate that world’s quest state, underground caverns, or Chapter 2 NPCs into Drilling Thunder later. Use rollback to finish an old project, export blueprints from the Lift, record videos, or archive screenshots — not as a permanent alternative to 1.0.
Detailed veteran context: returning player guide.
Survival saves — usually incompatible
Symptoms when forcing a pre-1.0 Survival save into 1.0:
- Infinite loading or crash on world select.
- Missing yellow quest markers and silent NPCs.
- Empty underground — no cavern layer because terrain predates new generation rules.
- Craftbot menus missing schematic-gated recipes with no unlock path.
If you want Drilling Thunder: create a new Survival world on Easy. Follow how to start fresh in 1.0 and getting started. Treat the old Survival save as archived on the Steam beta branch.
Axolot has not announced an official save migration tool as of patch 1.0.4 (August 1, 2026).
Creative saves — often load, but test first
Old Creative worlds can load in 1.0, but compatibility means the file opens — not that every machine behaves identically.
Before trusting your main Creative archive, duplicate the world file and test:
- Steering chains and wheel suspension.
- Controller logic, sensors and timer loops.
- Bearing stacks and frozen-bearing tricks from pre-1.0 physics.
- Workshop Parts dependencies — missing UUIDs spawn invisible collision.
- Modded blocks from authors without post-July 2026 updates.
If 1.0 breaks the copy, open the original on a legacy Steam branch, export critical builds as blueprints from the Lift, then import at the Scrap City Garage once reachable in a fresh Survival run.
Mods will break on rollback and on 1.0
Expect a transition period in both directions:
- Updating to 1.0 — many Workshop mods crash until authors re-upload for the new engine. Patch 1.0.1 fixed one crash class; 1.0.2 restored the Mods button in Creative.
- Rolling back to 0.5.1 — mods published for 1.0 may fail on the older client. Disable post-2026 subscriptions before opening legacy saves.
In multiplayer, every player needs identical mod lists on whichever branch you play.
When to stop fighting legacy and start fresh
Start a new 1.0 Survival world if any of these apply:
- You want the voiced Chapter 2 story, Mining Island, and underground boss.
- Your old Survival save already fails to load on 1.0.
- You are spending more time troubleshooting than playing.
- Your group agreed to wipe the hosted server for Drilling Thunder.
Keep legacy access if:
- You only need to export blueprints or screenshots from a Creative megabase.
- You are finishing a self-imposed Early Access challenge on 0.5.1.
- You rely on mods that have not yet published 1.0 builds — play vanilla 1.0 on a separate install path while keeping beta access for modded Creative.
Recommended workflow (one evening)
- Hour 0 — Back up
%AppData%\Axolot Games\Scrap Mechanic\User\. - Hour 0.5 — Roll back Steam beta, confirm old save loads, export one favorite blueprint.
- Hour 1 — Return Steam to default (no beta), update to 1.0.4, create new Easy Survival world.
- Hour 2+ — Follow getting started yellow markers.
- Parallel — Test Creative copy on 1.0; keep legacy branch bookmarked for archival access only.
Related guides
- Returning player guide — blueprint migration beats save surgery
- Start fresh in 1.0 — first-hour checklist
- Updates — patch notes through 1.0.4
Watch the community walkthrough for this guide:
Frequently Asked Questions
Quick answers to the most common questions.
Will Axolot add save migration?
No official tool has been announced through patch 1.0.4. Axolot's guidance remains: start fresh for Drilling Thunder or use Steam betas for temporary legacy access.
Can I copy .db files into a new folder to fix 1.0?
Copying database files sometimes loads surface terrain but does not inject underground caverns, Grow Labs state, or Chapter 2 NPCs. Blueprints are the supported cross-version format.
Does rollback delete my 1.0 worlds?
No, but opening the same save on mismatched clients risks corruption. Back up first and use separate world names for legacy and Drilling Thunder runs.