Best Rust PC Settings 2026: FPS and Performance Guide

Graphics Quality → 0–2 — The master slider in Rust. Dropping from 6 to 2 can recover 30–50 FPS on mid-range hardware with minimal visibility loss.
Shadow Quality → 0, Shadow Cascades → No Cascades — Together these two settings cost up to 38 FPS at their highest settings. Set both to zero immediately.
Water Quality → 0, Water Reflections → 0 — Combined they drain up to 27 FPS. You lose no competitive advantage by disabling water reflections.
Draw Distance → 2000 — This is the sweet spot. Pushing to 2500 gives you only about 5% more visibility while costing 7+ FPS. Dropping below 1500 hurts your ability to spot threats at range.
Add launch options — Right-click Rust in Steam → Properties → Launch Options: -window-mode exclusive -nolog -effects.maxgibs -1 -graphics.waves 0

Apply these five changes before adjusting anything else. They deliver around 70% of the total FPS gain you can realistically get from optimizing settings alone.

Why Rust Tanks FPS in Raids and Crowded Servers

Rust behaves differently from most games because it is severely CPU-bound, not GPU-bound. On most modern PCs, the GPU sits at 40–60% utilization while one CPU core is pegged at 100% — you are waiting for the processor, not the graphics card. Adding a better GPU will not fix this. Upgrading to a faster CPU with higher single-core performance and larger L3 cache will [7].

The situation gets worse over time. Rust has a well-documented memory leak: after 45–60 minutes of play, the Unity engine accumulates garbage in memory that it has not yet freed. FPS gradually degrades even though you have changed nothing. The fix is manual garbage collection [3]:

Open the F1 console and type gc.collect — this forces Unity to flush accumulated memory immediately
Set a keybind so you can trigger it without interrupting gameplay: bind p gc.collect
The gc.buffer 2048 command pre-allocates a memory buffer so collections happen less frequently, reducing micro-stutter between manual flushes

During raids specifically, a second bottleneck kicks in: entity density. Every explosion spawns debris objects (gibs), and every player in the raid area is an active entity the CPU must simulate. Setting effects.maxgibs 0 via launch options removes all gib debris, which can recover 10–15 FPS during active raids. It is also why Object Quality matters more during raids than during solo exploration — reducing it from 200 to 150 lowers the per-frame CPU cost of rendering all active entities in a dense area [4].

Understanding this bottleneck changes how you approach optimization. It is not about making the game look worse — it is about reducing the number of objects the CPU has to process per frame.

Full Graphics Settings Reference

This table covers every adjustable setting in Rust’s video options with recommended values across three tiers. Use the FPS impact column to prioritize what to change first [1][2].

Setting	Budget / Potato	Competitive	High-End	FPS Impact
Graphics Quality	0–1	2–3	5–6	High
Shadow Quality	0	0–1	2	−20 FPS (max)
Shadow Cascades	No Cascades	No Cascades	Two	−18 FPS (max)
Water Quality	0	0	1	−15 FPS (max)
Water Reflections	0	0	1	−12 FPS (max)
Object Quality	100	150	200	−10 FPS (max)
Shader Level	200	400	600	−8 FPS (max)
Draw Distance	1500	2000	2500	−7 FPS (max)
Anti-Aliasing	Off	SMAA	DLSS Quality	−6 FPS (MSAA)
Ambient Occlusion	Off	Off	On	−5 FPS
Anisotropic Filtering	2	4	16	Minimal
Tree Quality	100	200	200	Low
Grass Quality	0	0	50	Low
Terrain Quality	0	50	100	Low
Particle Quality	0	0	50	Low
Parallax Mapping	Off	Off	On	Low
Glass Displacement	Off	Off	Off	Negligible
Motion Blur	Off	Off	Off	Off always
Depth of Field	Off	Off	Off	Off always

Motion blur and depth of field deserve a separate note: they should be disabled at every tier. Neither adds visibility or competitive value, and both consume GPU time for a purely cosmetic effect that most players find disorienting in PvP.

The Three Settings That Matter Most

Shadows are Rust’s single biggest FPS drain. Shadow Quality at maximum costs 20 FPS compared to off, and Shadow Cascades at maximum costs another 18 FPS — a combined 38-frame penalty for a visual effect that helps you spot players only marginally better than the zero setting [2]. The competitive recommendation is Shadow Quality 0 across all hardware tiers. This is not about compromising visuals; shadows in Rust do not help you identify enemy positions the way they do in some games. Turn them off.

Water settings are the second priority. Water Quality and Water Reflections together cost up to 27 FPS at their highest values. Unless you spend most of your time near the ocean monument or swimming routes, water quality at zero has no practical downside. This is one of the highest-return changes you can make [2].

Draw Distance has a non-linear return. Going from 1500 to 2000 gives you meaningful extra spotting range and is worth the 3–4 FPS cost. Going from 2000 to 2500 gives you roughly 5% more visual range while costing another 3+ FPS with no equivalent competitive gain [2]. The sweet spot is 2000. Note that Draw Distance only affects how far terrain and objects render — players and structures render at a fixed distance regardless of this setting, so you cannot use it to see enemies further away.

Launch Options That Work in 2026

Set these in Steam by right-clicking Rust → Properties → General → Launch Options. The following combination is reliable and safe [1][2][4]:

