Uploading a Satisfactory save to a dedicated server

Unlike most games, Satisfactory makes this transfer easy: it happens from the client, without copying a single file by hand. Which is also why few people know it is possible.

The principle

Once the server is claimed and you are connected as admin, the session management interface offers to upload a save from your machine. You pick your single-player file, it goes up, and it becomes a session like any other.

Your factory, your research, your unlocks: all of it follows.

The steps

1. Save your single-player game manually before quitting, so you start from a known state rather than an autosave of uncertain age.
2. Claim the server if you have not already, and connect with the admin password.
3. Upload the save from session management.
4. Load the session and check, alone, that the factory is complete before inviting anyone.

What can block it

• A save that is too old. A game from an earlier version may fail to load on an up-to-date server.
• A very large save. A mature factory produces heavy files, and the upload can fail on a modest upstream connection. Retrying from a more stable network usually settles it.
• Mods. A single-player game created with mods will not load on a server without them. This is the most common cause of an inexplicable failure.

The other direction

Downloading works too: you can pull a session off the server to play it solo, or simply to keep a copy at home. It is the simplest way to build a backup outside the server, and it is worth making a habit of it.

After the transfer

Keep the original save on your machine until the session has run for several days. It costs nothing and it is your only way back.

Our Satisfactory hosting adds schedulable server-side backups, which complements the game's own mechanism rather than replacing it.