TRANSPARENT CALCULATIONS

How We Calculate

The math behind our tools is public and independently checkable. Updated: 31 October 2026.

QUICK ANSWER

Which formulas does this website use?

eDPI = DPI × in-game sensitivity multiplier; cm/360 = 360 × 2.54 ÷ (DPI × yaw × raw sensitivity); and target sensitivity = source yaw × source sensitivity × source DPI ÷ (target yaw × target DPI). Fortnite is handled in displayed percentage points for yaw and as a decimal multiplier for eDPI.

Formulas

eDPI = DPI × (percentage ? sensitivity / 100 : sensitivity)

cm/360 = (360 × 2.54) / (DPI × game yaw × displayed sensitivity)

Target sensitivity = (source DPI × source sensitivity × source yaw) / (target DPI × target yaw)

New sensitivity at new DPI = old sensitivity × old DPI / new DPI

Game yaw reference assumptions

A yaw constant models degrees turned per mouse count at the specified in-game input scale. These are community reference values, not official guarantees and can change with patches or settings.

GameYaw modelEntered sensitivity format
Valorant0.07Decimal
Counter-Strike 2 (CS2)0.022Decimal
Apex Legends0.022Decimal
Overwatch 20.0066Decimal
Fortnite0.005555Displayed percentage (e.g. 10 = 10%)

Fortnite convention: the 0.005555 yaw estimate is per one displayed percentage point. With 10% sensitivity, the modeled per-count rotation is 10 × 0.005555 = 0.05555 degrees. For eDPI only, the multiplier is 10 ÷ 100 = 0.10.

Worked values

SetupeDPIcm/360
Valorant, 800 DPI, 0.3225651.03
CS2, 800 DPI, 1.080051.95
Fortnite, 800 DPI, 10%8020.58

Data sources and verification

These starting constants follow community-documented FPS sensitivity models. Independent reference explanations include KrisTools conversion reference, Redmoon sensitivity converter and Gear Geeks sensitivity constants. No official game API feeds this website.

We test the formula engine against known cases in tests/math.test.js included in the download package. A source disagreement or game update may require revised constants; contact us with reproducible evidence.

What the model does not do

The tools cannot independently detect your actual mouse DPI, account for driver acceleration or guarantee a match in all game modes. FOV, ADS, scoped multipliers, independent horizontal/vertical sensitivity, game patches, rounding and hardware behavior can change the result.

Corrections

See Contact for reporting a discrepancy, including the game, values, expected rotation and testing procedure.