How sensitivity converters actually work (and why most are wrong)

If you've ever switched from Valorant to CS2 and wondered why your aim feels alien even though you "matched the sens", the answer isn't your skill — it's that you matched the wrong number. Game sensitivity sliders measure different things in different games. The only metric that actually transfers is cm/360°.

This piece walks through what's really happening under the hood when you convert sens between FPS titles, what the common pitfalls are, and what to look for in a converter that won't lie to you.

The yaw value: every game's secret multiplier

Every first-person shooter has an internal constant called yaw: how many degrees your view rotates per single mouse count. Valorant ships with 0.07°. CS2 ships with 0.022°. Apex, R6, COD, Overwatch — every one is different. Game devs picked these numbers somewhat arbitrarily decades ago, and now they're cemented into engine code that nobody's allowed to break.

That's why your "0.4 sens" in Valorant feels nothing like a "0.4 sens" in CS2. Same sens slider, but in Valorant each mouse count rotates the camera roughly 3× faster. Without converting, you over-flick by 300% on every shot.

cm/360°: the only metric that survives the trip

The way pros think about sens isn't "what's the slider value" — it's how many centimeters does my mouse move for one full rotation. That's cm/360°. It's the same in every game, every mouse, every monitor — because it's a measurement of your hand, not the game.

A converter's only real job is to find the slider value in Game B that produces the same cm/360° as your current setup in Game A. The formula is simple:

target_sens = source_sens × (source_yaw ÷ target_yaw)

That's it. One line of math. Anything more complicated than that means the converter is also adjusting for FOV, ADS, or zoom — which we'll get to.

eDPI: why pros' setups look so different

eDPI is your mouse DPI multiplied by your in-game sens. It's a useful shorthand within a single game — it lets you say "I run 280 Valorant eDPI" without spelling out 800×0.35 vs 400×0.7 vs 1600×0.175. They're all the same physical aim.

But eDPI doesn't transfer across games. A Valorant eDPI of 280 is around 28 cm/360°. The same cm/360° in CS2 requires an eDPI of about 880 — because of the yaw difference. You'll see confused players asking "why do CS pros have such high eDPIs" — they don't, really. Their aim is the same; the engine just makes the number bigger.

Use our eDPI calculator for within-game comparisons. Use our cm/360° calculator for across-game ones.

Three things that quietly break every conversion

1. Windows pointer speed

Windows applies a multiplier to every mouse count before your game receives it. Step 6/11 is the only setting that means "1×, no scaling". Anything else multiplies your mouse counts non-linearly and breaks every sens guide you'll ever read.

Open Settings → Mouse, set pointer speed to 6/11, and disable "Enhance pointer precision". One-time fix. See our Windows pointer tool for the full multiplier table.

2. FOV mismatch

Different games default to different FOVs. CS2 is locked at 90. Valorant defaults to 103. Apex defaults to 90 horizontal but most players bump to 110. When FOV is wider, the same camera rotation moves on-screen targets less — so your aim feels sluggish even when cm/360° is identical.

If you're switching games, set both to your preferred FOV first, then convert sens. Use our FOV adjuster to compensate when you're stuck with a fixed FOV in one game.

3. ADS / scope multipliers

Most games separate ADS sens from hipfire sens with a coefficient. The default behavior should be "Relative" or "Legacy" — the cursor stays on the same world point when you toggle ADS. Anything else and your scoped aim diverges from your hipfire training.

Apex Legends specifically: set "Mouse Sensitivity Coefficient" to Legacy, not Affected by FOV. Most pros do this and it's why their sens transfers cleanly between games. See our ADS / Hipfire sync tool.

What makes a converter trustworthy

Most online sens converters are scraped data plus a one-line formula, wrapped in 5MB of ads. They get the math right, mostly, but they don't tell you about the three pitfalls above — and they all assume you've already correctly set Windows pointer to 6/11.

A good converter:

• Shows you the cm/360° (so you can sanity-check the result against your physical setup).
• Shows the eDPI for both games (so you can see why the two slider values look so different).
• Lets you set DPI explicitly (because pros' DPIs vary, and the converter shouldn't assume).
• Doesn't gate the result behind a sign-up, ad-roll, or "subscribe to see your number".

Our sens converters do all of the above. They're free, no signup, run entirely in your browser, and the math is one line you can verify against any community reference.

Quick reference

That's it. Get those three pitfalls right, use the cm/360° as your north star, and your aim will transfer between any FPS without two weeks of "feeling weird". The math is simple — most of what makes sens conversion confusing is the noise around it.