Your Rust server reads settings from two places: fields on the Startup tab, and the server.cfg file Rust loads on boot. Mixing the two up is the most common reason a setting won't stick. Here's what lives where, the server.cfg convars worth knowing, and the admin commands you'll use most.
Where server.cfg lives
Every Rust server keeps its files under an identity folder; ours is fixed to rust. The file goes at server/rust/cfg/server.cfg, next to users.cfg in the same cfg folder. A new server doesn't have one: make a plain text file named server.cfg on your computer and Upload it into that cfg folder in the File Manager.
Rust only reads server.cfg at startup. Editing it while the server is running changes nothing until you restart.
Settings that belong on the Startup tab
A lot of what looks like server.cfg territory already has a field on the Startup tab. The Startup tab builds the command Rust launches with every time it boots, and Rust reads server.cfg after those launch settings. So when server.cfg sets the same thing, the server.cfg line wins and the Startup field is quietly overridden.
That covers Server Name, Server Description, Website URL, Server Banner Image, Server Logo, Map, World Size, World Seed, Max Players, Save Interval, RCON Port, RCON Password and Rust+ App Port. Change any of these from the Startup tab and press Save, then Restart, and keep them out of server.cfg so the Startup field is the one that counts.
Changing World Seed wipes your map on the next restart. How to set your Rust wipe schedule, map and blueprint wipes covers scheduling that properly, and our wipe calendar tracks Facepunch's forced-wipe dates so you're not guessing.
Useful server.cfg convars
Once the settings above are accounted for, server.cfg is for everything else. A few worth knowing:
Restart the server after any server.cfg edit for the new values to load.
Make yourself owner or moderator
Rust admin is granted per player by Steam ID, not a shared password.
- Join your server, then open the Console tab and type
users. It lists everyone connected with their SteamID64, the 17-digit number starting with7656. - Type
ownerid <SteamID64> "YourName", for exampleownerid 76561198123456789 "TomSmith". Owners can run every admin command, including granting admin to others. - For a friend who should have admin without being able to add more admins, use
moderatorid <SteamID64> "Name"instead. - Leave the server and rejoin. The new level only applies once you reconnect.
Rust writes both straight to server/rust/cfg/users.cfg, so there's no need to run server.writecfg afterwards.
To take access away, use removeowner <SteamID64> or removemoderator <SteamID64> the same way you granted it. You can also open users.cfg in the File Manager and delete their line by hand.
Everyday admin commands
Type these into the Console tab, which acts as your server's remote console already connected:
spectate <name or SteamID64>, god and noclip act on your own character, so they only work in your own in-game console (press F1 after joining as owner or moderator). Typing them into the panel's Console tab does nothing, because the panel has no character of its own in the world.
Remote admin tools (RCON)
Your server's RCON port and password are the RCON Port and RCON Password fields on the Startup tab. Point a tool like RustAdmin, or a web-based RCON client, at them to run any command above from outside the panel. For everyday admin the panel's Console tab does the same job with nothing extra to set up. Rust server setup: connect, admin and wipes covers connecting for the first time and finding those fields.
Apply your changes
A server.cfg edit needs a Restart before it does anything, since Rust only reads the file at boot. A command typed into the Console, like decay.scale 0.5 or env.time 12, takes effect immediately but lives in memory only: it's gone at the next restart unless you also run server.writecfg to save it into server.cfg, or add the line to server.cfg yourself.
Common mistakes
- A Startup tab field seems to be ignored. server.cfg sets the same thing, and server.cfg wins. Delete that line from server.cfg (or change it there), then restart.
- server.cfg changes don't seem to apply. You edited the file while the server kept running on the old copy in memory, or forgot to restart afterwards. Restart after every edit.
- No convar for gather rates. Rust doesn't expose gather multipliers through server.cfg. They need an Oxide or Carbon plugin. How to install Oxide/uMod plugins on your Rust server covers installing the framework and a plugin.
- ownerid didn't seem to work. It did. The new admin level only applies from your next join, so reconnect.
Related guides

Pair the Rust+ App With Your Rust Server
Check your Rust+ App Port, confirm it with app.info, and pair the Rust+ phone app from inside Rust.
4 min read
Set the Message of the Day on Rust
Set the server description, greet players on spawn with Welcomer and repeat chat announcements with Advert Messages on Rust.
4 min read
Change Deep Sea Settings on Rust
Use deepsea settings in server.cfg to control when Rust's deep sea opens, what spawns there, who can enter and lag while it opens.
4 min read