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.
Start with the least destructive explanation
When Final Fantasy XV Windows Edition progress appears missing, first verify the active PC location: 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. Expected files/folders: slotNUM folders; eight manual slots and two autosave slots are documented for the PC release.. Many apparent save failures are actually profile, storefront, path-redirection, or cloud-selection problems rather than damaged game data.
Preserve every surviving copy
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. Before renaming, moving, replacing, or opening candidate backups, copy them outside the live directory. Do not use the only surviving file as the test specimen for repair or editing.
Check launcher and cloud state
Storefront 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. Cloud notes: Steam Cloud, EA cloud, and Xbox Cloud are documented; Xbox/PC cross-save applies to the Microsoft ecosystem. A sync client can reintroduce an older or newer version after a manual restore, so recovery work should keep local and cloud copies conceptually separate until the wanted progress is confirmed.
Use format and compatibility clues
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. 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. If the file exists but is ignored, compare the complete directory structure, slot/profile naming, game edition, mods/DLC, and any companion metadata. Do not assume an extension change or generic checksum tool can repair a game-specific container.
Game-specific troubleshooting
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 a known-good backup works, preserve it and create a fresh in-game save before further experiments. If no copy works, prefer read-only inspection and source-backed game-specific tooling over repeated writes.
Verification context: Reviewed against current PCGamingWiki Final Fantasy XV save-location, slot-folder, cloud, and transfer notes.