Type your mouse DPI and in-game sensitivity; get your eDPI, your cm/360 where the game supports it, and where you sit against the typical pro range.
What eDPI actually measures
eDPI is mouse DPI multiplied by in-game sensitivity, and it answers one question: how far does your crosshair travel for a given hand movement — inside one game. 400 DPI at 1.0 and 800 DPI at 0.5 both land on 400 eDPI, so two players with those setups feel near-identical mouse speed. That is why pros and coaches quote eDPI instead of raw DPI. The product hides two dials: one on the mouse (DPI), one inside the game (sensitivity). Different games scale that second dial differently — which is exactly why a raw sensitivity number from CS2 means nothing in VALORANT. Multiplying them collapses the dials into one meaningful figure; this tool does the multiplication for the six games we track, each with its own documented convention.
Typical pro ranges, game by game
The bar in the calculator positions your eDPI against the range we see most tracked pros using. The table below lists those ranges and each game's sensitivity convention — because "eDPI" is not computed the same way everywhere. CS2, VALORANT and Apex use Source-style linear sensitivity: the formula is a plain multiplication and the cm/360 values are comparable across those three games. PUBG and Fortnite set sensitivity as a percentage, and Siege uses a horizontal-sensitivity multiplier — community conventions that keep the number comparable within each game, which is why cm/360 is not shown for them.
| Game | Sensitivity system | Typical pro range (eDPI) | ≈ cm/360 |
|---|---|---|---|
| CS2 | Source-style · DPI × sens | 600–1200 | ≈ 35–69 cm |
| VALORANT | Source-style · DPI × sens | 200–400 | ≈ 33–65 cm |
| Apex Legends | Source-style · DPI × sens | 1200–1800 | ≈ 23–35 cm |
| PUBG | Percentage · DPI × sens ÷ 100 | 250–450 | n/a |
| Fortnite | Percentage · DPI × X-Axis sens ÷ 100 | 48–80 | n/a |
| Rainbow Six: Siege | Community · DPI × horiz. sens × 0.02 | 60–120 | n/a |
cm/360: the number that travels between games
eDPI only makes sense inside one game, because each engine has its own yaw — how much the view turns per mouse count. VALORANT's yaw (0.07) is roughly three times CS2's (0.022): feed the same physical motion into both and the VALORANT crosshair swings much further per count. cm/360 — centimetres of pad for one full rotation — skips the engine math and measures the outcome on your desk. It is the fairest way to compare your sensitivity against another player's or another game's: - Under 30 cm — fast/high sensitivity: quick flicks, smaller pad, more wrist. - 35–45 cm — the middle band most FPS pros land in. - Over 55 cm — slow and deliberate: big pads and arm aim for maximum stability. Worked example: 800 DPI × 0.4 in VALORANT is 320 eDPI. With yaw 0.07, a full 360° takes 360 ÷ (320 × 0.07) ≈ 40.8 cm of mouse movement. The same eDPI in CS2 would feel very different, because CS2's yaw is 0.022 — the formula is what makes the comparison fair.
Switching between games
Between CS2 and VALORANT — the two most common transfers — the ratio is fixed by their yaw values. Multiply VALORANT sensitivity by 3.18 to get matching CS2; multiply CS2 by 0.31 to get VALORANT. So 0.4 VALORANT ≈ 1.27 CS2, and both produce roughly the same cm/360. Apex shares CS2's engine constants, so the same approach works there. Percentage-based games (PUBG, Fortnite) and Siege have no clean cross-game constant — their sensitivity is defined by their own UI, not an engine yaw. Treat them as self-contained, and only bridge to other games through cm/360.
Using this to find your own sensitivity
The calculator diagnoses; it doesn't prescribe. Inside the pro range, leave it alone — chasing someone else's exact value rarely helps. Far outside it, the range is a starting point, not a rule. A repeatable process: 1. Set the base dials first. Run 400 or 800 DPI, keep Windows pointer speed at the 6/11 notch (no acceleration), and enable raw input in the game. Every conversion above assumes this. 2. Start near the middle of the range for your game and play a full session. Only change when a pattern is obvious — consistently overshooting flicks, or needing two swipes to turn. 3. Move in small steps. Adjust in-game sensitivity by 5–10% per change, then give it time. Daily changes teach muscle memory nothing. 4. Change one thing at a time. Don't swap mouse, DPI and sensitivity in the same week — you won't know which change did what.
FAQ
Is a high eDPI good or bad?
Neither on its own. High eDPI moves the crosshair fast for a small hand movement — great for flicks, harder for micro-adjustments; low eDPI is the reverse. The bar is descriptive: it shows where most pros sit for that game.
If my eDPI matches a pro's, will my aim feel the same?
Only mouse speed will match. Aim is pad size, desk height, grip and thousands of hours — eDPI captures none of that. Matching is a reasonable experiment, not a shortcut.
Does 400 vs 800 DPI matter at the same eDPI?
Crosshair speed is identical; resolution differs slightly — at 800 each mouse count is finer, which can feel smoother on high-refresh displays. Both are fine; pros are split roughly 50/50.
Why does Fortnite eDPI look so small?
Because Fortnite sets sensitivity as a percentage, so the tool divides by 100. 800 DPI at 8% shows 64 eDPI — the same order of magnitude as the 48–80 pro range, even though the raw number looks tiny next to CS2’s.
Which is the better target: eDPI or cm/360?
cm/360 for comparing across games; eDPI for quick mental math within one. The tool shows both, and only shows cm/360 where the engine constant makes it trustworthy.
Does polling rate affect my eDPI or cm/360?
No — polling rate (500–8,000 Hz) is how often the mouse reports position; eDPI and cm/360 depend only on DPI, sensitivity and yaw. Higher polling can change feel (less lag between hand and crosshair) but never the numbers. Treat it as a separate axis; change one thing at a time.
I don't know my mouse DPI — can I still use this?
You need the real DPI or every number is meaningless. Check the mouse software (Logitech G Hub, Razer Synapse, the brand’s app), the manual, or the DPI button under the scroll wheel. No software and no button? Assume 800 DPI with Windows pointer at 6/11, then verify by feel.
I changed my settings and now my mouse feels like it’s "jumping around" — why?
If the crosshair stutters in-game, check polling rate and frame rate first — that’s usually performance, not sensitivity. If the cursor is erratic everywhere, it’s almost never eDPI: check the DPI button (easy to bump while reaching for the settings), a dirty sensor or shiny pad, mouse acceleration being on, or wireless interference on a wireless mouse.
Should I turn off "Enhance pointer precision" (mouse acceleration)?
Yes, for any aim game. That Windows setting makes your hand-to-crosshair mapping non-linear and unlearnable. Turn it off, keep pointer speed at 6/11, enable raw input in-game — then your eDPI is the only thing controlling aim speed.
Same eDPI as before, but aim feels different after switching mice?
eDPI measures speed, not feel. Shell weight, shape, feet and in-game FOV all change how fast the crosshair appears to move. Give a new mouse a week before judging it — and re-check its real DPI, since some mice report differently than the label says.
Is there a pixel skipping risk with high DPI?
Pixel skipping happens when the sensor reports fewer counts than the screen has pixels per tick — a concern for very low eDPI at low resolution, not for 400–1,600 DPI at normal eDPI. At those values the sensor out-resolves the game; skipping is a non-issue.