Hades is friendly to manual backup because its main PC save lives in the user Saved Games folder, but cloud recovery introduces a naming trap: files downloaded from Steam Cloud can have extra prefixes even though the game expects names such as Profile1.sav. SaveEditor recommends preserving the whole Hades directory and recording the active profile number. This makes it easier to recover both the main profile and companion temporary/versioned files without guessing which cloud-exported filename corresponds to the live save.
Prepare the source PC
On the source system, identify the actual Hades save root: Windows: %USERPROFILE%DocumentsSaved GamesHades ; Microsoft Store: %LOCALAPPDATA%PackagesSupergiantGamesLLC.Hades_q53c1yqmx7phaSystemAppDatawgs. The expected file/folder pattern is Profile1.sav / Profile2.sav etc.; temporary/versioned companion saves can exist alongside the active profile.. 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, Epic Games Launcher, Microsoft Store. Microsoft Store uses WGS. Steam/Epic normal PC installs use the Saved Games directory; a cloud-downloaded filename may not be the same as the runtime filename. 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 the entire Hades directory, with special attention to the active ProfileN.sav and its temporary/versioned companions. Preserve filenames exactly in the local runtime folder. 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, Epic cloud, Xbox Cloud, and Nintendo Switch cross-save are documented. 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
Hades stores profile-oriented saves in the Saved Games/Hades directory. Steam cloud exports can include prefixed filenames that need their original names restored before the game recognizes them. Compatibility note: A cloud-download archive may prepend metadata to filenames; restoring the bytes without restoring the expected ProfileN.sav name can make a valid save appear missing. If the destination does not see the transferred progress, If a profile is not detected, compare the filename to the expected ProfileN.sav naming and verify that the active profile number matches. Check WGS separately for Microsoft Store. Verify game edition/version, store, profile IDs, redirected folders, and mod/DLC dependencies before editing the save itself.
Verification context: Reviewed against current PCGamingWiki Hades save path/cloud data and Supergiant community support guidance identifying Profile1.sav.