Satisfactory uses a consistent LocalAppData SaveGames root across Steam and Epic, but the account-ID directory underneath is important: a player who switched storefronts can have more than one valid subfolder. SaveEditor recommends comparing timestamps and preserving all relevant .sav generations rather than uploading or editing the first file found. This is also a format-version-sensitive game, so an external calculator saying “unsupported save version” can simply mean that tool has not caught up with a new game build.
Choose the correct backup boundary
For Satisfactory, the researched PC save location is Windows: %LOCALAPPDATA%FactoryGameSavedSaveGames<account-id>. The known save file or folder pattern is *.sav files; the filename normally reflects the save/session name, with multiple autosave/manual versions possible.. Back up the complete account-ID folder, not just the latest autosave. Keep several generations before moving between Early Access/Experimental/current builds or using an external calculator/editor. Copying the complete documented save boundary is safer than selecting one visually obvious file, because companion metadata, indexes, backups, or multiple slots can be required together.
Make an offline copy before changing anything
Close the game first, wait for the active launcher to finish writing, then copy the save data to a separate folder that the game and sync client do not watch. Label the copy with the game, storefront, profile, and date. Documented launcher context: Steam, Epic Games Launcher. Steam and Epic can create different account-ID subfolders under the same root. Selecting the wrong folder can make the correct .sav look missing.
Account for cloud saves
Steam Cloud and Epic cloud are documented. Cloud conflicts are especially relevant when switching machines or branches. Before restoring an older backup, decide which copy should win. If the game or launcher starts while an older manual copy is in place, synchronization can replace it before you confirm that it works. Keep the untouched backup outside the live save path until the restored progress has been opened and saved normally.
Restore without changing format assumptions
Steam and Epic use the same SaveGames root but place saves in account-ID subfolders. The game format changes across builds, so external tools may lag behind the current save version. Compatibility note: A third-party tool rejecting a .sav can mean the tool has not yet added the current Satisfactory save version; it does not prove the game file itself is corrupt. Restore into the matching storefront/profile context whenever possible. Do not rename a save extension, move a folder into a different container type, or assume a console/mobile copy is equivalent unless a tested migration path specifically says so.
Recovery fallback
If the expected .sav is absent, look one level below SaveGames for all account-ID folders and compare timestamps. If an external parser rejects it, test the save in the game before diagnosing damage. If the restored copy fails, put the untouched original back first. Then compare location, account/profile, cloud state, and the full directory structure before trying a different backup. The objective is reversible recovery, not repeated destructive experiments on the only copy.
Verification context: Reviewed against current PCGamingWiki and Official Satisfactory Wiki save-file documentation, including the account-ID subfolder and current cloud-conflict guidance.