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.
Identify the exact save you intend to edit
The researched Hades PC save location is Windows: %USERPROFILE%DocumentsSaved GamesHades ; Microsoft Store: %LOCALAPPDATA%PackagesSupergiantGamesLLC.Hades_q53c1yqmx7phaSystemAppDatawgs. Known file/folder pattern: Profile1.sav / Profile2.sav etc.; temporary/versioned companion saves can exist alongside the active profile.. Storefront context: 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. Do not edit a similarly named file from a different profile, edition, or cloud cache.
Make an untouched backup first
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. Keep that copy outside the live save directory and do not overwrite it with later experiments. Cloud context: Steam Cloud, Epic cloud, Xbox Cloud, and Nintendo Switch cross-save are documented. If a launcher can synchronize the save, prevent it from silently replacing either the original or edited copy while testing.
Understand the format boundary
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. File-extension context: .sav 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. These facts help identify the save but do not automatically reveal every field, checksum, encryption rule, or version-specific structure inside it.
Use only a Tool whose claim matches the file
Generic viewers and diff tools can inspect bytes without claiming game-specific semantics. A game-specific editor should be used only when its Tool page explicitly lists Hades, a matching supported version/container, and a Verified operational runtime. A planned URL or Game Hub is not evidence that an editor exists.
Test the edited copy safely
Write to a new output file when the Tool supports it, keep the original backup, restore the edited copy into the correct profile/storefront location, and launch the game only after the file operation finishes. If the game rejects it, 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. Return to the untouched backup before trying another change.
Verification context: Reviewed against current PCGamingWiki Hades save path/cloud data and Supergiant community support guidance identifying Profile1.sav.