Rust Cheats & Console Commands: Noclip, God Mode, Give and the F1 List
Rust cheats are admin console commands: noclip, god, inventory.give, spawn and teleport, plus the F1 player commands for FPS, binds and graphics, and the auth level each needs.
Rust console commands are typed into the F1 console, and most of them need no special rights: any player can cap FPS, change graphics, bind keys and pull up their combat log. The famous Rust "cheats" (noclip, god mode, spawning items, teleporting) are console commands too, but they only work on a server where you have admin. This guide covers the player commands that actually matter, how to make them stick between sessions, which cheat commands exist and what they need, and how to find every remaining convar yourself.
Running a server, not just playing?
The first half of this page is client-side commands you run on your own machine. The cheats section further down lists the admin-only commands people search for. If you own or moderate a server and need
ownerid, kick and ban, events or weather, the full list is in Rust Admin Commands.
Here for the cheats?
The ones people want are
noclip,god true,inventory.give rifle.ak 1,spawn bearandteleport "PlayerName". They only work for an admin on that server, and they are all in the cheats section further down, with what each one needs.
How to Open the Console
Press F1 in-game to open the developer console. It is enabled by default. If nothing happens, check that no other program has grabbed the F1 key. Type a command and press Enter.
Commands here are typed without a leading slash. A / prefix means a plugin chat command, which is a different thing entirely.
Find Any Command Yourself
Before the lists below, learn this one. find searches every convar the game has and prints each match with its current value:
| Command | What it does |
|---|---|
find <text> |
List every command and convar matching your search, with descriptions |
console.clear |
Clear the F1 console |
console.copy |
Copy the console contents to your clipboard |
find grass shows you every grass convar. find audio shows the whole audio set. This is how you check whether a command someone posted online is real: if find doesn't return it, it doesn't exist. Most of the giant "FPS command" lists circulating fail that test.
General Commands
| Command | What it does |
|---|---|
combatlog |
Show your recent combat log: who hit you, weapon, distance, HP |
seed |
Show the current map's seed |
kill |
Kill your character and return to the respawn screen |
respawn |
Respawn, which works when kill fails because your player is bugged |
gesture <name> |
Play a gesture, e.g. gesture wave, gesture thumbsup |
mutelist |
List the players you have muted |
client.disconnect |
Disconnect from the current server |
quit |
Quit Rust to desktop |
Performance and FPS
| Command | What it does |
|---|---|
fps |
Print your current frame rate to the console |
fps.limit <n> |
Cap your frame rate, e.g. fps.limit 144. Use -1 for unlimited |
gc.buffer <mb> |
Garbage-collector buffer. Raise to 2048–4096 to reduce stutter on high-RAM machines |
gc.collect |
Force a garbage collection now, clearing a momentary hitch |
mesh.streaming true |
Stream meshes to smooth in-world loading |
netgraph.enabled true |
Network overlay showing entity traffic |
The perf overlay
perf is the built-in performance readout, and each level adds to the one before it:
| Level | Shows |
|---|---|
perf 0 |
Off |
perf 1 |
FPS |
perf 2 |
+ frame latency |
perf 3 |
+ RAM usage |
perf 4 |
+ ping |
perf 5 |
+ invokes |
perf 6 |
+ tasks |
perf 1 is what you want day to day. perf 4 is the one to use when you are trying to work out whether a problem is your machine or the server.
Most "FPS commands" you'll find online are placebo
The giant FPS-command lists floating around are largely outdated or invented. Many reference convars that no longer exist, and the rest just duplicate Options → Graphics. Run
findon any command you are unsure about; if it returns nothing, the command isn't real. The genuine console wins arefps.limit, raisinggc.buffer, and turning off motion blur and depth of field.
Low FPS might not be your PC
If your frame rate is fine on other servers but poor on one in particular, that is a server-side problem, not a client one. Entity counts, plugin load and tick rate all show up as stutter for players. Rust Server Lag & Performance covers it from the server owner's side. If the stutter ends in a "packet flooding" kick, Rust packet flooding kicks explains the cause and the server-side fix.
Graphics and Field of View
| Command | What it does |
|---|---|
graphics.fov <60-90> |
Set your field of view. 90 is the maximum |
graphics.quality <0-6> |
Overall graphics quality level |
graphics.shadowdistance <n> |
Shadow render distance; 0 disables shadows |
graphics.drawdistance <n> |
World draw distance |
graphics.vm_fov_scale false |
Stop your weapon model scaling with FOV |
graphics.vm_horizontal_flip true |
Move the weapon model to your left hand |
grass.on false |
Disable grass rendering entirely |
grass.displacement false |
Disable grass displacement |
effects.motionblur false |
Disable motion blur |
effects.dof false |
Disable depth of field |
gfx.ssao false |
Disable ambient occlusion |
gfx.bloom false |
Disable bloom |
gfx.grain false |
Disable film grain |
Shadows, water quality, anti-aliasing and particle quality are usually better changed in Options → Graphics. The sliders map to the same settings and you can see what you are doing. The console is for the ones the menu doesn't expose, like vm_fov_scale and vm_horizontal_flip.
Making Settings Stick
Convars you set in the F1 console apply to the current session only. To keep them:
writecfg That writes your current settings and keybinds to your client config files, so they survive a restart. Run it after any change you want to keep. It is the step people forget when their binds vanish overnight. (server.writecfg is a different, admin-only command that saves server settings.)
Keybinds
Bind any command to a key with bind <key> "<command>", then run writecfg to save. Binds live client-side in your keys.cfg.
| Bind | What it does |
|---|---|
bind q forward;sprint |
Auto-run; tap any movement key to stop |
bind t "+voice" |
Push-to-talk on T |
bind f lighttoggle |
Toggle flashlight or weapon light |
bind p combatlog |
Open the combat log instantly |
bind <key> gestures |
Open the gesture wheel |
unbind <key> |
Remove a single bind |
Some binds will get you banned
Macro-style movement binds, such as bunny-hop and auto-jump combinations, are treated as cheating on many servers. Auto-run, push-to-talk and light toggles are universally accepted.
Chat and Audio
| Command | What it does |
|---|---|
chat.say "message" |
Send a message to global chat |
chat.teamsay "message" |
Send a message to team chat only |
audio.master <0-1> |
Master volume |
audio.voices <0-1> |
Player voice volume |
audio.game <0-1> |
Game and effects volume |
audio.musicvolume <0-1> |
Music volume |
voice.loopback true |
Hear your own mic to test it |
Streamer Mode
| Command | What it does |
|---|---|
streamermode true |
Hide player names and server information |
streamermode false |
Turn it back off |
Streamer mode hides identifying details that let viewers work out which server you are on and stream-snipe you. Worth binding to a key if you broadcast regularly.
Combat Log
The combat log is the fastest way to answer "how did I just die?" Type combatlog in the F1 console to see your recent damage events: attacker, weapon, ammo, hit area, distance, and your HP before and after each hit.
It is the first thing to check when a death looks suspicious. A player who killed you in three shots at 40 metres with a bolt-action is having a normal day; the log is how you tell that apart from something that warrants a report. Admins can read another player's log with combatlog <SteamID64>.
Connect by IP
| Command | What it does |
|---|---|
client.connect <ip:port> |
Join a server directly, e.g. client.connect 203.0.113.10:28015 |
client.disconnect |
Leave the current server |
Useful when a server is not showing in the browser, or to jump straight back into your own server after a restart. Rust's default game port is 28015.
Rust Cheats: Noclip, God Mode, Spawn and Teleport
Rust has no cheat codes in the single-player sense. What people call "Rust cheats" are ordinary console commands that the server only accepts from an admin. Type them on a public server as a normal player and nothing happens. On a server where you have admin, they work instantly.
What you need before any of these work
Rust has two admin levels, and every cheat below works at either of them:
| Auth level | Granted with | Can use the cheats below? |
|---|---|---|
| 0 | (every normal player) | No |
| 1 (moderator) | moderatorid <SteamID64> "name" |
Yes |
| 2 (owner) | ownerid <SteamID64> "name" |
Yes, and can also grant ownerid to others |
The server code grants these commands to any connection with an auth level above 0, so a moderator can fly, spawn items and teleport just like the owner. That matters if you hand out moderator to staff: they get the cheats too. Only granting owner status (and seeing player IP addresses in status) is reserved for level 2.
To make yourself admin on your own server, run ownerid from the server console. Rust Admin Commands walks through it, including where users.cfg lives on a GSK server.
The cheat commands
| Command | What it does | Needs |
|---|---|---|
noclip |
Toggle fly mode through walls and terrain. Run again to land | Admin (level 1 or 2) |
god true / god false |
No damage, no hunger or thirst loss | Admin (level 1 or 2) |
debugcamera |
Detach into a free-fly camera; run again to return | Admin (level 1 or 2) |
inventory.give <item> <amount> |
Give yourself an item, e.g. inventory.give rifle.ak 1 |
Admin (level 1 or 2) |
inventory.giveto "<player>" <item> <amount> |
Give an item to another player | Admin (level 1 or 2) |
inventory.giveall <item> <amount> |
Give an item to everyone online | Admin (level 1 or 2) |
inventory.givebp <item> |
Give yourself the blueprint instead of the item | Admin (level 1 or 2) |
spawnitem <item> |
Drop an item where you are looking | Admin (level 1 or 2) |
spawn <entity> |
Spawn an entity or animal where you are looking, e.g. spawn bear |
Admin (level 1 or 2) |
teleport "<player>" |
Teleport to a player | Admin (level 1 or 2) |
teleport2me "<player>" |
Bring a player to you | Admin (level 1 or 2) |
teleport2marker |
Teleport to the marker on your map | Admin (level 1 or 2) |
teleportpos "x, y, z" |
Teleport to coordinates | Admin (level 1 or 2) |
teleportany <entity> |
Teleport to an entity of that type somewhere on the map | Admin (level 1 or 2) |
heal <amount> / refillvitals |
Heal, or refill health, hunger and thirst (full names debug.heal and debug.refillvitals) |
Admin (level 1 or 2) |
admintime <0-24> |
Change the time of day for you only; -1 resets |
Admin (level 1 or 2) |
env.time <0-24> |
Change the time of day for the whole server | Admin (level 1 or 2) |
ent kill |
Destroy the entity you are looking at | Admin (level 1 or 2) |
kill |
Kill your own character | Anyone |
Short names such as give usually work because Rust registers a short alias for most commands, but the full inventory.give form is never ambiguous. Item short names (rifle.ak, wood, scrap, metal.fragments) and the rest of the spawning, entity and event commands are in Rust Admin Commands.
Why noclip doesn't trip the anti-hack
Rust's server-side anti-hack ignores admins who are using admin cheats while
antihack.admincheatistrue, which is the default. Set it tofalseif you want admins held to the same movement checks as everyone else.
Building without limits: creative mode
If what you actually want is free building for a test or build server, Rust has a built-in creative mode rather than a cheat command. creative.allusers true applies it to everyone, creative.freebuild true makes building blocks free, and creative.togglecreativemodeuser "<player>" true enables it for one player. Run these from the server console or RCON.
Cheat software is a different thing
If you searched "Rust cheats" looking for aimbots or ESP: those are third-party hacks, not console commands. Rust servers run Easy Anti-Cheat, and using hacks on someone else's server is how accounts get banned. The console cheats above are legitimate on a server you run, because you are the admin.
Console Commands vs Admin Commands
These get mixed up constantly, so here is the line:
| Console commands (most of this page) | Admin commands and cheats | |
|---|---|---|
| Who can use them | Any player | Server owner or moderator (auth level 1 or 2) |
| Where they run | The F1 console, on your own client | F1 console or RCON, on a server you control |
| What they change | Only your game | The server, or your player on it |
| Examples | fps.limit, graphics.fov, bind, combatlog |
noclip, god, inventory.give, teleport, kick, ban |
If you are trying to grant admin, moderate players, spawn items or run events on a server you own, that is the other guide: Rust Admin Commands.
FAQ
How do I open the console in Rust?
Press F1 in-game. It is enabled by default in current builds.
What are the cheats in Rust?
The main ones are noclip (fly), god true (invincibility), inventory.give <item> <amount> (items), spawn <entity> and the teleport family. They are admin commands, so they only work on a server where you are a moderator or owner.
How do I enable cheats in Rust?
There is no cheat toggle. Get admin on the server with ownerid <SteamID64> from the server console, reconnect if the commands are still refused, then type the commands in F1. See Rust Admin Commands for the full steps.
Do moderators get noclip and god mode?
Yes. Every cheat on this page works at auth level 1 (moderatorid) as well as level 2 (ownerid). Only give moderator to people you would trust with item spawning.
How do I change the time of day in Rust?
admintime 12 changes it for you only and admintime -1 puts you back on server time. env.time 12 changes it for everyone on the server. Both need admin.
How do I give myself items in Rust?
inventory.give <item> <amount>, for example inventory.give wood 1000, on a server where you are admin. Use the item's short name, not its display name; find and the Rust Admin Commands list help you find them.
How do I see my FPS in Rust?
Type perf 1 for a live overlay, or fps to print the current figure once. perf 0 turns the overlay off.
How do I find every Rust console command?
Type find followed by a keyword: find graphics, find audio, find grass. It lists every matching convar with its description and current value, which is also how you check whether a command you saw online actually exists.
How do I change my FOV in Rust?
graphics.fov 90, which is the maximum. It can also be set in Options → Screen.
Do Rust FPS commands actually work?
A few do. fps.limit, raising gc.buffer to cut stutter, and disabling motion blur and depth of field are real. Most long "FPS command" lists are placebo. Run find on anything you're unsure about.
Why do my console settings reset when I restart?
Convars set in the console only last for that session. Run writecfg to write them to your config files so they persist.
How do I bind auto-run in Rust?
bind q forward;sprint, then writecfg to save it. Press any movement key to stop running.
How do I turn on streamer mode?
streamermode true hides player names and server info; streamermode false turns it off.
Related Rust Guides
- Rust Admin Commands: the server-owner side, covering ownerid, moderation, spawning and events.
- Getting started with your Rust server: setup, connecting and your first admin.
- Rust Server Lag & Performance: when the stutter is the server's fault, not yours.
- Rust Recycle Chart: what each component gives at 40%, 50%, 60% and 75% recyclers.
- Rust Wipe Guide: force wipe schedule and what a wipe resets.
- Rust Raid Chart: C4, rockets and satchels for every wall and door, with sulfur costs.
Made with 💜 by GameServerKings

Playing with friends?
Your own Rust server is a world that stays up when you log off — nobody has to host it from their own PC, and it's there whenever your group wants to play.
From $13.00 /month