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.
Prepare the source PC
On the source system, identify the actual Final Fantasy XV Windows Edition save root: 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 expected file/folder pattern is slotNUM folders; eight manual slots and two autosave slots are documented for the PC release.. Close the game, let the active launcher finish writing and synchronizing, then make a complete offline copy rather than transferring a file that may still be open.
Preserve storefront and profile identity
Documented 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. A transfer between two PCs is simplest when both systems use the same storefront/account/profile context. If the destination uses a different store or container, treat that as a migration problem rather than an ordinary restore.
Move the complete save boundary
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. Put the copied data on the destination only after confirming the destination save path. If the game creates a new empty save first, keep that new folder as another backup so you can compare structures and revert.
Handle cloud sync deliberately
Steam Cloud, EA cloud, and Xbox Cloud are documented; Xbox/PC cross-save applies to the Microsoft ecosystem. Decide whether the local transferred copy or cloud copy should be authoritative before launching the game. If possible, preserve both. After the transferred save loads correctly, make a fresh in-game save and let the launcher synchronize normally.
Check compatibility before blaming the transfer
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. If the destination does not see the transferred progress, 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. Verify game edition/version, store, profile IDs, redirected folders, and mod/DLC dependencies before editing the save itself.
Verification context: Reviewed against current PCGamingWiki Final Fantasy XV save-location, slot-folder, cloud, and transfer notes.