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.
Which storefront context matters
Documented Final Fantasy XV Windows Edition PC launchers/storefronts: 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. The active storefront/account should be identified before any restore because cloud and local storage may not use the same path or container across editions.
Documented cloud behavior
Steam Cloud, EA cloud, and Xbox Cloud are documented; Xbox/PC cross-save applies to the Microsoft ecosystem. Cloud synchronization is useful for continuity, but it can also turn a restore into a conflict-resolution event. Let synchronization settle before making a manual backup, and keep an offline copy outside any folder monitored by the launcher or operating-system sync service.
Local save roots still matter
The researched local save boundary 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 file or folder pattern is slotNUM folders; eight manual slots and two autosave slots are documented for the PC release.. A cloud-enabled game still has concrete local data involved in ordinary play, and that local context is what you need when identifying which copy was modified most recently.
Avoid accidental overwrite loops
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. When restoring, close the game and launcher, preserve both the current local copy and the backup you want to test, then place the intended data in the matching profile/storefront location. Do not repeatedly open the game between different copies without noting which side the cloud client selected.
Compatibility and conflict checks
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 progress disappears or rolls back, 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. Resolve identity/path/cloud questions first. A cloud conflict is not proof that the save itself is corrupt, and a successful upload is not proof that files from another storefront are compatible.
Verification context: Reviewed against current PCGamingWiki Final Fantasy XV save-location, slot-folder, cloud, and transfer notes.