Dragon Quest XI has an uncomplicated-looking Saved/SaveGames path, but the critical backup detail is edition identity. The original Windows release and Dragon Quest XI S are not merely storefront labels for the same executable, so SaveEditor does not collapse them into one compatibility claim. A good backup includes the full SaveGames folder plus a note of which edition created it. This prevents a perfectly valid save from being diagnosed as corrupt when the real problem is that it belongs to a different release.
Known Dragon Quest XI save-file structure
The researched filename or folder pattern is Unreal Engine save files beneath SavedSaveGames; exact generated filenames can vary with slot/profile context.. File-extension context: .sav The documented format notes are: The original Windows release uses an Unreal Engine Saved/SaveGames tree beneath Documents. It is distinct from later Definitive Edition products and should not be mixed across editions.
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. Do not assume a save from Dragon Quest XI S or a console edition is compatible with this original PC release. Edition identity is part of the backup metadata. 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: %USERPROFILE%DocumentsMy GamesDRAGON QUEST XISavedSaveGames. Storefront context: Steam. The 2018 PC release and Dragon Quest XI S are separate products with different data expectations. This hub documents the original Dragon Quest XI URL from the project plan. 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 entire SavedSaveGames directory and label it with the exact game edition and build. Keep configuration/mod backups separately so a gameplay save can be restored without changing unrelated settings. 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 is documented; OneDrive can also affect Documents when backup is enabled. 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 progress is not detected after a restore, verify that the installed title is the same edition and that Documents/OneDrive points to the location you backed up. Those questions require a verified parser/profile or a game-specific source, not a generic format guess.
Verification context: Reviewed against current PCGamingWiki Dragon Quest XI save location and cloud documentation.