Slay the Spire 2 Save Recovery — Restore Lost Progress Safely

FIRST CHECK

Back up the entire profile first, stop Steam Cloud from overwriting it, then restore the developer-created progress backup before trying community tools.

Do not delete anything first. Exit Slay the Spire 2, copy the entire affected profile folder to a dated backup, and then use the developer's pinned recovery sequence. The current official guidance says the game may leave progress.save.backup or progress.save.corrupt beside the active progress file after a crash. Those files are the safest first recovery candidates.

Before changing the save

1. Close Slay the Spire 2 and Steam.
2. Copy the complete SlayTheSpire2 folder to another drive or a clearly named desktop backup.
3. Preserve every profile, not only progress.save.
4. Record whether the failure followed a crash, a device switch, a mod change, or a Steam Cloud conflict.

The pinned developer post identifies the Windows profile under the user's roaming application-data folder. A Steam account ID and profile number appear inside the path, so do not copy another player's literal account number.

Official progress-backup procedure

The developer's current troubleshooting sequence is:

1. Open the in-game console with the tilde key if the game still reaches a usable screen.
2. Enter cloud delete twice as instructed by the pinned post. The game should close after the confirmation sequence.
3. Do not reopen it yet.
4. Open the affected profile's saves folder.
5. Move the small or broken progress.save into a separate quarantine folder instead of permanently deleting it.
6. Rename progress.save.backup or progress.save.corrupt to progress.save.
7. Relaunch and confirm that characters, unlocks, run history, and settings are present.

If the restored file is older, losing one run is safer than repeatedly overwriting a recoverable profile. Keep the original backup until several successful launches have completed.

When the problem followed mods

The same developer post separates removed-mod failures from ordinary progress corruption. For a mod-related issue, it instructs players to run the cloud-delete sequence and remove the affected current_run.save, not to erase the whole profile. Treat these as different symptoms: a broken current run does not automatically mean permanent progress is gone.

If no backup works

Stop cycling files after one controlled attempt. Submit an in-game report with F2 when available, or use the support channel named in the developer post. Include the operating system, whether Steam Cloud was enabled, the crash time, mod status, and a copy of the untouched profile. The developer also links a third-party rebuild tool, but explicitly does not guarantee it; use it only on a duplicate, never on the sole remaining copy.

Return to the Slay the Spire 2 guide hub or review co-op setup before resuming a shared run.

Sources

• Developer-pinned Slay the Spire 2 troubleshooting
• Player report confirming backup recovery after a crash
• Official Slay the Spire 2 Steam listing