Mouse DPI Test — Measure Your Real DPI Online
This mouse dpi test measures the DPI your mouse actually reports, not the number printed on the box. Enter the distance you are about to move and the DPI your mouse is supposed to be on, click the red dot, pull the mouse that far across the desk in one straight horizontal move, then click again. The page counts the pointer movement it receives, divides by the distance in inches, and reports the measured DPI, the error against your rated setting, and an average across attempts. Read the limits section before trusting the figure: a web page only sees the movement the operating system hands it.
How the measurement works
DPI is counts per inch, so measuring it needs two numbers: how many counts the mouse reported, and how many inches your hand moved. The tool handles the first — clicking the start dot asks the browser for pointer lock, which frees the cursor from the screen edges, then sums horizontal pointer deltas until you click again. At a true 800 DPI, a 3 cm (1.18 in) pull should produce roughly 945 counts.
You supply the second number, which is why the setup matters more than the click. Tape a ruler to the desk, line the mouse up with a mark, and move to another mark without lifting or arcing. Use a longer distance than the 3 cm default — 10 cm makes a 2 mm hand error worth 2% instead of 7%. Run the mouse DPI test four or five times; the history log keeps every attempt, and the average beats any single pull. If the cursor also stutters or drifts while you drag, the buttons or the sensor may be the real problem — check those with the mouse tester first.
Set these before you measure, or the number is wrong
Anything that scales pointer movement between sensor and browser gets measured as if it were DPI. Clear these first:
- Windows pointer speed: set it to the neutral notch — 6/11 in Control Panel, 10/20 in Settings. Every other position multiplies the counts before any application sees them.
- Enhance pointer precision: off. It is acceleration — move faster and the same centimetre produces more pointer movement, so the result changes with how quickly you pull.
- macOS tracking speed: macOS applies an acceleration curve System Settings cannot switch off, so readings on a Mac are indicative at best.
- Browser zoom and display scaling: zoom at 100%, and note that 125% or 150% Windows scaling changes how device pixels map to the pixels the page counts.
- Mouse software: note which DPI stage is active, turn off angle snapping and in-driver acceleration, and check X and Y DPI match.
- Surface: measure on the pad you actually use, mouse flat.
The display PPI calibration panel is a separate sanity check: match the on-screen rectangle against a real credit card to learn your screen's pixel density. It does not feed the DPI result, which depends only on the distance you entered.
Why the measured DPI is never exactly the advertised number
A gap of a few percent is normal, not a defect. Optical sensors carry a tolerance of roughly 1–5%, and the count rate also depends on how high the lens sits above the surface — worn feet, a different pad, glass versus cloth all move the figure. Two identical mice set to 1600 can measure differently, and owners regularly report a mouse set to 400 landing anywhere in the 370–410 range.
Two things make the gap bigger than tolerance. The first is interpolation: many sensors have a native resolution (commonly 800, 1600 or 3200), and any stage between those is calculated rather than sensed, which adds an offset and jitter. The second is software you forgot to neutralise — if your measurement is more than about 10% off the rated value, suspect acceleration, a non-neutral pointer speed slider, browser zoom or display scaling long before the sensor.
DPI, CPI and sensitivity are three different layers
DPI and CPI describe the same hardware setting. CPI — counts per inch — is the correct term, because a mouse reports counts, not printed dots; DPI is borrowed from printing and stuck because vendors put it on the box. Either way, it is the only layer that lives in the mouse.
Sensitivity is the layer above. Windows pointer speed multiplies counts for the desktop, and each game applies its own multiplier on top, which is why one 800 DPI mouse feels different in two games. The product decides how far you turn per centimetre of pad: multiply DPI by in-game sensitivity with the edpi calculator to get one comparable number, and use the sensitivity converter to keep the same physical aim in a game that scales its slider differently. Measure your DPI first: both calculations are only as accurate as the DPI you feed them.
What DPI should you actually use for gaming?
For aim-heavy shooters, between 400 and 1600, with 800 as the sane default. Low DPI with a large pad gives more hand travel per degree of rotation, which is why competitive players train in that range; the usual target is a 360° turn taking 25–40 cm of pad. Higher DPI is not more accurate — each count simply covers more screen, so hand tremor is amplified too.
High DPI earns its place on a 4K desktop and in games whose sensitivity slider is so coarse that a low DPI leaves no usable steps. The practical rule: pick a stage your sensor supports natively, keep it, and change your feel through in-game sensitivity — muscle memory tracks the combined value, not the DPI alone.
The honest limits of a browser DPI test
This test is accurate to a few percent at best, and the biggest source of error is you. It depends entirely on how precisely you measured a real-world distance by hand: over a 3 cm pull, being 1 mm out is already a 3% error, and a curved path or a mouse that lifts at the end adds more. Longer distances and averaging runs reduce this; they do not remove it.
The second limit is the operating system. The page reads pointer deltas as the OS delivers them, so any acceleration applied on the way — Enhance pointer precision on Windows, the built-in curve on macOS — is already baked into the counts, and a non-neutral pointer speed slider or display scaling silently rescales them. A browser cannot read the sensor's configuration register, so it can never state your DPI with the authority of the vendor software that set it.
What it is genuinely good for: telling whether an unlabelled mouse is roughly 800 or roughly 1600, confirming a DPI stage changed when you pressed the button, checking one stage really is double another, and catching a setup where acceleration or scaling is mangling every pointer input. Treat it as an estimate with an error bar, not an instrument reading.
Frequently asked questions
Can I find out the DPI of my mouse without the gaming software?
Yes, by measuring it — Windows itself never stores a DPI value, so there is nothing to look up in Settings or the registry. Move the mouse a known physical distance and divide the pointer counts by that distance in inches, which is what the test above does. Look up the model's default stage on the vendor spec page, then confirm it by measuring; expect the two to agree within a few percent rather than exactly.
Why is my measured DPI different from the DPI I set?
A 1–5% gap is normal hardware tolerance, not a fault. Sensor lens alignment, how high the sensor sits above the pad, mouse feet thickness and pad texture all shift counts per inch, so two identical mice on the same setting can track slightly differently. Above roughly 10%, stop blaming the mouse: that size of error almost always means pointer acceleration, a non-neutral Windows pointer speed slider, browser zoom or display scaling is still active.
What DPI does everybody play on?
Most competitive shooter players sit between 400 and 1600, with 800 the most common single answer. The DPI on its own is not the setting that matters — DPI multiplied by in-game sensitivity is, because that product decides how far you rotate per centimetre of pad. Pick a stage your sensor supports natively, then tune the in-game slider until a 180° turn takes a comfortable amount of desk, usually 12–20 cm.
Do mice perform worse at higher DPI?
Above the sensor's native resolution, yes. Stages beyond native are interpolated — the mouse is scaling data it never sensed — which adds jitter and a bigger gap between set and measured DPI. At or below native, the sensor is fine and the limitation is your hand: every count covers more screen, so tremor is amplified along with the movement. Higher DPI is faster, not more precise.
What is the difference between DPI and CPI on a mouse?
They are the same setting under two names. CPI, counts per inch, is the accurate term: a mouse sensor reports movement counts, and the count rate per inch is what you are changing. DPI — dots per inch — comes from printing and survived because vendors print it on the box. A handful of specifications are genuinely different: IPS is tracking speed, polling rate is report frequency, and neither changes counts per inch.
Windows has two mouse sensitivity sliders — how can I know my true DPI?
Neither slider is DPI. The 1–20 slider in Settings and the 1–11 slider in the old Control Panel are the same value shown twice, and both are a multiplier Windows applies after the mouse has already reported its counts. Neutral is 10/20, which is 6/11 — anything else rescales every input. Set it neutral, turn Enhance pointer precision off, then measure; only that combination gives you the mouse's own DPI.
What can cause a mouse's DPI to change?
Usually the surface or the feet, not the sensor. Worn or replaced mouse feet change the sensor's height above the pad, and a swapped pad changes how much surface detail it tracks — both shift measured counts per inch by a few percent, enough to feel wrong. Also check the obvious: a DPI button pressed by accident, a profile that reverted after a firmware update, or onboard memory overriding the software profile.