Upload a Satisfactory save to a dedicated server

Prepare the factory save

Create a manual save with a recognizable name in the source session, then leave the game. On Windows, save files normally live under:

%LOCALAPPDATA%\FactoryGame\Saved\SaveGames

Keep a copy outside the game and record the version and installed mods. Confirm the session and timestamp; a newer autosave may belong to another world.

If the destination already contains a factory, protect that session as well. Uploading and loading another world should not eliminate your only recovery point.

Upload and load through the game

Add the server in Server Manager using the provider's connection details and authenticate as administrator. NitroServ's procedure uses Manage Saves, then Upload Save. Select the local save to transfer.

After upload, open Load Save, select the transferred file and load it. Wait for completion before inviting the whole group. This managed import requires an accessible running service; manual SFTP replacement follows a different procedure with a prior shutdown.

Verify more than the terrain

Visit the main factory, inspect storage and check the power network. Have players verify their inventories and characters. An apparently new character can result from the login identity used; do not immediately delete the previous character as a repair attempt.

For a modded save, all required components must support dedicated servers. Do not assume personal blueprint files are included in a simple save upload. Check separately for blueprints the group wants to retain.

Confirm ongoing persistence

Create a new server save and verify its availability after restarting. Check passwords and automatic pause because they control access and production while nobody is connected.

Retire the original session only after these checks. If loading fails, retain the uploaded file and logs to distinguish a version mismatch, unsupported mod or incomplete transfer.

Frequently asked questions