Overwatch Sensitivity Converter: Match Your Settings From Valorant, CS2, Apex and More (2026)

The Overwatch sensitivity converter you need is simpler than most calculator pages make it look. Below is the one formula every tool uses under the hood, the exact multiplier for every mainstream FPS, a table of common presets at 800 DPI, and the three traps — zoom sensitivity, ADS and FOV scaling — that quietly break your aim after a clean conversion.

Why an Overwatch sensitivity converter matters

Every FPS stores your sensitivity on its own scale. Valorant 0.4, CS2 2.0 and Overwatch 5.0 can mean the same real-life turn speed, or three completely different ones — the games just report different numbers. If you build muscle memory in one game and swap sens by eye in another, you spend weeks relearning your flicks for no reason.

The fix is to lock in a single cm/360 (centimeters per full 360° turn) and convert every game to match it. That is what every converter site actually does — the math underneath is identical across them, so you can do it by hand once you know the yaw constants.

The one formula every converter uses

At the engine level, each game multiplies your sensitivity by a hidden yaw constant, measured in degrees of rotation per mouse count. Overwatch's yaw is 0.0066, Valorant's is 0.07, and CS2's is 0.022. That means at the same DPI and the same raw mouse motion, Valorant turns about 10.6× faster per sensitivity unit than Overwatch.

• Overwatch — 0.0066 degrees per count
• Marvel Rivals — 0.0066 (same as Overwatch)
• Valorant — 0.07
• CS2 / CS:GO — 0.022
• Apex Legends — 0.022
• Rainbow Six Siege — 0.00572957795
• Call of Duty (Standard scale) — 0.0066
• The Finals — 0.0066
• Deadlock — 0.022

The conversion formula is: new_sens = old_sens × (yaw_source / yaw_target) at the same DPI. The cm/360 formula is: cm/360 = 914.4 / (DPI × sens × yaw). Both are standard across every converter and verified against in-game turn tests on aiming.pro's calculators.

Overwatch sensitivity converter: exact multipliers

To go from Overwatch to another game at the same DPI, multiply your Overwatch sensitivity by the number below. Flip the fraction to convert the other way.

• Overwatch → Valorant: × 0.0943
• Overwatch → CS2 / CS:GO: × 0.3
• Overwatch → Apex Legends: × 0.3
• Overwatch → Marvel Rivals: × 1 (identical scale)
• Overwatch → Rainbow Six Siege: × 1.152
• Overwatch → The Finals: × 1
• Overwatch → Call of Duty (Standard): × 1
• Valorant → Overwatch: × 10.606
• CS2 → Overwatch: × 3.333
• Apex → Overwatch: × 3.333

Worked example: a Valorant player on 0.4 sensitivity at 800 DPI. New Overwatch sens = 0.4 × 10.606 = 4.24. Both settings produce roughly 34.6 cm/360 — identical hand motion, different numbers on the slider.

Preset table — common Overwatch sensitivities, fully converted

All values below assume 800 DPI, the de facto standard in aim trainers and across most pros. Multiply the DPI column by any factor and the cm/360 column divides by the same factor, so these ratios hold at any DPI.

• OW 3.0 → Val 0.283 · CS2 0.90 · Apex 0.90 · R6 3.46 — about 57.7 cm/360
• OW 4.0 → Val 0.377 · CS2 1.20 · Apex 1.20 · R6 4.61 — about 43.3 cm/360
• OW 5.0 → Val 0.471 · CS2 1.50 · Apex 1.50 · R6 5.76 — about 34.6 cm/360
• OW 6.0 → Val 0.566 · CS2 1.80 · Apex 1.80 · R6 6.91 — about 28.9 cm/360
• OW 7.0 → Val 0.660 · CS2 2.10 · Apex 2.10 · R6 8.06 — about 24.7 cm/360
• OW 8.0 → Val 0.754 · CS2 2.40 · Apex 2.40 · R6 9.22 — about 21.6 cm/360

cm/360 is the only number that actually matters

Sensitivity sliders are arbitrary. cm/360 is physical: it tells you how many centimeters of mousepad you cross for one full turn. That is the number your arm learns. Keep it steady across games and your aim transfers; change it and you reset months of training.

