eDPI Calculator
Work out effective DPI (mouse DPI × in-game sensitivity). When that game has a yaw, you also get centimetres and inches per 360. Solve for a sensitivity, or keep the same eDPI when DPI changes.
eDPI calculator
For the same turn, CS2 sensitivity is (0.07 ÷ 0.022) times Valorant sensitivity, so Valorant eDPI is smaller. Zoom sensitivity is separate and is not applied.
eDPI compares only inside Valorant. cm/360 uses that yaw and does not include ADS or zoom. The sensitivity filled in for each game, and the DPI presets, are examples, not a ranking.
Reverse: find your sens
Changing DPI? Keep the same turn
Formula: new sens = old sens × old DPI ÷ new DPI. If the game rounds the sens field, pick the closest value it accepts.
This page does not read the mouse, Windows pointer speed, or raw input. eDPI = DPI × sensitivity, and that product compares only inside one game. cm/360 = 360 ÷ (DPI × sensitivity × yaw) × 2.54, with yaw in degrees per count at sensitivity 1 (Valorant 0.07, CS2 and Apex 0.022, Overwatch 2 0.0066, Fortnite 0.5555 for a decimal slider). Rainbow Six Siege and Call of Duty have no yaw here, so they show n/a. ADS and zoom multipliers are not applied. A DPI, sensitivity, or yaw of 0, or any non-finite value, shows a dash. The distance matches your hand only when the game receives one count per dot at the DPI you typed.
How eDPI works
What eDPI is
eDPI (effective DPI) is your mouse DPI multiplied by your in-game sensitivity. For example, 800 DPI × 0.35 Valorant sensitivity is 280 eDPI, and so is 400 DPI × 0.7. Inside Valorant those two turn the same amount for the same hand movement. eDPI is not comparable across games, because each game uses its own yaw. That same 280 Valorant eDPI is 280 × (0.07 ÷ 0.022), or 890.9 eDPI in CS2 when rounded to one decimal: the same turn, not the same eDPI. Use the sensitivity converter to match a turn on the games listed there, or compare cm/360.
Low and high cm/360
A larger cm/360 means more mouse travel for a full turn. That can steady small corrections, and it needs more pad. A smaller cm/360 turns farther for the same hand movement, so a small miss covers a larger angle. This page does not rank those choices. The aim trainer is a browser pointer exercise. It does not load this eDPI, this yaw, or your in-game sensitivity.
DPI presets are not a ranking
400, 800, 1600 and 3200 are buttons on this form, not a survey of what players use. The number you type is the number the formula uses. This calculator does not read the sensor, and it does not check whether firmware smooths high DPI settings.
This page does not read the mouse
If you want a counted DPI instead of the number on the box, the mouse DPI test divides pointer counts by a distance you measure. You can type that average here. Doing so still does not tell this page whether the game uses raw input, or whether Windows pointer speed is scaling counts. Polling is not part of the math. The mouse polling rate test counts pointer events the browser delivers. It does not read the USB polling rate, and it does not change these results.
Related tools
Match a turn on the games listed in the sensitivity converter, count movement over a measured distance with the mouse DPI test, warm up pointer aim in the aim trainer (it does not apply this eDPI), or count browser pointer events with the mouse polling rate test.
Frequently asked questions
What is eDPI?
eDPI is mouse DPI multiplied by the in-game sensitivity you type. For example, 800 × 0.35 = 280. Two setups with the same eDPI turn the same amount in that game. The product is not comparable across games, because each game uses its own yaw.
How is cm/360 calculated?
cm/360 = 360 ÷ (DPI × sensitivity × yaw) × 2.54. Yaw is degrees per mouse count at sensitivity 1. This page uses Valorant 0.07, CS2 0.022, Apex 0.022, Overwatch 2 0.0066, and Fortnite 0.5555 when the slider is a decimal (8% is 0.08). Inches per 360 are that distance divided by 2.54. A DPI, sensitivity, or yaw of 0, or any value that is not finite, shows a dash rather than Infinity.
Why is cm/360 n/a for some games?
Rainbow Six Siege and Call of Duty have no yaw on this page. Siege also uses a config multiplier and per-scope ADS values. Call of Duty scaling changes by title, FOV, and ADS. A stand-in yaw would not match your settings, so those games show n/a instead of a distance. eDPI is still DPI × sensitivity, and it only compares setups inside the same game.
Does this calculator read my mouse or Windows settings?
No. It does not read the mouse, Windows pointer speed, raw input, or Enhance Pointer Precision. It only uses the DPI and sensitivity you type. If the game does not receive one count per dot at that DPI, the cm/360 on screen will not match your hand.
Are ADS and zoom sensitivities included?
No. Results use the hip-fire sensitivity you type. ADS, zoom, scope, and targeting multipliers are separate, and this page does not apply them.
How do I keep the same turn when I change DPI?
New sensitivity = old sensitivity × old DPI ÷ new DPI. That keeps eDPI the same, so cm/360 stays the same inside one game. If the game rounds the field, pick the closest value it accepts. A new DPI of 0, or any DPI outside 50 to 100,000, shows a dash.
Can I copy eDPI from one game to another?
Not as the same number. For example, 280 eDPI in Valorant is the same turn as 280 × (0.07 ÷ 0.022), which is 890.9 eDPI in CS2 when rounded to one decimal. Use cm/360, or the sensitivity converter, for games listed there. Games marked n/a cannot be matched from this page.