Valorant to Overwatch 2 sens: multiply your Valorant sens by 10.606 at the same DPI, or your OW2 sens by 0.0943 to go back. Includes a two-way converter, 800 and 1,600 DPI charts and zoom reference values for Widowmaker, Ana and Ashe.
Last updated: October 10, 2026

To convert Valorant to Overwatch 2 sens, multiply your Valorant sens by 10.606 while using the same DPI in both games. For Overwatch 2 to Valorant, use OW2 sens × 0.0943. Example: Valorant 0.4 at 800 DPI equals Overwatch 2 4.24; OW2 5 becomes Valorant 0.471. Zoom sensitivity for Widowmaker and Ana is set separately – the community reference value for the same feel at the crosshair is 37.89.
Overwatch 2 and Valorant share a lot of players: both are hero or agent shooters built around abilities – only the aiming works differently. Overwatch uses much bigger sensitivity numbers, so an OW2 sens of 5 looks absurdly high next to Valorant 0.47. Yet at 800 DPI both describe exactly the same hand movement. Here’s the Valorant to Overwatch 2 sens conversion with a two-way converter, charts for 800 and 1,600 DPI, and guidance on zoom sensitivity for Widowmaker, Ana and Ashe.
Pick a direction, enter your sens and DPI, and the result is there instantly. When you switch direction, the converter uses the last result as the new input. It converts your normal, unzoomed sens; per-hero zoom sensitivity is covered further down.
The conversion keeps your hipfire turn distance (cm/360) identical. ADS, scope and zoom values are set separately – see below.
Overwatch turns the camera by 0.0066° per mouse count at sens 1, Valorant by 0.07°. That’s why Overwatch numbers are so large: you need roughly 10.6 times the sens for the same turn.
Both yaw values are measured standard values, not official figures from Riot or Blizzard. For Overwatch, csdb.gg, KovaaK’s, senslab.pro and hangon.live all list 0.0066. The turn-distance check: OW2 5 at 800 DPI gives 360 ÷ (800 × 5 × 0.0066) × 2.54 = 34.6 cm – the same as Valorant 0.471 at 800 DPI.
The values below were recalculated with yaw 0.07 and 0.0066 and rounded to three decimals. cm/360 is identical in both games.
| Valorant sens | eDPI | cm/360 | Overwatch 2 sens |
|---|---|---|---|
| 0.20 | 160 | 81.6 | 2.121 |
| 0.25 | 200 | 65.3 | 2.652 |
| 0.30 | 240 | 54.4 | 3.182 |
| 0.35 | 280 | 46.7 | 3.712 |
| 0.40 | 320 | 40.8 | 4.242 |
| 0.45 | 360 | 36.3 | 4.773 |
| 0.50 | 400 | 32.7 | 5.303 |
| 0.55 | 440 | 29.7 | 5.833 |
| 0.60 | 480 | 27.2 | 6.364 |
At 1,600 DPI the sens halves in both games. Valorant 0.2 at 1,600 DPI therefore equals 0.4 at 800 DPI and gives 2.121 in Overwatch 2.
| Valorant sens | eDPI | cm/360 | Overwatch 2 sens |
|---|---|---|---|
| 0.10 | 160 | 81.6 | 1.061 |
| 0.125 | 200 | 65.3 | 1.326 |
| 0.15 | 240 | 54.4 | 1.591 |
| 0.175 | 280 | 46.7 | 1.856 |
| 0.20 | 320 | 40.8 | 2.121 |
| 0.25 | 400 | 32.7 | 2.652 |
| 0.30 | 480 | 27.2 | 3.182 |
So Valorant 0.2 to 0.6 at 800 DPI translates to roughly 2.1 to 6.4 in Overwatch 2. If you see single-digit sens values on Overwatch forums, that doesn’t contradict Valorant – it’s just a different scale.
For the reverse direction, here are common Overwatch values. The Valorant sens applies at the same DPI; the columns on the right show your 360° distance at 800 and 1,600 DPI.
| Overwatch 2 sens | Valorant sens | cm/360 at 800 DPI | cm/360 at 1,600 DPI |
|---|---|---|---|
| 3 | 0.283 | 57.7 | 28.9 |
| 3.5 | 0.330 | 49.5 | 24.7 |
| 4 | 0.377 | 43.3 | 21.6 |
| 4.5 | 0.424 | 38.5 | 19.2 |
| 5 | 0.471 | 34.6 | 17.3 |
| 5.5 | 0.519 | 31.5 | 15.7 |
| 6 | 0.566 | 28.9 | 14.4 |
| 7 | 0.660 | 24.7 | 12.4 |
| 8 | 0.754 | 21.6 | 10.8 |
| 10 | 0.943 | 17.3 | 8.7 |
OW2 6 at 800 DPI becomes Valorant 0.566 with 28.9 cm per turn, OW2 8 becomes 0.754 with 21.6 cm. The latter is already a fast sens for Valorant – see the switching tips below.
The conversion above only covers unzoomed aim. In Overwatch 2, zoom sensitivity is set with “Relative Aim Sensitivity While Zoomed” – per hero. That lets you tune Widowmaker differently from Ana or Ashe. Valorant only has one Scoped Sensitivity Multiplier for all snipers and one ADS Sensitivity Multiplier for rifles and SMGs, both defaulting to 1.0.
| Game & weapon/hero | Setting | Reference |
|---|---|---|
| Overwatch 2: Widowmaker, Ana | Relative Aim Sensitivity While Zoomed | 37.89 (community value) |
| Overwatch 2: Ashe | Relative Aim Sensitivity While Zoomed | 51.47 (community value) |
| Valorant: Operator, 1st zoom (2.5×) | Scoped Sensitivity Multiplier | ≈ 0.747 |
| Valorant: Marshal, Outlaw (3.5×) | Scoped Sensitivity Multiplier | ≈ 0.731 |
| Valorant: Guardian (1.5×) | ADS Sensitivity Multiplier | ≈ 0.815 |
The 37.89 and 51.47 values come from a 2018 discussion on the official Blizzard forums and are still used by community tools today; Blizzard itself has not confirmed them. They make small corrections right at the crosshair travel the same distance zoomed as unzoomed. The Valorant values follow the same logic and can be calculated from the fixed 103° field of view and the zoom levels.



