Skip to content
Game save workbench
Local-first tools No installation Support status shown
DEVICE-LOCAL Favorites and recent pages stay in this browser.

Backups & Safety

How to Back Up Octopath Traveler II Saves

A game-specific Octopath Traveler II backup and restore workflow based on the researched save boundary, launcher/cloud behavior, compatibility notes, and recovery risks for the PC release.

Editorial state
Reviewed
Reading time
3 min
Difficulty
Beginner
Last reviewed

Before you start

Close the game before copying or replacing saves. Keep one untouched backup outside the live save directory. Identify the storefront/launcher and active player/profile before changing files.

Key takeaways

What this guide establishes.

  • Use the documented save directory for the PC storefront/profile you actually play.
  • Back up the complete save boundary before restore, migration, repair, or editing.
  • Treat cloud synchronization as a separate copy that can overwrite a manual restore.
  • If progress is missing, verify storefront, account/profile, path redirection, and cloud state before assuming corruption.

Octopath Traveler II looks similar to the first game at a glance, but its Steam directory adds an explicit Steam branch and current transfer reports call out SystemData.sav alongside SaveData slot files. That makes whole-folder backup more important than copying a single large slot. SaveEditor records the current Microsoft Store WGS path separately and avoids claiming that a Game Pass blob can simply be renamed into a Steam SaveData file without the system-data context.

Choose the correct backup boundary

For Octopath Traveler II, the researched PC save location is Windows: Steam: %USERPROFILE%DocumentsMy GamesOctopath_Traveler2Steam<user-id>SaveGames ; Microsoft Store: %LOCALAPPDATA%Packages39EA002F.OCTOPATHTRAVELER2_n746a19ndrrjgSystemAppDatawgs. The known save file or folder pattern is SaveData*.sav plus SystemData.sav on current Steam builds.. Copy the whole SaveGames directory on Steam, including SystemData.sav. For Microsoft Store, preserve all WGS containers before identifying slot and system payloads. Copying the complete documented save boundary is safer than selecting one visually obvious file, because companion metadata, indexes, backups, or multiple slots can be required together.

Make an offline copy before changing anything

Close the game first, wait for the active launcher to finish writing, then copy the save data to a separate folder that the game and sync client do not watch. Label the copy with the game, storefront, profile, and date. Documented launcher context: Steam, Microsoft Store. Steam and Game Pass storage differ. Current community migration notes identify both slot-sized files and separate system data in WGS.

Account for cloud saves

Steam Cloud and Xbox Cloud are documented. Before restoring an older backup, decide which copy should win. If the game or launcher starts while an older manual copy is in place, synchronization can replace it before you confirm that it works. Keep the untouched backup outside the live save path until the restored progress has been opened and saved normally.

Restore without changing format assumptions

The sequel uses a Steam-specific Documents branch and separates slot saves from system data. Microsoft Store uses WGS. SystemData should be backed up with the slots because it can contain state not represented by one SaveData file. Compatibility note: Do not restore only one SaveData slot if you are trying to reproduce the complete profile state. Cross-store migration may need both slot and system payload handling. Restore into the matching storefront/profile context whenever possible. Do not rename a save extension, move a folder into a different container type, or assume a console/mobile copy is equivalent unless a tested migration path specifically says so.

Recovery fallback

If an imported slot seems blank or incomplete, check whether SystemData came from the same snapshot and whether Steam Cloud restored the previous directory. If the restored copy fails, put the untouched original back first. Then compare location, account/profile, cloud state, and the full directory structure before trying a different backup. The objective is reversible recovery, not repeated destructive experiments on the only copy.

Verification context: Reviewed against current PCGamingWiki Octopath Traveler II save path and 2026 community notes describing SystemData during WGS-to-Steam transfers.

Troubleshooting

If the expected result does not match.

Game-specific note: If an imported slot seems blank or incomplete, check whether SystemData came from the same snapshot and whether Steam Cloud restored the previous directory.

Verification and sources

How this guide was checked.

Phase 27 generated this Guide from the reviewed Phase 23/24 Game Hub evidence for Octopath Traveler II. The backup boundary, cloud context, and restore risks were cross-checked against the same public references recorded on the Game Hub. No unsupported game-specific editor, checksum, encryption, or cross-platform conversion capability is implied.

  1. www.pcgamingwiki.com