SensConverter

Team Fortress 2 to DOOM (2016) sensitivity converter

Convert your Team Fortress 2 sensitivity to DOOM (2016) instantly. Same hand motion, perfect muscle memory across both games.

Converted sensitivity
0.4
Team Fortress 2DOOM (2016)
eDPI
320
Team Fortress 2
cm / 360°
129.89
Team Fortress 2
in / 360°
51.14
Team Fortress 2
eDPI: 320 (DOOM (2016))

Why Team Fortress 2 sens doesn't match DOOM (2016)

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 DOOM (2016), you need sens 0.4 — about 1.00× your Team Fortress 2 number. Nothing changed except DOOM (2016)'s yaw of 0.022 vs Team Fortress 2's 0.022; the centimeters of mouse travel stay the same.

Team Fortress 2 and DOOM (2016) side-by-side
Team Fortress 2 · Yaw
0.022
DOOM (2016) · Yaw
0.022
Team Fortress 2 · Default FOV
90
DOOM (2016) · Default FOV
90

How to apply the converted sensitivity in DOOM (2016)

Open DOOM (2016)'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 DOOM (2016)

  • Copying the sens without matching DPI

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

  • Ignoring scoped and ADS overrides

    Team Fortress 2 and DOOM (2016) 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 DOOM (2016) separately, otherwise scoped aim will feel wrong even with a perfect hipfire match.

Team Fortress 2 → DOOM (2016) FAQ

Why is my converted DOOM (2016) sens different from my Team Fortress 2 number?+

DOOM (2016) has a yaw of 0.022 compared to Team Fortress 2's 0.022. Their ratio is about 1.00×, 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 DOOM (2016)?+

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

How many decimals should I use in DOOM (2016)?+

DOOM (2016) 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 DOOM (2016) 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 DOOM (2016)