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.
For this PC reference, the documented storage is Windows: %USERPROFILE%Saved GamesHades II ; Microsoft Store: %LOCALAPPDATA%PackagesSupergiantGamesLLC.HadesII_q53c1yqmx7phaSystemAppDatawgs. The known file or folder pattern is Profile*.sav. 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.
Backup guidance: Back up every Profile*.sav in the Hades II directory before experimenting with a slot. Preserve the whole WGS tree on Microsoft Store. Steam Cloud, Epic cloud, and Xbox Cloud are documented. Launcher and cloud context matters because 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.
Compatibility and recovery should stay conservative. 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. If the expected progress is not visible, 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. SaveEditor.com only labels a game-specific editor as available when a separate linked Tool has a verified operational runtime; this reference page by itself is not an editor claim.