When to make a backup
- Before running a SteamCMD update.
- Before editing
config.jsonor changing world startup settings. - Before moving from a home PC to a VPS or managed host.
- Before testing large world generation or changing player limits.
- After a long session where the group made major progress.
Simple backup routine
- Tell players the server is going down for a quick backup.
- Stop the server cleanly and wait for the process to exit.
- Copy the world/save folder, config file, and any server settings into a dated folder.
- Name the folder clearly, for example
2026-05-31-before-update. - Keep at least three recent backups instead of overwriting the same one.
- Restart the server and confirm the current world still loads.
Backup schedule
| Server use | Suggested backup | Why |
|---|---|---|
| Testing with one friend | Before major changes | Low risk, low effort. |
| Weekend co-op group | Before and after each session | Protects long play sessions. |
| Always-on server | Daily plus before updates | Reduces damage from crashes or bad config edits. |
| Hosted server | Panel backups plus manual downloads | Do not depend on one backup location. |
Restore test
A backup is only useful if you know how to restore it. Test with a copy: stop the server, replace the world files with the backup copy, start the server, and confirm the world appears.
Related Romestead server guides
Back up before editing config.json, before updating with SteamCMD App ID 4763510, and before moving to a managed host or VPS.