Octopath Traveler uses a clear SaveGames directory on the conventional Steam PC build, but the user-ID layer and numbered slot names are important when restoring progress. Community guides consistently identify SaveData0.sav as the autosave and subsequent numbered files as manual slots. SaveEditor recommends backing up the entire directory so slot context and Steam cloud metadata remain available. Microsoft Store uses WGS, so its files are described as a separate container rather than an ordinary .sav location.
Identify the exact save you intend to edit
The researched Octopath Traveler PC save location is Windows: Steam: %USERPROFILE%DocumentsMy GamesOctopath_Traveler<user-id>SaveGames ; Microsoft Store: %LOCALAPPDATA%Packages39EA002F.FrigateMS_n746a19ndrrjgSystemAppDatawgs. Known file/folder pattern: SaveData0.sav is commonly the autosave; numbered SaveData*.sav files represent manual slots on Steam.. Storefront context: Steam, Epic Games Launcher, Microsoft Store. Storefront paths differ. Steam/Epic PC save data can resemble ordinary .sav files while Microsoft Store uses WGS containers. Do not edit a similarly named file from a different profile, edition, or cloud cache.
Make an untouched backup first
Back up the full SaveGames folder, including every SaveData*.sav and steam_autocloud.vdf if present. Keep the original slot numbering when testing a restore. Keep that copy outside the live save directory and do not overwrite it with later experiments. Cloud context: Steam Cloud and Xbox Cloud are documented; OneDrive may also synchronize Documents. If a launcher can synchronize the save, prevent it from silently replacing either the original or edited copy while testing.
Understand the format boundary
The Steam release uses an Unreal-style Documents SaveGames directory under a user ID. Microsoft Store uses WGS. Slot numbering matters when replacing a particular save. File-extension context: .sav Compatibility note: Switch/PC and Microsoft/Steam transfers reported by the community are migration workflows, not proof that all storefront containers are byte-identical. 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 Octopath Traveler, 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 save does not appear, verify the user-ID folder, exact SaveData slot number, and cloud state. For Microsoft Store, identify the correct WGS payload before any conversion. Return to the untouched backup before trying another change.
Verification context: Reviewed against current PCGamingWiki Octopath Traveler save path plus long-running community slot/file-name documentation.