How to Find Your Ideal Mouse Sensitivity (cm/360 Explained)

What cm/360 Actually Means

Ask ten players what sensitivity they use and you'll get ten meaningless answers: "0.4", "800 DPI", "7 in Overwatch". None of those numbers describe anything physical, and none of them transfer between games. The measurement that does is cm/360: the distance, in centimeters, that your mouse travels across the pad to turn your character a full 360 degrees in-game.

cm/360 is the great equalizer. A player on 400 DPI with a high in-game sens and a player on 1600 DPI with a low one can have the exact same cm/360 — and their aim will feel identical, because their hands are making identical movements. When people say "low sens" or "high sens", cm/360 is what they're really talking about, whether they know it or not. A higher cm/360 number means a lower sensitivity: more physical movement per turn.

Thinking in cm/360 also forces you to think about the thing that actually matters: how far your hand moves. Aiming is a motor skill. Your brain is learning a mapping between hand distance and crosshair distance, and cm/360 is that mapping written down as a number.

How to Measure It With a Ruler

You don't need software to find your cm/360. You need a ruler and two minutes:

1. In any FPS (or a practice range), line your crosshair up on a distinct landmark — a doorframe, a sign, anything with a hard edge.
2. Place your mouse at one edge of your pad and lay the ruler alongside it.
3. Drag the mouse in a straight horizontal line — slowly and without lifting — until the crosshair comes all the way around and lands back on the same landmark.
4. Read the distance traveled off the ruler. That's your cm/360.

If your pad is too small to do a full turn in one swipe, do a 180 instead (aim at a landmark, turn until you're facing exactly away, using a landmark behind you) and double the measurement. Repeat the measurement two or three times and average it — small errors in where you stop the drag are normal.

DPI vs In-Game Sens vs eDPI

Three numbers combine to produce your actual sensitivity, and players constantly confuse them:

• DPI (dots per inch) is a hardware setting on the mouse itself: how many movement "counts" the sensor reports per inch of physical travel. It's set in your mouse software, not in the game.
• In-game sensitivity is a multiplier the game applies to each of those counts. A sens of 2.0 turns you twice as far per count as 1.0.
• eDPI (effective DPI) is simply DPI × in-game sens. It's a convenient shorthand for comparing players within the same game: 800 DPI × 0.5 sens and 400 DPI × 1.0 sens are both 400 eDPI and feel the same.

The critical caveat: eDPI is not comparable across different games, because each game translates a mouse count into a different amount of rotation. The same eDPI produces a very different cm/360 in different titles. That's why cm/360 — a physical measurement — is the only number worth writing down.

For the hardware side of this equation — what DPI to run, polling rate, and the Windows settings that silently distort your aim — see our guide to gaming mouse settings that actually matter. The short version: 400–1600 DPI is standard, and consistency in the total (your cm/360) matters far more than how you split it between DPI and in-game sens.

Typical cm/360 Ranges by Playstyle

There is no correct sensitivity, but there are ranges most players in each genre settle into, because the genre's demands push them there. Treat these as commonly used ballparks, not rules:

Two honest observations from years of watching players tune sens. First, beginners almost always play too fast — a high sensitivity feels responsive and exciting, but it amplifies every tremor in your hand and makes precise stops nearly impossible. Second, lower sensitivities shift work from the wrist to the arm, which is generally more stable for smooth tracking but slower for large flicks. Your grip style influences which end of the range will feel natural, since some grips favor wrist aiming and others favor the arm.

The PSA Method: Bisecting Your Way to a Sens

If you want a structured way to pick a sensitivity rather than guessing, the most popular approach in the aim community is the Perfect Sensitivity Approximation (PSA) — essentially a binary search over sensitivity values. It works like this:

1. Pick two bounds: a sensitivity that's clearly too slow for you and one that's clearly too fast. (Doubling and halving your current sens works fine.)
2. Play a few minutes on each bound, then set your sens to the midpoint of the two.
3. Compare the midpoint against each bound in short play sessions. Whichever half of the range felt more controllable becomes your new range.
4. Take the midpoint of the new, narrower range and repeat. After four or five iterations the range gets so narrow that further changes are imperceptible — stop there.

PSA's real value isn't that it finds a magic number — it doesn't, and no method can, because your "perfect" sens drifts with your form on any given day. Its value is that it converges quickly on a reasonable number you chose through structured comparison instead of impulse, which makes it much easier to commit to.

Consistency Beats Optimization

Here's the part most sensitivity guides bury: once you're inside a sane range, which sensitivity you use matters far less than how long you stick with it. Aim is a learned mapping between hand movement and crosshair movement, and motor learning research consistently shows that skills consolidate through repetition under stable conditions. Every time you change your sens, you invalidate part of that mapping and start rebuilding it.

Chronic sensitivity switching is one of the most common habits keeping players stuck — you'll find it alongside its cousins in our list of aim mistakes that keep you hardstuck. The player who picks a middling 35cm/360 and grinds it for three months will outshoot the player who spent those months hopping between "optimized" values every bad game.

Dialing It In on AimBetween

AimBetween has a sensitivity slider in Settings, and the trainer uses pointer lock with raw input — your OS pointer acceleration is bypassed, the same principle as raw input in a proper FPS. That means the physical-distance skills you build here transfer, as long as the slider is set to match how your game feels.

To match it: open Settings, then adjust the slider until a comfortable, familiar hand movement — the swipe you'd use to snap between two targets a screen-width apart in your main game — covers a similar distance on the trainer's screen. Then verify by feel: play a round of Flick and ask whether you're consistently overshooting (slider too high) or undershooting and dragging (slider too low). Nudge and repeat until your natural flicks land. It usually takes two or three rounds to lock in.

Test Your Sens in Flick Mode

Converting Between Games

The principle is simple: keep your cm/360 constant and everything transfers. Your hands don't know which game is running — if a 30cm swipe does a full turn in one game, set the new game so a 30cm swipe does a full turn there too, and your muscle memory carries over on day one.

In practice you have two options. Sensitivity converter tools will compute the exact in-game value for you if you know your current game, target game, and DPI. Or you can do it manually with the ruler method from earlier: measure your cm/360 in your main game, then adjust the new game's sensitivity and re-measure until the numbers match. The manual way takes five minutes and requires trusting no one's math but your own.

One honest caveat: scoped sensitivities, ADS multipliers, and differing field-of-view settings mean the transfer is never mathematically perfect across every situation — hipfire cm/360 is the anchor, and the rest you tune by feel. Once your sens is locked in, the best thing you can do for it is show up daily — a short structured session like our 10-minute aim warmup routine builds the mapping faster than marathon sessions ever will.