SensConverter

Team Fortress 2 to Rainbow Six Extraction sensitivity converter

Convert your Team Fortress 2 sensitivity to Rainbow Six Extraction instantly. Same hand motion, perfect muscle memory across both games.

Converted sensitivity
1.5359
Team Fortress 2Rainbow Six Extraction
eDPI
320
Team Fortress 2
cm / 360°
129.89
Team Fortress 2
in / 360°
51.14
Team Fortress 2
eDPI: 1229 (Rainbow Six Extraction)

Why Team Fortress 2 sens doesn't match Rainbow Six Extraction

At 0.4 sens on 800 DPI, Team Fortress 2 sweeps 129.89 cm across a full 360°. To reproduce that exact arm motion in Rainbow Six Extraction, you need sens 1.5359 — about 3.84× your Team Fortress 2 number. Nothing changed except Rainbow Six Extraction's yaw of 0.00572958 vs Team Fortress 2's 0.022; the centimeters of mouse travel stay the same.

Team Fortress 2 and Rainbow Six Extraction side-by-side
Team Fortress 2 · Yaw
0.022
Rainbow Six Extraction · Yaw
0.00572958
Team Fortress 2 · Default FOV
90
Rainbow Six Extraction · Default FOV
90

How to apply the converted sensitivity in Rainbow Six Extraction

Open Rainbow Six Extraction's settings, paste the converted sensitivity into the sens field and keep your 800 DPI if that matches how you play Team Fortress 2. Run a 360° check on a practice map: the mouse sweep should cover roughly 129.89 cm on your pad — the same distance as in Team Fortress 2. Only start tuning if the sweep feels off, never before the 360° check.

Common mistakes when converting Team Fortress 2 to Rainbow Six Extraction

  • Copying the sens without matching DPI

    A converted Team Fortress 2-to-Rainbow Six Extraction number is tied to the DPI you used during conversion. If your Rainbow Six Extraction 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 Team Fortress 2 and Rainbow Six Extraction does not give matching turn speed, because their yaws are 0.022 and 0.00572958. Always compare cm/360° (or in/360°), not eDPI, when swapping games.

  • Ignoring scoped and ADS overrides

    Team Fortress 2 and Rainbow Six Extraction 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 Rainbow Six Extraction separately, otherwise scoped aim will feel wrong even with a perfect hipfire match.

Team Fortress 2 → Rainbow Six Extraction FAQ

Why is my converted Rainbow Six Extraction sens different from my Team Fortress 2 number?+

Rainbow Six Extraction has a yaw of 0.00572958 compared to Team Fortress 2's 0.022. Their ratio is about 3.84×, so Sens Converter multiplies your Team Fortress 2 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 Team Fortress 2 and Rainbow Six Extraction?+

Yes, when possible. Keeping DPI identical means only the in-game multiplier changes, which is the cleanest switch. If you run different DPI in Rainbow Six Extraction, enable 'different DPI' in the converter and it absorbs the extra math.

How many decimals should I use in Rainbow Six Extraction?+

Rainbow Six Extraction 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 Team Fortress 2 to Rainbow Six Extraction 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.

Go deeper

More Team Fortress 2 conversions

Convert into Rainbow Six Extraction