How to Load an Older Autosave on a Satisfactory Dedicated Server

To roll a Satisfactory dedicated server back to an earlier point, open Server Manager, select the server, sign in as admin, go to Manage Saves, open your session, pick the autosave from before the problem by its time, and click Load Game. The server reloads the factory from that moment. By default the server keeps only 3 rotating autosaves at a 5 minute interval, so act quickly after a mistake, and raise the number kept so you have more room next time.

When you would roll back

• Someone dismantled a whole production line or a train network by accident.
• A blueprint went down in the wrong place and broke a factory floor.
• A mod update or game patch broke parts of the save, and an earlier save behaves.
• A vehicle or train glitch destroyed things and you want them back.

Anything built after the save you load is lost for everyone, so tell the group before you load.

How the server's autosaves work

The server autosaves on a timer set in Server Manager (Autosave Interval, 5 minutes by default) and keeps a small rotating set of files per session:

<SessionName>_autosave_0.sav
<SessionName>_autosave_1.sav
<SessionName>_autosave_2.sav

The numbers are slots, not ages. The server writes into the next slot each time and wraps around, so _autosave_0 is not always the newest. Always go by the time shown in Server Manager or the file date.

With 3 slots and a 5 minute interval, the oldest autosave is about 15 minutes old. A mistake discovered half an hour later has already rotated out of the autosaves. That is why manual saves and your own backups matter (see the end of this guide).

Step 1: Pause autosaves from overwriting your target

As soon as you notice the problem, the clock is running: each new autosave pushes the oldest one out. Two quick ways to protect the save you want:

• Ask everyone to leave the server. With Auto Pause on (the default), the server pauses when empty and stops autosaving.
• Or load the target save straight away in Step 2 before the next autosave interval.

Step 2: Load the older save in Server Manager

1. In Satisfactory, open Server Manager from the main menu.
2. Select your server and sign in with the admin password if asked.
3. Open the Manage Saves tab.
4. Find your session and expand it to see every save in it: autosaves and manual saves, each with its date and time.
5. Pick the save from just before the problem.
6. Click Load Game and confirm.

The server unloads the current world and loads the one you picked. Players who were connected are disconnected and rejoin through Server Manager as usual.

Step 3: Download a copy for safety

While you are in Manage Saves, select the save you just loaded and download it to your PC. If anything goes wrong later, you can upload it again in a minute. The upload guide covers uploading a save back.

Step 4: Check Auto-Load Session Name

If Auto-Load Session Name in the server settings points to your session, the server loads the newest save in that session after every restart. Loading an older save does not change that, and as soon as the server autosaves again, the newest save is the one you rolled back to. Just make sure the session name is right, so a restart does not load a different session.

When Server Manager will not load it

If the save list is empty, the load fails, or you cannot reach Server Manager, work with the files directly:

1. Stop the server.
2. Open the server's save folder:
   • Linux: ~/.config/Epic/FactoryGame/Saved/SaveGames/server/
   • Windows: %LOCALAPPDATA%\FactoryGame\Saved\SaveGames\server\
3. Download the whole folder as a backup.
4. Find the autosave you want by its modified time.
5. Make it the newest save of the session. The simplest way is to copy it to a new name, like MyFactory_rollback.sav, so it gets the newest date.
6. Start the server and load that save by name in Server Manager, or set it in Auto-Load Session Name if the session name changed.

Do not edit or rename saves while the server runs. It writes autosaves on its own and can overwrite your changes.

Keep more history for next time

Three autosaves is not much for a big group. Raise the count and add your own saves:

• More autosaves. On a GamezServers server, set Autosaves to keep in the panel. On a self hosted server it is mNumRotatingAutosaves in Engine.ini, as covered in the server settings guide. Values of 5 to 10 cost only disk space.
• Named saves before big jobs. Before tearing down a factory floor or placing a blueprint over existing builds, save the game with a clear name from the pause menu. Named saves do not rotate.
• Off server backups. Download the newest save once a week, or take a server backup before patches.

Common problems

• The older autosave is gone. It rotated out. Look for a manual save, a downloaded copy, or a server backup.
• Load fails with a version message. The save was made by a newer game version than the server. Update the server first. More in updating a Satisfactory server.
• Players cannot rejoin after the load. Give the server a moment to finish loading a large save, then rejoin. If it persists, see Satisfactory server can't connect.

Rollbacks with backups built in

On a GamezServers Satisfactory server, Autosaves to keep is a panel setting, one click backups give you restore points that never rotate out, and the save folder is in the file manager for the manual route. The server stays up for the whole group without anyone's PC running. See the Satisfactory game page for plans.

FAQ

How many autosaves does a Satisfactory server keep?

Three by default, rotating every autosave interval (5 minutes by default). Raise the number kept to get more history.

Can I roll back just one part of the factory?

No. Loading a save rolls back the whole world. Rebuild small mistakes by hand, or use a blueprint saved earlier.

Where are Satisfactory dedicated server saves?

On Linux in ~/.config/Epic/FactoryGame/Saved/SaveGames/server/, on Windows in %LOCALAPPDATA%\FactoryGame\Saved\SaveGames\server\.

Why is _autosave_0 not my newest save?

The numbers are rotating slots. The server writes into the next slot each time, so check the date and time, not the number.