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.
Which storefront context matters
Documented Octopath Traveler PC launchers/storefronts: 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. The active storefront/account should be identified before any restore because cloud and local storage may not use the same path or container across editions.
Documented cloud behavior
Steam Cloud and Xbox Cloud are documented; OneDrive may also synchronize Documents. Cloud synchronization is useful for continuity, but it can also turn a restore into a conflict-resolution event. Let synchronization settle before making a manual backup, and keep an offline copy outside any folder monitored by the launcher or operating-system sync service.
Local save roots still matter
The researched local save boundary is Windows: Steam: %USERPROFILE%DocumentsMy GamesOctopath_Traveler<user-id>SaveGames ; Microsoft Store: %LOCALAPPDATA%Packages39EA002F.FrigateMS_n746a19ndrrjgSystemAppDatawgs; the known file or folder pattern is SaveData0.sav is commonly the autosave; numbered SaveData*.sav files represent manual slots on Steam.. A cloud-enabled game still has concrete local data involved in ordinary play, and that local context is what you need when identifying which copy was modified most recently.
Avoid accidental overwrite loops
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. When restoring, close the game and launcher, preserve both the current local copy and the backup you want to test, then place the intended data in the matching profile/storefront location. Do not repeatedly open the game between different copies without noting which side the cloud client selected.
Compatibility and conflict checks
Switch/PC and Microsoft/Steam transfers reported by the community are migration workflows, not proof that all storefront containers are byte-identical. If progress disappears or rolls back, 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. Resolve identity/path/cloud questions first. A cloud conflict is not proof that the save itself is corrupt, and a successful upload is not proof that files from another storefront are compatible.
Verification context: Reviewed against current PCGamingWiki Octopath Traveler save path plus long-running community slot/file-name documentation.