Rust dedicated servers require a 17-digit decimal SteamID64 for native permissions, bans, and whitelist entries in users.cfg. Steam Hex is the base-16 representation of that same ID, used primarily by external tools such as Discord bots, multi-game RCON panels, and database systems.
If you paste a Steam Hex ID into a native Rust console command, the command fails. To manage player access without errors, you must know which format your config file expects and how to convert between them.
What Format Does Rust Use in Config Files? #
Native Rust server files use decimal SteamID64 values. The server console commands ownerid, moderatorid, and ban read 17-digit decimal numbers that start with 76561198 or 76561199.
External administration tools often store player data in hexadecimal format. If your community manages both Rust and FiveM servers, your web dashboard or Discord bot might store player identifiers as a 15-character hex string starting with 1100001.
| Field | SteamID64 (Decimal) | Steam Hex (Base-16) |
|---|---|---|
| Example Value | 76561197960287930 |
1100001000056ba |
| Characters | 17 digits | 15–16 hex characters |
| Where Used | Rust users.cfg, bans.cfg, RCON console |
FiveM server.cfg, Discord bots, web databases |
| Native Rust Support | Yes (Built-in) | No (Requires plugin or tool conversion) |
As explained in our complete Steam Hex guide, both formats represent the exact same account. The difference is only the mathematical base.
How to Add Admins and Moderators in `users.cfg` #
To assign owner or moderator permissions in Rust, add the player's 17-digit SteamID64 to the server permission list. You can do this through the live server console or by editing users.cfg directly.
Method 1: Console Commands (Recommended) #
- Open your Rust server console or connected RCON tool.
- For server owners with full access, type:
TEXT
ownerid 76561197960287930 "PlayerName" "Server Owner" - For moderators with kick and ban privileges, type:
TEXT
moderatorid 76561197960287930 "PlayerName" "Staff Moderator" - Save the changes to disk immediately:
TEXT
server.writecfg
Method 2: Direct File Editing #
If your server is offline:
- Navigate to your server directory:
/server/<server_identity>/cfg/. - Open
users.cfgin a plain text editor. - Add the permission line:
INI
// users.cfg format: <role> <steamid64> "name" "reason" ownerid 76561197960287930 "AdminAlex" "Head Administrator" moderatorid 76561198000111222 "ModSarah" "Community Moderator" - Save the file. When the server boots, it loads these permissions automatically. If the server is running while you edit the file, run
server.readcfgin the console to reload.
When Do Rust Server Admins Need Steam Hex? #
Rust admins need Steam Hex when integrating their server with external management platforms.
You need Steam Hex in these scenarios:
- Discord-to-RCON verification bots: Many bots verify user identity across multiple games (such as Rust and FiveM) using a single base-16 identifier.
- Cross-game ban databases: Shared ban lists between game communities often index players by hex string to match SQL schemas.
- Third-party web panels: Custom web stores or VIP perk systems often request Steam Hex to sync with external API services.
If an external tool gives you a player's hex ID (1100001000056ba), paste it into our SteamID Converter to retrieve the decimal SteamID64 before using native Rust console commands.
Common Mistakes and Troubleshooting #
Server administrators frequently encounter these errors when configuring Rust permissions:
- Missing
server.writecfg: When you runowneridin the console, Rust updates server memory. If the server crashes or restarts before you typeserver.writecfg, all changes are lost. - Adding the
steam:prefix inusers.cfg: FiveM requiressteam:1100001..., but Rust rejects prefixes. Do not typeownerid steam:7656119.... Use the raw numbers only. - Pasting Steam Hex into native console commands: If you run
ownerid 1100001000056ba, Rust outputs an invalid SteamID error. Convert the hex string to decimal first. - Using legacy SteamID2: The old format
STEAM_0:0:11101is not supported in modern Rust commands. Always use the 17-digit SteamID64.
Frequently Asked Questions #
Does vanilla Rust accept Steam Hex in users.cfg? #
No. Vanilla Rust server commands and users.cfg accept only the 17-digit decimal SteamID64 format. If you enter a hexadecimal ID, the server rejects the command.
Where is users.cfg located on a Rust dedicated server? #
The file is located at /server/<server_identity>/cfg/users.cfg in your dedicated server root directory.
Why did my admin permissions disappear after restarting my Rust server? #
You must run the console command server.writecfg after adding an admin. If you do not run this command, changes remain in RAM and are lost on restart.
Can I add an admin to users.cfg while the player is offline? #
Yes. Add their 17-digit SteamID64 directly to users.cfg, save the file, and run server.readcfg in your server console.
Need to convert between decimal SteamID64 and Steam Hex for your server setup? Use our free SteamID Converter to transform identifiers instantly. For FiveM setup instructions, see our guide on how to whitelist players by Steam Hex.
Last updated: October 2026