Free tool · Mouse DPI test · cm or inches
This mouse DPI analyzer measures the DPI your mouse really delivers. Set the mouse to a DPI, move it a distance you measured with a ruler in centimetres or inches, and read how many counts that produced: counts divided by inches is your real DPI, and the gap to the number on the box is your mouse’s DPI deviation. It doubles as an eDPI calculator, cm per 360 calculator and sensitivity converter. Everything runs in your browser, and it says plainly where a browser reading can and cannot be trusted.
Nothing you enter or move is uploaded, stored or logged.
Three steps: set up, move a measured distance, read the result.
A mouse at 800 DPI should report about 3,150 counts for 10 cm.
The same three steps work with any mouse and any ruler. The analyzer above does the arithmetic; this is why each step matters.
Pick the DPI you want to test in the mouse’s own software, and turn off anything that changes movement after the sensor: pointer acceleration and per-app sensitivity boosts. In Windows, “Enhance pointer precision” is the setting Microsoft describes as making the pointer more accurate when moving slowly, and Windows applies pointer acceleration (which Microsoft calls ballistics) to ordinary pointer movement. Test with it off. Windows also has a pointer speed slider; players usually leave it on the middle notch, but we could not find a Microsoft page that documents that notch as a neutral, 1:1 setting, so treat it as convention, not fact.
Put a ruler or tape measure beside the mouse pad, mark where the mouse starts, and decide the distance: 10 cm is a good first choice. Slide the mouse in a straight line along the ruler and stop exactly on the mark. Longer is better: a 10 cm move read to the nearest millimetre is only good to ±1%.
Use the capture pad on this page, or a number you read somewhere else (a game’s sensitivity readout, a mouse-software test area). Then enter the distance, the counts and the DPI you set. The analyzer shows counts per inch, the deviation from the setting and a verdict that respects how precisely you measured.
A reading is only as honest as the path it took. These are the parts of the path you control, with the documentation each claim comes from.
Microsoft’s mouse settings guide describes “Enhance pointer precision” as making the pointer more accurate when moving slowly. That is acceleration, which is the opposite of what you want while measuring, so switch it off. Its own Win32 documentation says ordinary pointer movement gets acceleration applied, while raw input does not.
Microsoft Support: Change mouse settingsMicrosoft says WM_INPUT data comes directly from the HID stack and has no ballistics applied. Source-engine games have an m_rawinput setting for it; Valve’s Team Fortress 2 list shows its default as 0.
Microsoft Learn: Taking Advantage of High-Definition Mouse MovementThat is what the capture pad does. MDN documents the unadjustedMovement option as the way to disable OS-level acceleration for pointer lock.
MDN Web Docs (Mozilla): Pointer Lock API: movementX, movementY and unadjustedMovementYaw is the number of degrees the view turns per mouse count at sensitivity 1. Only values a publisher documents are listed.
| Game | Yaw (m_yaw) | Default sensitivity | Source |
|---|---|---|---|
| Counter-Strike 2 | 0.022 | 2.5 | Valve Developer Community |
| Team Fortress 2 (Source engine) | 0.022 | not listed | Valve Developer Community |
Games not listed here (VALORANT, Overwatch, Apex Legends, Fortnite and others) are left out on purpose: their publishers do not document a yaw on a page we could read. Choose “Another game” in the converter and type the value from that game’s own documentation.
A browser sees the mouse after the operating system has processed it. Pointer movement on the web reaches a page as movementX and movementY, which MDN documents as the difference between successive screen positions. The Pointer Lock API can ask for “unadjusted” movement, which MDN says bypasses OS-level acceleration. Even so, nothing guarantees the unit is a raw sensor count on every screen, browser and scaling setting, and we could not verify it for yours. So the capture pad is a fast, useful reading, and a game’s raw-input readout is the reference.
The method is old and it works because a ruler is the one thing in the loop nobody has tampered with. Move a known distance, count, divide. The uncertainty is simply one ruler division divided by the distance, which is why the analyzer shows the measuring precision beside the verdict and never calls a small gap a defect.
We deliberately do not list yaw values for VALORANT, Overwatch, Apex Legends or Fortnite. None of those publishers documents one on a page we could read, and the numbers that circulate online are not verifiable from here. Valve does publish its own: the Valve Developer Community lists m_yaw as 0.022 for Counter-Strike 2 and Team Fortress 2. Type any other yaw into the converter and it works the same.
Real DPI is counts divided by inches. A centimetre distance is divided by 2.54 first. The deviation is (measured minus claimed) divided by claimed, and the verdict compares it with the measuring precision of your move (one ruler division divided by the distance), not with a threshold we invented.
A game turns your view by yaw × sensitivity degrees for each count, so a full turn is 360 ÷ (yaw × sensitivity) counts, and dividing by DPI gives inches (multiply by 2.54 for cm). eDPI is DPI × sensitivity. To hit a target cm per 360, the tool solves the same equation for sensitivity.
The pad adds up movementX from mouse-move events. With pointer lock the mouse can travel as far as you like without leaving the pad; without it, movement counts only while the pointer is over the pad. Pointer lock is requested with unadjusted movement first, and falls back to normal if the browser refuses. Nothing you move is stored or sent anywhere.
Move the mouse a distance you measured with a ruler, count what the computer reports for that move, and divide counts by inches. At 800 DPI, a 10 cm move should report about 3,150 counts (10 cm is 3.94 inches). If you read a very different number, the mouse is not delivering the DPI it is set to, or something between the sensor and the reading (acceleration, scaling) has changed it. The analyzer above does the division and shows the deviation.
eDPI, or effective DPI, is your mouse DPI multiplied by your in-game sensitivity. It lets you compare settings across different DPIs: 800 DPI at 2.5 sensitivity is 2,000 eDPI. eDPI is only a fair comparison between games that share the same yaw, so for anything else use cm per 360, which is exact whatever the game.
We do not publish a pro average, because we could not find one from a source we can check. Pro-settings sites list players one at a time, but no game publisher documents a typical DPI, and copying numbers from a ranking page would not meet our standard for figures on this site. What is safe to say: DPI is a hardware setting, and what defines your aim is cm per 360, the physical distance you move for a full turn. Work out yours in the converter and compare that.
Not by itself. Logitech describes DPI as a measure of how responsive a mouse is to movement: a higher DPI moves the pointer further for the same physical distance. It does not make you more accurate on its own. Doubling DPI and halving sensitivity gives the same turn: 800 DPI at 2.5 and 1,600 DPI at 1.25 both need 20.8 cm for a full turn at a 0.022 yaw.
cm/360 is how far you move the mouse, in centimetres, to turn your character a full 360 degrees. It is 360 divided by (yaw × sensitivity) counts, divided by DPI, converted to cm. In Counter-Strike 2, whose yaw Valve lists as 0.022, 800 DPI at its default 2.5 sensitivity is 20.8 cm per 360 (8.2 inches).
Three things. First, your measurement: a 10 cm move read to the nearest millimetre cannot show anything under about 1%, so a small gap is often just the ruler. Second, the path between sensor and reading: Microsoft’s documentation says ordinary pointer movement in Windows has acceleration applied and is limited to screen resolution, while raw input does not, so a browser or desktop reading can differ from what a game with raw input sees. Third, the mouse itself may count slightly differently from its setting. We could not find a first-party figure for how large that can be, so we do not quote one.
In practice, yes. Logitech notes that mouse sensitivity is sometimes called dots per inch (DPI) or counts per inch (CPI). CPI is the more literal term: it counts what the sensor reports per inch of movement, not printed dots. This page uses DPI because that is what most mice and games call it, and CPI in the maths.
Match cm per 360, not the sensitivity number. Enter your DPI, sensitivity and the game’s yaw in the converter to get cm per 360, then type the same distance into the target game’s yaw to get its sensitivity. We include yaw only for Counter-Strike 2 and Team Fortress 2 (Source engine), the ones Valve documents; for any other game, find its yaw in the game’s own documentation and type it in.
Every figure the calculator uses was checked against these pages on .
Published. Measure mode (real DPI, deviation and measuring precision from a distance in cm or inches, with a capture pad), Convert mode (eDPI, cm and inches per 360, target-sensitivity solver, DPI-change solver) and yaw values for the two Valve games whose yaw Valve documents. Every source was re-read on 29 September 2026.
Lead Editorial, Virtwave · Built and maintains this calculator
Layla leads the Virtwave content desk. She oversees every blog post before publication, with a focus on long-form gift card guides, payment wallets, and SEO best practice for the gift card industry.
Data & Market Research Lead, Virtwave · Checks every figure before an update
Noor runs market research for Virtwave, tracking gift card volumes, redemption patterns and fraud trends across the 80+ countries we deliver to. She compiles our data reports from primary government sources (FTC, central banks) and the major market-research houses, and cross-checks every figure against our own transaction data before publication.
Virtwave sells gift cards and game top-ups, not mice, so we gain nothing from what your DPI turns out to be. Nothing you enter or move on this page leaves your browser.
You are welcome to quote any figure on this page. Please link back to the calculator so your readers can check the numbers when Roblox changes them — we keep this page up to date.
<a href="https://www.virtwave.com/tools/mouse-dpi-analyzer">Mouse DPI Analyzer by Virtwave</a>Farah, L. (2026). Mouse DPI Analyzer. Virtwave. https://www.virtwave.com/tools/mouse-dpi-analyzerVirtwave is not affiliated with, endorsed by or sponsored by Valve Corporation, Microsoft, Logitech or Mozilla. Product and game names are used for identification only.
Click a question to see the answer
Select a question below
to get instant answers