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.
Choose the correct backup boundary
For Final Fantasy IX, the researched PC save location is Windows: Steam: %USERPROFILE%AppDataLocalLowSquareEnixFINAL FANTASY IXSteamEncryptedSavedData ; Microsoft Store: %LOCALAPPDATA%Packages39EA002F.FINALFANTASYIX_n746a19ndrrjgSystemAppDatawgs. The known save file or folder pattern is Steam master save commonly includes SavedData_ww.dat; Memoria/modded setups may create additional derived files.. 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. 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 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.
Account for cloud saves
Steam Cloud and Xbox Cloud are documented for their corresponding editions. 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 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. Compatibility note: 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. 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 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. 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 Final Fantasy IX save path and current community notes describing SavedData_ww and Memoria-derived files.