Mouse Sensitivity Converter
Estimate a starting sensitivity across 57 legacy game profiles, then verify it in-game.
Loading the 57 legacy profiles...
How to use the sensitivity converter
- Select the source and target profiles, enter your current in-game sensitivity, and enter both DPI settings.
- Use the result as a starting estimate. The 57 profiles retain the site's legacy coefficients; they have not been independently validated against current versions of every game.
- Check the target game's allowed sensitivity range and rounding. A blank result means invalid input or a result outside the profile's positive range.
- Verify the setting in the actual game before replacing your saved setup.
What the calculation covers
The profiles express sensitivity on one reference scale, adjust once for source DPI divided by target DPI, and invert the target profile. For a linear same-game scale, doubling DPI halves the required sensitivity. The Battlefield profiles include an offset, so that simple numeric rule does not apply to their sliders.
There is no FOV, aspect-ratio, zoom, ADS or acceleration correction. Equal turn distance does not guarantee the same visual feel. The Counter-Strike entry is the legacy CS:GO profile; it is not a separately verified current CS2 profile.
Turn-distance assumptions
The model uses 360 divided by (0.022 × reference sensitivity × DPI) for inches, then multiplies by 2.54 for centimetres. Valve's Source SDK mouse code documents the 0.022 reference yaw factor. This supports the reference model, not the accuracy of every legacy profile. A full camera turn is not applicable to osu!, so those conversions show N/A for turn distance.
For a DPI change within one linear-scale game, a worked arithmetic example is 800 DPI × 1.0 sensitivity = 400 DPI × 2.0 sensitivity. Keep the game's other input settings unchanged and check it in practice.
For a fuller procedure, see the sensitivity conversion guide and same-game eDPI calculator.
Frequently asked questions
Does matching eDPI match different games?
No. DPI multiplied by sensitivity is comparable only within the same game and input mode. Different games use different scales; this converter applies legacy profile estimates as a starting point.
What does the modelled cm/360 mean?
It estimates the mouse distance for a full camera turn under the selected profile assumptions. It changes with DPI and sensitivity. It is not a physical measurement, does not match FOV or scoped aim, and is not applicable to a 2D cursor game such as osu!.
How should I verify a converted setting?
In the target game, keep the input mode and zoom state fixed. Mark a starting point, measure the mouse distance for a full turn, repeat, and adjust the setting if the observed distance differs. Game updates and non-default controls can invalidate a legacy profile.