Hades II deliberately has its own Saved Games root and should be backed up independently from the original Hades. The familiar Profile*.sav naming can tempt a user to assume cross-game compatibility, but SaveEditor treats the names as organizational similarity only. The safe workflow is to copy the Hades II folder as a set, label the backup with build/date, and restore only into the same game/storefront. Microsoft Store remains separate because its data is contained in WGS.
Identify the exact save you intend to edit
The researched Hades II PC save location is Windows: %USERPROFILE%Saved GamesHades II ; Microsoft Store: %LOCALAPPDATA%PackagesSupergiantGamesLLC.HadesII_q53c1yqmx7phaSystemAppDatawgs. Known file/folder pattern: Profile*.sav. Storefront context: Steam, Epic Games Launcher, Microsoft Store. Do not put Hades I Profile*.sav files in the Hades II directory. Microsoft Store uses a WGS container instead of the normal profile directory. Do not edit a similarly named file from a different profile, edition, or cloud cache.
Make an untouched backup first
Back up every Profile*.sav in the Hades II directory before experimenting with a slot. Preserve the whole WGS tree on Microsoft Store. Keep that copy outside the live save directory and do not overwrite it with later experiments. Cloud context: Steam Cloud, Epic cloud, and Xbox Cloud 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 II uses a dedicated Saved Games/Hades II root and Profile*.sav naming. It is a separate save generation from Hades even though the profile concept is similar. File-extension context: .sav Compatibility note: Profile naming similarity to the first Hades does not imply file-format compatibility. Treat the sequel as its own data format and restore only same-game snapshots. 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 II, 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 does not appear, confirm the folder is Hades II rather than Hades, then check the storefront and cloud conflict state before replacing files again. Return to the untouched backup before trying another change.
Verification context: Reviewed against current PCGamingWiki Hades II save-location/cloud data.