Stop the Satisfactory dedicated server cleanly, then copy its entire server save directory to storage outside the live server path. Keep several dated copies, and restore only after stopping the server and preserving the current directory. This protects the world from accidental overwrites, failed updates, and disk loss far better than relying on autosaves, the local overwrite folder, or cloud synchronization alone.
Playing with friends? Godlike.Host runs hosted Satisfactory servers from 10 data-center locations, with free DDoS protection.
What you are actually backing up
A Satisfactory dedicated server world is represented by the complete server directory, not by the server executable, installation folder, or a server-settings file. That directory contains the save files the running service reads and writes. Copy the whole directory so that every .sav file and the supporting files in the same location travel together.
As an Amazon Associate I earn from qualifying purchases.
The copy must be independent of the live save path. A second folder on the same disk is useful for quickly undoing an overwrite, but it will not help if the disk fails or the filesystem becomes inaccessible. An external hard drive or SSD, a separate backup host, or another storage system provides actual path and device separation.
Use dated generations rather than one continually replaced archive. A name such as satisfactory-server-2026-10-15-before-update tells you what the copy is and when it was made. Include a server or session label when the machine hosts more than one world.
#1 Best Overall
- Easily store and access 2TB to content on the go with the Seagate Portable Drive, a USB external hard drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Where Satisfactory dedicated-server saves are stored
The correct path depends on the operating system and, on Windows, the account that runs the service. Back up the profile belonging to the dedicated-server process, not necessarily the profile of the person administering it.
Linux
The official dedicated-server documentation lists this Linux location:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
~/.config/Epic/FactoryGame/Saved/SaveGames/serverThe tilde means the home directory of the account running the server. If the service runs under a dedicated system user, expand the path for that user. Looking under your personal home directory can produce an apparently valid but unrelated folder when the service runs as someone else.
Windows user installation
For a server started under a normal Windows user account, the documented location is:
%LocalAppData%FactoryGameSavedSaveGamesserverCoffee Stain’s support guidance gives the broader Windows save root as %LOCALAPPDATA%FactoryGameSavedSaveGames. The dedicated-server saves are in its server subdirectory. Enter the path in File Explorer’s address bar or resolve the environment variable in a command prompt under the account that owns the server process.
Windows services, NSSM, and service accounts
A Windows service may run as LocalSystem, NetworkService, or another account. Those identities have different profile directories from your interactive login. The dedicated-server guide documents the corresponding systemprofile and NetworkService locations. Check the service’s “Log On” identity, then locate the FactoryGameSavedSaveGamesserver tree inside that account’s profile.
Rank #2
- Easily store and access 5TB of content on the go with the Seagate portable drive, a USB external hard Drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
If you are unsure, stop the service, inspect the file modification times in candidate directories, start the service briefly, and see which directory receives the next save. Do not edit or delete candidates while testing. Once identified, record the exact path in your backup procedure so future copies do not depend on guesswork.
Do not confuse these locations
- Game or server installation directory: contains binaries and configuration, but it is not the world-save backup.
- Server-settings file: controls settings and access; it does not contain the world state.
- Personal single-player save directory: can contain a different world from the dedicated server.
SaveGames_backup: is an automatic overwrite safeguard, not a complete off-device backup.
Make a consistent manual backup
Copying while the server is writing can capture an incomplete or inconsistent set of files. The safest routine is a short maintenance window in which no player is connected and the process is fully stopped.
- Announce the maintenance window. Ask players to leave the world and stop joining while the copy is made. A player disconnect can trigger a save, so wait for that activity to finish.
- Stop the server cleanly. Use the method appropriate to your installation: the service manager for a Windows service, the terminal session or service unit for Linux, or the server’s normal shutdown control. Confirm that the dedicated-server process has exited before copying.
- Open the account-specific
serverdirectory. Verify that it is the directory used by this instance and that it contains the expected.savfiles. If several worlds are present, identify the one you intend to protect by its filename and modification time. - Copy the entire directory. Copy the folder itself, including every save file and any companion files, to an external drive, separate backup host, or other storage not used as the live save path. Do not copy only the newest-looking file.
- Apply an unambiguous name. Add the date, approximate time, and server or session label to the destination folder or archive. Keep the original directory structure inside the copy so it can be restored without reconstructing paths.
- Check that the copy completed. Confirm that the destination contains the expected files and that the copy operation reported no errors. If the destination is removable, eject it safely after the copy so it is not left exposed to a later filesystem problem.
- Start the server again. Tell players when the maintenance window ends and watch the first startup for errors before allowing normal play.
The source files do not specify a required schedule. Choose a frequency based on how much recent progress your group could recreate. Make an additional copy before server upgrades, operating-system changes, mod changes, or moving the instance to another machine.
Keep generations and test that they can be restored
A single successful copy can still be unusable if it was made after corruption or if the destination later fails. Retain multiple dated generations so an older, known-good world remains available. A practical policy is to keep recent copies for routine mistakes and older milestone copies for major updates, but the exact number is an operational choice rather than an official Satisfactory requirement.
Periodically test one generation on a disposable copy of the server or a maintenance instance. The test should verify that the world starts, the expected save appears, and players can load into it. Do not test by overwriting the only live directory. Preserve the live directory first, and use a separate test location or a temporary instance.
Label a tested copy as known good. If a backup has never been opened, treat it as unverified even when the file copy itself completed without an error.
Rank #3
- Easily store and access 1TB to content on the go with the Seagate Portable Drive, a USB external hard drive.Specific uses: Personal
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop. Reformatting may be required for Mac
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
What automatic safeguards do—and do not—protect
The SaveGames_backup folder
Satisfactory’s save-file documentation says that when one save overwrites another, the previous file is placed in SaveGames_backup. That is helpful when a manual save accidentally replaces the wrong version. An autosave does not create that backup unless it manually overwrites a save.
The folder remains on the same storage as the live saves and is therefore vulnerable to disk failure, filesystem damage, mistaken deletion, and a problem that affects the whole server account. It is a quick rollback mechanism, not an independent disaster-recovery copy. Include the main server directory in your external backup routine rather than treating SaveGames_backup as the destination.
Autosave interval and player-disconnect saves
Dedicated-server settings include an autosave interval and an “Auto-Save on Player Disconnect” option. Shorter intervals and disconnect saves reduce the amount of recent progress that could be lost if the process stops unexpectedly. They still write to the same live storage, however, and do not create an off-machine copy. Keep them enabled according to your group’s tolerance for save interruptions, but continue making independent backups.
Cloud synchronization
Cloud synchronization is convenient, but Coffee Stain’s support guidance recommends regularly copying saves to another location, especially when cloud saves are in use. Conflicts can appear when switching between stable and experimental versions, moving saves between platforms, or continuing on another machine. A synchronized copy can also propagate an unwanted or damaged state instead of preserving the older one you need.
Keep a separately dated copy before changing versions or machines. If a conflict prompt appears, stop and preserve all competing copies before choosing one; do not let a synchronization client silently replace the only local version.
Compare backup approaches
Evaluate a method on five questions: does it undo an accidental overwrite, survive disk failure, support automation, restore quickly, and remain isolated from the live server?
Rank #4
- Easily store and access 4TB of content on the go with the Seagate Portable Drive, a USB external hard drive.Specific uses: Personal
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
| Approach | Accidental-overwrite recovery | Survives live-disk failure | Automation | Recovery speed | Isolation from live server |
|---|---|---|---|---|---|
SaveGames_backup on the server disk |
Good for eligible overwrites | No | Automatic | Fast | Poor |
| Second folder on the same disk | Good if kept intact | No | Easy to script | Fast | Low |
| External hard drive or SSD | Good when generations are retained | Yes, if disconnected or otherwise separate | Manual or scriptable | Depends on drive and copy size | High when offline |
| Separate backup host | Good with versioned copies | Yes, when independently operated | Well suited to scheduled jobs | Depends on network and storage | High |
| Cloud synchronization | Uncertain during conflicts | Depends on provider history and retention | Automatic | Usually convenient | Variable |
| Administrative API download | Can obtain a named save | Only if the downloaded file is stored separately | Potentially scriptable | Depends on API and network | High when exported elsewhere |
The strongest basic arrangement is a stopped-server copy to an external drive or separate host, with several dated generations. A local overwrite folder and autosaves remain useful as first-line safeguards, while cloud or API copies add convenience only when you retain an independently stored version.
Restore a Satisfactory dedicated-server save
Restoration is a controlled replacement, not a merge. Select a known-good generation, stop all writes, preserve the current state, and then put the selected directory back in the exact account-specific location.
- Stop player access. Ask everyone to leave and prevent new connections during the maintenance window.
- Stop the dedicated-server process. Use the service manager or normal shutdown method and wait until the process has exited completely.
- Preserve the current directory. Rename or copy the existing
serverdirectory to a quarantine location with the date and reason, such asserver-before-restore-2026-10-15. This gives you a way back if the selected generation is not the one you wanted. - Select the generation. Choose a dated copy that you have tested or that predates the incident. Do not select solely by filename; check its timestamp and the event you are trying to undo.
- Replace the live directory. Copy the selected generation into the exact
SaveGamesserverorSaveGames/serverpath for the account that runs the service. The resulting structure should not contain an extra nesting level such asserverserver.... - Start the server. Watch the startup output and verify that the expected save is available. If the server reports an error, stop it and restore the preserved pre-restore directory rather than repeatedly modifying the backup.
- Verify the world in-game. Confirm the map, player progress, inventories, and recent construction before reopening the server to the group.
Keep the pre-restore directory until the restored world has been verified. Only then should you archive or delete it under your normal retention policy.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsUsing the administrative API
When the API is configured, the dedicated-server documentation describes enumerating saves and downloading a named save by supplying SaveName. This can be useful for an administrative export or for retrieving a particular generation without browsing the filesystem. Treat the downloaded result as a backup only after storing it outside the live save path. The same shutdown, preservation, and verification rules apply when putting it back into service.
Troubleshoot common backup and restore failures
The copied folder contains no current save
You probably copied the profile of the administrator instead of the profile of the service account, or you copied a personal save location. Check the service’s log-on identity and compare modification times before and after one controlled server save. On Windows, inspect the documented systemprofile or NetworkService profile when those accounts are used.
Files change during the copy
The process was still running, a player was disconnecting, or another scheduled task was touching the directory. Stop the server, wait for the process to exit, and repeat the copy. Do not assume that a partially completed copy is restorable.
Best Value
- High capacity in a small enclosure – The small, lightweight design offers up to 6TB* capacity, making WD Elements portable hard drives the ideal companion for consumers on the go.
- Plug-and-play expandability
- Vast capacities up to 6TB[1] to store your photos, videos, music, important documents and more
- SuperSpeed USB 3.2 Gen 1 (5Gbps)
The restore starts the wrong world
Check that the selected generation belongs to this server and that the restored files are directly inside the account’s server directory. An extra directory level, a similarly named session, or a copy placed under the wrong Windows profile can make a valid backup appear to be missing.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →A cloud client reports a conflict
Stop the server and preserve every local and downloaded version before resolving the prompt. Version changes, platform moves, and switching between stable and experimental builds are known conflict situations. Decide which dated copy is authoritative, then restore it manually rather than allowing an automatic replacement to discard the alternatives.
The automatic overwrite copy is missing
SaveGames_backup is created when a save overwrites another save; an autosave does not necessarily trigger it. If no overwrite occurred, there may be no automatic copy. Use your independent dated generations for recovery.
The selected save fails after a version change
First return to the game and server version associated with the known-good generation, if possible, and test the restore on a disposable instance. Keep the current directory preserved while diagnosing the mismatch. Do not delete the backup while experimenting.
Operational checklist
- Identify the exact
serverdirectory for the service account. - Schedule a maintenance window and stop player access.
- Stop the server completely before copying.
- Copy the entire directory, including every
.savfile. - Store the copy outside the live save path.
- Use dated names and retain multiple generations.
- Make an extra copy before upgrades, version switches, or migration.
- Test a generation on a disposable or maintenance instance.
- During restoration, preserve the current directory before replacement.
- Verify the world in-game before inviting players back.
Key points to remember
The complete account-specific server directory is the backup unit. Linux paths follow the home directory of the service user; Windows paths change when a service runs as systemprofile, NetworkService, or another identity. Automatic overwrite files, autosaves, and cloud synchronization can reduce inconvenience, but none replaces a separately stored, dated generation. A clean stop before copying and a preserved directory before restoring are the two controls that prevent most avoidable save damage.
Recommended Free Tools
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
