Tradeit Calculators Mouse DPI Analyzer

Mouse DPI Analyzer

Measure the DPI your system actually receives, using a ruler and a few swipes. No install, no sign-in, and for most browsers nothing in Windows to change first.

{{ cap.title }} {{ cap.body }}
In short

A DPI analyzer measures the DPI your system receives by comparing a distance you move the mouse against the movement your browser records. Set a distance, lay a ruler on the desk, move the mouse across it and click to end the run. Repeat a few times, because the average across runs is the trustworthy number rather than any single one.

This measurement needs a mouse

You are on a touch device, so there is no mouse sensor to measure and the tool would report nothing useful. Rather than show you a control that cannot work, here is the other route.

If you want the DPI your mouse is configured to, the how-to-check section below covers manufacturer software by name and where Windows keeps its pointer settings. Come back on a desktop when you want the measured figure.

1. Set up the measurement

A longer distance gives a better reading. Five centimetres works, ten is better if your desk allows it.

{{ distError }}
On a wireless mouse a weak signal drops counts, which reads as a lower DPI than you actually have. Plug it in or move the receiver closer if the numbers look low.
Change these two settings first
Your browser did not give us movement with operating-system scaling removed, so Windows is sitting between your sensor and this page. These are the settings that distort the reading.
{{ c.n }} {{ c.title }} {{ c.body }}
{{ zoomWarning }}

2. Run it

{{ runCountLabel }}

{{ runIntro }}

Recording run {{ liveRun }}
{{ liveCount }}
counts registered so far
Move the mouse {{ distLabel }} in a straight line, then click to end the run. Press Escape to cancel without losing finished runs.
{{ padPrompt }}
Your cursor disappears while a run is recording. That is the tool locking the pointer so you cannot hit the edge of the screen, not the page freezing.
Horizontal counts
{{ liveHorizontal }}
Vertical counts
{{ liveVertical }}
Movement counts
{{ liveMovement }}
Current DPI
{{ liveDpi }}
Movement angle
{{ liveAngle }}
Elapsed
{{ liveElapsed }}
{{ runNotice }}

3. Your measured result

{{ resultLabel }}
{{ resultText }}
{{ resultSub }}
{{ conf.label }} {{ conf.body }}
{{ s.k }}
{{ s.v }}
{{ nearestLine }}
{{ axisLine }}
{{ modeReminder }}
Every run, not just the average
Run {{ r.n }} {{ r.detail }} {{ r.dpi }}

4. Send it somewhere useful

{{ handoffSub }}

Changing DPI and keeping the same feel
Enter your current in-game sensitivity and the DPI you are moving to. This is the value that keeps your cm/360 where it is.
New sensitivity
{{ equivText }}
{{ equivNote }}

What is a DPI analyzer?

A DPI analyzer measures the DPI your system actually receives, by comparing a physical distance you move the mouse against the movement the browser records. It is a measurement rather than a lookup, which is why it can disagree with the number in your mouse software.

Those two figures come apart for a few reasons. Windows can scale movement before any application sees it. A sensor can output slightly more or fewer counts per inch than the value it was set to. And a measurement made by hand carries its own small error, which is why one run is never enough.

The honest description is this. No browser can read a sensor's hardware CPI directly, and anything claiming to is inferring it the same way we are. What this page gives you is a measured result with the spread across runs shown, so you can see how much to trust it.

Where the error comes from
{{ e.k }} {{ e.v }}

How to measure your mouse DPI

Set a distance, lay a ruler next to the mouse, move it across that distance and click to finish, then repeat. Four steps, and the fourth one is the one people skip and then wonder why their number moves around.

{{ s.n }}
{{ s.title }}
{{ s.body }}
Weekly CS2 skin giveaway, free entry Enter free for a chance to win CS2 skins Enter the giveaway

How to check what DPI your mouse is set to

If you only want to read the configured number rather than measure it, open your mouse software. Every major brand shows the current DPI, usually on the first screen, and most let you see every step on the wheel.

{{ b.brand }}
{{ b.app }}
No software, or a mouse without it
Check the box or the product page for the sensor specification, which lists the DPI steps. Office mice usually have one fixed value, commonly 800 or 1000. If the mouse has a button that changes speed, each press moves between those steps, and measuring is the only way to know which one you are on.
Where Windows keeps its pointer settings
Settings, then Bluetooth and devices, then Mouse, then Additional mouse settings, then the Pointer Options tab. That slider is not DPI. It is Windows scaling your mouse movement on top of whatever the sensor reports, which is exactly why it distorts a measurement. Our CS2 settings guide covers where it should sit.

Why your measured DPI may not match your setting

Six things move the number, and this tool removes some of them for you. The table says which, because a measurement you cannot interpret is not worth much.

CauseWhat it does to the readingHandled here
{{ m.cause }} {{ m.effect }} {{ m.handled }}

Does the DPI on the box match reality?

Usually it is close, and sometimes it is not exact. A sensor set to 800 DPI can output slightly more or fewer counts per inch than that, and the gap tends to be wider on cheaper hardware than on flagship sensors. That is the reason to measure rather than assume.

A small deviation matters less than people think. What matters is that the number you feed into a sensitivity calculation is the number your system is really using, because every figure downstream inherits the error. If your measured result sits a few percent off a round step, use the measured one.

One caveat on this page rather than a claim about any brand. Our measurement has its own error, so a small difference between the box and the reading is not proof the hardware is wrong. A consistent difference across many tight runs is worth taking seriously.

What to do with your DPI once you know it

DPI on its own tells you very little. What decides how far your crosshair travels is eDPI, your DPI multiplied by in-game sensitivity, and that is the number players compare. Feed the measured figure into the eDPI calculator to get it, along with your cm/360.

If you play more than one game, the mouse sensitivity converter carries the same physical distance per turn from one to the other, which a raw sensitivity number cannot do. For Counter-Strike specifically, the CS2 eDPI calculator also handles scoped sensitivity, which generic tools ignore.

Going from 800 DPI to 1600 DPI
Halve your in-game sensitivity. Doubling DPI doubles the counts your mouse sends per inch, so halving sensitivity puts the total back exactly where it was and your cm/360 does not move.
{{ c.from }} {{ c.to }}
The same rule runs both ways. Halving DPI means doubling sensitivity, and any other change is just the ratio of the two DPI values.

Mouse DPI FAQ

{{ f.a }}
About this tool
Marcus Hale
CS2 Trading Editor at Tradeit. Author page
Method
The browser reports mouse movement in counts while the pointer is locked. We ask for that movement with operating-system scaling removed, divide the counts by the distance you measured, and average across runs. The result is a measured estimate, not a hardware readout. Last reviewed 24 August 2026.
What this tool does not do
Everything happens in your browser. Nothing is installed, no driver is touched, no movement data leaves the page, and no setting on your machine is changed by the measurement.
Trade for the skins you actually want Browse the market and trade securely Start trading