Final Fantasy XV has more than one plausible-looking PC save location, which makes a full-folder backup more reliable than hunting for a single file. On Steam, cloud behavior can route active saves through Steam userdata even though a Documents savestorage tree also exists. The numbered slot folders are significant: moving the contents while changing the slot number is not equivalent to restoring the original directory. SaveEditor therefore records both the storefront root and the slot structure and recommends testing a copied slot only after the original folder is preserved.
Choose the correct backup boundary
For Final Fantasy XV Windows Edition, the researched PC save location is Windows: Steam: %USERPROFILE%DocumentsMy GamesFINAL FANTASY XVSteam<user-id>savestorage and <Steam-folder>userdata<user-id>637650remote ; EA app: %USERPROFILE%DocumentsMy GamesFINAL FANTASY XVOriginsavestorage ; Microsoft Store: %LOCALAPPDATA%Packages39EA002F.FINALFANTASYXVforPC_n746a19ndrrjgSystemAppDatawgs. The known save file or folder pattern is slotNUM folders; eight manual slots and two autosave slots are documented for the PC release.. Back up the entire savestorage or active remote folder, not only one payload file. Keep each slotNUM directory under its original number so previews and related data remain grouped. 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, EA app, Microsoft Store. Steam Cloud can make the Steam userdata remote folder authoritative even offline. EA/Origin and Microsoft Store use separate storage conventions.
Account for cloud saves
Steam Cloud, EA cloud, and Xbox Cloud are documented; Xbox/PC cross-save applies to the Microsoft ecosystem. 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
Final Fantasy XV organizes saves by numbered slot folders. Steam may use both Documents savestorage and its userdata remote location when cloud saves are enabled. The slot number must remain aligned when importing a folder. Compatibility note: A folder copied into the wrong slot number may not load as intended. Microsoft Store WGS is not the same layout as Steam or EA Documents storage, so cross-store migration should be handled explicitly. 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 imported slot does not appear, verify the slot number, active storefront, and whether Steam Cloud replaced the local copy. Screenshot previews can remain stale until the game saves that slot again. 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 XV save-location, slot-folder, cloud, and transfer notes.