How to Find Your Perfect Sensitivity: A Repeatable Method

I spent my first two years in competitive shooters changing my sensitivity roughly every fortnight. I would watch a pro, copy their number, play badly for three days, decide it was wrong, and change again. What I was actually doing was resetting my muscle memory to zero twenty-six times a year.

The fix was not finding the magic number. It was having a method, and then leaving it alone long enough for the method to produce a result.

Step 1: Measure in cm/360, not in-game numbers

A sensitivity of 0.5 in Valorant and 0.5 in CS2 are completely different speeds, because each engine multiplies your input by its own yaw constant. So "what sensitivity do you use" is an unanswerable question unless you both play the same game.

cm/360 — how many centimetres of mouse movement it takes to spin exactly 360 degrees — is physical and therefore universal. It is the only number worth thinking in.

Measure yours right now:

1. Put a strip of tape on your mousepad at the left edge of your mouse.
2. In-game, in a safe spot, sweep the mouse right in one continuous motion until your character has spun exactly one full turn — pick a wall detail as your reference point.
3. Mark where the mouse ended up.
4. Measure between the marks. That is your cm/360.

Do it three times and average. If you cannot complete a full turn in one sweep, do a 180 and double it.

Or skip the tape and use the sensitivity converter, which does the arithmetic from your DPI and in-game value directly.

Step 2: Set DPI once and leave it

DPI is a red herring. On any sensor made in the last five years, 400, 800 and 1600 DPI perform identically in blind testing. What matters is the product of DPI and in-game sensitivity.

Set 800 DPI if you want the most common convention, which makes it easy to read other people's settings.

Set 1600 DPI if your game has a coarse sensitivity slider and you want finer steps, or if you are on a very high-resolution display where pointer movement at 800 feels sluggish on the desktop.

Set it in your mouse's onboard software — Logitech G Hub, Razer Synapse, Corsair iCUE — and disable any DPI-shift buttons so you cannot knock it mid-game. Then stop thinking about it. All future adjustment happens in the in-game slider.

Also, right now, turn off acceleration everywhere:

• Windows: Settings → Bluetooth & devices → Mouse → Additional mouse settings → Pointer Options → untick Enhance pointer precision.
• Mouse software: any "acceleration" or "angle snapping" option → off.
• In-game: Raw input on, mouse acceleration off.

Acceleration means identical hand movements produce different results depending on speed. You cannot build muscle memory against a moving target.

Step 3: Pick a starting point by genre

Adjust the starting point for your desk and your grip. If you have less than about 40 cm of free mousepad, take 20% off the starting value or you will physically run out of space. If you are a fingertip-grip player, you have less range of motion than a palm-grip player and should also start lower.

Do not copy a specific professional. Their number is the product of their mousepad, their desk height, their chair, their grip, and a decade of accumulated habit. The genre baseline is a better starting point than any individual's setting.

Step 4: Binary search with the overshoot test

Now you converge. The whole method is one question, asked honestly after each session.

Play a session and watch for two specific failures:

Failure A — you consistently overshoot. You flick to a target and land past it, then correct back. Your micro-adjustments feel twitchy and you cannot hold a crosshair still on a strafing target. → Your sensitivity is too high. Increase cm/360 by 20%.

Failure B — you run out of mousepad, or you cannot turn fast enough. You lift the mouse mid-flick to reset. Someone gets behind you and you cannot come round in time. Your wrist is at the edge of its comfortable range on a normal turn. → Your sensitivity is too low. Decrease cm/360 by 20%.

If neither is happening consistently, you are in the right zone. Now change in 10% steps instead of 20%, and then in 5%.

Use an aim trainer to get signal faster. Aim Lab and Kovaak's both give you a number instead of a feeling. Pick two scenarios — one flicking (Gridshot or similar), one tracking (a smooth pursuit scenario) — and run five minutes of each at every candidate value, at the same time of day. Write the scores down. Over a week the numbers separate clearly, and they are far more honest than "it felt better".

A caveat worth stating: high sensitivity often produces better aim-trainer scores than it does match performance, because a trainer has no crosshair placement, no movement, and no consequences for an overshoot. Weight your real games more heavily.

Step 5: Commit for a week before judging

This is the step people skip, and skipping it is why they never converge.

The first three days after any sensitivity change feel worse. Always. Your muscle memory is calibrated to the old value and every shot is fighting it. If you judge in that window you will conclude that every change is bad, revert, and stay permanently mediocre at whatever value you started with.

Set a rule: seven days minimum before you touch it again. Put the date in your phone. If after seven days of regular play the overshoot test still points one way, make the next 20% step. If it does not, you are done — lock it in and go practise something that actually matters.

Match it across your games. Once you have a cm/360 you trust, convert it into every other shooter you play. One consistent value across four games builds muscle memory four times as fast as four different values.

What does not help

Scoped and ADS sensitivity

One thing genuinely worth setting rather than leaving default: your zoomed sensitivity should be coefficient-matched so that the same hand movement moves the crosshair the same distance on screen at every zoom level.

In most modern shooters this is a single option — Valorant and Apex both offer it directly, and CS2 players typically use zoom_sensitivity_ratio_mouse 1.0. Match it, and scoping stops being a separate skill you have to learn twice.

Once your sensitivity is settled, the next thing limiting consistency is usually frame pacing rather than aim — an inconsistent frametime makes tracking feel unreliable in a way that looks exactly like a sensitivity problem. The stuttering guide covers how to check that properly, and the eDPI calculator is there if you need to compare notes with a teammate in the same game.