1:1 Aim

My recommendations

This is my full setup: 1600 DPI and 16:9. The base sens is 1:1 across games and the scoped values are 1:1 with hipfire. On a different sens or DPI? Use the calculator.

Overwatch

CS2

Valorant

Apex Legends

Marvel Rivals

Deadlock

Per-weapon details and sources: Overwatch, CS2, Valorant, Apex Legends, Marvel Rivals, Deadlock.

Calculator

If I want the same sensitivity in every game, it also has to land on a usable value in every game. So I checked each conversion against the eDPI range pros of that game typically play in. Not a hard restriction, but a good starting point. You don't have to copy my FOVs either: pick your own Overwatch and Apex FOV, and for CS2 your aspect ratio. Enter your base game, sens, and DPI. The why behind this formula is explained in the rest of the page:

sens₂ = sens₁ × (yaw₁ / yaw₂) × tan(F₂⁄2) / tan(F₁⁄2)

Pros in wide-FOV games run higher eDPI, which is exactly what a 0% conversion predicts and cm/360 misses (they disagree by 26% on Apex). Pro ranges: prosettings.net, proconfig.net.

What is 1:1 aim?

1:1 aim isn't as intuitive as I thought. My assumption was: a target is X cm from my crosshair, so I need to move my mouse X cm. Turns out that's not true. Moving your mouse X centimeters turns your crosshair X degrees, and degrees don't map evenly onto a flat screen (the math). So there's no clean 1:1 translation, just three common interpretations:

• Same cm per 360: same mouse distance for a full turn.
• Same cm to the screen edge: a.k.a. 100% monitor distance.
• Same cm near the crosshair: a.k.a. 0% monitor distance.

They give genuinely different numbers, and every converter or in-game default silently picks one.

Which 1:1 should you pick?

My conclusion, and what seems to be the common consensus: go for consistency near your crosshair (0% monitor distance). Even on large flicks good players finish with a micro-flick onto the target, so the flick that decides the fight happens near your crosshair. Every value on this page is a 0% match.

How does FOV come into play?

Zooming reduces your FOV: you see fewer degrees, so the same mouse movement (= degrees) covers more of your screen. The same happens between games with different hipfire FOVs: Overwatch and Valorant run 103°, CS2 runs 106.26°, Apex at the 100 setting runs 115.63°, Marvel Rivals is fixed at roughly 90°, and Deadlock's Camera FOV slider caps at 90° (all 16:9). Any conversion that ignores FOV, like plain cm/360, gives you a different on-screen result in every game.

How does the math work?

Your mouse turns centimeters into degrees of rotation. Your flat monitor turns degrees into pixels through a tangent:

screen position = distance × tan(angle)

The tangent grows faster as the angle increases, so one degree of rotation covers few pixels near the crosshair and many near the edge:

The formulas

F₁ = hipfire FOV, F₂ = scoped FOV, p = monitor-distance fraction (0…1), both FOVs in the same aspect ratio.

Same cm to the screen edge = 100% monitor distance (linear / FOV-ratio)

sens% = (F₂ / F₁) × 100

Same cm at the crosshair = 0% monitor distance (tangent, “true 1:1”)

sens% = ( tan(F₂⁄2) / tan(F₁⁄2) ) × 100

General: exact 1:1 for a target at monitor distance p

sens%(p) = ( atan( p·tan(F₂⁄2) ) / atan( p·tan(F₁⁄2) ) ) × 100

As p → 0 this reduces to the tangent method; at p = 1 it equals the linear method. Everything on this page is computed from these three lines.

Per-game yaw value

Each game multiplies your mouse input by an engine constant called yaw: degrees of rotation per mouse count, per sensitivity unit. It's why "sens 2" means something completely different in Overwatch than in Valorant.

Community-established constants, as used by e.g. mouse-sensitivity.com. Heads up: some converters list Marvel Rivals with the standard Unreal 0.022 yaw, but measurements point to pi/180 (0.017453), as ultimatemove.eu documents.

eDPI

eDPI = in-game sensitivity × mouse DPI. It lets players with different DPI compare how fast they actually turn, but only within one game, since each game applies its own yaw.

Zoom values: Overwatch

Relative Aim Sensitivity While Zoomed, per hero, exact at the crosshair on 103 FOV.

