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.
Prepare the source PC
On the source system, identify the actual Satisfactory save root: Windows: %LOCALAPPDATA%FactoryGameSavedSaveGames<account-id>. The expected file/folder pattern is *.sav files; the filename normally reflects the save/session name, with multiple autosave/manual versions possible.. 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, 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. 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 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. 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 and Epic cloud are documented. Cloud conflicts are especially relevant when switching machines or branches. 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
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. If the destination does not see the transferred progress, 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. Verify game edition/version, store, profile IDs, redirected folders, and mod/DLC dependencies before editing the save itself.
Verification context: Reviewed against current PCGamingWiki and Official Satisfactory Wiki save-file documentation, including the account-ID subfolder and current cloud-conflict guidance.