Rust Server Save Interval: How to Change It

This guide explains how to change how often your Rust server saves the world, which controls how much progress you can lose on a crash or restart. You’ll edit the server’s configuration file to set a custom save interval, then verify the change works.

What You’ll Need

• Access to your Rust server’s files (via FTP, a control panel like Pterodactyl, or a local folder).
• A text editor (Notepad, VS Code, or any plain text editor).
• Ability to restart your server for the change to take effect.

Step-by-Step

1. Stop the server – Always stop the server before editing config files to avoid corruption or the file being overwritten on shutdown.
2. Locate the server.cfg file – This file is usually in the server’s root directory or in a cfg subfolder. Common paths include server.cfg or cfg/server.cfg.
3. Open server.cfg in a text editor – Use a plain text editor; do not use Word or other rich-text editors that might add formatting.
4. Find or add the saveinterval setting – Search for saveinterval. If it exists, note the current value. If not, you’ll add a new line.
5. Set the value – The value is in seconds. For example, to save every 5 minutes, set saveinterval 300. For 10 minutes, use 600. A typical default is 600 (10 minutes), but some hosts use 300.
6. Save the file – Save the changes and close the editor.
7. Restart the server – Start the server again. It will read the new setting on startup.
8. Verify the setting – In the server console (or by checking the log), you should see a line like Saving complete at the interval you set. You can also type saveinterval in the console to confirm the current value.

Common Mistakes

• Setting the value in minutes instead of seconds – The setting expects seconds, so 300 is 5 minutes, not 300 minutes.
• Editing the wrong file – Some hosts use a separate file like server.cfg vs config.cfg. Make sure you’re editing the one that’s actually loaded.
• Not stopping the server first – If the server is running, it may overwrite your changes on shutdown.
• Using a value that’s too low – Saving too frequently (e.g., every 10 seconds) can cause lag and disk wear. A minimum of 60 seconds is recommended.
• Forgetting to restart – The setting only loads on server start, not on a map change or reload.

Tips

• Balance frequency – A save interval of 300–600 seconds is typical. Lower it if you have frequent crashes, but not below 60 seconds.
• Use the console command – You can also set saveinterval via the in-game console (if you have rcon) without editing the file, but it won’t persist after a restart unless you add it to server.cfg.
• Back up your config – Before making changes, copy the original server.cfg so you can revert if needed.
• Combine with world.save() – You can manually trigger a save with the world.save() command in the console, which is useful before a planned restart.

Troubleshooting

Change doesn’t seem to take effect – Check that you edited the correct file and that the server actually read it. Look for a line in the startup log that says Loaded config from server.cfg or similar. If not, the file might be in a different location.

Server crashes after changing the value – If you set an extremely low value (like 1), it might cause performance issues. Revert to a safe value (300 or 600) and test.

Cannot find server.cfg – Some hosts use a different name like server.cfg or config.cfg. Check your host’s documentation or look for any .cfg file in the server root. If you’re using a control panel, look for a “Configuration” or “Settings” section that exposes the save interval.

Save interval resets after update – Server updates may overwrite config files. Keep a backup and reapply your setting after updates.

Frequently Asked Questions

What is the default save interval for a Rust server?

The default is typically 600 seconds (10 minutes), but some hosts may use 300 seconds (5 minutes). You can check your current setting with the saveinterval console command.

Can I change the save interval without restarting the server?

Yes, you can use the console command saveinterval 300 to change it on the fly, but it will revert to the cfg value on the next restart unless you also edit the file.

What happens if I set the save interval too low?

If you set it below 60 seconds, the server may experience lag, increased disk I/O, and potential instability. It’s not recommended to go below 60 seconds.

Does the save interval affect performance?

Yes, saving writes the entire world to disk, which can cause a brief freeze or lag spike. More frequent saves mean more frequent lag spikes, so balance frequency with safety.

How do I manually trigger a save?

Use the console command world.save() to force a save immediately. This is useful before a restart or when you suspect a crash.

Where is the server.cfg file located on a typical hosting panel?

It’s usually in the server root directory, but some panels (like Pterodactyl) have a dedicated “Config” section where you can edit it without FTP access.

Related

• Best Disk Space Analyzers to Find Lost Gigabytes
• Fish a Slime Codes? What They Are & How They Work
• India Antitrust: Google Pay & Play Store Billing