No official Blizzard source exists; these are the community-measured values, with the scoped FOVs back-solved from them (16:9). You'll sometimes see slightly different numbers (like 51.66 for Ashe): those come from re-deriving the value from a rounded FOV like 66°, so I stick to the measured ones. Emre's is the least settled: the only public measurement gives 54.69, while 55.08 also circulates (from a method that varies with aspect ratio, so it isn't a crosshair match). The spread is under half a percent, too small to feel.

• Blizzard forums (FOV 50.94, 37.89%)
• Blizzard forums (51.47%)
• Blizzard forums (51.47%, same as Ashe)
• Blizzard forums (measured, 54.69%)
• @Renanthera on X (62.50%)

Zoom values: CS2

The default zoom_sensitivity_ratio 1 matches at the edge of a 4:3 screen (75% monitor distance on a 16:9 monitor). One variable covers every weapon; 0.818933 is exact for the first zoom of the AWP and SSG 08, the rest lands within ~4%.

Scoped FOVs are community-measured; Valve publishes neither them nor the formula. Sources:

• teamfortress.tv (derivation of the 0% formula)
• teamfortress.tv (0.818933 for CS:GO/CS2)
• Steam discussions (per-weapon scoped FOVs)

Zoom values: Valorant

Valorant has two settings: the ADS Sensitivity Multiplier for weapons that aim down sights, and the Scoped Sensitivity Multiplier for the snipers. Both default to 1.0, which matches at the 16:9 screen edge (100% monitor distance). Each multiplier still covers several zoom tiers, so set it for the zoom you rely on most; the rest lands within a few percent (the Guardian strays furthest, about 7% off my rifle value).

Scoped FOVs are the locked 103° divided by Riot's zoom number: the magnification is a straight FOV ratio, so 2.5× means 103 / 2.5 = 41.2°. That's the FOV aim trainers use to replicate the Operator, and it's what every sensitivity calculator I checked agrees on. Sources:

• mouse-sensitivity.com (Valorant 1.0 = MDV 177.78%)
• Official VALORANT Wiki (per-weapon zoom magnifications)

Zoom values: Apex Legends

Apex scales ADS sensitivity by the focal-length (tangent) ratio, so the default 1.0 is already an exact 0% match for every optic, at any FOV. Leave everything at 1.0. The optic FOVs are tuned to exact magnifications at 70 FOV and scale linearly with your FOV setting, so the table shows the effective zoom at 100 FOV.

One gotcha when comparing FOV numbers: Apex's FOV setting is 4:3 based, while Overwatch and Valorant count theirs in 16:9. So 103 in Apex is not 103 in Overwatch: Apex at 100 is really 115.63° on a 16:9 monitor, and to match Overwatch's 103° you'd set Apex to about 86.6.

Sources:

• Apex weapon configs via R5 (per-optic zoom_fov, "2x @ 70" annotations)
• KovaaK's forums, Drimzi (Apex ADS scales by focal length, 0% by default)
• Titanfall 2 modding docs (ADS FOV scales with the base FOV setting)

Zoom values: Marvel Rivals

Good news: like Apex, Marvel Rivals scales ADS sensitivity at the crosshair (0%) natively, so the default ADS Sensitivity Multiplier of 1.0 is already 1:1. Black Widow's scope is the only real zoom. Iron Man's Armor Overdrive, The Punisher's turret and Hela's ultimate don't change your FOV, so they just use your hipfire sens.

Two caveats. NetEase doesn't publish the FOV and there is no FOV setting: community measurements point to roughly 90° at 16:9, which is what I use in the calculator, but you'll also see 103 claimed. I tested this myself with a ruler: measuring a full 360 and then sweeping a landmark from screen edge to screen edge puts the FOV at 90° and clearly rules out 103. My raw sweeps read a couple degrees high (92 to 94), but that's the parallax you'd expect from the third-person camera orbiting behind the character rather than rotating in place. The same test confirmed the pi/180 yaw. And since it's a third-person game, 1:1 here means camera rotation, with some third-person quirks around the crosshair that no setting can fully fix.

Sources:

• mouse-sensitivity.com forums, DPI Wizard (ADS scales at 0% monitor distance; abilities without FOV change use hipfire sens)
• ultimatemove.eu (measured yaw pi/180 = 0.017453, not the often-listed 0.022)
• Aimlabs Steam discussion (FOV ~90 horizontal, community-measured)

Zoom values: Deadlock

Deadlock runs on Source 2 and uses the same 0.022 yaw as CS2, so a CS2 sens carries over 1:1 before the FOV correction. The Camera FOV slider goes from 75 to 90 (horizontal, 16:9); I max it at 90, and the calculator defaults to that. Every hero has a right-click weapon zoom controlled by the Zoom Sensitivity Ratio setting, and Vindicta's ultimate adds a proper scope with multiple zoom levels.

This is the one game where I can't give you exact 0% values, because nobody has published measured scoped FOVs. mouse-sensitivity.com models the zooms per hero group (most heroes share one, a few differ, plus the Sharpshooter item and Vindicta's scope), but the numbers sit behind their premium tier. On top of that the zoom sensitivity has a bug history: for a while Vindicta's scope ignored the setting entirely until a developer fixed it. So I leave the ratio at the default 1.0 for now. The standard weapon zoom is mild, and the milder the zoom, the less the match methods disagree, so whatever the default matches, the error at the crosshair stays small. Like Marvel Rivals it's a third-person game, so 1:1 here means camera rotation. I'll update this section once solid measurements exist.

Sources:

• mouse-sensitivity.com forums, DPI Wizard (same engine scale as CS2; per-hero zoom aims; config file more accurate than the slider)
• mouse-sensitivity.com (Camera FOV range 75–90, hero-group ADS and Vindicta Zoom aims)
• ultimatemove.eu (yaw 0.022, 1:1 with CS2)
• Deadlock forums (zoom ratio and Vindicta scope sensitivity bugs, dev-confirmed fix)
• esportsmice.com (pro eDPI ≈680–1200, median 880)

Disclaimer

• Aim isn't muscle memory, it's hand-eye coordination. The brain re-calibrates to a changed input gain within a short practice session (Krakauer et al., J. Neurosci., motor adaptation). 1:1 removes re-adaptation overhead; it won't make or break your aim.
• Pros don't agree on any of this. Pro sens within one game varies 3×+ (prosettings.net), and ~69% of Valorant pros leave the scoped multiplier at 1.0 (proconfig.net), though the ones who deviate drift toward the 0.9/0.8 values on this page.

All scoped FOVs and engine constants are community-derived (sources per section). Overwatch, Counter-Strike, Valorant, Apex Legends, Marvel Rivals, and Deadlock are trademarks of their respective owners; this is an unofficial fan resource.