Mouse Sensitivity Calculator

Frequently Asked Questions

What is eDPI and why does it matter?

eDPI = mouse DPI × in-game sensitivity. It is the true effective sensitivity, letting you compare players on different mice and settings. A 400 DPI × 2.0 sens equals 1600 DPI × 0.5 - both 800 eDPI.

How do I calculate cm/360?

cm/360 is the physical mouse travel for a full 360° turn. It depends on DPI, in-game sensitivity and the game's yaw constant. Lower cm/360 is faster (twitchy); higher is more precise (arm aim).

How do I convert sensitivity between games?

Match cm/360 (or 360 distance): keep DPI fixed and set the new game's sensitivity so its yaw × sens equals your old game's. The calculator does this using each game's yaw/conversion factor.

What is a good sensitivity for FPS aiming?

Many competitive players use 25–45 cm/360 (relatively low) for stable tracking and flicks. There is no single best value - consistency and a setting your arm can repeat matters more than the exact number.

Provided by AllCalculators.io
Free online calculators for everyday. No registration required.

Estimates for informational purposes only.

Important Disclaimer: Estimates for informational purposes only.

This calculator provides estimates for informational purposes only. Results are based on assumptions and may not reflect actual outcomes. Consult qualified professionals in relevant fields before making important decisions based on these results.

JavaScript is required to use the interactive calculator above. The questions and answers below remain readable without JavaScript.

How This Calculator Works

Your real aiming speed in any first-person game is governed by three numbers: mouse DPI (counts reported per inch of physical movement), the in-game sensitivity slider, and the game's internal yaw constant (degrees of view rotation per mouse count at sensitivity 1). The single most-quoted figure is eDPI = DPI × in-game sensitivity - it lets two players on different mice compare turn speed directly, because a 400-DPI player at 4.0 sensitivity and an 800-DPI player at 2.0 share an eDPI of 1600 and therefore the same on-screen response. The more physically meaningful number is cm/360: the distance your hand must travel on the pad to spin a full circle in-game. This tool computes counts per 360° as 360 ÷ (yaw × sensitivity), divides by DPI to get inches/360, and multiplies by 2.54 for cm/360. Lower cm/360 means a faster, twitchier setup; higher means slower and more precise.

Formula / Method

Counts per 360° = 360 ÷ (yaw × sens). Inches per 360° = counts ÷ DPI. cm/360 = inches/360 × 2.54. eDPI = DPI × sens. To convert a sensitivity between two games while keeping cm/360 identical, the product yaw × sens must stay constant, so the new sensitivity = (yaw_old × sens_old) ÷ yaw_new. The default yaw of 0.022 is the Source/Quake-style value shared by many shooters; some titles use different constants or expose only a 0–10 slider that maps non-linearly, so always confirm the constant for your specific game.

Worked Example

At DPI = 800 and sensitivity = 1.5 with yaw 0.022: counts/360 = 360 ÷ (0.022 × 1.5) = 360 ÷ 0.033 ≈ 10,909 counts. Inches/360 = 10,909 ÷ 800 ≈ 13.64 in, and cm/360 ≈ 13.64 × 2.54 ≈ 34.6 cm - a fairly low, fast setup favoured by many duel-focused players. eDPI = 800 × 1.5 = 1200, on the lower end of competitive ranges (typical 800–1600). If a second game also uses yaw 0.022 the converted sensitivity is unchanged at 1.5; if it used 0.0066 instead you would need 0.022 × 1.5 ÷ 0.0066 = 5.0 to keep the same 34.6 cm/360.

Common Mistakes

Comparing raw sensitivity sliders across games - they are meaningless without the yaw constant; only eDPI or cm/360 transfer.

Forgetting Windows pointer-speed or in-game "mouse acceleration", which break the linear relationship this tool assumes.

Mixing up cm and inches: a 26 cm/360 player and a 26 in/360 player are vastly different (2.54× apart).

Assuming higher DPI is always "better" - what matters is eDPI and stable sensor tracking, not the headline DPI number.

Using the wrong yaw constant for the game; many modern engines do not use 0.022, and ADS/scoped sensitivity often has its own multiplier.

Tips & FAQ

What cm/360 should I use? Pure aim-duel players cluster around 20–40 cm/360 for micro-adjustment; tactical and battle-royale players often run 30–55 cm to steady recoil and movement. There is no universally correct value - pick one, keep it identical across every game and after every mouse change, and let muscle memory build over weeks. Does higher DPI reduce input lag? Marginally on very old sensors; on any modern mouse the difference is imperceptible, so choose a DPI your sensor tracks cleanly (often 800–1600) and adjust the in-game slider to hit your target cm/360. Why does my flick feel off after switching games? Almost always a yaw mismatch - use the conversion field so the muscle memory in your arm produces the same on-screen rotation. Keep this consistent and your aim transfers between titles instead of resetting every time.

Mouse Sensitivity Calculator

Frequently Asked Questions

Related Gaming Calculators