Mouse Sensitivity Converter

About the Mouse Sensitivity Converter

Switching between FPS games shouldn't mean relearning your aim. This sensitivity converter translates your mouse sensitivity from one game to another using yaw values — the degrees of rotation per count of mouse movement.

Every FPS game has a different internal sensitivity scale. A sensitivity of 2.0 in CS2 feels completely different from 2.0 in Overwatch. By converting through a common unit (degrees per count), you can maintain identical mouse feel across games.

Enter your source game sensitivity, DPI, and the yaw values for both games to get a perfectly matched sensitivity in the target game.

Use the estimate as a planning baseline and adjust it once you have real session data from the game you are playing.

When This Page Helps

Consistent mouse sensitivity across games builds and maintains muscle memory. When your aim feels identical regardless of which game you're playing, your muscle memory transfers directly, reducing warmup time and improving accuracy in every game.

How to Use the Inputs

1. Select or enter the source game and its yaw value.
2. Enter your in-game sensitivity for the source game.
3. Enter your mouse DPI.
4. Select or enter the target game and its yaw value.
5. View the converted sensitivity for the target game.

Example Calculation

Tips & Best Practices

• Use cm/360 as a universal reference — it measures physical mouse distance for a full rotation.
• Common yaw values: CS2 = 0.022, Overwatch = 0.0066, Valorant = 0.07, Apex = 0.022.
• Verify the conversion by doing a 360-degree spin in both games and comparing mouse distance.
• Some games have additional sensitivity multipliers for ADS (aim-down-sight) that need separate conversion.
• Keep your DPI consistent across games to simplify sensitivity management.
• Write down your sensitivity settings for each game in a master reference list.

Why Sensitivity Conversion Matters

Professional FPS players often compete in multiple titles. Maintaining identical physical sensitivity across games ensures that muscle memory from thousands of hours of practice applies universally.

The Role of Yaw Values

Game engines differ in how they translate mouse input to camera rotation. The yaw value encodes this relationship. Converting sensitivity between games requires knowing both games' yaw values, which are typically documented by the community.

Fine-Tuning After Conversion

A mathematically perfect conversion might still feel slightly off due to FOV differences, mouse smoothing, or frame rate variations. After converting, spend 10-15 minutes in an aim trainer to verify the feel and make micro-adjustments if needed.

Frequently Asked Questions

• What is yaw value?

  Yaw value is the number of degrees the camera rotates per unit of mouse input at sensitivity 1.0. Each game engine uses a different yaw value, which is why the same numeric sensitivity feels different across games.

• Does DPI matter for conversion?

  DPI cancels out when converting between games at the same DPI. The conversion ratio depends only on the yaw values. However, DPI is needed to calculate cm/360 as a reference measurement.

• What is cm/360?

  cm/360 is the number of centimeters you need to move your mouse to complete a full 360-degree rotation in-game. It's the universal sensitivity metric that works across all games regardless of their internal sensitivity scales.

• Why doesn't my converted sensitivity feel right?

  FOV differences between games can make the same cm/360 feel different. Higher FOV makes movement appear faster on screen. Some players adjust slightly for FOV, while purists maintain exact cm/360 regardless.

• Should I use the same sensitivity in all games?

  For consistent muscle memory, yes. The only exception is if a game has very different movement mechanics that benefit from adjusted sensitivity. Most competitive players maintain consistent cm/360 across all FPS titles.

• What about controller sensitivity?

  This converter is specifically for mouse sensitivity. Controller sensitivity uses different scales (response curves, dead zones) that don't convert directly to mouse metrics.