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.
Known Hades II save-file structure
The researched filename or folder pattern is Profile*.sav. File-extension context: .sav The documented format notes are: 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.
Why an extension is not enough
A save filename can identify a likely container, but it does not prove the internal schema, game version, checksum rules, encryption state, or editability. 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. SaveEditor therefore separates file identification from Tool compatibility and only labels a game-specific Tool Verified when its exact profile/version evidence passes the runtime gate.
Where the format is stored
PC save locations: Windows: %USERPROFILE%Saved GamesHades II ; Microsoft Store: %LOCALAPPDATA%PackagesSupergiantGamesLLC.HadesII_q53c1yqmx7phaSystemAppDatawgs. 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. This matters because two releases can use different containers or companion files even when the visible slot name is similar.
Back up before inspecting or editing
Back up every Profile*.sav in the Hades II directory before experimenting with a slot. Preserve the whole WGS tree on Microsoft Store. A read-only viewer is lower risk than a writer, but the live save should still be copied first. Cloud context also matters: Steam Cloud, Epic cloud, and Xbox Cloud are documented. Keep the original bytes available so any experiment can be reversed without relying on a cloud service or automatic backup.
What this reference does not claim
This page does not infer an undocumented checksum algorithm, encryption key, compression layer, or cross-store conversion from the file extension. Troubleshooting evidence: 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. Those questions require a verified parser/profile or a game-specific source, not a generic format guess.
Verification context: Reviewed against current PCGamingWiki Hades II save-location/cloud data.