Satisfactory: move your existing save to your server

1. Press Win+R, paste %LOCALAPPDATA%\FactoryGame\Saved\SaveGames, and press Enter.

2. Inside is one folder per account, named with a long number (your Steam or Epic account). Open it. Every .sav file in there is a save; one game usually has several, one per autosave.

3. Not sure which is the right one? Sort by Date modified. Save names also match what you see in the game's Load Game menu.

Played on a friend's world? The files are on the PC that hosted it, in the same place. Ask them for the .sav files.

1. Power down your server. Upload World is disabled while the server is running.

2. Open the Backups card and click Upload World, next to New Backup.

3. Drop in your save. Any of these works:

• one .sav file, or several (pick them together);

• the folder named with your account number, dragged in whole;

• a ZIP, RAR, 7Z, or TAR.GZ of any of the above, or of the whole SaveGames folder.

The upload finds the saves wherever they are inside. Password-protected archives are rejected.

1. Click Upload and replace world (on a brand-new server with no backups yet, the button reads Upload world) and wait for the import to finish.

2. Power up. The server loads your upload and from now on loads it at every start. Players join through Server Manager as usual.

Setting up a brand-new server? Switch on Upload Existing World during setup and drop the same files there. The first power-up loads your save.

• Nothing is deleted. Your uploaded saves are added next to the ones the server already has. The game that was running before is still there in Manage Saves, and a full copy of the server's saves is kept first as Backup before world upload in the Backups list. Restore it any time to go back.

• Same file name: if a save in your upload has exactly the same file name as one on the server, your upload replaces that one file. The dashboard tells you which, and the old copy is in Backup before world upload. If two saves in your upload share a file name but belong to different games (a Steam and an Epic folder, say), both are kept: one gets " (2)" added to its name, and the dashboard tells you which.

• Several games in one upload: they are all added, and the one you saved most recently is the one that loads. The dashboard names it. To play another, sign in to Server Manager as Administrator and load it from Manage Saves.

• Blueprints: if you upload your whole SaveGames folder, the blueprints in its blueprints folder come along too.

• Files that aren't saves (logs, settings, blueprints on their own, other games' files, the game's program files) are left out. An upload with no Satisfactory save in it is refused with a message that says what it holds instead, and nothing on your server changes. A save renamed with an extra ending, such as .sav.bak, is not read: rename it so it ends in .sav.

• An empty save file (0 bytes, often a OneDrive or Steam Cloud placeholder that never downloaded) is refused with its name. Open your save folder, make sure the file has downloaded, and upload it again. Next to real saves, an empty one is left out and the dashboard says so.

• A save that was copied while Satisfactory was still writing it is cut short, and the game would crash opening it. The upload refuses it with its name, or leaves it out next to whole saves and loads that game's previous save. Close Satisfactory, copy the save again, and upload the new copy.

A dedicated server keeps its saves in FactoryGame/Saved/SaveGames/server, inside .config/Epic in its home folder on Linux and Docker, or in %LOCALAPPDATA% on Windows. Download that server folder (or the whole SaveGames folder) from your old host's file manager or with SFTP, and upload it here as it is or zipped. The server's settings file ServerSettings.<port>.sav is left out: your Haptic server keeps its own name and passwords.

If a save in your upload was made with mods, the upload tells you which ones. Install the same mods on the Mods card before you start the server, or before you load that save in Manage Saves. If a mod is not on the Mods card, upload its LinuxServer .smod file from ficsit.app to FactoryGame/Mods on the Files card. Without its mods the server still opens the save, but it removes everything those mods added, and its next save makes that permanent. If that already happened, install the mods and upload the save again. Newer versions of a mod open older saves.

A save on a custom map (for example from the Platform Expansion Program mod) needs that mod too. Without it the server opens the save on the standard map, and its next save makes that permanent.

If you'd rather skip the dashboard: in Server Manager, sign in as Administrator with the Admin Password from the Details tab of your server's Overview card (click the eye icon to reveal it).

Then open Manage Saves and use its upload option to send a save from your PC to the server, and load it from the same tab. Satisfactory offers this for every dedicated server.

• Did the server start since the upload? The upload loads at the next power-up. If the server was already running, restart it.

• Is your save from the Experimental branch? A server on the stable version can't open a save made with a newer version of the game. Your server keeps running the game it had, the save moves to the SaveGames/haptic-not-loaded folder in Files, and the server card tells you. To use it, turn on Experimental Branch on the Details tab, then upload the save again.

If the game stops while opening an uploaded save, the next start moves that save into the SaveGames/haptic-not-loaded folder, starts the game you had before, and tells you on the server card. If the file is damaged or the server ran out of memory, the card says so. The server never tries that file again on its own, and you can download it from Files. To try again, copy the save with Satisfactory closed and upload the new copy.

Still on the old world? Contact us with the server name and the name of the save you uploaded. Your upload is on the server either way.

A save written on the Experimental branch may not open on a stable server. If your game runs Experimental, turn on Experimental Branch on the Details tab before uploading, or switch your game back to stable first. Once Experimental has touched a save, moving that save back to stable can cause problems, so keep a copy of the original before you switch. See Satisfactory: Experimental branch and updates.

Satisfactory decides that with its own Auto-Load Session Name setting: at every start the server loads the most recent save of that game (Satisfactory wiki). Loading your upload makes it the game the server loads at every start, and the save we make each time the server stops keeps that game's latest progress, so a restart picks up where you left off. If the game can't open your upload, the server keeps loading the game it had.

Switched to a different game in Manage Saves? Loading it changes what's running now. To make it the one that loads at every start, change Auto-Load Session Name in Server Manager's server settings too.

If you need the raw files, open the Files card or connect with SFTP. Every save is in .config/Epic/FactoryGame/Saved/SaveGames/server/, and blueprints are in .config/Epic/FactoryGame/Saved/SaveGames/blueprints/, one folder per game. That's not under FactoryGame/Saved/ where you might expect it. Saves the server could not open are in .config/Epic/FactoryGame/Saved/SaveGames/haptic-not-loaded/. If you upload your whole save folder again later, those saves are left out. Upload one on its own to try it again.

To bring a world back to your PC, download a backup, unzip it, and with the game closed copy the .sav files from its server folder into your account folder from the first section, then look for the game in Load Game.

Reach us on Discord or at support@haptic.gg. Include your server name, the exact message under the upload box, and the name of the save you uploaded.