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.
Where Final Fantasy VII Remake Intergrade stores PC saves
The researched save-location boundary is Windows: Steam: %USERPROFILE%DocumentsMy GamesFINAL FANTASY VII REMAKESteam ; Epic: %USERPROFILE%DocumentsMy GamesFINAL FANTASY VII REMAKEEOS ; Microsoft Store: %LOCALAPPDATA%Packages39EA002F.EXED1_n746a19ndrrjgSystemAppDatawgs. The known file or folder pattern is Storefront-specific save subfolders beneath the documented FINAL FANTASY VII REMAKE profile root.. This is the practical starting point because launcher, profile, and storefront context can change which copy is active even when two folders look similar.
Storefront and profile differences
Documented launchers or storefronts: 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. When looking for a missing save, identify the executable/storefront you actually launched and the user/profile that created the progress before copying anything between directories.
Cloud synchronization
Steam Cloud, Epic cloud, and Xbox Cloud are documented for their respective storefronts; OneDrive may also affect Documents when folder backup is enabled. A cloud service should be treated as another copy of the save, not as proof that the local folder is disposable. Before a manual restore, let synchronization finish, make an offline backup, and avoid starting the game while files are being replaced.
What the files represent
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. The current filename/folder evidence is Storefront-specific save subfolders beneath the documented FINAL FANTASY VII REMAKE profile root.. File-extension context: .sav A location guide does not claim that every file in the directory is safe to edit or that files from another storefront are automatically interchangeable.
If the save is not where expected
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. Also check redirected Documents folders, Steam Play prefixes, account IDs, and launcher-specific containers where applicable. Preserve every candidate copy before testing a restore so troubleshooting does not destroy the only surviving version.
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.