The Definitive Guide to Mouse DPI, CPI Sensitivity & In-Game Aim Mechanics
Understand hardware CPI vs software DPI, calculate eDPI and cm/360 physical distance, avoid sensor smoothing latency, and optimize your gaming sensitivity.
01.DPI vs. CPI: Understanding Sensor Sensitivity
DPI (Dots Per Inch) and CPI (Counts Per Inch) refer to the exact same metric: the number of discrete position reports (counts) sent to the computer for every 1 physical inch (2.54 cm) of mouse movement across a mousepad.
While "DPI" originated from printer ink resolution, "CPI" is the technically correct term used by sensor engineers. At 800 CPI, moving your mouse 1 inch across your desk generates 800 coordinate counts for the operating system.
02.Calculating eDPI & Physical cm/360 Distance
Comparing sensitivity between players using different hardware DPI and in-game sensitivity sliders requires calculating Effective DPI (eDPI):
For example: a player using 800 DPI at 0.35 sensitivity in Valorant has an eDPI of 280 (38.5 cm/360). A player using 1600 DPI at 0.175 sensitivity also has an eDPI of 280 — producing identical physical in-game rotation distance!
03.Why 1600 DPI is Superior to 400 DPI in Modern Gaming
Many esports veterans historically used 400 DPI out of habit. However, extensive motion latency testing reveals that 1600 DPI significantly reduces initial movement input delay compared to 400 DPI:
At 400 DPI, your hand must move physical 0.0635 mm before the sensor registers a single count. This introduces up to 4ms - 8ms of start-of-motion delay.
At 1600 DPI, physical motion requires only 0.0158 mm to send the first count, cutting motion initiation latency down to under 1ms.
04.How to Use the MouseTests True DPI Measurement Arena
Many mouse sensors suffer from factory DPI variance (e.g. set to 800 DPI but actually measuring 840 DPI due to lens distance tolerances). Our DPI Analyzer lets you physically slide your mouse across a measured 1 inch or 5 cm line to calculate your sensor's exact native DPI output.