Game sensitivity converter
Keep your aim consistent across FPS games. The invariant is cm/360 — the mouse travel for a full turn — so your muscle memory transfers even when each game's sensitivity number differs. Enter your source game's sensitivity and DPI, pick the target game, and it gives the matching sensitivity and the true cm/360.
Related tools
All Games & puzzles tools →Need Target sensitivity, cm / 360°, inches / 360°? The Game sensitivity converter derives it from Source game, Source sensitivity, Source DPI, Target game, Target DPI (0 = same as source) in one step. For instance, with Source game = cs2, Source sensitivity = 2, Source DPI = 800, Target game = cs2 and Target DPI (0 = same as source) = 0 it returns Target sensitivity = 2, cm / 360° = 25.977 and inches / 360° = 10.227.
How to use it
- Enter your values: Source game, Source sensitivity, Source DPI, Target game, Target DPI (0 = same as source).
- Read the result instantly: Target sensitivity, cm / 360°, inches / 360°.
Frequently asked questions
What does the Game sensitivity converter actually compute?
It takes Source game, Source sensitivity, Source DPI, Target game and Target DPI (0 = same as source) and derives Target sensitivity, cm / 360° and inches / 360° from them. The calculation is live as you type, so the result updates on every change.
What information do I need to provide?
5 values: Source game, Source sensitivity, Source DPI, Target game and Target DPI (0 = same as source). Nothing else is required — no account, no file upload.
Can you show a worked example?
With Source game = cs2, Source sensitivity = 2, Source DPI = 800, Target game = cs2 and Target DPI (0 = same as source) = 0, the calculator returns Target sensitivity = 2, cm / 360° = 25.977 and inches / 360° = 10.227. Those figures come from running this exact tool, so you can reproduce them by entering the same values.
What happens if I enter larger values?
It moves a lot. Using Source game = valorant, Source sensitivity = 4, Source DPI = 1,600, Target game = valorant and Target DPI (0 = same as source) = 5 instead, Target sensitivity goes from 2 to 1,280 — which is why it is worth testing a few scenarios rather than trusting a single figure.
Which “Source game” option should I choose?
You can pick between « cs2 », « valorant », « overwatch2 », « apex », « fortnite » and « cod ». Each one changes what the calculator works out, so switch and compare — the default is « cs2 ».
What does it give for smaller values?
Scaled down to Source game = cs2, Source sensitivity = 1, Source DPI = 400, Target game = cs2 and Target DPI (0 = same as source) = 1, Target sensitivity comes out at 400. The relationship is worth checking at both ends before you rely on a single result.
When would I actually use this?
Comparing before committing: whether a build really does more damage, whether this season's ratio moved or just the sample size, what a currency bundle costs per unit, and what sensitivity keeps your aim identical after switching game.
What is the most common mistake?
Comparing two figures measured under different conditions. A ratio across two modes, a damage number with the reload left out, a sensitivity compared without matching the mouse's own resolution, a currency rate taken from a different pack size — each is arithmetic that is correct and a comparison that is not. Fix the conditions first, then compare.
How accurate is it, and what are the limits?
Approximate — based on each game's horizontal yaw. Games with non-linear or ADS-specific sensitivity (Fortnite, some CoD modes) may differ slightly; cm/360 is the reliable invariant.
What is the difference between the Game sensitivity converter and the In-game currency converter?
This one returns Target sensitivity and cm / 360°; the In-game currency converter returns Result and Currency / value. That is the whole difference — open the one whose figure you need.