Best Rust Settings for FPS & PvP

The best Rust settings are the ones that delete everything between you and the player you're trying to shoot. Shadows off, water quality at 0, grass displacement off, anti-aliasing off or FXAA — that's the core of it, and it's most of your FPS back. Then set your FOV to 90, drop your sensitivity until a 180 takes a real arm sweep, and stop touching it.

Rust is not a well-optimised game and no settings config fixes that. What a good config does is stop your frames from collapsing at the exact moment they matter — the fight at Outpost, the roof camp, the moment six people push your door. A steady 90 FPS beats a spiky 140 every single time, because the spike always lands when you're being shot at.

Below: the settings that actually move the needle, the ones that only cost you visibility, launch options, and what to do if your PC is genuinely struggling.

Best Rust Settings for FPS

These are the heavy hitters. If you change nothing else, change these four.

Shadow Quality → 0 and Shadow Cascades → No Cascades. Shadows are the single most expensive thing Rust renders, and turning them down is the biggest gain available to you. You lose almost nothing competitively — Rust's shadows aren't detailed enough to spot people by, and anyone who tells you they track players by shadow is telling you a story.

Water Quality → 0 and Water Reflections → 0. Costs you nothing unless you spend your life on the coast, and if you do play near water or run rivers, this is where a chunk of your frames are going. Water reflections in particular are pure GPU spend for a prettier ocean you are not looking at.

Grass Displacement → Off. This one has a real tradeoff, so read it properly. Grass displacement is the effect where grass bends as players walk through it. Turning it off gains you frames. It also means you can no longer see the trail someone leaves running through a field. Most players take the frames. If you're a dedicated bush camper, that's your call to make.

Anti-aliasing → Off or FXAA. FXAA is cheap and cleans up the worst of the shimmer. TSSAA looks better and costs more. Off is fastest and looks rough at distance. FXAA is the sane middle.

Everything else — Parallax Mapping to 0, Max Shadow Lights down, motion blur off, depth of field off — is smaller individually but adds up, and none of it costs you anything you'd miss. The FPS calculator has the full recommended table and will build your launch string at the same time.

Best Rust Settings for PvP

FPS settings and PvP settings are mostly the same settings, which is the happy accident at the centre of Rust's config. Low graphics settings don't just run faster — they render a cleaner, flatter, less cluttered world, and a player standing in it is easier to see. There's no visual-fidelity-versus-competitive tradeoff to agonise over. Ugly wins.

FOV → 90. Rust's field of view slider goes to 90 and you should put it there. A wider FOV means more of the world on screen, which means you see the person flanking you a fraction of a second earlier. The cost is that distant players look slightly smaller. That trade is worth taking — in Rust you die to the person you didn't see far more often than the person you saw and missed.

Sensitivity. The short version: 800 DPI, in-game around 0.3, and don't change it again for at least a couple of wipes. Low sensitivity spreads recoil correction across more mouse movement, and more movement means more precision, which is the whole reason good players are arm aimers on big mousepads. The long version — ADS multipliers, scope sens, the AK pattern — is in the aim and sensitivity guide, which covers it properly.

Draw distance and object quality. This is the one place where cranking a setting up helps you. If your rig has room, push object draw distance out. Rendering a player at 200 metres who'd otherwise be culled is a real advantage, especially if you're the one holding a bolt on a hill. If your rig doesn't have room, don't — a slideshow at long range helps nobody.

Contrast, brightness, gamma. Nudge brightness up a little if your nights are unplayable. Don't go hunting for a magic gamma value that makes night look like day; Rust's night is dark on purpose, and the real answer to night is a lit base and a decent monitor, not a config trick.

Launch Options

Launch options go in Steam: right-click Rust → Properties → General → Launch Options. Paste the string, restart Rust.

The ones worth having are -high (gives Rust higher CPU priority), -USEALLAVAILABLECORES, and -gc.buffer 2048 (a bigger garbage-collection buffer, which is aimed squarely at Rust's stutter rather than its average frame rate). Beyond that there are flags that disable specific effects at launch — gibs, subsurface scattering — which help most on weaker GPUs.

Rather than copy a string off a forum post from three wipes ago, use the FPS calculator — you tick what you want and it builds the string, so you're not pasting flags you don't understand into a game that will silently ignore the broken ones.

None of this is bannable. Launch options and console commands are built into Rust by Facepunch. You are not modifying the game, you're using settings it ships with.

Console Commands Worth Knowing

Press F1 for the console. Two commands earn their place in your muscle memory:

fps.limit 0 uncaps your frame rate. Or set it to a number — capping slightly below what your machine can actually do is a legitimate way to buy frame consistency at the cost of peak frames, which is usually the better deal.

gc.collect forces garbage collection. When Rust starts hitching after a couple of hours, this is the thing that clears it. It causes a brief freeze and then things are smooth again. It's a patch, not a cure, but it's a patch that works.

The full list is on the FPS commands page.

Low-End PC Settings

If you're below Rust's system requirements, understand what you're fighting. Rust wants 16 GB of RAM and an SSD, and the two things that most often make it unplayable on a weaker machine aren't your graphics card at all — they're RAM and storage.

Rust is a memory-hungry game. If you're on 8 GB, you are not going to config your way out of it; the game will page to disk and stutter no matter what your shadow quality says. And if you're installed on a mechanical hard drive, your load times will be enormous and you'll hitch as the world streams in around you. An SSD and more RAM will do more for your Rust experience than any setting on this page. That's an annoying answer because it costs money, but it's the true one.

What you can do in software: graphics quality to 0, every setting above at its minimum, resolution scaled down (dropping render resolution is the biggest lever left once everything else is off), and -gc.buffer 2048 to fight the stutter. Cap your FPS somewhere your machine can actually hold rather than letting it swing wildly. Expect to be playing a genuinely ugly game — that's the deal, and plenty of good players take it deliberately.

Console Edition Settings

Rust Console Edition has its own, much shorter settings menu — you don't get the graphics config or launch options described here, because you're on fixed hardware and Double Eleven tunes it for you. FOV and sensitivity sliders are the meaningful ones, and the FOV advice carries over: push it up.

Console is a separate game with its own wipe schedule and its own patch cadence, not a port you can tweak like the PC build. The Console Edition guide covers what's actually different.

What Doesn't Help

A short list, because Rust attracts more performance folklore than almost any game:

There is no secret config file that doubles your FPS. There is no launch option Facepunch forgot to tell you about. Third-party "optimiser" programs that claim to boost Rust are, at best, doing nothing, and at worst are getting you banned or stealing your Steam session — Rust has a valuable skin inventory attached to it, which makes its players a target, and "free FPS boost" is a good lure.

Turning your resolution up doesn't help you spot players. Stretched resolutions don't work the way they do in CS. And the person on YouTube claiming a specific number of extra frames from one setting is guessing about your hardware — the gains are real, but their magnitude depends entirely on whether you're CPU- or GPU-bound, which is a question about your machine, not about Rust.