Final Fantasy IX needs a particularly cautious backup workflow because the Steam save directory is named EncryptedSavedData and modern mod setups may write additional derived files into the same area. The safest baseline is an untouched copy of the whole directory before any editor or Memoria operation. That gives you a known-good source even if a mod creates exported slot files or changes which file is loaded. The Microsoft Store release uses WGS instead, so SaveEditor does not present a simple rename-and-copy operation as universal compatibility.
Known Final Fantasy IX save-file structure
The researched filename or folder pattern is Steam master save commonly includes SavedData_ww.dat; Memoria/modded setups may create additional derived files.. File-extension context: .dat The documented format notes are: The Steam release stores an encrypted save-data set under LocalLow. Microsoft Store uses WGS. Mod frameworks can add their own companion or exported files, so a clean backup should preserve the original game-owned data before modded copies.
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. A Steam master save and Microsoft WGS container are not interchangeable by filename alone. Mod-created Memoria files may depend on the mod version and should be kept separate from the original backup. 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%AppDataLocalLowSquareEnixFINAL FANTASY IXSteamEncryptedSavedData ; Microsoft Store: %LOCALAPPDATA%Packages39EA002F.FINALFANTASYIX_n746a19ndrrjgSystemAppDatawgs. Storefront context: Steam, Microsoft Store. Steam and Microsoft Store paths are different. Memoria or other mods can add extra files beside the original save and should not be confused with the untouched source data. 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 EncryptedSavedData folder on Steam before installing a save editor or mod framework. On Microsoft Store, back up the WGS container rather than renaming arbitrary files into the Steam directory. 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 for their corresponding editions. 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 an edit or restore seems ignored, disable competing cloud restoration temporarily, verify whether the game is loading the original or a Memoria-derived file, and use Load rather than assuming Continue points to the intended slot. Those questions require a verified parser/profile or a game-specific source, not a generic format guess.
Verification context: Reviewed against current PCGamingWiki Final Fantasy IX save path and current community notes describing SavedData_ww and Memoria-derived files.