-window-mode exclusive -nolog -effects.maxgibs -1 -graphics.waves 0

What each flag does:

-window-mode exclusive — Forces exclusive fullscreen, which gives the GPU direct control over the display and reduces input latency compared to borderless windowed mode
-nolog — Disables the game log file. Rust writes continuously to a log file during play; disabling it removes this minor I/O overhead
-effects.maxgibs -1 (or 0) — Removes raid debris. Setting this to -1 or 0 means no gibs spawn, freeing CPU time during explosions and raids
-graphics.waves 0 — Disables ocean wave simulation. Waves are a CPU-side calculation; turning them off saves processing time even when you are far from water

If you have 16 GB or more of RAM, you can also add -maxMem=16384 (or 32768 for 32 GB). This pre-allocates more memory to the game and can reduce stutters caused by dynamic memory allocation during long sessions [1].

For broader PC-level optimizations beyond launch options, the PC performance optimization hub covers system-level tweaks that apply to all games.

Console Commands Worth Knowing

Access the F1 console in-game. These commands provide real performance or QoL benefit [3][4]:

perf 1 — Displays an on-screen FPS counter. Use this to measure the impact of your changes before and after
gc.buffer 2048 — Sets the garbage collection buffer size. Higher values (up to 4096) make GC events less frequent but slightly longer, eliminating the constant micro-stutters that build up over a session
gc.collect or bind p gc.collect — Manually triggers Unity’s garbage collector. Run this if your FPS has dropped significantly after 30–45 minutes of play without changing any settings
effects.maxgibs 0 — In-game equivalent of the launch option. Useful if you did not set it before launching
fps.limit 0 — Removes the FPS cap. If your FPS is artificially capped, this frees it
graphics.vm_fov_scale false — Makes the weapon viewmodel smaller on screen, giving slightly better peripheral visibility during gunfights

Understanding what these settings actually do is easier with context from our game settings explained guide, which covers the mechanics behind common options like V-sync, anti-aliasing, and frame capping.

Windows and System Tweaks

Three system-level changes give disproportionate returns in Rust specifically, because of its CPU dependency:

Enable XMP or EXPO in BIOS. Many systems ship with RAM running at its default JEDEC speed (often 2133 MHz) rather than its rated speed (3600–6000 MHz). If your RAM is rated at 3600 MHz but running at 2133 MHz in BIOS, you are losing 5–10% of potential performance across all CPU-bound games including Rust. Enable XMP (Intel) or EXPO (AMD) in your motherboard BIOS to fix this [2].

Set Power Plan to Ultimate Performance. The default Balanced power plan throttles CPU clock speeds during brief idle moments between frames. Ultimate Performance eliminates this throttling. Enable it via PowerShell: powercfg -duplicatescheme e9a42b02-d5df-448d-aa00-03f14749eb61, then select it in Windows Power Options.

Enable Hardware-Accelerated GPU Scheduling (HAGS) in Windows → Display → Graphics → Change default graphics settings. HAGS reduces GPU scheduling overhead and can lower input latency by 1–5 ms, which matters in competitive Rust play.

If you are on NVIDIA, pair these changes with the settings in our NVIDIA Control Panel guide — global settings like Low Latency Mode and Threaded Optimization apply to Rust and amplify the gains from in-game changes.

Upscaling in Rust: DLSS Yes, FSR No

Rust has native DLSS 3.7 support, accessible via the Anti-Aliasing dropdown in video settings. If you have an NVIDIA GPU, select DLSS Quality for a clean 30–40% FPS gain with minimal image quality trade-off. DLSS Performance mode pushes FPS gains to 60–70% but introduces noticeable softness, which most players consider acceptable for potato or budget hardware [6].

Rust does not have native FSR support as of 2026. If you are on AMD hardware, your best upscaling option is to use the in-game SMAA anti-aliasing setting (free, no FPS cost) combined with AMD’s AFMF2 driver-level frame generation, available in AMD Adrenalin Software for RDNA 2 and 3 cards.

DLSS 5 was announced in March 2026 and is expected to reach game support in fall 2026. Facepunch has not confirmed a Rust implementation date yet [6].

FAQ

Does a better GPU actually help in Rust?

Only marginally at 1080p and 1440p, where Rust is CPU-bound. At 4K with graphics settings on High or Ultra, the GPU becomes the bottleneck and an upgrade makes a real difference. For competitive 1080p play, a faster CPU (especially an AMD X3D chip) will give you more FPS than upgrading your GPU.

Why does my FPS drop after an hour of playing?

Rust’s Unity engine accumulates garbage memory over time and does not always free it promptly. This is the memory leak issue described earlier. The fix is to run gc.collect in the F1 console when you notice degradation. Setting gc.buffer 2048 at session start slows the accumulation rate.

Does 16 GB RAM still meet requirements for Rust?

Barely on large modded servers. The official minimum spec is 10 GB, and the recommended spec is 16 GB. In practice, Rust on a busy server with large bases nearby will push 14–15 GB of RAM usage. Running with exactly 16 GB leaves no headroom for Windows, Discord, and browser overlays. If you are hitting stutter on a high-pop server, check Task Manager — if RAM usage is above 90%, that is your bottleneck [5][7].