Satisfactory Server Save Backup Guide
This guide walks you through backing up your Satisfactory dedicated server save files, so you can restore your factory after a crash, update, or accidental loss. You’ll need access to your server’s file system (via the host’s file manager, FTP, or SSH) and know where your server is installed. The process takes about five minutes and can save you hours of rebuilding.
What You’ll Need
- Access to your server’s file system (FTP, SSH, or your hosting provider’s file manager).
- The path to your Satisfactory server installation folder.
- A safe location to store the backup (another drive, cloud storage, or your local PC).
- Optional: A tool like WinSCP (Windows) or Cyberduck (Mac) for FTP transfers.
Step-by-Step
- Stop the server. If you’re using a game server hosting panel, click “Stop” or “Kill” on the server. If you’re running the server manually, close the terminal window or press Ctrl+C. This prevents the save file from being written to while you’re copying it, which can corrupt the backup.
- Locate the save folder. On Windows, the default path is
C:\Program Files\Epic Games\SatisfactoryDedicatedServer\FactoryGame\Saved\SaveGames\server. On Linux, it’s typically/home/youruser/.config/Epic/FactoryGame/Saved/SaveGames/serveror wherever you installed the server. If you used a hosting panel, the path is usually shown in the panel’s file manager. - Identify the save files. In the
serverfolder, you’ll see files with a.savextension (e.g.,MyFactory.sav). There may also be abackupsubfolder—that’s the server’s automatic backup, but you’ll make your own manual backup. - Copy the entire server folder. Select the
serverfolder (or at least all the.savfiles you want to back up) and copy it to your local machine or cloud storage. If using FTP, drag the folder to your desktop. If using SSH, you can usescporrsyncto copy it. - Verify the backup. Check that the copied files are the same size as the originals and that the most recent save file’s timestamp matches the last time you played. If you’re unsure, try opening the save locally in Satisfactory (single-player) to confirm it loads.
- Restart the server. Start the server again from your panel or terminal. Confirm it loads the save correctly by checking the logs or joining the game.
- Label and store the backup. Rename the backup folder with the date (e.g.,
ServerBackup_2025-04-01) and keep it in a safe place. Consider keeping at least three recent backups on different storage devices.
Common Mistakes
- Backing up while the server is running. This can result in a corrupted save because the file is in use. Always stop the server first.
- Only copying the .sav file and missing the .bak files. The .bak files are older versions that can be useful if the main save is corrupted. Copy everything.
- Not verifying the backup. A backup that’s zero bytes or incomplete is useless. Always check the file size and ideally test it by loading it locally.
- Overwriting your only backup. If you copy the same folder over an existing backup, you lose the previous version. Keep multiple dated backups.
- Using the wrong server folder. Some servers have separate folders for the game files and the save files. Double-check you’re in the
SaveGames/serverdirectory.
Tips
- Schedule automatic backups. If your hosting panel supports it, set up a cron job or scheduled task to copy the save folder to another location daily.
- Use the in-game backup feature. Satisfactory’s dedicated server automatically creates a
backupfolder with older saves. You can adjust the backup frequency inServerSettings.ini(e.g.,BackupIntervalMinutes=30). - Store backups off-site. If your server’s drive fails, a backup on the same machine will be lost. Use cloud storage or a different physical drive.
- Test your restore process. Once in a while, try restoring a backup to a test server to ensure you know how to do it when it matters.
- Keep your save folder tidy. Delete old saves you don’t need to reduce backup time and storage usage.
Troubleshooting
I can’t find the save folder. Search for FactoryGame.sav on your server. On Windows, use Explorer’s search; on Linux, use find / -name "*.sav". If you’re using a hosting provider, contact their support or check their documentation.
The backup file is 0 KB. This usually means the server was still running when you copied the file, or the disk is full. Stop the server, free up space, and re-copy.
The save won’t load after restoring. Make sure you placed the .sav file in the correct folder and that the server is stopped during the restore. If the save is corrupted, try an older backup from the backup folder.
I get an “Access Denied” error. Check file permissions. On Linux, ensure the user running the server has read permission to the backup folder. On Windows, run your FTP client as administrator if needed.
My server panel doesn’t have a file manager. Use FTP with the credentials provided by your host. If you don’t have them, contact support.
Frequently Asked Questions
How often should I back up my server? At least once a day if you play regularly, and always before a major update or mod installation.
Can I back up while the server is running? It’s not recommended—you might get a corrupted save. The server writes to the file constantly.
Where are the automatic backups stored? In the same server folder, in a subfolder called backup. They are named with a timestamp.
Can I restore a backup to a different server? Yes, as long as it’s the same game version. Copy the .sav file to the new server’s SaveGames/server folder.
Do I need to back up the entire server folder? No, just the SaveGames/server folder is enough for save data. But if you want to preserve server settings, also copy ServerSettings.ini in the SaveGames folder.
How do I restore a backup? Stop the server, replace the current .sav file with your backup (rename it to the same name), and start the server again.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.