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.
Identify the exact save you intend to edit
The researched Dragon Quest XI PC save location is Windows: %USERPROFILE%DocumentsMy GamesDRAGON QUEST XISavedSaveGames. Known file/folder pattern: Unreal Engine save files beneath SavedSaveGames; exact generated filenames can vary with slot/profile context.. 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. Do not edit a similarly named file from a different profile, edition, or cloud cache.
Make an untouched backup first
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. Keep that copy outside the live save directory and do not overwrite it with later experiments. Cloud context: Steam Cloud is documented; OneDrive can also affect Documents when backup is enabled. 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 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. File-extension context: .sav Compatibility note: 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. 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 Dragon Quest XI, 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 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. Return to the untouched backup before trying another change.
Verification context: Reviewed against current PCGamingWiki Dragon Quest XI save location and cloud documentation.