How Does the Sensitivity Converter Work?

Every FPS game moves the in-game camera a specific number of degrees per unit of mouse movement. This value is called the yaw (or sensitivity multiplier). By converting your sensitivity to cm/360° — the physical mouse distance needed for a full 360° rotation — and then applying the target game’s yaw formula, you get the exact sensitivity that produces the same turning speed in both games.

The formula is:

Game Sensitivity Yaw Values Used in This Converter

These are the sensitivity multipliers (degrees per count) used in the conversion. They are sourced from each game’s official documentation and verified against community measurement.

Common Sensitivity Conversions — CS2 to Other Games

These are the most searched sensitivity conversions at standard 800 DPI. Your exact converted value may differ if you use a different DPI — use the calculator above for precise results.

What Is cm/360°? (And Why It Matters)

cm/360° is the most reliable way to describe and compare mouse sensitivity across games and players. It measures the physical distance your mouse must travel across your mousepad to rotate your in-game view exactly 360 degrees.

Because cm/360° is independent of DPI and game sensitivity scales, it is the universal benchmark competitive players use when discussing settings:

Most professional FPS players fall between 25–55 cm/360°. Extreme outliers exist — some pro CS2 players use >80 cm/360° — but they are rare.

Sensitivity Conversion Is Not 1:1 Feel

A converted sensitivity gives you the same turning speed, but feel can still differ between games for several reasons:

• Field of View (FOV): CS2 at 90° FOV and Apex at 110° FOV produce a different sense of speed even at the same cm/360°. Objects appear closer in lower FOV, making the same movement feel slower.
• ADS multipliers: Most games reduce sensitivity when aiming down sights. This multiplier varies per game and per scope type. Hipfire conversion is precise; ADS conversion requires per-scope multiplier adjustments.
• Mouse acceleration and smoothing: Some games apply input smoothing or acceleration by default. If these are active, converted sensitivity will feel inconsistent. Disable raw input options in game settings where available.
• Muscle memory: Even a mathematically perfect conversion requires 1–2 weeks of play before it feels natural.

How to Apply Your Converted Sensitivity

1. Enter your current game, DPI, and sensitivity into the converter above.
2. Note the converted sensitivity value for your target game.
3. Open the target game and go to Settings → Mouse / Sensitivity.
4. Enter the converted sensitivity value. Use decimal precision — most games accept 3+ decimal places.
5. In CS2, make sure m_rawinput 1 is active in the console to bypass Windows mouse acceleration.
6. In Valorant, set Enhanced Pointer Precision to Off in Windows mouse settings.
7. Use a custom aim training scenario to verify the feel before playing ranked matches.

Does Polling Rate Affect Sensitivity Feel?

Yes — significantly. Your converted sensitivity can be mathematically perfect, but polling rate determines how smoothly that sensitivity is expressed on-screen.

At 125Hz (8ms updates), fast movements produce visible stepping and stutter because the game only receives 8 position updates per second. At 1000Hz (1ms), the same sensitivity feels fluid. At 8000Hz, micro-movements are captured with extreme precision.

If your converted sensitivity feels jittery or inconsistent in either game, verify your polling rate matches your hardware spec. Use our free mouse polling rate test — it takes under 10 seconds in your browser and requires no download.

Frequently Asked Questions

How do I convert CS2 sensitivity to Valorant?

Multiply your CS2 sensitivity by 0.3143. This is the fixed conversion ratio derived from each game’s yaw value (CS2: 0.022, Valorant: 0.07). For example, CS2 2.0 sensitivity converts to 0.629 in Valorant at the same DPI. Use the calculator above for instant results at any DPI.

Why is Overwatch 2 sensitivity so much higher than CS2?

Overwatch 2 uses a very low yaw value (0.0066 vs CS2’s 0.022). This means OW2’s sensitivity slider moves the camera much less per unit compared to CS2. To achieve the same turning speed, you need a proportionally higher sensitivity number in Overwatch 2. The physics are identical — only the scale differs.

Does DPI affect the conversion result?

The converted sensitivity value changes with DPI, but the resulting physical movement (cm/360°) stays the same. If you use 1600 DPI instead of 800 DPI, your converted sensitivity will be half as large — but your mouse will travel the same physical distance for a 360° turn. The conversion is always cm/360° neutral.

Can I convert controller sensitivity the same way?

No. Controller sensitivity uses a fundamentally different input model — analog sticks report directional position (axis values), not pixel-delta movement. There is no cm/360° equivalent for controllers. However, your controller’s polling rate still affects how quickly those axis values are reported to the game.

Why does my converted Valorant sensitivity feel different from my CS2 sensitivity?

The most common reason is FOV difference. CS2 uses 90° FOV by default; Valorant uses 103° (approx.). At the same cm/360°, Valorant’s wider FOV makes movement feel slightly faster. Some players adjust their Valorant sensitivity 5–10% lower than the mathematically converted value to compensate. Try the exact conversion first, then fine-tune based on feel.