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.
Known Final Fantasy XV Windows Edition save-file structure
The researched filename or folder pattern is slotNUM folders; eight manual slots and two autosave slots are documented for the PC release.. File-extension context: No single extension is sufficient to identify every relevant save record. The documented format notes are: 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.
Why an extension is not enough
A save filename can identify a likely container, but it does not prove the internal schema, game version, checksum rules, encryption state, or editability. 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. SaveEditor therefore separates file identification from Tool compatibility and only labels a game-specific Tool Verified when its exact profile/version evidence passes the runtime gate.
Where the format is stored
PC save locations: 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. 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. This matters because two releases can use different containers or companion files even when the visible slot name is similar.
Back up before inspecting or editing
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. A read-only viewer is lower risk than a writer, but the live save should still be copied first. Cloud context also matters: Steam Cloud, EA cloud, and Xbox Cloud are documented; Xbox/PC cross-save applies to the Microsoft ecosystem. Keep the original bytes available so any experiment can be reversed without relying on a cloud service or automatic backup.
What this reference does not claim
This page does not infer an undocumented checksum algorithm, encryption key, compression layer, or cross-store conversion from the file extension. Troubleshooting evidence: 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. Those questions require a verified parser/profile or a game-specific source, not a generic format guess.
Verification context: Reviewed against current PCGamingWiki Final Fantasy XV save-location, slot-folder, cloud, and transfer notes.