Satisfactory Save Location: Find, Back Up and Upload Your Save
Where Satisfactory saves are on Windows, Linux, Steam Deck and a dedicated server, how to back them up, and how to upload a save to your server.
The Satisfactory save location on Windows is %LOCALAPPDATA%\FactoryGame\Saved\SaveGames\<your ID>\, and it's the same folder for Steam and Epic. On a dedicated server running Linux, including ours, saves go in .config/Epic/FactoryGame/Saved/SaveGames/server/ and not in the install folder. Satisfactory uses one save format, so a single-player or co-op world loads on a dedicated server without conversion, as long as the server runs the same build and branch as the game that saved it. An Experimental save won't open on a Stable server. You can upload a save two ways: from the in-game **Server Manager**, or by copying the .sav into the folder above through the panel.
This guide uses the Console, File Manager and Backups tabs of your Satisfactory game server panel for the manual route, and the in-game Server Manager for the direct one.
One Concept First: Sessions, Not Files
Satisfactory groups saves by the session name written inside the file — not by file name. mygame_autosave_1.sav and mygame_2026-08-16.sav with the same session name are one session to the server, and the server's auto-load setting loads the most recent save of a session. Keep this in mind when your uploaded session shares a name with something already on the server: the two merge into one list, and the newest file wins.
Satisfactory Save File Location on Every Platform
| Where the game runs | Save folder |
|---|---|
| Windows (Steam or Epic) | %LOCALAPPDATA%\FactoryGame\Saved\SaveGames\<your ID>\ |
| Linux desktop, Steam with Proton | ~/.local/share/Steam/steamapps/compatdata/526870/pfx/drive_c/users/steamuser/Local Settings/Application Data/FactoryGame/Saved/SaveGames/<your Steam ID>/ |
| Linux, Flatpak Steam | ~/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/compatdata/526870/pfx/drive_c/users/steamuser/AppData/Local/FactoryGame/Saved/SaveGames/<your Steam ID>/ |
| Steam Deck | /home/deck/.steam/root/steamapps/compatdata/526870/pfx/dosdevices/c:/users/steamuser/AppData/Local/FactoryGame/Saved/SaveGames/<your Steam ID>/ |
| Your GameServerKings server | .config/Epic/FactoryGame/Saved/SaveGames/server/ (the File Manager root is the server's home folder) |
| A Windows server you host yourself | %LocalAppData%\FactoryGame\Saved\SaveGames\server\ |
A few things about the PC folders:
- The
<your ID>folder is your store account ID, which is a long string of characters and not your username. If you own the game on both Steam and Epic, you'll see two folders next to each other. The official wiki notes that the Steam ID is usually the shorter one. - No Steam folder? That happens if you bought the game on Steam after playing on Epic. Start a new game on Steam and save it once, and the folder will appear.
- On Linux and Steam Deck the folder is hidden. Turn on hidden files in your file manager first. The official wiki spells the regular Steam path with
Local Settings/Application Data/and the Flatpak and Steam Deck paths withAppData/Local/. If one doesn't exist in your Proton folder, try the other. - Each
.savstarts with the session name, not the name you gave the save. Autosaves rotate through<session>_autosave_0.sav,_1and_2. On your server, the Number of Rotating Autosaves field in the Startup tab sets how many are kept. It defaults to3, and the panel writes it toEngine.ini(mNumRotatingAutosaves) every time the server starts. To find your latest save, sort the folder by date modified. - The game keeps a backup when you overwrite a save. If you save over an existing save, the game copies the old one to
SaveGames\SaveGames_backupfirst. This doesn't happen for autosaves.
On a server, the SaveGames/ folder holds more than the server/ folder. ServerSettings.<port>.sav stores the server name, passwords, admin claim and auto-load session. blueprints/ appears once someone saves a blueprint. Neither one is a world save.
Route A: Upload From Inside the Game (No Files Needed)
Launch Satisfactory and open Server Manager from the main menu, then select your server (add it with Add Server if it isn't listed yet — see getting started).
Open the Manage Saves tab.
Use the tab's upload control, pick the save from your local list, and send it to the server.
Select the uploaded save and Load.
That's the whole route. If it works for you, skip to verifying the load. The manual route below exists for when the in-game uploader misbehaves, for very large saves, or when you're moving files between servers.
Route B: Upload Through the Panel
Step 1: Stop the Server
Click Stop on the Console tab. Copying save files under a running server risks a half-written autosave landing on top of your upload.

Step 2: Upload the .sav
In the File Manager, open the server's save folder. The Linux dedicated server keeps its saves in the home folder under ~/.config/Epic/, not in the install's own FactoryGame/Saved/ folder. On your server the home folder is the File Manager's root, so the path is:
.config/Epic/FactoryGame/Saved/SaveGames/server/ The FactoryGame/Saved/SaveGames/ folder next to the game files isn't where the server looks, so a .sav uploaded there is ignored.
Upload your .sav into it. If the browser upload stalls, SFTP into the same folder resumes interrupted transfers.
Step 3: Load the Save and Verify
Start the server, connect in-game, and open Server Manager → Manage Saves. Your uploaded session appears in the list — select the save and Load. There is no documented console command that loads a save: the handful the server has cover saving, autosave tuning and shutdown, and loading lives in the Server Manager or behind the HTTPS API's LoadGame call.
To make the server come back to this world on every restart, set Auto-Load Session Name to your session in the Server Manager's Settings → Dedicated Server section.
Then verify: the session name, play time and milestone progress in the Server Manager should match your local game. Walk your factory floor before you call it done.
After the Move
- Back it up. Take a snapshot through the Backups tab now, so the migrated factory is your restore point. A panel snapshot plus the server's own rotating autosaves is the right pair — the autosaves cover an in-session mistake, the snapshot covers everything else.
- Creative Mode travels with the save. What used to be called Advanced Game Settings was renamed Creative Mode in Update 1.2, and it is a flag in the save file's own header rather than a server setting. A local world that had it enabled arrives with it enabled, silently, and it cannot be turned back off — achievements stay disabled for that world permanently. The individual toggles inside it remain adjustable; only the initial opt-in is one-way.
Backing Up a Satisfactory Save
On your PC, copy the whole <your ID> folder somewhere outside SaveGames, for example to another drive or a cloud folder you manage yourself. A copy you made is more dependable than a cloud sync you didn't check.
On your server, save first, so the copy holds your latest progress and not the last autosave. Run server.SaveGame "Before update" in the Console tab of the in-game Server Manager, not the panel's Console tab (why). Then pick one of these:
- A panel backup. Open the Backups tab and click Create Backup. This snapshots the whole server, including
ServerSettings.<port>.sav, so a restore also brings back the server name, passwords and claim. See How to create a backup. - A copy on your own PC. In the File Manager, open
.config/Epic/FactoryGame/Saved/SaveGames/server/and click Download on a single.sav. To get the whole folder, use Archive onserver/first and download the archive the panel creates. The panel downloads files, not folders.
That copy on your PC is what saves you if the server is reinstalled or the world gets corrupted. Make one before every game update and every mod change.
Common Issues
- The uploaded save isn't in Manage Saves: It landed in the wrong folder. It must be inside the
server/subfolder, notSaveGames/itself —SaveGames/also holdsblueprints/and theServerSettings.<PORT>.savfile, and neither is a save game. - The server loaded an older version of my world: Session-name collision. The server auto-loads the newest save of the session, and an existing autosave postdated your upload. Load your save explicitly from Manage Saves, or clear the stale session first — carefully: deleting a session is a different action from deleting a save file, and it removes every save belonging to that session.
- Progress loads but mods are missing: Mods are not inside the save. The server needs the same mods installed — see How to install mods for Satisfactory.
- Loading takes minutes: Normal for a late-game factory. One to three minutes to deserialize a large save is expected; watch the Console rather than restarting.
- I can't find my save folder: The folder is named after your store ID, not your username, so look for the long string inside
SaveGames. On Linux and Steam Deck it's inside a hidden Proton folder (see the table above). - My older save came back after switching PCs or branches: Steam or Epic Cloud Sync asked whether to upload or download, and the cloud copy won. The official wiki says that unless you're actually moving between PCs, choose to upload your local save to the cloud. Keep your own copy before you switch branches.
- I uploaded into
FactoryGame/Saved/SaveGames/next to the game files: That folder belongs to the install, and the server doesn't read saves from it. The server only reads saves from the.config/Epic/...path.
Common Questions
Where are Satisfactory saves stored on Steam and on Epic?
They're in the same place: %LOCALAPPDATA%\FactoryGame\Saved\SaveGames\, with a separate subfolder for each store account. You can copy a .sav between the two folders, or onto a server, without converting it.
Where does the dedicated server keep its saves?
On Linux, ~/.config/Epic/FactoryGame/Saved/SaveGames/server/. On our servers, that's .config/Epic/FactoryGame/Saved/SaveGames/server/ at the top of the File Manager. A Windows server you run yourself uses %LocalAppData%\FactoryGame\Saved\SaveGames\server\.
Can I take my world back off the server to play it single-player?
Yes. Saves work in both directions. Download the .sav from the server's server/ folder, put it in your local <your ID> folder, and load it in the game. Your PC needs to be on the same branch as the server.
How many autosaves does my server keep?
By default it keeps 3, set by Number of Rotating Autosaves in the Startup tab. The game deletes the oldest autosave when it writes a new one, so autosaves only reach a little way back. For anything older, use a panel backup or a downloaded copy.
What to Read Next
Getting started with your Satisfactory server for first boot and the in-game Server Manager basics
Satisfactory Dedicated Server Commands, API and Settings for
server.SaveGame, autosave tuning and the HTTPS API behind Manage SavesConfiguring your Satisfactory server for the settings your migrated world runs under
Is Satisfactory crossplay? — which players can join the world once you have uploaded it
Made with 💜 by GameServerKings

Need a Satisfactory server?
Deploy an instantly-provisioned Satisfactory server on high-clock hardware. DDoS protected, no contracts, cancel anytime.
From $10.40 /month