• Below 20 cm/360 — twitch range, used by some Valorant duelists and a few flex DPS in Overwatch; punishing for tracking
• 20–30 cm/360 — hybrid range, dominant among Valorant pros and Overwatch hitscan mains like Tracer and Sojourn
• 30–45 cm/360 — the Overwatch pro average, strong for projectile heroes and tracking (Soldier, Sojourn, D.Va)
• 45–60 cm/360 — control range, favored by CS2 pros and some Widowmaker specialists
• Above 60 cm/360 — rare at the top level; almost exclusively flick-only snipers

Overwatch's roster leans heavily toward tracking, so the sweet spot sits lower on the hand-speed curve than Valorant's. A Valorant pro at 25 cm/360 who converts cleanly to Overwatch keeps the same cm/360 but may still want to go slower (closer to 35) once Pharah and Echo start flying.

Pro Overwatch sensitivities worth copying

These are not aspirational numbers — they are what players at the top level actually use. Convert them to your DPI with the formulas above, and remember that the hand motion is what matters, not the slider value.

• Super (Shock, main tank) — 4.5 sens / 800 DPI → about 38.5 cm/360
• Fitzyhere (Winston specialist) — 5.5 / 800 → about 31.4 cm/360
• Flats (Reinhardt, main tank) — 6.0 / 800 → about 28.8 cm/360
• Kabaji (flex DPS) — 5.0 / 800 → about 34.6 cm/360
• Emongg (support/flex) — 5.0 / 800 → about 34.6 cm/360
• Dafran (hitscan DPS, legacy) — 7.0 / 1000 → about 19.7 cm/360
• Seagull (legacy flex) — 2.3 / 1600 → about 37.5 cm/360

Where converters go wrong — zoom, ADS and FOV traps

A clean hipfire conversion still leaves three settings mismatched. Fix them manually or your aim will feel 10% off in exactly the moments that matter — scope flicks, long-range tracking, close-range duels.

• Zoom sensitivity multiplier — Overwatch's Widowmaker and Ashe use a 'relative aim sensitivity while zoomed' slider that defaults to 30. Set it to 38.6 for true 1:1 zoom-to-hipfire tracking at every scope level.
• ADS vs hipfire — Valorant and CS2 use ADS multipliers that are not the same as Overwatch's zoom slider. A clean hipfire match does not transfer to ADS unless you also set Valorant's ADS multiplier to 1.0 and leave CS2's zoom_sensitivity_ratio_mouse at 1.0.
• FOV scaling — Overwatch is capped at 103 FOV; Valorant renders a wider effective view because of its lower vertical FOV. Two games on the same cm/360 will not feel identical if your perceived target size differs — this is why most pros use a slightly slower sens in Overwatch than in Valorant.
• Polling rate — a mouse polling at 500 Hz in one game and 1000 Hz in another (common on wireless setups) changes how micro-corrections register. Lock both to 1000 Hz.
• Mouse acceleration — must be off in Windows and in game. One tick of acceleration ruins any conversion.

How to measure your current cm/360 the correct way

If you want to transfer your real sensitivity to Overwatch and you do not know your cm/360, do this once with a ruler. It takes two minutes and it is more reliable than any formula.

• Open the game you currently play. Make sure in-game FOV, polling rate, DPI and mouse acceleration all match what you want to measure.
• Place a strip of tape on your mousepad and line your mouse up against it.
• Pick a fixed point in the game world and face it directly.
• Lift the mouse and reset to the tape. Without lifting again, drag horizontally until you have made a full 360° turn and are facing the exact same point.
• Measure the distance in centimeters between your start and end position. That is your cm/360.
• Plug it into cm/360 = 914.4 / (DPI × sens × yaw) and solve for sens in Overwatch using yaw = 0.0066.

Which Overwatch sensitivity converter should you trust?

The two converters that are consistently correct, kept up to date for 2026 patches and verified against in-game turn measurements are aiming.pro and mouse-sensitivity.com. Both apply the math on this page without hidden adjustments. Avoid converters that ask for FOV but output a single sens — they are blending hipfire and effective aim, and the number will not match your muscle memory.

FAQ — Overwatch sensitivity converter

FAQ

Sources: in-engine yaw measurements and the official Overwatch sensitivity scale, cross-referenced with aiming.pro. Pro settings compiled from team-published player configurations.