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 ID (your Steam or Epic account). Open it. Every .sav file in there is a save; a session 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. Drag in your save as a ZIP, RAR, 7Z, or TAR.GZ. Loose .sav files aren't accepted on their own, so zip them first: a single .sav, your account folder, or the whole SaveGames folder all work. The importer finds the saves at any depth and keeps the session folder, so the structure doesn't have to be exact. Password-protected archives are rejected.

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

5. Now load it in-game. Open Server Manager, select your server, and 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).

6. Open the Manage Saves tab, pick your save, and load it. The server switches to it right away.

Your previous server world is kept as Backup before world upload in the Backups list. Restore it any time.

Setting up a brand-new server? Switch on Upload Existing World during setup and drop the same file there, then do steps 5 and 6 after the first power-up.

If you'd rather skip the dashboard: in Server Manager, sign in as Administrator, open Manage Saves, and use its upload option to send a save from your PC to the server. Then load it from the same tab. Satisfactory offers this for every dedicated server.

That's step 5 and 6 above. Uploading puts the save on the server's disk; loading it is a separate admin action in Manage Saves. That's how Satisfactory's dedicated server works, not something we control.

That's decided by Satisfactory's own Auto-Load Session Name setting: on startup the server loads the most recent save of that session (Satisfactory wiki). It's a game setting rather than a dashboard one, so treat it as a convenience, not a guarantee. After a restart, open Server Manager and check which world is running; if it isn't the one you want, load it again from Manage Saves. Every save you uploaded is still on the server either way.

A save written on the Experimental branch may not open cleanly 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.

If you need the raw files, open the Files card or connect with SFTP. Saves are at .config/Epic/FactoryGame/Saved/SaveGames/, one folder per session, not under FactoryGame/Saved/ where you might expect them.

To bring a world back to your PC, download a backup, unzip it, and with the game closed copy the .sav files into your account folder from the first section, then look for the session in Load Game. Saves written by a dedicated server sit in a server session folder rather than under your account ID, so they may not list the same way a single player save does.

Reach us on Discord or at support@haptic.gg. Include your server name, the exact message under the upload box, and which save you loaded in Manage Saves.