Slay the Spire is different from the usual one-folder save model: PCGamingWiki lists preferences, runs, saves, and betaPreferences as game data. That means “backup the save file” is incomplete advice. A user may restore card/progression information yet lose an active run or related preferences if only one directory is copied. SaveEditor therefore treats the four directories as one logical backup set for standard desktop builds while keeping the Microsoft Store package path separate.
Choose the correct backup boundary
For Slay the Spire, the researched PC save location is Windows: Desktop builds: <path-to-game>preferences, <path-to-game>runs, <path-to-game>saves and betaPreferences ; Microsoft Store: %LOCALAPPDATA%PackagesHumbleBundle.SlayTheSpire_q2mcdwmzx4qjaLocalCacheLocalMicrosoftWritablePackageRootsaves. The known save file or folder pattern is Multiple files across preferences, runs, saves, and betaPreferences rather than one universal slot file.. Back up preferences, runs, saves, and betaPreferences together before reinstalling or moving the game. On Microsoft Store, preserve the package-local save path separately. Copying the complete documented save boundary is safer than selecting one visually obvious file, because companion metadata, indexes, backups, or multiple slots can be required together.
Make an offline copy before changing anything
Close the game first, wait for the active launcher to finish writing, then copy the save data to a separate folder that the game and sync client do not watch. Label the copy with the game, storefront, profile, and date. Documented launcher context: Steam, GOG, Microsoft Store. The Microsoft Store sandbox path differs significantly from Steam/GOG. Standard desktop installs can keep data alongside game resources, so reinstall/move operations deserve an explicit backup first.
Account for cloud saves
Steam Cloud and Xbox Cloud support are documented depending on edition. Before restoring an older backup, decide which copy should win. If the game or launcher starts while an older manual copy is in place, synchronization can replace it before you confirm that it works. Keep the untouched backup outside the live save path until the restored progress has been opened and saved normally.
Restore without changing format assumptions
Slay the Spire stores meaningful state in several sibling directories under the installation resources for standard desktop builds. Backing up only saves can omit preferences/unlocks or run state. Compatibility note: Unlock/progression data and an in-progress run are not necessarily represented by the same file. A partial directory copy can therefore restore one aspect but not another. Restore into the matching storefront/profile context whenever possible. Do not rename a save extension, move a folder into a different container type, or assume a console/mobile copy is equivalent unless a tested migration path specifically says so.
Recovery fallback
If ascension/unlocks or the current run do not match after restoration, compare all four data directories rather than repeatedly overwriting the saves folder alone. If the restored copy fails, put the untouched original back first. Then compare location, account/profile, cloud state, and the full directory structure before trying a different backup. The objective is reversible recovery, not repeated destructive experiments on the only copy.
Verification context: Reviewed against current PCGamingWiki Slay the Spire save-data locations and multi-directory layout.