Home / Guides / Rust / Create a server.cfg
🔧 Rust · Server Setup

How to Create a server.cfg for Rust

Rust doesn't auto-generate a config file on first install — which trips up every new admin. This is the step-by-step setup: where the file goes, what to put in it, how to save it, and the one console command (writecfg) that lets you tweak settings live and keep them.

⚙️
Or skip the manual setup entirely
Build a working server.cfg with checkboxes and sliders. Pick your options, copy the output, paste into the file. No typos, no missing quotes.
Open Generator →
📂

Where does server.cfg go?

Rust looks for the file at one specific path: 

/server/<identity>/cfg/server.cfg

Replace <identity> with whatever you set as server.identity in your launch script (or with the default if you never set one). If the cfg folder doesn't exist, create it manually — Rust won't create it for you.

Examples:

📝

Step by step

1
Open a plain-text editor
Notepad on Windows, TextEdit on Mac, nano or vim on Linux. Anything that produces plain text. Don't use Word — it'll silently inject formatting that breaks the parser.
2
Paste your settings
Use the example below as a starting point. Modify server.hostname, rcon.password, server.identity, and anything else you want changed. Full setting reference is on the Common Rust Server Settings Guide.
3
Save as server.cfg in the right folder
Save the file at /server/<identity>/cfg/server.cfg. On Windows, watch out for Notepad sneakily adding .txt — set "Save as type" to "All Files" and confirm the filename is exactly server.cfg, not server.cfg.txt. You can verify in Explorer (after enabling visible file extensions) that it ends in .cfg.
4
Restart the server
Stop the server and start it again. Rust loads server.cfg at startup — settings won't apply until the next launch. Live edits during a running server don't reload automatically.
📄

Starter server.cfg

Working starter config. Replace identifiers and passwords with your own, then drop into /server/<identity>/cfg/server.cfg. 

// GamesOMG starter Rust server.cfg
server.hostname      "GamesOMG Vanilla+ QOL"
server.description   "Weekly wipe | PvE friendly | Discord.gg/example"
server.url           "https://gamesomg.com/rust"
server.headerimage   "https://example.com/banner.png"
server.identity      "rust_main"
server.tags          "vanilla,monthly,pve,US"
server.maxplayers    75
server.worldsize     3500
server.seed          98765
server.secure        true
server.saveinterval  300
server.tickrate      30
rcon.password        "CHANGE_ME_TO_SOMETHING_STRONG"
rcon.port            28017
rcon.web             1
decay.scale          0.75
decay.upkeep_period_minutes 1440
ownerid              76561198042260039  // replace with YOUR SteamID64

For the full setting list — decay brackets, NPC tuning, AI behavior, performance tweaks — see the Common Rust Server Settings Guide.

💾

The writecfg trick (test live, save later)

You don't have to edit and restart every time you want to change something. Rust has a workflow most new admins miss:

  1. Type the command live in the server console: server.maxplayers 60
  2. The change takes effect immediately, in memory
  3. If you like the result, run server.writecfg — Rust dumps the current in-memory settings to disk, overwriting server.cfg
  4. Next restart, the change persists. If you skip writecfg, the change vanishes
Why this matters: Test settings without committing — try a tickrate bump, fool around with decay rates, see how it feels. If it doesn't work, restart and you're back to the saved config. If it does, writecfg locks it in. The single most useful workflow tip for active Rust admins.

The related command is server.readcfg — it reloads server.cfg from disk without restarting. Useful if you edited the file in a text editor and want the server to pick up the changes without a full restart.

💡

Tips for new Rust admins

⚠️

Common server.cfg mistakes

The failure modes new Rust admins hit, in roughly the order they hit them.

1. Putting the file in the wrong spot
server.cfg must live in /server/<identity>/cfg/. No cfg folder? Create one. Drop it anywhere else and Rust silently ignores it.
2. Forgetting to restart
Editing a live server.cfg on disk won't change running settings. Save, restart, then Rust reads the new values. (For live changes that persist, use the console + writecfg workflow.)
3. Command-line overrides
Anything in your startup command line takes priority over server.cfg. If your server.hostname keeps reverting, check the launch script — odds are it's setting the hostname there and overriding your cfg.
4. Missing quotes around text values
String settings (hostname, description, password, url, headerimage) need quotes. Without them, your server name breaks or truncates at the first space.
server.hostname GamesOMG Server ❌
server.hostname "GamesOMG Server" ✅
5. Wrong SteamID format for ownerid/moderatorid
Use the full SteamID64 (17 digits). Not your username. Not SteamID3. Wrong format = no admin powers, even though the command "looks fine."
6. Port collisions
Game port, query port, and RCON port must all be unique. Overlap = connection failures and lots of head-scratching. Common defaults: game port 28015, RCON 28017 — keep every port distinct from the others (including the Steam query port).
7. Leaving the RCON password blank or default
Bots scan for blank or default RCON passwords. If yours is set to password123, assume you're already compromised. Use a strong unique password.
8. Forgetting to writecfg after console changes
Console changes apply in-memory but vanish on restart unless you run server.writecfg. If you added admins via console and they're gone after restart — this is why.
9. Editing the wrong identity
Running multiple Rust servers? Each has its own identity folder, its own cfg. Spend an hour editing the wrong one and watching nothing change — at least once. It's a rite of passage.
10. Copy-pasting random configs from old forum threads
A lot of 5-year-old Rust cfgs from forums and YouTube descriptions reference settings that no longer exist or have been renamed. Always cross-check against the current settings guide or the Rust wiki.

Common questions

Why doesn't Rust create a server.cfg by default?
Rust expects admins to customize settings from scratch rather than ship a one-size-fits-all preset. The trade-off is the awkward first-time setup experience this guide walks through — most other games create a default config on first launch.
What settings should I add first?
Start with the essentials: server.hostname, server.description, rcon.password (strong!), server.identity, server.maxplayers, and server.worldsize. Once those are dialed in, move to gameplay tuning — decay, NPCs, performance. Full reference: Common Rust Server Settings Guide.
Can I edit server.cfg while the server is running?
You can edit the file on disk, but Rust won't reload it live — you need a restart for changes to apply. The alternative: run commands via the in-game/RCON console (applies immediately in memory), then use server.writecfg to commit them to disk.
What does server.writecfg do?
It dumps your current in-memory server settings to disk, overwriting server.cfg with the live values (including owner/moderator IDs you added during the session). Without writecfg, console changes vanish on restart.
What does server.readcfg do?
Reloads server.cfg from disk without a full server restart. Useful if you edited the file in a text editor and want the server to pick up the changes immediately. Note: some settings still require a true restart to apply (decay-related ones especially).
Where do I find my SteamID64?
Use steamid.io or steamidfinder.com — paste your Steam profile URL or username, get the 17-digit SteamID64. That's the number you use in ownerid, moderatorid, banid, and whitelistid.
What's the difference between server.cfg and the startup command line?
Command-line values are loaded first and override server.cfg. Use the cfg for permanent settings; use command-line only for things that change between launches (server identity, port assignments).
Can I load mods or plugins from server.cfg?
No — Oxide/uMod plugins load through their own config system, separately from server.cfg. Plugins live in oxide/plugins/ with configs in oxide/config/. The server.cfg only handles base Rust commands.