How Mouse DPI and Sensitivity Work
Your mouse and your game each scale your hand movement, and the combination sets how fast you turn. Understanding the two stages separately — hardware counts, then software scaling — clears up most of the myths about “high DPI” and “low sensitivity”, and it explains why two players with completely different settings can have identical aim feel.
DPI: the hardware side
DPI is dots per inch: how many counts your mouse sensor reports for one inch of physical movement. At 800 DPI, moving the mouse one inch reports 800 counts to the computer. At 1600 DPI, the same inch reports 1600 counts — finer steps, each representing a smaller movement.
A few consequences follow directly:
- Higher DPI means finer steps, not faster turning. Turning speed depends on what the game does with those counts. A high-DPI mouse at low in-game sensitivity can turn more slowly than a low-DPI mouse at high sensitivity.
- Counts are the raw material. Everything downstream — sensitivity, eDPI, cm/360 — is computed from counts. If the sensor misses or miscounts movement, no software setting can recover it.
- DPI is set on the mouse, not in the game. Most gaming mice let you switch DPI with a button or companion software, and many store the setting on the mouse itself. Your in-game sensitivity is a separate number, stored by the game.
Polling rate is a different hardware property that is often confused with DPI: it is how often per second the mouse reports its position, measured in hertz. DPI decides how many counts per inch; polling rate decides how frequently those counts are delivered. Both affect feel, but they are independent settings, and changing one does not change the other.
Sensitivity: the software side
In-game sensitivity multiplies the counts. In most games, the rotation produced by one count is:
Rotation per count = sensitivity × yaw
where yaw is the game’s rotation per count at sensitivity 1 (for example 0.022 degrees for CS2, 0.07 degrees for Valorant — community-documented values, not official publisher specifications, cross-checked 2026-10-25).
At sensitivity 2.0, each count turns you twice as far as at 1.0. At sensitivity 0.5, each count turns you half as far. Sensitivity is usually a slider or a decimal number, and its scale differs wildly between games: a “normal” sensitivity in Overwatch 2 looks like a large number (often around 5), while in Valorant it looks like a small decimal (often around 0.35). Those numbers are not comparable across games, because the yaw underneath them differs.
Why DPI and sensitivity are interchangeable (within one game)
Because turning speed is the product of the two stages, you can trade one against the other:
Turn speed ∝ DPI × sensitivity
Within a single game, these setups turn at the same speed:
| Mouse DPI | Sensitivity (CS2) | eDPI | Turn speed |
|---|---|---|---|
| 400 | 2.0 | 800 | Same |
| 800 | 1.0 | 800 | Same |
| 1600 | 0.5 | 800 | Same |
The product DPI × sensitivity is called eDPI, and it is the number players actually compare within a game. See What Is eDPI? for the full treatment, including why eDPI does not transfer across games.
So why does anyone care about DPI at all, if sensitivity can compensate? Three practical reasons:
- Step size. At very low DPI, each count represents a relatively large movement, and fine aiming can feel steppy — the crosshair jumps in visible increments rather than gliding. Higher DPI gives finer steps, which feels smoother for micro-adjustments.
- Sensor behaviour. Extremely high DPI can run into sensor or operating-system quirks in some setups, where the reported counts become less clean. There is a middle ground, not a maximum.
- Desktop use. Your mouse DPI also affects how the cursor moves outside games. A DPI that feels right in a game might feel too fast or too slow on the desktop, so most players pick a DPI that works for both and tune the game around it.
Many players settle on 400, 800 or 1600 DPI and then tune sensitivity to taste. Those are common choices, not rules — the right DPI is the one where your aim feels smooth and your desktop use feels natural.
From counts to cm/360: the physical picture
DPI and sensitivity together determine a physical quantity you can feel: how far you move your mouse for a full 360-degree turn, measured in cm/360. The formula is:
cm/360 = (360 × 2.54) / (DPI × sensitivity × yaw)
Worked example — CS2 at 800 DPI, sensitivity 1.0, yaw 0.022:
- cm/360 = 914.4 / (800 × 1.0 × 0.022) = 914.4 / 17.6 ≈ 51.95 cm
The same player at 1600 DPI, sensitivity 0.5: 914.4 / (1600 × 0.5 × 0.022) = 914.4 / 17.6 ≈ 51.95 cm — identical, as expected, because DPI × sensitivity is unchanged.
Valorant at 800 DPI, sensitivity 0.35, yaw 0.07:
- cm/360 = 914.4 / (800 × 0.35 × 0.07) = 914.4 / 19.6 ≈ 46.65 cm
cm/360 is the fair way to compare sensitivity across games, because it is a physical distance, not a game-specific number. Full explanation: What Is cm/360?.
Finding your own settings
There is no universally correct DPI or sensitivity, but there is a reliable process:
- Pick a DPI that feels good on the desktop — commonly 400, 800 or 1600 — and leave it there. Changing DPI constantly makes your muscle memory a moving target.
- Tune sensitivity in one game until tracking a moving target and flicking to a point both feel controlled, not frantic or sluggish. Note the resulting cm/360.
- Carry that cm/360 to other games using the Sensitivity Converter, instead of copying sensitivity numbers (which will be wrong, because yaw differs).
- Give changes time. A new sensitivity always feels wrong for the first few sessions. Judge it after a week of consistent play, not after one match.
- Check your mousepad. Your cm/360 must fit your available space. A 52 cm/360 on a 30 cm pad means constant lifting and repositioning. The cm/360 calculator on this site shows a mousepad indicator for exactly this reason.
Common mistakes
- “Higher DPI is better aim.” DPI alone does not aim for you. A high-DPI mouse at high sensitivity turns wildly; a low-DPI mouse at low sensitivity turns slowly. Only the product matters, plus step size.
- Copying a pro’s sensitivity number. A pro’s “0.35” in Valorant means nothing in CS2, where the yaw is different. Copy the cm/360 (if you must copy anything), not the slider number — and even then, remember that their mousepad, grip and arm length differ from yours.
- Changing DPI and sensitivity at the same time. Change one, keep the other fixed, so you know which change caused the difference in feel.
- Ignoring the desktop. A DPI that only works in one game and feels unusable everywhere else will not stick. Choose a DPI you can live with all day.
Frequently asked questions
Should I use 400, 800 or 1600 DPI?
Any of them can work, because sensitivity compensates. 800 DPI is the most common starting point: fine enough steps for smooth aiming, low enough to avoid sensor quirks, and comfortable on the desktop. Start there, tune sensitivity, and only change DPI if you have a specific reason (steppiness at low DPI, or desktop comfort).
Does Windows mouse sensitivity affect in-game sensitivity?
It can, depending on the game and whether the game reads raw mouse input. Games that use raw input bypass the operating system’s scaling entirely; games that do not are affected by it. If your aim feels inconsistent between games, check whether each game uses raw input, and keep the OS setting consistent.
Why does my aim feel different after changing DPI if eDPI is the same?
Usually step size or polling behaviour changed, or your muscle memory is recalibrating. Give it several sessions. If the difference persists and feels steppy, your DPI may be too low for fine adjustments; if it feels jittery, it may be too high for your sensor or setup.
What is the difference between DPI and eDPI?
DPI is a hardware setting (counts per inch). eDPI is DPI × in-game sensitivity — the effective sensitivity you actually feel in one specific game. DPI without sensitivity is incomplete; eDPI without naming the game is meaningless, because yaw differs between games.
Try it: Mouse DPI Calculator · cm/360 Calculator · eDPI Calculator