You don’t have to use these values. In Valorant the default of 1.0 matches the feel at the edge of the screen, and many pros stick with it. But if you’re a Widowmaker player used to 37.89, about 0.747 on the Operator is the matching starting point – both then follow the same principle.
Call of Duty – specifically Black Ops 6, Black Ops 7 and Warzone – uses the same yaw as Overwatch according to senslab.pro, KovaaK’s and hangon.live: 0.0066. Your Overwatch 2 hipfire sens carries over 1:1 to CoD, and the charts on this page also work for “Valorant to CoD sens”. For aiming down sights, Call of Duty has its own ADS options that you set separately.
Marvel Rivals is sometimes said to use the Overwatch scale. Consistent measurements say otherwise: senslab.pro, KovaaK’s and game-sens.jor.dev land at about 0.0175° per count, and Valorant sens × 4 gives your Rivals sens. If you move from Overwatch 2 to Marvel Rivals, don’t just copy your sens over.
Overwatch has many heroes where you track targets for longer, while Valorant mostly asks for short corrections at head height. If you mainly play tracking heroes in Overwatch, your converted sens may feel faster in Valorant than you’d like. Here’s how to approach it:
To see which eDPI values are common in Valorant and where yours fits, read our eDPI guide.
Each game pair has its own page with a converter, charts and the zoom quirks of that game.
Factor 3.18, AWP vs Operator and whether your CS:GO sens still works in CS2.
Also factor 3.18, plus per-optic ADS and the FOV slider.
A percentage scale with factor 12.6 and separate X/Y sliders.
Valorant to Overwatch 2 means × 10.606, and × 0.0943 to go back – at the same DPI. The big Overwatch numbers are just a different scale, not a higher sensitivity. Zoom sensitivity isn’t part of the conversion: 37.89 for Widowmaker and Ana is a community reference, and in Valorant that corresponds to about 0.747 on the Operator’s first zoom. Call of Duty shares the Overwatch scale, Marvel Rivals does not.
Overwatch 2 sens 5 equals a Valorant sens of 0.471 at the same DPI. At 800 DPI that’s 34.6 cm for a 360° turn.
OW2 6 gives Valorant 0.566 at the same DPI. At 800 DPI that’s 28.9 cm per 360° turn.
Valorant 0.4 equals an Overwatch 2 sens of 4.24 (0.4 × 10.606) at the same DPI. At 800 DPI both games give 40.8 cm per turn.
Yes. Common converters use the same 0.0066 yaw for “Overwatch” and Overwatch 2. Overwatch 2 replaced the original Overwatch in October 2022.
For the same feel right at the crosshair, the community uses 37.89 for Widowmaker and Ana in “Relative Aim Sensitivity While Zoomed”, and 51.47 for Ashe. Blizzard hasn’t confirmed these values – treat them as a starting point, not a rule.
For hipfire, yes: according to several converter tools, Call of Duty (Black Ops 6, Black Ops 7, Warzone) also uses the 0.0066 yaw. CoD’s ADS settings are configured separately.
Multiply your Overwatch sens by 0.0943 (0.0066 ÷ 0.07) at the same DPI. OW2 8 becomes Valorant 0.754.
May I set a statistics cookie?
With your consent, Matomo (self-hosted in Germany, no sharing, IP shortened) uses a cookie to remember whether you come back – so I can see which pages really help. Without consent I keep measuring anonymously with no cookies at all. Change it any time via “Cookie settings” in the footer. Privacy policy