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

Save File Formats

Octopath Traveler Save File Format Reference

Octopath Traveler save-file format reference covering the known PC file or folder pattern, documented format characteristics, compatibility boundaries, and what should not be inferred from an extension alone.

Editorial state
Reviewed
Reading time
3 min
Difficulty
Beginner
Last reviewed

Before you start

Work from a copied save rather than the live file. Use the documented path and filename/folder pattern to identify the correct record before inspecting bytes or text.

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.
  • Do not infer editability from a filename extension; format and version compatibility must be verified.

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.

Known Octopath Traveler save-file structure

The researched filename or folder pattern is SaveData0.sav is commonly the autosave; numbered SaveData*.sav files represent manual slots on Steam.. File-extension context: .sav The documented format notes are: 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.

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. Switch/PC and Microsoft/Steam transfers reported by the community are migration workflows, not proof that all storefront containers are byte-identical. 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: Steam: %USERPROFILE%DocumentsMy GamesOctopath_Traveler<user-id>SaveGames ; Microsoft Store: %LOCALAPPDATA%Packages39EA002F.FrigateMS_n746a19ndrrjgSystemAppDatawgs. 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. 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 the full SaveGames folder, including every SaveData*.sav and steam_autocloud.vdf if present. Keep the original slot numbering when testing a restore. 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 and Xbox Cloud are documented; OneDrive may also synchronize Documents. 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 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. Those questions require a verified parser/profile or a game-specific source, not a generic format guess.

Verification context: Reviewed against current PCGamingWiki Octopath Traveler save path plus long-running community slot/file-name documentation.

Troubleshooting

If the expected result does not match.

Game-specific note: 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.

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. The file/folder naming and documented format boundary 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