How to Find and Edit the server.cfg File on a Rust Server (2026 Guide)

On most Rust server installations, the configuration file is server/<identity>/cfg/server.cfg. Open it with your host’s file manager or through SFTP, edit it as plain text with one Rust console command per line and no leading plus sign, save it, then restart the server. Do not edit serverauto.cfg: the file is intended to return to defaults and can undo your changes.

Godlike.Host offers hosted Rust servers with its own game panel, SFTP access and free DDoS protection, if you would rather not host it yourself.

Understand the Rust server.cfg path

The usual location is a relative path inside the server’s data directory:

#	Preview	Product	Price
1		Rust Key Cards, Rust Red Key Card, Cobalt Restricted Access Cards, Rust Gift For Gamers, Blue Key...	$25.00	Buy on Amazon
2		Rust Video Game Notebook	$15.00	Buy on Amazon
3		Rust Game Props Large Furnace (S)	$14.99	Buy on Amazon

As an Amazon Associate I earn from qualifying purchases.

server/<identity>/cfg/server.cfg

Here, <identity> is the name of the particular Rust server instance. A host may use an identity such as rust, but the folder name is not universal. If you run more than one instance, each identity has its own configuration directory and its own server.cfg. Editing the file under the wrong identity changes a different server, not the one your players join.

An absolute path shown by one hosting setup is /home/container/server/rust/cfg/server.cfg. Treat that as an example of how a host may expand the standard path, not as a universal Linux location. Control panels can place the container elsewhere, and self-managed installations may use a different root directory.

#1 Best Overall

Rust Key Cards, Rust Red Key Card, Cobalt Restricted Access Cards, Rust Gift For Gamers, Blue Key Card, Green Key Card (ALL THREE)

• Inspired by the Rust Video Game – These cards replicate the iconic keycards found in Rust (Red, Blue, Green).
• High Quality PVC Plastic – Printed on both sides, durable and water-resistant. Not a sticker.
• Great Rust Gift Idea – Perfect for fans of Rust, whether for cosplay, loot-themed gifts, or collection.
• Wallet-Size Replica – Standard 3.375x2.125 inches, 30 mil thick—fits in any wallet.
• NOT a sticker*

$25.00

Buy on Amazon

What the folders mean

• server is the directory that holds Rust server identities and their data.
• identity selects one server instance’s world and configuration set.
• cfg is the configuration subdirectory for that identity.
• server.cfg is the plain-text file that stores commands you want loaded for that instance.

If you cannot see the expected path, do not create a second server tree immediately. First confirm the identity name and the root directory displayed by your provider’s file browser. Folder names and absolute paths vary by host.

Choose an access method

You normally have two ways to reach the file. Use the panel editor when your provider exposes the server files directly; use SFTP when you need to download a copy, edit locally or manage a self-hosted installation.

Host panel or file manager

1. Stop the Rust server if your host recommends stopping it before file edits. If the panel offers a restart-only workflow, at minimum ensure the file is saved before the restart begins.
2. Open the server’s Files, File Manager or similarly named section. A documented panel workflow uses the Files tab.
3. Open server, then the folder for the correct identity, then cfg.
4. Select server.cfg. Use the panel’s edit action rather than opening a similarly named automatic configuration file.
5. Make the changes, save the file and use the panel’s normal restart control so Rust reads the saved contents.

Panel editors are convenient because they preserve the server’s location and usually save directly into the active container. They can also hide the absolute path, so verify the identity folder before editing if the account contains multiple servers.

SFTP

1. Obtain the SFTP host, port, username, password or key and starting directory from your provider. These connection details are host-specific.
2. Connect with an SFTP client and locate the server data directory.
3. Browse to server/<identity>/cfg, selecting the identity that belongs to the server you intend to change.
4. Download server.cfg before editing if you want a rollback copy. One provider documents editing in its panel or downloading the file over SFTP.
5. Edit the downloaded file as plain text, upload it back to the same cfg directory and allow the client to replace the old copy.
6. Restart the Rust server from the host panel, service manager or your own server-management procedure.

SFTP is useful when the panel has no editor or when you need a local backup. It also makes it easier to notice whether you are working in the wrong identity directory, because the complete folder tree is visible.

If server.cfg does not exist

Some Rust installations do not create server.cfg during the first installation. An empty cfg folder therefore does not necessarily indicate a broken server.

1. Confirm that you are inside server/<identity>/cfg for the active identity.
2. Create a new plain-text file named exactly server.cfg.
3. Check the filename after saving. On Windows, Notepad can silently append .txt, creating server.cfg.txt, which Rust will not treat as the intended file.
4. When using Notepad’s Save As dialog, set Save as type to All Files and enter server.cfg as the filename.
5. Upload or save the file in the cfg folder, add your commands and restart the server.

If your panel automatically creates a file with a different name, do not assume it is interchangeable with server.cfg. Check the displayed filename and the directory before adding settings.

Edit the file in Rust’s expected format

Treat server.cfg as a command list, not as an INI, JSON or YAML document. Put one Rust console command on each line. Do not prefix commands with a plus sign. Preserve the command spelling and value syntax expected by the setting you are changing.

Rank #2

Rust Video Game Notebook

$15.00

Buy on Amazon

• One command per line keeps individual settings separable and makes a bad line easier to find.
• Do not add a leading +; the plus-prefixed form belongs to some startup-argument conventions, not the documented file format described for server.cfg.
• Save as plain text. Avoid word-processor formats that add styling or hidden document data.
• Keep a copy of the last known-good file before making a large batch of edits.
• After saving, reopen the file in the panel or SFTP client to confirm that the new contents are actually present in the server directory.

