Back Up a Space Engineers Server & Restore Worlds

This guide explains how to back up a Space Engineers dedicated server and restore worlds from those backups. You’ll learn where save files live, how to copy them safely, and how to put them back if a world gets corrupted, a mod breaks, or a rollback is needed.

What You’ll Need

• Access to the server’s file system (via the hosting provider’s file manager, FTP, or a local folder if you run the server yourself).
• If the server is running, a way to stop it or at least pause it (most dedicated servers allow a graceful shutdown from the console or control panel).
• Enough free disk space to store a copy of the save folder (worlds can be several gigabytes).
• A tool to compress the backup (optional but recommended) – built-in OS compression or a free archiver.

Step-by-Step

1. Stop the server. The safest way to back up is with the server fully stopped. Use your control panel’s stop button or the console command save followed by stop. If you cannot stop it, at least force a save with the save command and then proceed quickly – but stopping is strongly recommended to avoid a corrupted copy.
2. Locate the save folder. On a Windows dedicated server, the default path is C:\Program Files (x86)\Steam\steamapps\common\SpaceEngineers\DedicatedServer64\Content\Saves. On Linux, it’s typically ~/.config/SpaceEngineers/DedicatedServer/Saves or under the server’s install directory. If you use a hosting provider, check their file manager or documentation for the exact path.
3. Identify the world folder. Inside the Saves folder you’ll see one or more folders named after your world (e.g., MyWorld). Each contains the world data, including Sandbox.sbc, Sandbox_config.sbc, and a Backup subfolder.
4. Copy the entire world folder. Right-click the world folder and select Copy, then paste it to a safe location on your local machine or a different drive. If you’re using FTP, download the folder recursively. Do not copy only the .sbc files – the folder contains essential binary data.
5. Compress the backup (optional). To save space and keep the backup tidy, compress the copied folder into a ZIP or 7z archive. Name it with the world name and date, e.g., MyWorld_2025-04-01.zip.
6. Restart the server. If you stopped it, start it again and verify the world loads correctly.
7. To restore a world: Stop the server again. Rename the current (corrupted or unwanted) world folder to something like MyWorld_old – do not delete it yet. Then copy your backup folder (or extract the archive) into the Saves folder, ensuring the folder name matches the original (e.g., MyWorld).
8. Start the server and test. Launch the server and select the restored world from the server’s world list. If it loads without errors, you can delete the _old folder to free space.

Common Mistakes

• Backing up while the server is running. This can result in a corrupted copy because files are being written to during the copy. Always stop the server or at least force a save first.
• Copying only the .sbc files. The world folder contains more than config files – the Sandbox.sbc alone doesn’t include all entity data. Copy the whole folder.
• Restoring to the wrong folder. If the folder name doesn’t match the world name in the server config, the server won’t recognize it. Keep the original folder name.
• Not testing the backup. A backup that hasn’t been tested is not a backup. Periodically restore it to a test server or a local copy to verify it works.
• Overwriting the current world without renaming. If you copy the backup over the existing folder, you might lose the current state permanently. Always rename the old folder first.

Tips

• Automate backups. Many hosting panels and dedicated server tools offer scheduled backups. If not, use a script (e.g., a batch file or cron job) that stops the server, copies the folder, and restarts it.
• Keep multiple versions. Rotate backups – keep the last 3-5 days’ worth so you can roll back to a specific point, not just the most recent.
• Store backups off-site. If your server is on a VPS, download backups to your local machine or cloud storage. If the host goes down, you still have your worlds.
• Use the in-game backup folder. Space Engineers automatically creates a Backup subfolder inside each world folder. You can copy that too, but it’s not a substitute for a full manual backup.
• Check file integrity after restore. If the world loads but behaves oddly (missing grids, errors in log), verify the backup wasn’t taken mid-write.

Troubleshooting

• Server won’t start after restore. Check the server log (usually SpaceEngineersDedicated.log in the server folder) for errors. If it says the world is corrupt, try restoring an older backup. Also ensure the folder name matches exactly.
• World loads but players lose progress. This usually means the backup was taken before the last save. Restore a more recent backup or accept the rollback.
• Backup folder is too large to download. Use an archive and split it if needed, or use a direct server-to-server copy (e.g., from the server to a network drive).
• Permission errors when copying. On Linux, ensure the user running the server has read access to the Saves folder. On Windows, run the file manager as administrator.
• Restored world has missing mods. The backup only contains the world, not the mods. Re-subscribe to the same mods on the Steam Workshop or re-upload them to the server’s Mods folder.

Frequently Asked Questions

How often should I back up my Space Engineers server?

At least once a day if the server is active. For heavily modded or large servers, consider every few hours. Automate it to avoid forgetting.

Can I back up while the server is running?

It’s risky. If you must, use the save command first to force a write, then copy quickly. But a stopped server is the only safe way to guarantee a clean copy.

Where does Space Engineers store server saves?

On Windows dedicated servers, it’s typically ...\DedicatedServer64\Content\Saves. On Linux, it’s often ~/.config/SpaceEngineers/DedicatedServer/Saves. Hosting providers may use custom paths.

Can I restore a world from a single-player save to a server?

Yes, but you need to copy the entire save folder into the server’s Saves folder and adjust the server’s world settings. The folder structure is the same.

What if my backup is corrupted?

Try an older backup. If none work, you may need to start a new world. To prevent this, always test backups by restoring to a test server.

Does restoring a backup affect mods?

No, the backup only contains world data. You must ensure the same mods are installed on the server. The world will reference mod IDs, but the mod files themselves are not included.

Related

• Notion & n8n Regret: Why It Happens & What to Do
• 32k SUV Outsmarts Rivals With More Power and Tech?
• Power Tools Never Buy Cordless? The Truth