Most players who ask "what's the best sensitivity" are really asking the wrong question — there isn't a best number, only a best-for-you number, and the difference is that the second one is actually findable. This guide skips the debate over whether low or high is objectively superior (we cover that tradeoff separately in our low vs high sensitivity guide) and focuses instead on the practical part: the exact process for measuring, testing, and locking in a sensitivity that fits your hand, your desk, and your game, across Valorant, CS2, and Apex alike. You can test each step live using the free browser aim trainer as you read.
The Two Numbers You Need to Stop Confusing
Before you can run a real process, you need the vocabulary to measure what you're actually changing. Raw in-game sensitivity numbers are close to useless on their own — a "2.0" in one game and a "2.0" in another can feel completely different because the underlying scaling math isn't shared between titles.
DPI: the hardware layer
DPI (dots per inch, sometimes CPI) lives on your mouse itself, set in its software or onboard memory. It determines how many counts the sensor reports per inch of physical movement — higher DPI means more on-screen travel for the same hand motion, completely independent of any game you're playing.
In-game sensitivity: the software layer
This is a multiplier the game applies on top of your DPI, and every title uses its own internal scale. This mismatch is exactly why copying a raw sensitivity number between games gives you a different actual feel each time.
eDPI: the number that actually lets you compare
eDPI (effective DPI) solves the mismatch by combining both into one figure: eDPI = DPI × in-game sensitivity. 800 DPI at 4.0 sensitivity and 1600 DPI at 2.0 sensitivity both land on an eDPI of 3200 — meaning they produce the same real speed, even though the individual numbers look nothing alike. Rather than doing this arithmetic by hand every time you tweak something, the eDPI calculator does it instantly, which matters because you'll be recalculating this constantly during the process below.
cm/360: the number your hand actually feels
eDPI is great for comparing setups, but it's still an abstract number derived from software scaling. cm/360 skips that entirely — it's simply the physical distance, in centimeters, your mouse travels across the pad to complete one full 360-degree turn in-game. It answers the only question your muscle memory actually cares about: how far does my hand have to move to spin all the way around? A 30 cm/360 turn takes the same physical effort in any game, regardless of what the eDPI numbers say on paper, which is why serious players treat it as the ground truth.
| cm/360 range | Feel | Best suited for |
|---|---|---|
| 10-20 cm | Very fast, twitchy | Quick 180s, movement-heavy games, tight close-range duels |
| 20-30 cm | Balanced-fast | Aggressive players who flick often |
| 30-40 cm | Balanced-slow | Most tactical shooter players, strong micro-control |
| 40-55 cm | Very slow, precise | Pure arm aimers, long-range precision, recoil control |
If you want the fuller breakdown of why low and high each have real tradeoffs — and how your arm-vs-wrist aiming style factors into which end suits you — that's covered in depth in the low vs high sensitivity guide. This article assumes you've picked a rough direction and now need the actual method to dial it in.
The Step-by-Step Process
This is the part most guides skip in favor of just handing you a number. Numbers copied from someone else's hand rarely fit yours — this process converges on your own, using a handful of sessions rather than five minutes of guessing.
- Lock your DPI and never touch it again. Set your mouse to a stable, common value like 800 and leave it there permanently. From this point forward, every adjustment happens through in-game sensitivity only. This single rule keeps every future comparison clean — if you're not sure what your mouse is currently set to, check with the DPI analyzer before you start.
- Pick a sane starting point, not a random one. With no prior reference, aim for roughly 30-40 cm/360, which lands most players in a genuinely controllable zone. If you'd rather start from eDPI, a medium value around 400 is a reasonable anchor. The sensitivity converter can translate whichever number you land on into the correct in-game value for your specific game.
- Physically measure your cm/360. Mark a starting point on your mousepad with tape or a finger, perform one clean in-game 360, and measure how far your mouse actually traveled. Write this number down — it becomes your anchor for every future comparison and every other game you play.
- Stress-test it with a flick drill. In the aim trainer, run a flick or click-timing exercise. Constant overshoot past the target means your sensitivity is too high for your current control. Arriving late and feeling sluggish means it's too low.
- Stress-test it with tracking. Run a tracking drill on a moving target and watch your own crosshair, not just the score. Jittery, twitchy correction is a strong sign the setting is faster than your hand can currently control cleanly.
- Adjust in small steps only — about 10% at a time. Bigger jumps make it impossible to isolate what actually changed, and they reset more muscle memory than they need to. Re-measure your cm/360 after every adjustment so you always know exactly where you stand.
- Commit for two full weeks before judging anything. Once a value feels roughly close, stop adjusting and just play it. Muscle memory needs sustained repetition to form, and almost any new setting feels slightly wrong for the first several days regardless of whether it's actually right for you.
- Re-evaluate on consistency, not your best clip. After the two-week commitment, judge based on your overall reliability — are you landing shots consistently and rarely overshooting? — rather than one highlight moment. If yes, lock it in and stop searching.
While you're running this process, don't ignore your crosshair. A clean, high-contrast reticle makes it much easier to tell whether a sensitivity change is genuinely helping you land shots or just feels different in the moment — a cluttered crosshair muddies that signal.
Troubleshooting: What Your Symptoms Are Actually Telling You
If a setting still feels off after the process above, the specific way it feels wrong usually points to the fix.
- You constantly overshoot targets → your sensitivity is too high for your current control level. Drop by 10% and re-test rather than abandoning the whole range.
- You feel slow reacting to close peeks → likely too low for your desk space or reaction style. Raise slightly, or check whether you actually have enough physical mousepad room to move freely.
- Your aim feels fine in the trainer but falls apart in real matches → this usually isn't a sensitivity problem at all. Check your FOV settings with the FOV calculator — a mismatch between how your trainer and your actual game render distance can make an identical sensitivity feel completely different.
- You keep changing settings every few days without ever feeling settled → this is the actual root problem more often than the number itself. Force yourself through the full two-week commitment window before touching anything again.
Carrying the Same Feel Across Multiple Games
Once you've found a sensitivity you genuinely like, you'll want that identical feel in every shooter you play — but since each game scales sensitivity differently under the hood, you can't just copy the raw in-game number over.
- Keep DPI identical everywhere. Since DPI lives on the hardware, it already carries across every game automatically — this is exactly why locking it early matters so much.
- Match by cm/360 for the truest transfer. Measure your turn distance in your main game, then adjust each new game's in-game sensitivity until you land on that same physical distance. This is the most accurate method available.
- Use eDPI as a fast approximation when you don't want to physically measure — it gets you close in most cases, though game-specific scaling means it won't always be pixel-perfect.
- Recheck after changing FOV or aspect ratio. Field-of-view differences can subtly shift how an otherwise-matched sensitivity feels, so run a quick flick test in the new game rather than assuming a perfect transfer.
Getting your feel consistent across Valorant, CS2, and Apex really is mostly a matter of measuring once carefully and converting deliberately from there — after that, your muscle memory works for you in every title instead of restarting from scratch each time you switch.
The Discipline That Actually Matters More Than the Number
It's worth repeating because it's the single most common mistake: the exact value you land on matters far less than your willingness to actually stick with it. Aim is a closed-loop motor skill — your brain learns, through genuinely thousands of reps, exactly how far to move your hand for a given amount of on-screen movement. That calibration only compounds if the input stays fixed. Every meaningful settings change partially wipes it out and starts the clock over.
Two players with identical hardware can land on very different "perfect" sensitivities and both end up excellent, simply because each one committed long enough to build deep, reliable muscle memory around their own number. The players who plateau are usually the ones endlessly copying whatever the latest pro is running this patch. Pick something reasonable using the process above, then treat changing it again as a rare, deliberate decision — not a weekly experiment.
Frequently Asked Questions
What counts as a good eDPI?
For most players, a balanced eDPI sits somewhere between 400 and 800, blending flick speed with enough control for precise micro-adjustments. Precision-leaning players often land lower, around 200-400, while movement-heavy players sometimes go higher. There's no single correct value — use these as guardrails, find a controllable point inside them, and commit.
What DPI should I actually run?
800 DPI is a common, reliable starting point that works well with nearly any sensor. The specific value matters far less than keeping it fixed — do all your fine-tuning through in-game sensitivity instead, and avoid switching DPI between sessions, since that breaks the consistency your eDPI and cm/360 comparisons depend on.
How do I actually keep the same feel across different games?
Keep DPI identical everywhere, then match either cm/360 (most accurate) or eDPI (a faster approximation) when configuring each game's sensitivity. Measuring your full-turn distance once and converting it per game gives the truest transfer — follow it up with a quick flick test in the new game to confirm it actually feels right.
Should I go lower or higher if I'm still not sure?
Neither direction is universally correct. Lower sensitivity favors stable, arm-driven precision and tends to suit tactical shooters; higher sensitivity favors faster turns and tends to suit movement-heavy games. What actually matters is landing on a value that lets you turn comfortably while still making small corrections cleanly, then sticking with it long enough to actually learn it.
How long do I need to wait before deciding a setting isn't working?
Give any setting a genuine two weeks of consistent play before judging it. Muscle memory needs sustained repetition to form, and a single rough session is not real evidence the number is wrong. Only make changes after that window, and even then, move in small 10% steps rather than large jumps.
Put the Process to Work
Finding your sensitivity is part math and part patience, but it always comes down to the same loop: measure, test, adjust in small steps, and commit long enough to know for sure. For the hardware side of this, see our best DPI settings for FPS games guide, and once your sensitivity is locked in, our complete guide to improving your aim covers what to actually train on top of it.
The fastest way to validate any change is with focused drills, not vibes. Open the free browser aim trainer, measure your cm/360, run a flick and a tracking exercise, and start converging on the number that's actually yours.