Rust guides

Best Rust Sensitivity and DPI Settings (2026)

There is no single "pro" Rust sensitivity. What separates good players is a consistent setup and a process for tuning it, so this guide gives you sane starting values and a method to find what actually fits your hand and desk space.

6 min read

DPI and sensitivity are one number, not two

Your true turn speed is DPI multiplied by in-game sensitivity. A high DPI with low sensitivity and a low DPI with high sensitivity can feel identical, so chasing a magic DPI value on its own is pointless.

400 or 800 DPI can be reasonable starting examples, but there is no single best DPI or verified competitive-player majority established here. What matters for turning is the resulting sensitivity and whether it suits your mouse space and comfort.

Changing DPI changes the effective sensitivity unless you compensate in-game. Record your settings so you can make controlled comparisons rather than assuming a DPI change erases learned skill.

cm/360: the number that actually matters

cm/360 is how many centimetres you have to move the mouse to spin a full 360 degrees. It combines DPI and sensitivity into one honest figure, and it is the value worth thinking in because it maps directly to how much desk space a turn costs you.

A lower cm/360 needs less mouse travel for a turn; a higher value needs more. For a starting experiment, try 25 to 40 cm/360 if your pad allows it, then adjust for comfortable turning and small corrections. This is a suggestion, not a measured player norm.

To measure yours without maths: put a mark on your mousepad, place the mouse there, do a slow controlled 360 in game, and see how far the mouse travelled. Adjust the in-game slider until a full turn fits comfortably inside your pad with room to spare.

ADS, scope and hipfire sensitivity

Rust offers a separate ADS sensitivity multiplier. A value of 1.0 is a starting setting, not a guarantee of identical physical turning distance for every sight. Measure hipfire and ADS separately with the scopes you use.

Some players drop ADS sensitivity slightly below 1.0 for steadier long-range tap shots, especially with scopes, since a scope zooms the view and makes any hand movement feel amplified. If you try that, change it in small steps and give it time before judging.

Compare the sights you actually use before choosing a multiplier. Keep settings that allow comfortable tracking and precise corrections at those zoom levels.

  • Start at an ADS multiplier of 1.0 and only move it if aiming feels too twitchy or too sluggish versus hipfire
  • If you use scopes a lot, test a small reduction (for example around 0.8 to 1.0) for steadier zoomed shots
  • Change one thing at a time so you can actually tell what helped

Polling rate, FOV and the rest of the setup

Facepunch currently warns that mouse polling rates of 1000Hz or higher can add CPU overhead and cause frame drops after the Unity 6 upgrade. Until Facepunch documents a fix, try 500Hz or another setting below 1000Hz if Rust feels less stable; keep the lowest rate that removes the issue without making input feel rough.

A wider field of view shows more peripheral space while making distant targets look smaller. FOV 90 is an available starting option; compare it with a lower value for your screen and viewing distance.

Turn off mouse acceleration and any smoothing in Windows and your mouse software so that the same hand movement always produces the same turn. Consistency is the whole point: a repeatable input is what lets your brain learn the spray behaviour on top of it.

Sensible starting values and how to tune from them

Use these as a starting point, not a prescription. The goal is to get close, then let your own testing pull the numbers into place over a few sessions.

Keep a record of your baseline and compare one change at a time. Give yourself enough practice to judge comfort and hit consistency; there is no proven universal one-week adaptation deadline.

  • DPI: 400 to 800, chosen once and left alone
  • In-game sensitivity: tuned so a full 360 lands around 25 to 40 cm on your pad
  • ADS multiplier: around 1.0 to start, lower slightly only if scopes feel twitchy
  • Polling rate: try 500Hz, or another value below 1000Hz, while Facepunch's performance warning remains unresolved
  • FOV: 90 (the Rust maximum) for awareness
  • Mouse acceleration: off, in both Windows and mouse software

Why settings only get you to the start line

Facepunch reworked automatic-weapon recoil in June 2022. Current weapons still have learnable recoil tendencies; spread is a separate accuracy mechanic. Practice with the current weapon and attachments. Since May 2024, the movement accuracy penalty builds during sustained fire instead of applying fully to the first shot.

This is where a good tuning process pays off. With a repeatable sensitivity, your pulldown and micro-corrections become learnable, so time on target translates into real progress instead of fighting your own mouse.

RustFront Combat is a coaching-first, EU-based way to measure that progress, free in open beta and offline for maintenance right now with the rest of the network. Its range scores your spray control under the current recoil system while you fire, so once the servers come back you can test a sensitivity change against a number instead of a feeling. For the wider fundamentals, see the improve-aim hub.

Common questions

What is the best DPI for Rust?

There is no single best DPI. 400 and 800 are starting examples; tune the in-game sensitivity for your available mouse space and measure the resulting turning distance.

What sensitivity should I use in Rust?

Aim for a full 360 turn that takes roughly 25 to 40 cm of mouse movement on your pad, then adjust to taste. That cm/360 figure matters more than the raw slider number because it accounts for both DPI and sensitivity.

Should ADS sensitivity be the same as hipfire in Rust?

Use 1.0 as a starting ADS multiplier if comfortable, then measure and test each sight. It does not guarantee identical hipfire and scoped cm/360.

Does polling rate or FOV really affect my aim in Rust?

Yes. Facepunch currently warns that polling rates of 1000Hz or higher can add CPU overhead and cause frame drops, so try 500Hz or another value below 1000Hz until a fix is documented. FOV 90 gives the widest peripheral view. These settings help, but stable sensitivity and trained recoil control matter more.