The file only helps if the command itself is valid for your Rust server version and applies to the instance you started. A correctly located file can still appear ineffective when a command is misspelled, placed on the wrong line or superseded by another configuration source.

Restart the server to apply file changes

Changes written to server.cfg do not affect a server that is already running. Use this order:

1. Save the file and wait for the panel or SFTP client to report that the write completed.
2. Stop the server if it is running, following your host’s normal shutdown control.
3. Start it again, or use a panel restart that performs a complete stop-and-start cycle.
4. Wait for the server to finish starting before checking the setting in-game or through the console.

A quick editor save followed by continued play on the same process is not a valid test. The running process loaded its configuration earlier, so it will continue using the old in-memory values until the restart.

Know which configuration source wins

Host documentation is not consistent about precedence. One guide states that values in server.cfg override startup options; another warns that values entered on a panel’s Settings page override manual edits to the file. There is no single precedence rule you can safely apply to every host panel.

When a value does not stick, identify every place that may set it:

• the panel’s structured Settings page;
• the server’s startup or launch options;
• server.cfg under the active identity;
• commands entered at the server console or through RCON; and
• automatic configuration files managed by the host.

Change the setting in the source your provider documents as authoritative, then restart and verify the effective value. If the panel regenerates launch options from its Settings page, a later restart may put those values back even though your manual file edit remains on disk. Record which source you changed so you can undo it without creating conflicting entries elsewhere.

Live console changes and writecfg

One host guide suggests that console or RCON commands can change values immediately in the running process and that a writecfg command can save console changes back to a configuration file. That workflow is not established consistently across hosts, server builds or panel setups.

Rank #3

Rust Game Props Large Furnace (S)

• Acrylic Painting Pla Plastic

$14.99

Buy on Amazon

Use it only when your own server documentation confirms the behavior. Before relying on it for a production server, test on a disposable instance:

1. Issue the command through the console or RCON interface.
2. Confirm that the running server reflects the change.
3. Use the documented save command, if supported.
4. Inspect the resulting file in the correct identity’s cfg folder.
5. Restart and verify that the value survives a full reload.

If any step fails, make the change directly in server.cfg and use the normal restart process instead of assuming that an in-memory change was persisted.

Never edit serverauto.cfg for permanent settings

serverauto.cfg is not the file to customize for this task. Physgun’s guidance warns that editing it causes it to reset to default values. Put deliberate, persistent settings in server.cfg and leave the automatic file under the host’s management.

If you already changed serverauto.cfg and the values disappeared, restore the intended commands in server.cfg, save them in the active identity directory and restart. Do not use the automatic file as a workaround for a setting that is being overridden elsewhere.

Panel editor or SFTP: which should you use?

Troubleshoot a server.cfg change that is not working

The file cannot be found

• Check that you opened server, the active identity and then cfg.
• Search for a hidden .txt extension, especially if the file was created in Windows Notepad.
• Confirm that the panel is showing the server instance players actually use.
• If the file is absent, create server.cfg in that exact directory rather than placing it beside the identity folder.

The file saves but nothing changes

• Restart the server; a running process does not reload the file after an editor save.
• Check for a second server identity with a similarly named configuration.
• Look at the panel’s Settings page and startup options for a competing value.
• Verify that each line is a valid command and that no leading plus sign was added.

The setting works once and then reverts

• Determine whether the panel rewrites startup settings during a restart.
• Check whether you edited serverauto.cfg instead of server.cfg.
• Move the intended value to the configuration source your host identifies as authoritative.
• Restart again and inspect the effective value after the server has completed startup.

The server fails to start after an edit

• Stop the server and restore the last known-good copy of server.cfg.
• Remove the most recent line or batch of lines, then start the server to isolate the offending entry.
• Re-add changes one at a time, restarting between tests so the failing command is identifiable.
• If the panel has a structured Settings page, check whether the same value is being written there with a conflicting format.

A console change survives until restart but not afterward

That pattern indicates an in-memory change rather than a confirmed file change. Use the documented persistence procedure for your host, inspect the saved file, and perform a full restart test before treating the setting as permanent.

A safe editing checklist

• Identify the exact server identity used by the running instance.
• Open server/<identity>/cfg/server.cfg, or confirm the host’s equivalent absolute path.
• Download a backup before substantial edits.
• Keep the file as plain text.
• Use one command per line and no leading plus sign.
• Save to the same identity’s cfg directory.
• Do not edit serverauto.cfg.
• Restart the server after saving.
• Check panel Settings and startup options if the value is ignored or later overwritten.
• Test live console persistence separately instead of assuming that an RCON change was written to disk.

Following that sequence separates the common failure points: wrong identity, wrong filename, invalid line format, unsaved upload, a server that was never restarted and a host-level setting that takes precedence.

Quick Recap

Bestseller No. 1

Rust Key Cards, Rust Red Key Card, Cobalt Restricted Access Cards, Rust Gift For Gamers, Blue Key Card, Green Key Card (ALL THREE)

Wallet-Size Replica – Standard 3.375x2.125 inches, 30 mil thick—fits in any wallet.; NOT a sticker*

$25.00

Bestseller No. 2

Rust Video Game Notebook

$15.00

Bestseller No. 3

Rust Game Props Large Furnace (S)

Acrylic Painting Pla Plastic

$14.99

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.