Satisfactory Save File Location: PC, Linux, and Servers

The Satisfactory save file location depends on where you play: Windows keeps local saves under your user profile, Linux Steam uses a Proton prefix, and a dedicated server stores its world in a separate server folder. Steam and Epic players on PC can use the same dedicated server; PlayStation and Xbox cannot join one. This guide gives you the paths, explains which files matter, and points to the right next step if you are moving a world.

Find the Satisfactory save file location on Windows#

On Windows, Steam and Epic saves are in the same location. Press Win + R, paste this path, and press Enter:

%LOCALAPPDATA%\FactoryGame\Saved\SaveGames\

Windows opens the local AppData folder for your signed-in account. Inside SaveGames, open the folder named with a long numeric ID. That ID belongs to a Steam or Epic account that has launched Satisfactory on this Windows profile. The game creates separate folders when different accounts have played on the same Windows login, so do not assume the newest-looking folder belongs to the account you are using now.

The per-account directory contains the world save files, which end in .sav. If the path does not open, check that Satisfactory has been started at least once under this Windows user. Also check that you did not paste the path into a different Windows account’s File Explorer session. The official save-file reference lists the same Windows location for Steam and Epic.

If you have several numeric folders, compare their recent file dates and look for the session you recognize in the game’s Load Game list. A filename can be changed, so use the session name and saved date as a pair when identifying a world. Copy the whole .sav file to another folder before testing it; do not edit the only copy in place.

This is the PC client’s local folder. A dedicated server does not read from it automatically; you have to move or upload a copy through the game’s Server Manager or another supported file-transfer method. For the full setup, see the dedicated-server installation guide.

Find a Linux or Steam Deck save inside Proton#

The Windows version of Satisfactory runs through Proton on Linux, so its saves live inside the game’s compatibility prefix rather than a native Linux SaveGames directory. The Steam app ID is 526870. On a typical desktop Steam installation, start here:

~/.local/share/Steam/steamapps/compatdata/526870/pfx/drive_c/users/steamuser/Local Settings/Application Data/FactoryGame/Saved/SaveGames/

On Steam Deck, the official path is commonly under the Steam root:

/home/deck/.steam/root/steamapps/compatdata/526870/pfx/dosdevices/c:/users/steamuser/AppData/Local/FactoryGame/Saved/SaveGames/

Open the numeric account folder inside that directory to find the .sav files. Linux paths are case-sensitive, and Steam may install its library on a different drive. If the path is missing, locate the compatdata/526870 directory under the Steam library where Satisfactory is installed, then follow the pfx path from there. The official save-file page also documents the Linux Steam Play path. These Proton paths are documented locations; the exact library path can vary with your Steam setup.

Locate a dedicated server’s world on Linux or Windows#

Server saves are separate from local client saves. On a typical Linux server they live under the account that runs the server:

~/.config/Epic/FactoryGame/Saved/SaveGames/server/

The leading dot makes .config hidden in many Linux file managers. ~ means the server process user’s home directory, which may not be the account you use to log in. If the directory is empty, first confirm which user starts the server and whether a world has been created or loaded.

On Windows, the standard user path is:

%LOCALAPPDATA%\FactoryGame\Saved\SaveGames\server\

Windows services can run as a different account, so the save directory may instead be under the service profile. The official dedicated-server file locations list these service paths:

Do not put a server save in the parent SaveGames directory and expect it to appear in the server’s session list. The server scans its server folder. Game Hosting’s Satisfactory panel has a Saves shortcut to that folder and a separate Blueprints shortcut; it does not provide a general in-browser save editor. If you are choosing where the world should live, our Satisfactory hosting guide explains what to compare.

Find Docker saves in the host bind folder#

The robtme/satisfactory-server Docker image (formerly published under the wolveix username) uses a host directory mounted at /config. Its README says that /config/saved contains the saves, blueprints, and server configuration. In the container, the game’s normal Linux SaveGames path is symlinked into this directory. That means you should open the host folder you mounted to /config, then look inside saved/server for world files.

For example, with this volume mapping:

volumes:
  - ./satisfactory-server:/config

the server saves appear on the Docker host under:

./satisfactory-server/saved/server/

The actual host path is relative to the directory where your Compose file runs. Docker Desktop on Windows may show the same mounted files through the Windows path you selected for the bind mount. Do not search only inside the container’s hidden .config path: this image maps that game directory to the persistent /config/saved location. Check the image maintainer’s current README before changing a volume mapping. The maintainer, Rob Thomas, has renamed his GitHub username to robtme; the existing wolveix/satisfactory-server image continues to receive updates.

Tell world saves, blueprints, and settings apart#

The server folder contains session save files. A manual save can use a filename you choose, while rotating autosaves commonly use names ending in _autosave_0, _autosave_1, and _autosave_2. The session name is saved inside the file header; changing the filename does not rename the session shown in Server Manager. Use Manage Saves or the server’s session list to identify the world before moving anything.

Blueprints are stored separately under SaveGames/blueprints/. That folder may not appear until a blueprint has been saved. A blueprint file is not a world save, and copying it does not move your factory. The official blueprint reference covers how blueprints work; do not mix .sbp files with .sav worlds.

The server’s settings file is also separate from the world. For a server using port 7777, it is named ServerSettings.7777.sav in the parent SaveGames directory, beside server and blueprints. If you changed the configured game port, the filename uses that port. This settings file stores server configuration and claim-related data; it is not the factory you load. See the server settings reference for its supported controls.

Keep the newest world safe before changing versions#

Before copying or replacing a world, identify the session name and latest save time, then preserve a separate copy. Autosaves rotate on the same server disk; they are useful recovery points, but they are not an independent backup. A backup should remain available if an update, disk problem, or mistaken file operation affects the active server.

Save the active session before a planned stop or update. The server does not promise to save the current factory just because its process is stopped. Make a backup before switching between Stable and Experimental or changing mods, and verify that you can restore the copy before removing the original. A save written by a newer game build may not load on an older one, so check both the save’s source and the server build before downgrading. Coffee Stain’s support FAQ recommends backing up saves before changing versions.

If you are moving a co-op world, follow the claim and server setup steps before uploading it. If you want to keep the server online without leaving your PC running, check the hosting options; the service supports PC players on Steam and Epic, while console players cannot join dedicated servers. For a deeper backup routine, start with our host-selection checklist and save file locations.

Get the right path for your next task#

Use the local account folder for a world saved on your PC, the server folder for a dedicated-server world, and the Docker bind mount when the server runs in a container. Keep settings, blueprints, and session saves separate so you do not replace the wrong file. If you are specifically setting up a dedicated server, the Satisfactory server guide walks through installation and connection; for options such as passwords and autosaves, use the server settings guide.