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.
Prepare the source PC
On the source system, identify the actual Slay the Spire save root: Windows: Desktop builds: <path-to-game>preferences, <path-to-game>runs, <path-to-game>saves and betaPreferences ; Microsoft Store: %LOCALAPPDATA%PackagesHumbleBundle.SlayTheSpire_q2mcdwmzx4qjaLocalCacheLocalMicrosoftWritablePackageRootsaves. The expected file/folder pattern is Multiple files across preferences, runs, saves, and betaPreferences rather than one universal slot file.. Close the game, let the active launcher finish writing and synchronizing, then make a complete offline copy rather than transferring a file that may still be open.
Preserve storefront and profile identity
Documented storefronts: 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. A transfer between two PCs is simplest when both systems use the same storefront/account/profile context. If the destination uses a different store or container, treat that as a migration problem rather than an ordinary restore.
Move the complete save boundary
Back up preferences, runs, saves, and betaPreferences together before reinstalling or moving the game. On Microsoft Store, preserve the package-local save path separately. Put the copied data on the destination only after confirming the destination save path. If the game creates a new empty save first, keep that new folder as another backup so you can compare structures and revert.
Handle cloud sync deliberately
Steam Cloud and Xbox Cloud support are documented depending on edition. Decide whether the local transferred copy or cloud copy should be authoritative before launching the game. If possible, preserve both. After the transferred save loads correctly, make a fresh in-game save and let the launcher synchronize normally.
Check compatibility before blaming the transfer
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. If the destination does not see the transferred progress, 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. Verify game edition/version, store, profile IDs, redirected folders, and mod/DLC dependencies before editing the save itself.
Verification context: Reviewed against current PCGamingWiki Slay the Spire save-data locations and multi-directory layout.