Hogwarts Legacy needs more careful path checking than a single copy-and-paste instruction suggests. Different PC storefronts and packaging contexts can produce `Hogwarts Legacy`, `HogwartsLegacy`, `Hogwarts`, or `Phoenix` paths, while Microsoft Store uses WGS. The safest backup begins by finding which directory changed most recently after an in-game save, then copying the entire user-ID folder. Keep alternate folders until you have positively identified the live one.
Identify the exact save you intend to edit
The researched Hogwarts Legacy PC save location is Windows: Steam: %LOCALAPPDATA%Hogwarts LegacySavedSaveGames<user-id>
Epic may use %LOCALAPPDATA%HogwartsLegacySavedSaveGames<user-id>
Microsoft Store: %LOCALAPPDATA%PackagesWarnerBros.Interactive.PHX_ktmk1xygcecdaSystemAppDatawgs<user-id> | Linux / Steam Play: Steam Play: <SteamLibrary-folder>/steamapps/compatdata/990080/pfx/. Known file/folder pattern: *.sav. Storefront context: Steam, Epic Games Launcher, Microsoft Store / Xbox app. PCGamingWiki documents multiple folder-name variants, including launcher/streaming-specific paths. Identify the active storefront and actual modified folder before restoring anything. Do not edit a similarly named file from a different profile, edition, or cloud cache.
Make an untouched backup first
Copy the full active SaveGames user-ID folder. If more than one Hogwarts/Phoenix path exists, compare modification times and preserve all candidates before cleanup. 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 for the corresponding releases. If a launcher can synchronize the save, prevent it from silently replacing either the original or edited copy while testing.
Understand the format boundary
Steam/Epic PC saves are .sav files under Unreal Engine-style Saved/SaveGames directories. Microsoft Store uses WGS instead of the same visible-file layout. File-extension context: .sav Compatibility note: Microsoft Store WGS data should not be treated as a renamed Steam/Epic .sav file. Storefront migration is a separate conversion problem. 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 Hogwarts Legacy, 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 the expected path is empty, search the documented alternate HogwartsLegacy/Hogwarts/Phoenix directories and check the storefront. Do not delete the older folder until the active save set is confirmed. Return to the untouched backup before trying another change.
Verification context: Multiple Windows storefront paths, Steam Play behavior, and cloud services were reviewed against current PCGamingWiki coverage.