Mouse Sensitivity Converter

Switching games shouldn't cost you your aim. Tell the converter what you run now. It hands back a sensitivity that covers a full 360 the same distance on your pad, so your aim works the same in the next game.

From
Game
To
Game
Counter-Strike 2 sensitivity
1.273
cm/360
40.8
From eDPI
320
To eDPI
1018
↗ Suggest an improvement

How sensitivity conversion works

Every game decides how far your view turns for one count of mouse movement. That rate is different in Valorant, CS2, Apex, and Overwatch 2. Type the same number into two of them and your crosshair travels a different distance in each, so a sensitivity that feels perfect in one throws your aim off in the next. The converter does that math for you, reading each game's turn rate and finding the value that moves your view the same distance. The aim you built doesn't reset when you switch.

What your hand actually learned is cm/360, the physical sweep of the mouse for one full turn. Hold that fixed and your aim comes with you, whatever the in-game number reads. DPI is part of the same math. Give each game its own DPI field and the distance stays the same even when those numbers differ.

eDPI is a within-game shortcut, not a cross-game one. Two games with the same eDPI still turn different amounts, so equal eDPI won't mean equal aim. Track cm/360 instead.

The match is mathematical, not a feeling. Your cm/360 lines up exactly, but the game can still feel off. FOV and input smoothing change how far things move on screen even at the same rotation distance. Give it a few hours in the new game before you adjust your sensitivity. Valorant and Apex both feel different at first even with identical cm/360.

FAQ

What is cm/360 and why does it matter?
It's the physical distance your mouse travels for one full 360-degree turn. Muscle memory is built on that distance, not on the number in the sensitivity slider. Match it across games and your aim transfers.
Is the conversion exact?
For games with a fixed turn rate, the math is exact. Games marked approximate tie aim to FOV, so the number is very close but not perfect. Do one in-game check: spin a full 360 and measure how far your hand moved.
What if my game isn't listed?
A game only goes in after its turn rate is verified by hand, so a wrong constant never reaches the converter. Missing one you play? Hit the suggest button below and we'll add it to the queue.
Should I convert my sensitivity or relearn from scratch?
Convert first. Your trained aim transfers with the matched cm/360. If the new game's FOV makes it feel off after a few hours, adjust your sensitivity slider from that baseline.

Embed the sensitivity converter on your site

Running an aim or FPS blog? Add the sensitivity converter so readers match their cm/360 across games without leaving your guide. One snippet, and you can preset the game pair so it opens on the conversion you cover.

Want the whole set on your pages? See every tool you can embed →