Rust to Team Fortress 2 sensitivity converter
Convert your Rust sensitivity to Team Fortress 2 instantly. Same hand motion, perfect muscle memory across both games.
Why Rust sens doesn't match Team Fortress 2
At 0.4 sens on 800 DPI, Rust sweeps 39.69 cm across a full 360°. To reproduce that exact arm motion in Team Fortress 2, you need sens 1.3091 — about 3.27× your Rust number. Nothing changed except Team Fortress 2's yaw of 0.022 vs Rust's 0.072; the centimeters of mouse travel stay the same.
- Rust · Yaw
- 0.072
- Team Fortress 2 · Yaw
- 0.022
- Rust · Default FOV
- 90
- Team Fortress 2 · Default FOV
- 90
How to apply the converted sensitivity in Team Fortress 2
Open Team Fortress 2's settings, paste the converted sensitivity into the sens field and keep your 800 DPI if that matches how you play Rust. Run a 360° check on a practice map: the mouse sweep should cover roughly 39.69 cm on your pad — the same distance as in Rust. Only start tuning if the sweep feels off, never before the 360° check.
Common mistakes when converting Rust to Team Fortress 2
- Copying the sens without matching DPI
A converted Rust-to-Team Fortress 2 number is tied to the DPI you used during conversion. If your Team Fortress 2 mouse profile runs a different DPI, the math no longer holds — use Sens Converter's 'different DPI' toggle instead of eyeballing.
- Trusting eDPI across engines
Matching eDPI between Rust and Team Fortress 2 does not give matching turn speed, because their yaws are 0.072 and 0.022. Always compare cm/360° (or in/360°), not eDPI, when swapping games.
- Ignoring scoped and ADS overrides
Rust and Team Fortress 2 each apply their own scoped / ADS multiplier on top of the base sensitivity. Converting the base is step one — confirm the per-zoom multiplier in Team Fortress 2 separately, otherwise scoped aim will feel wrong even with a perfect hipfire match.
Rust → Team Fortress 2 FAQ
Why is my converted Team Fortress 2 sens different from my Rust number?+
Team Fortress 2 has a yaw of 0.022 compared to Rust's 0.072. Their ratio is about 3.27×, so Sens Converter multiplies your Rust sens by that factor to keep cm/360° identical. The raw number looks different, but the arm motion is the same.
Should I keep the same DPI in Rust and Team Fortress 2?+
Yes, when possible. Keeping DPI identical means only the in-game multiplier changes, which is the cleanest switch. If you run different DPI in Team Fortress 2, enable 'different DPI' in the converter and it absorbs the extra math.
How many decimals should I use in Team Fortress 2?+
Team Fortress 2 accepts at least 3 decimals; 4-6 is common. Sens Converter outputs enough precision that rounding to 3 decimals keeps the 360° error below one millimetre on a typical 800 DPI setup.
Does FOV affect Rust to Team Fortress 2 conversion?+
For the base sensitivity, no — sens is independent of FOV in both engines. If you use a 0% MonitorDistance or similar scaling mode in either game, convert at the FOV you actually run in-game.