Skip to content
Game save workbench
Local-first tools No installation Support status shown
DEVICE-LOCAL Favorites and recent pages stay in this browser.

Game Hub / Save Reference

Satisfactory Save Files & Tools

Satisfactory PC save location, backup, file-format, launcher, cloud-sync, and compatibility reference. This Game Hub documents save-file facts without implying that a game-specific Save Editor is available.

PC

01 / Overview

Save reference at a glance.

Game Hubs separate documented save-file facts from actual Tool support. A Game Hub can be useful even when no custom editor exists.

Developer
Coffee Stain Studios
Publisher
Coffee Stain Publishing
Platforms
PC
Save extensions
.sav

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.

For this PC reference, the documented storage is Windows: %LOCALAPPDATA%FactoryGameSavedSaveGames<account-id>. The known file or folder pattern is *.sav files; the filename normally reflects the save/session name, with multiple autosave/manual versions possible.. 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.

Backup guidance: 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. Steam Cloud and Epic cloud are documented. Cloud conflicts are especially relevant when switching machines or branches. Launcher and cloud context matters because Steam and Epic can create different account-ID subfolders under the same root. Selecting the wrong folder can make the correct .sav look missing.

Compatibility and recovery should stay conservative. 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 expected progress is not visible, 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. SaveEditor.com only labels a game-specific editor as available when a separate linked Tool has a verified operational runtime; this reference page by itself is not an editor claim.

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.

02 / Save locations

Where the save files are stored.

Paths are displayed only when they have been explicitly documented for this Game Hub. Environment variables and launcher-specific differences should remain visible instead of being silently normalized.

Windows
%LOCALAPPDATA%FactoryGameSavedSaveGames<account-id>

Launcher / edition differences

Steam and Epic can create different account-ID subfolders under the same root. Selecting the wrong folder can make the correct .sav look missing.

03 / File format

Files, extensions, and format notes.

This section documents only known file names and structures. Format notes can later connect directly to SaveEditor.com parsers, checksum engines, and converters.

Extensions

.sav

File names / patterns

  • *.sav files
  • the filename normally reflects the save/session name
  • with multiple autosave/manual versions possible.

Format notes

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.

Launchers / stores

Steam / Epic Games Launcher

Cloud save notes

Steam Cloud and Epic cloud are documented. Cloud conflicts are especially relevant when switching machines or branches.

04 / Tools

Actual linked Tool support.

No verified game-specific Save Editor is currently listed. This Game Hub remains useful for save locations, file details, backup guidance, and other linked utilities.

No active game-specific Tool is currently listed.

Planned and deprecated Tool records are intentionally excluded. The save-reference information on this page remains separate from Tool availability.

05 / Backup

Protect the original before editing.

Save editing should be reversible. Keep an untouched copy outside the active save directory before replacing, converting, repairing, or modifying a save.

  1. 01
    Close the game.

    Avoid modifying a save while the game or launcher may still be writing to it.

  2. 02
    Copy the entire relevant save set.

    Some games use multiple files, profile folders, metadata, or companion files rather than one isolated save.

  3. 03
    Store the backup elsewhere.

    Use a separate folder or archive so cloud sync or the game cannot overwrite the untouched backup.

  4. 04
    Edit a copy, then validate.

    Follow the exact compatibility and processing notes on the Tool page before replacing the active save.

Game-specific backup note

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.

06 / Troubleshooting

When a save is missing or rejected.

Start with reversible checks. Do not delete or overwrite the only copy while diagnosing a path, cloud-sync, version, or format problem.

Game-specific notes

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.

A

Confirm the correct profile.

Games, launchers, and operating systems may keep separate save folders for different users, editions, or profiles.

B

Check cloud synchronization.

A cloud service can restore an older file or overwrite a local change. Preserve both copies before resolving a conflict.

C

Check Tool compatibility.

A matching filename does not prove a matching format. Verify platform, game version, extension, and Tool support state.

D

Restore the untouched backup.

If the game rejects a modified save, return to the original backup before attempting another change.

07 / FAQ

Satisfactory save-file questions.

Answers are generated only from visible Game Hub metadata and actual linked Tool states, plus universal backup guidance.

Where are Satisfactory save files stored?

The currently documented save locations are listed in the Save locations section above. Use the location that matches your platform or environment.

What save-file extension does Satisfactory use?

The extensions currently documented on this page are: .sav.

Does SaveEditor.com have a verified Satisfactory Save Editor?

No verified game-specific Save Editor is currently listed. This Game Hub remains useful for save locations, file details, backup guidance, and other linked utilities.

Should I back up the save before using a Tool?

Yes. Keep an untouched copy outside the active save directory before modifying or converting the file. Some games use multiple companion files, so back up the relevant save folder when in doubt.

Are there cloud-save considerations for Satisfactory?

Steam Cloud and Epic cloud are documented. Cloud conflicts are especially relevant when switching machines or branches.

Editorial review

Game-specific metadata on this hub was last reviewed on 2026-08-08. Individual Tool pages maintain their own verification dates and compatibility notes.

Verification notes

Reviewed against current PCGamingWiki and Official Satisfactory Wiki save-file documentation, including the account-ID subfolder and current cloud-conflict guidance.