Pick a target cm/360° (how far you move the mouse for a full turn), calculate eDPI in your main game with the eDPI calculator, then use the sensitivity converter to sync other titles. Same physical distance = same muscle memory — even when the in-game number changes.
This guide covers feel and math only. For broken buttons, scroll skips, or polling drops, use the mouse hardware test guide instead.
Why DPI alone is misleading
| Setting | What it controls | What it does not tell you |
|---|---|---|
| Mouse DPI | Cursor pixels per inch of hand movement | In-game turn speed |
| In-game sens | Game-specific multiplier | Cross-game equivalence |
| eDPI | DPI × in-game sens in one title | Physical cm/360 across games |
| cm/360° | Centimeters for a 360° turn | Whether your mouse is defective |
Example: 800 DPI × 0.7 sens in Valorant = 560 eDPI. 800 × 1.0 in CS2 = 800 eDPI — different numbers, potentially similar feel because each engine uses different yaw math. That is why pros talk in cm/360, not raw sens alone.
Step 1 — Calculate eDPI in your main game
- Open the eDPI calculator and select your primary title (CS2, Valorant, Fortnite, Apex, etc.).
- Enter mouse DPI from your software (400, 800, 1600 are common native steps).
- Enter in-game sensitivity from the game settings menu.
- Read eDPI and cm/360° on the results card.
Game-specific landing pages if you search one title only:
Tip: Disable mouse acceleration (Windows “Enhance pointer precision” off, raw input on in-game) before trusting any math.
Step 2 — Use cm/360 as your anchor
cm/360° is the distance your hand travels for one full horizontal rotation. It stays meaningful when you switch games — unlike copying “2.5 sens” from a streamer in a different title.
| cm/360 range | Typical player profile |
|---|---|
| 20–30 cm | High sens — wrist aim, small mousepad |
| 30–45 cm | Medium — hybrid arm/wrist |
| 45–60+ cm | Low sens — large pad, arm aim |
Measure in-game: mark a starting point on your pad, turn exactly 360° in a private match, measure the travel with a ruler. Compare to the calculator. If they diverge by more than ~5%, verify real DPI with the DPI test — rated 800 DPI is not always true 800.
Step 3 — Convert sensitivity between games
Each FPS engine uses different yaw values. The same in-game number in CS2 and Valorant does not produce the same turn speed.
- Lock your cm/360 in the game you play most (Step 1).
- Open the sensitivity converter — popular pairings:
- Enter your known sens in the source game; copy the converted value into the destination game.
- Confirm with a quick 360° ruler check in the new title.
Rule: Match cm/360, not eDPI, when crossing games. eDPI is for comparing setups inside one engine.
Step 4 — Pro settings are ranges, not targets
Public pro references illustrate competitive bands — not prescriptions. Hand size, desk space, role, and mousepad matter more than copying one number.
| Player | Game | Approx. eDPI | Notes |
|---|---|---|---|
| TenZ | Valorant | ~560 | High-profile duelist — not “correct” for everyone |
| NiKo | CS2 | ~632 | Rifler anchor sens |
| ZywOo | CS2 | ~800 | Slightly higher than many AWPers |
| s1mple | CS2 | ~1236 | Historically higher sens AWPer |
| Aceu | Apex | ~1200 | Battle royale tracking bias |
Use the eDPI calculator pro reference chart as a sanity check. If your cm/360 is 15 cm and every pro you admire sits at 40+ cm, copying their sens will feel wrong — by design.
When to raise or lower sens
- Too high — overshoot flicks, inconsistent micro-adjustments, tension in wrist.
- Too low — cannot clear 180° flicks on your pad size, shoulder fatigue from lifting.
- Just right — repeatable flicks, comfortable tracking, no constant re-gripping.
Change sens in small steps (~5–10% eDPI). Large jumps reset muscle memory. After each change, run the precision aim test for a few minutes — not to “score high,” but to feel consistency.
Common mistakes
| Mistake | Fix |
|---|---|
| Copying a pro’s sens without matching cm/360 | Convert through yaw, verify with ruler |
| Using different DPI in software vs what you calculated | Stick to one native DPI step |
| Windows acceleration on | Turn off; enable raw input in each game |
| Changing sens daily | Pick a cm/360 band and stay 2+ weeks |
| Confusing hardware issues with “wrong sens” | Stutter or skips → mouse test guide |
FAQ-style quick answers
Why does 800 eDPI in Valorant feel different from 800 eDPI in CS2?
Different yaw constants. Use cm/360 or the converter, not raw eDPI across titles.
Should I use 400 or 800 DPI?
Either works if eDPI and cm/360 match your goal. Prefer a native sensor step your mouse supports without interpolation.
Is lower sens always better for aim?
No — optimal sens fits your pad, posture, and game role. Many top players sit in medium bands.
Does polling rate change cm/360?
No. Polling affects click smoothness and latency, not turn distance. See the hardware guide for polling tests.
Tools for this workflow
| Step | Tool |
|---|---|
| Calculate eDPI + cm/360 | eDPI calculator |
| Convert between games | Sensitivity converter |
| Verify real DPI | DPI test |
| Practice after changes | Precision aim test |
| Broken mouse / scroll | Mouse hardware guide |
Gaming hub: All gaming tools · Input tools: Tools directory
