Mouse Sensitivity Converter
{{ intro }}
{{ pairLine }}
Measured in the selected aim mode, with the same scope, loadout and DPI kept throughout. Two source runs check repeatability; no game coefficient is used.
{{ worldFovNote }}
Calculated turn distances
Both columns use the selected reference profiles, not independent in-game measurements.
{{ fromShort }} reference{{ toShort }} reference
{{ tableTitle }}
Common {{ fromName }} values with their {{ toName }} equivalents. The converted sensitivity does not change with DPI, but the distance per 360 does, so all three DPI columns are shown.
Target for {{ toName }}
{{ measuredStatus }}
- Source average
- {{ measuredAverage }}
- Source run spread
- {{ measuredSpread }}
- Target difference
- {{ measuredDifference }}
Adjust the target game's sensitivity until its measured distance matches this target. Re-measure after changing zoom, loadout or DPI. No slider value is inferred from an unknown response curve.
{{ answerBlock }}
How to convert mouse sensitivity between games
To convert mouse sensitivity between games, enter your DPI and your current sensitivity, then pick the game you are moving to and read off the value the converter returns. It works by holding your distance per 360 degree turn constant, which is the only property two games with different sensitivity scales can actually share.
Games supported
30 games, either directionChoose any two supported games above. Game pages cover their sensitivity settings and conversion limits. Profiles assume the settings shown in the calculator; custom camera controls and acceleration can change the result.
{{ carryTitle }}
The sensitivity number converts and nothing else does. Raw input, mouse acceleration, scoped and ADS multipliers, field of view and aspect ratio all stay behind in the game you came from, and they are where people conclude the conversion was wrong when it was not. Our CS2 settings guide covers where each of these lives.
What is cm/360 and why conversions use it
cm/360 is how far your hand has to travel for the camera to turn all the way around, and it is the figure every conversion holds constant. It is measured in centimetres of real desk, so it means the same thing in every game, at every DPI, on every mouse.
That is why this converter holds it constant. Two games can never share a sensitivity number, because each one scales its slider differently, but they can share a physical distance. When the cm/360 figures above match, your muscle memory carries over.
If you want the same figure alongside your eDPI, the eDPI calculator returns eDPI, cm/360 and inches/360 from your DPI and sensitivity, and it plots the result against the range players in your game actually use.
Why your converted sensitivity feels different
A converted sensitivity feels different because matching the distance per 360 does not match what you see on screen. Field of view, resolution and aspect ratio all change how far a target appears to travel for the same physical mouse movement, so a correct conversion can still feel fast or slow for the first few sessions.
Give it a week before changing anything. Most people who abandon a converted setting do it in the first hour, then spend a month rebuilding muscle memory they already had. If it still feels wrong after that, adjust in steps of five percent rather than starting over, and rule out frame pacing and your launch options before blaming the number.