Final Fantasy VII Remake is a good example of why a save-location page must name the storefront, not merely the game. The Steam and Epic releases both use the Documents-based FINAL FANTASY VII REMAKE tree but separate data under Steam and EOS, while the Microsoft Store build uses a WGS container. A useful backup therefore starts by identifying which executable/storefront produced the save. Copying the parent folder blindly can mix unrelated metadata and make later troubleshooting harder. SaveEditor treats this hub as a reference for locating and preserving the PC data; it does not infer that slot data is safely interchangeable across every storefront.
Known Final Fantasy VII Remake Intergrade save-file structure
The researched filename or folder pattern is Storefront-specific save subfolders beneath the documented FINAL FANTASY VII REMAKE profile root.. File-extension context: .sav The documented format notes are: The PC releases separate Steam, Epic/EOS, and Microsoft Store WGS storage. Backups should preserve the whole active storefront save directory because slot files and companion metadata can travel together.
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. PC storefront saves are related game data but their container paths differ. Treat manual cross-store transfer as a separate migration task rather than ordinary restore unless a tested conversion workflow is available. 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 VII REMAKESteam ; Epic: %USERPROFILE%DocumentsMy GamesFINAL FANTASY VII REMAKEEOS ; Microsoft Store: %LOCALAPPDATA%Packages39EA002F.EXED1_n746a19ndrrjgSystemAppDatawgs. Storefront context: Steam, Epic Games Launcher, Microsoft Store. The storefront changes the save root. Do not copy a Steam folder into EOS or WGS and assume the container layout is equivalent. 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
Close the game and launcher, identify the storefront actually used, and copy the complete matching Steam, EOS, or WGS save directory before replacing any slot. Label the backup with storefront and date. 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, Epic cloud, and Xbox Cloud are documented for their respective storefronts; OneDrive may also affect Documents when folder backup is enabled. 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 progress looks missing, first check Steam versus EOS versus Microsoft Store and whether Documents is redirected by OneDrive. A cloud conflict can restore a newer or older copy after a manual replacement. Those questions require a verified parser/profile or a game-specific source, not a generic format guess.
Verification context: Reviewed against current PCGamingWiki coverage for Final Fantasy VII Remake Intergrade, including storefront-specific save roots and cloud support. No game-specific editor is claimed.