Game Sensitivity Converter
Every FPS player has felt it: you switch from Valorant to Counter-Strike 2, set the “same” sensitivity number, and your aim feels completely alien. That is because in-game sensitivity numbers are not comparable between games — each engine multiplies your mouse input by a different yaw value (degrees turned per mouse count). A Game Sensitivity Calculator cuts through the confusion: enter your DPI and sensitivity to get your true eDPI, your cm/360° turn distance, and the exact matching sensitivity in every major shooter.
This guide explains the three universal sensitivity metrics, derives the cm/360 formula, shows how cross-game conversion works mathematically, and covers the aim-style science behind choosing your sensitivity. Two fully worked examples convert real settings step by step.
The Three Numbers That Actually Describe Sensitivity
1. eDPI (effective DPI) = mouse DPI × in-game sensitivity. It is the only number comparable within one game across different DPI settings — 400 DPI × 2.0 sens and 800 DPI × 1.0 sens are identical in-game (both 800 eDPI), though higher DPI is technically smoother.
2. cm/360° = the physical mousepad distance for a full 360° turn. This is the universal metric — comparable across all games, because it measures physical reality. Pro players think in cm/360, not in-game numbers.
3. In-game sensitivity = the arbitrary slider number, meaningful only inside its own game. Valorant 0.5 and CS2 0.5 are wildly different sensitivities.
Deriving the cm/360 Formula
Your mouse reports counts (DPI = counts per inch). Each count rotates your view by yaw × sensitivity degrees. A full 360° turn needs 360 / (sens × yaw) counts; at DPI counts per inch, that is 360 / (DPI × sens × yaw) inches; times 2.54 for centimeters:
cm/360 = (360 × 2.54) / (DPI × sensitivity × yaw)
Each game’s yaw is fixed by its engine: CS2 0.022°, Valorant 0.07°, Overwatch 2 0.0066°, Apex Legends 0.022°, Fortnite 0.0556°. (Apex shares CS2’s yaw — same sens number, same feel, at equal DPI.)
How Cross-Game Conversion Works
To keep the same cm/360 in a new game, the products DPI × sens × yaw must be equal. At the same DPI, the matching sensitivity is simply:
sens₂ = sens₁ × yaw₁ / yaw₂
CS2 sens 1.0 (yaw 0.022) → Valorant: 1.0 × 0.022/0.07 = 0.314. That single ratio is why Valorant sensitivities look “lower” — its yaw is 3.18× larger, so equal-feel numbers are 3.18× smaller.
How to Use the Calculator
- Enter your mouse DPI — from your mouse software.
- Enter your in-game sensitivity — the exact slider value.
- Select your current game (or enter a custom yaw).
- Click Convert — get eDPI, cm/360, inches/360, your aim-style classification, and matching sensitivities for all five games.
Worked Example 1: 800 DPI, CS2 Sens 1.2 → Full Profile
A player uses 800 DPI and 1.2 sensitivity in CS2 (yaw 0.022).
Step 1 — eDPI: 800 × 1.2 = 960 eDPI.
Step 2 — Counts per 360°: 360 / (1.2 × 0.022) = 360 / 0.0264 = 13,636 counts.
Step 3 — cm/360: 13,636 / 800 = 17.045 inches × 2.54 = 43.3 cm (or directly: 914.4/(800×1.2×0.022) = 914.4/21.12 = 43.3 cm).
Step 4 — Aim style: 43.3 cm falls in the medium hybrid range — wrist for micro-adjustments, arm for turns.
Step 5 — Valorant equivalent: 1.2 × 0.022/0.07 = 0.377. Set Valorant to 0.377 at 800 DPI for the identical 43.3 cm/360.
Verdict: This is a classic all-rounder setup — 960 eDPI sits near the pro average for tactical shooters, and the player now knows their true universal number is 43.3 cm/360.
Worked Example 2: Valorant 0.35 at 1600 DPI → Overwatch 2
A Valorant player runs 1600 DPI, sens 0.35 (yaw 0.07), moving to Overwatch 2 (yaw 0.0066).
Step 1 — eDPI: 1600 × 0.35 = 560 eDPI.
Step 2 — cm/360: 914.4 / (1600 × 0.35 × 0.07) = 914.4 / 39.2 = 23.3 cm — a high sensitivity, wrist-aim territory.
Step 3 — Overwatch 2 match: 0.35 × 0.07/0.0066 = 0.35 × 10.606 = 3.712. Overwatch sens 3.71 at 1600 DPI reproduces 23.3 cm/360.
Step 4 — Sanity check via counts: Valorant: 360/(0.35×0.07) = 14,694 counts; /1600 = 9.18 in. Overwatch: 360/(3.712×0.0066) = 14,694 counts — identical. ✓
Verdict: The 10.6× ratio between the yaws explains the dramatic number jump — and the counts check proves the conversion is exact, not approximate.
Aim Styles and the cm/360 Spectrum
Under ~25 cm/360: high-sens wrist aimers — fast target switching, less precision, small mousepads suffice. 25-45 cm: the hybrid majority — wrist micro + arm macro, the pro sweet spot for tactical FPS. 45-60+ cm: low-sens arm aimers — maximum precision, needs a large pad and full arm movement. No style is objectively best — but consistency beats optimization: pick one cm/360 and keep it identical across every game you play, which is exactly what the converter enables.
DPI vs. Sensitivity: Does It Matter?
At equal eDPI, higher DPI is technically superior: 1600 DPI × 0.5 renders twice the angular granularity of 800 DPI × 1.0 (smaller minimum rotation steps), reducing pixel-skipping on high-resolution monitors. Most pros use 400-1600 DPI; above 3200 offers no perceptible benefit and can introduce sensor smoothing on some mice. Rule of thumb: set DPI to 800 or 1600, then tune in-game sens to your target cm/360.
Common Sensitivity Mistakes
Mistake 1 — Copying sens numbers between games. Valorant 0.5 ≠ CS2 0.5 — always convert via yaw.
Mistake 2 — Leaving mouse acceleration on. Windows “Enhance pointer precision” and in-game accel destroy muscle memory; disable both.
Mistake 3 — Changing sens weekly. Muscle memory needs weeks of consistency; constant tweaking resets adaptation.
Mistake 4 — Ignoring FOV. Conversions assume matched FOV settings; wildly different FOVs change perceived sensitivity.
FOV and Sensitivity: The Hidden Variable
Two players with identical cm/360 can experience completely different aim feel if their field of view differs. FOV changes how much of the world each pixel represents: at 110° FOV, a 5 cm flick crosses more visual angle than the same 5 cm at 90° FOV, so the sensitivity feels faster even though the physical rotation is identical. This is why converting sens between games with different default FOVs (CS2’s 90 vs. Overwatch’s 103) sometimes feels “off” despite perfect cm/360 math.
The fix used by serious players is FOV-matched conversion: several converter tools scale sensitivity by the ratio of focal lengths (monitor-distance matching) rather than pure 360° rotation. The two standards are 0% monitor match (identical crosshair-centered feel — best for precise aiming) and 100% monitor match (identical edge-of-screen feel — best for flicks). For most players, pure cm/360 conversion plus manually matching FOV numbers across games gets 95% of the way there — only scope sensitivities (which often use separate zoom_sensitivity ratios) truly need monitor matching.
Practical rule: when switching games, first match your FOV (using each game’s FOV setting or config), then convert sensitivity with the calculator. If the game offers a scope/ADS sensitivity multiplier, leave it at 1.0 initially — change it only after your hipfire feels locked in. And remember that ultrawide monitors effectively widen FOV: a 21:9 display at “103 FOV” shows more than 16:9 at the same setting, subtly changing perceived speed.
Pro Settings Analysis: What the Data Shows
Aggregated pro settings reveal clear patterns. In Counter-Strike 2, the pro average sits around 850 eDPI / 40 cm/360, with most players between 600-1200 eDPI. Valorant pros cluster near 280 eDPI (0.35 at 800 DPI) / 42 cm/360 — remarkably similar to CS2 in universal terms, confirming that tactical shooters converge on the same physical sensitivity regardless of their arbitrary slider numbers.
Overwatch 2 pros run hotter — around 4800 eDPI / 35 cm/360 equivalent — because hitscan heroes demand faster 180° turns in chaotic fights. Apex Legends controller dominance aside, mouse pros sit near 900 eDPI / 38 cm. The pattern: tactical shooters ~40 cm, arena/fast shooters ~30-35 cm. Almost no pro plays below 20 cm/360 (too twitchy for precision) or above 60 (too slow for turns) — the human motor system has a workable band, and the meta found it.
But copying pros is cargo cult without context: pros also use huge mousepads, low chairs, specific grips, and thousands of hours of adaptation. Use pro averages as a starting bracket (try 35-45 cm/360), then adjust by feel over weeks. The data’s real lesson is the band, not any individual’s number — if your cm/360 is inside 25-55, you are not losing to your settings.
Mouse Hardware: What Actually Matters
Beyond DPI, three hardware specs affect aim. Polling rate (Hz) is how often the mouse reports position: 1000 Hz (1 ms) is the standard; 4000-8000 Hz mice exist but show diminishing returns — measurable in latency tests (~0.5 ms), imperceptible to humans, and occasionally unstable on some systems. Weight matters more than marketing suggests: lighter mice (50-65 g) reduce fatigue and enable faster micro-adjustments, which is why the pro meta moved decisively ultralight.
Sensor quality is largely solved — any modern PixArt 33xx/39xx sensor tracks flawlessly; “gaming grade” differences between current sensors are negligible. What is not solved is skates and mousepad: worn skates or a dirty pad add friction variance that no settings fix can overcome. Clean your pad monthly, replace skates yearly, and keep the lift-off distance low if you reposition the mouse often.
The hierarchy of aim investment: consistent sensitivity > large clean mousepad > light reliable mouse > everything else. A $30 mouse with perfect settings and a clean pad beats a $150 flagship with acceleration on and a cm/360 that changes weekly. Hardware is the last 5%; settings discipline is the first 95%.
Finding Your Sensitivity: A Practical Protocol
Stop guessing and run a two-week protocol. Week one: set 40 cm/360 (the tactical-shooter center) via the converter and play normally — no changes allowed. Run a tracking scenario (smoothly following a moving target) and a flick scenario (fast 90° turns to targets) in an aim trainer for 10 minutes daily, noting scores. If tracking feels shaky but flicks feel great, lower sensitivity slightly (increase cm/360 by 10%); if flicks overshoot but tracking is smooth, raise it slightly.
Week two: lock the adjusted value and repeat. Change at most 10% per adjustment — the motor system adapts to small deltas but rebels against large ones. Most players converge within 2-3 iterations to a personal value inside 30-50 cm/360. Once found, write it down everywhere (phone note, config files, the converter’s memory) and commit for at least a season. The players with the best aim are not those with the best sensitivity — they are those who stopped changing it longest ago.
A final note on scope sensitivities: most games scale scoped sens relative to hipfire via a separate multiplier (often defaulting near 1.0). Because scopes magnify the view, a 1.0 multiplier usually feels faster than hipfire — many players settle near 0.8-0.9 for a matched feel. Tune hipfire first with the converter, lock it in for two weeks, then adjust scopes. Changing both simultaneously makes it impossible to tell which variable fixed (or broke) your aim.
Tips for Dialing In Your Aim
- Learn your cm/360 — it is your sensitivity’s true identity.
- Keep one cm/360 across all games using the converter.
- Disable all acceleration — Windows and in-game.
- Use 800 or 1600 DPI as your base; tune in-game sens from there.
- Give changes two weeks before judging — adaptation is slow.
- Match your FOV across games for consistent perceived speed.
- Size your mousepad to your cm/360 — low sens needs 45cm+ pads.
- Track eDPI per game in a note so rebuilds take seconds.
- Warm up with the same sens you compete with — no exceptions.
- Change one variable at a time — DPI or sens, never both at once.
Frequently Asked Questions
1. What is eDPI?
Effective DPI = mouse DPI × in-game sensitivity. It lets you compare settings within the same game regardless of DPI choice.
2. What is cm/360?
The centimeters of mouse movement for a full 360° turn — the universal, cross-game measure of sensitivity.
3. What is mouse yaw?
The degrees your view rotates per mouse count at sensitivity 1.0 — fixed per game engine (CS2: 0.022, Valorant: 0.07, Overwatch 2: 0.0066).
4. How do I convert sensitivity between games?
Matching sens = your sens × your game’s yaw ÷ target game’s yaw (at equal DPI). The calculator does this for five games instantly.
5. What cm/360 do pros use?
Most tactical-FPS pros sit between 25-50 cm/360, clustering around 35-45. Arena shooters trend lower (faster).
6. Is higher DPI better?
At equal eDPI, moderately higher DPI (800-1600) gives smoother, finer aim steps. Beyond ~3200 DPI there is no practical benefit.
7. Should I use the same sensitivity in every game?
Yes — the same cm/360 everywhere builds one consistent muscle memory instead of several conflicting ones.
8. What is mouse acceleration and why disable it?
Acceleration makes cursor speed depend on how fast you move, not just how far — destroying the consistent distance-to-rotation mapping your muscle memory needs.
9. Does FOV affect sensitivity?
Perceived sensitivity, yes — the same cm/360 feels faster at high FOV. Keep FOV similar across games for true consistency.
10. Wrist aim or arm aim — which is better?
Neither universally — wrist suits high sens and fast switching; arm suits low sens and precision. Most players are hybrids around 30-45 cm/360.
11. Why does Valorant sens look lower than CS2?
Valorant’s yaw (0.07) is 3.18× CS2’s (0.022), so equal-feel sensitivity numbers are 3.18× smaller. The cm/360 is what matches, not the number.
12. How long does it take to adapt to a new sensitivity?
Typically 1-3 weeks of consistent play. Avoid changing it during the adaptation window.
13. What mousepad size do I need?
At least your cm/360 plus margin — a 40 cm/360 player wants a 45cm+ wide pad for full turns without lifting.
14. Does polling rate affect sensitivity?
Not sensitivity itself, but higher polling (1000Hz+) reduces input latency, making any sensitivity feel more responsive.
15. Can I use a custom game’s yaw?
Yes — select “Custom yaw” and enter the game’s degrees-per-count (found on sensitivity wikis); conversions then work for any title.
CONCLUSION
Sensitivity numbers lie; centimeters do not. eDPI normalizes your settings within a game, cm/360 normalizes them across all games, and the yaw ratio converts between them exactly. Find the cm/360 that fits your aim style, lock it in everywhere with the converter, kill acceleration, and stop tweaking. Consistency is the real aim trainer — the math just makes consistency portable.