Smart Calculators

Smart

Calculators

CS2 eDPI Calculator

Calculate your eDPI, cm/360 and inches/360 for Counter-Strike 2. Compare your sensitivity against ZywOo, s1mple, NiKo, donk, m0NESY and device.

DPI

Found in CS2 → Settings → Mouse → Sensitivity.

eDPI

1,600

cm / 360°

25.98 cm

Pro player references for Counter-Strike 2

PlayerDPISenseDPIcm/360Δ vs you
ZywOo400280052-800
s1mple4003.091,23633.6-364
NiKo8000.972057.7-880
donk8001.251,00041.6-600
m0NESY4002.392045.2-680
device8001.1592045.2-680

Step 1 — eDPI is just DPI multiplied by your in-game sensitivity.

\text{eDPI} = \text{DPI} \times \text{sens} = 800 \times 2 = 1600

Step 2 — Each game has a yaw constant (degrees per mouse count). cm/360 is how many centimetres of mouse travel rotate your character a full 360°.

\text{cm/360} = \dfrac{360}{\text{yaw} \times \text{DPI} \times \text{sens}} \times 2.54 = \dfrac{360}{0.022 \times 800 \times 2} \times 2.54 = 25.9773\,\text{cm}

Step 3 — Convert centimetres to inches by dividing by 2.54.

\text{in/360} = \dfrac{\text{cm/360}}{2.54} = \dfrac{25.9773}{2.54} = 10.2273\,\text{in}
Updated May 5, 2026
Pro player setups change frequently. Reference values are verified quarterly; treat them as orientation, not gospel.
eDPI CalculatorGenshin Pity Calculator

CS2 eDPI calculator. Effective DPI, cm/360 and closest pro for Counter-Strike 2.

A CS2 eDPI calculator multiplies your mouse DPI by your in-game sensitivity to give one number you can compare against any other CS2 player's setup. It also returns cm/360 — the physical mouse distance for a full in-game turn — using CS2's yaw of 0.022 degrees per count, the same value the Source engine has used since 1.6.

What is eDPI in Counter-Strike 2?

eDPI (effective dots per inch) is your mouse DPI multiplied by your in-game CS2 sensitivity. The formula is eDPI = DPI × sens, so 800 DPI at 1.0 sensitivity is 800 eDPI, exactly the same as 400 DPI at 2.0 sensitivity (ZywOo's setup) or 1600 DPI at 0.5 sensitivity. Two players at the same eDPI have identical on-screen turn speed in CS2 regardless of which DPI they run on the mouse itself.
eDPI became the community standard for comparing pro settings in Counter-Strike because it collapses two configurable values — hardware DPI and the in-game slider — into a single number that travels cleanly between forums, prosettings.net cards, and stream overlays. According to prosettings.net's tracked roster of 895 active CS2 pros (May 2026), the median eDPI is 830 and the inter-quartile range sits between 600 and 1200; the modal DPI choice is 400 at 66% of the roster, with 800 DPI second at 28% and 1600 DPI at 5%. The 800 eDPI most users land on therefore comes from the canonical 800 DPI × 1.0 sensitivity setup, not from the modal hardware DPI itself.
Where eDPI breaks down is across games. CS2 uses a yaw of 0.022 deg/count (inherited unchanged from CS:GO and CS 1.6), Valorant uses 0.07, and Overwatch 2 uses 0.0066. The same 800 eDPI produces a 51.95 cm/360 turn in CS2, only 16.32 cm in Valorant, and 173.18 cm in Overwatch 2 — three completely different physical setups. That is why pros publish both eDPI (for CS2 peers) and cm/360 (for everyone else).

How to calculate your CS2 eDPI and cm/360

The calculator above does both numbers in one click. Here is the manual version so the result is auditable.
1. Find your mouse DPI in your mouse software (Logitech G Hub, Razer Synapse, SteelSeries GG, Pulsar Fusion, Glorious Core). Most CS2 pros sit at 400, 800, or 1600 DPI; 400 is the modal value (66% of the prosettings.net roster) and 800 is second (28%). Either is a safe starting point because both are high enough to avoid sensor-skipping at sub-counts and low enough that 1:1 in-game movement still feels precise.
2. Open CS2 and go to Settings → Mouse → Mouse Sensitivity. Read the slider value to two decimal places. Use the raw in-game value, not Windows pointer speed.
3. Multiply DPI × sensitivity to get eDPI. Example: 800 × 1.0 = 800 eDPI (the median CS2 pro setup).
4. To get cm/360, divide 360 by (0.022 × DPI × sensitivity), then multiply by 2.54. Example for 800 DPI / 1.0 sens: 360 / (0.022 × 800 × 1.0) × 2.54 = 51.95 cm. That is the physical distance your mouse hand has to travel for a full in-game turn.
5. To get inches/360, divide cm/360 by 2.54. The same example becomes 20.45 in/360.
In the calculator you only enter DPI and sensitivity — the CS2 yaw 0.022 is fixed, so the only inputs that matter are your two numbers. The closest-pro panel then matches your eDPI against ZywOo, s1mple, NiKo, donk, m0NESY, and device (verified against prosettings.net 2026-05-05) and shows whose setup is closest to yours.

CS2 eDPI and cm/360 formulas

eDPI=DPI×senscm/360=3600.022×DPI×sens×2.54\text{eDPI} = \text{DPI} \times \text{sens} \quad\quad \text{cm/360} = \frac{360}{0.022 \times \text{DPI} \times \text{sens}} \times 2.54
  • DPIDPI = Mouse hardware DPI (e.g. 400, 800, 1600 — the three modal values among CS2 pros)
  • senssens = CS2 in-game sensitivity slider (Settings → Mouse → Mouse Sensitivity)
  • 0.0220.022 = CS2 yaw constant, the degrees of camera rotation per mouse count, unchanged from CS:GO and the original Source engine
  • 2.542.54 = NIST-defined exact inch-to-centimetre conversion (1 inch = 2.54 cm)
eDPI is the easy half. Multiply DPI by sensitivity and you have a single number that compares directly with every other CS2 player and every published pro card.
cm/360 is where the yaw constant matters. CS2's yaw of 0.022 deg/count is baked into the engine and inherited unchanged from CS:GO and CS 1.6 — this is why your CS:GO sensitivity transfers 1:1 to CS2 with the same DPI, and why every Source-engine title (TF2, Day of Defeat: Source, Apex Legends, Deadlock) shares the same yaw and produces the same cm/360 at matching settings.
The inches/360 value is simply cm/360 divided by 2.54. Players in the US, UK, and Australia tend to talk in inches/360; everywhere else cm/360 is the lingua franca on Reddit, Discord, and HLTV threads.
The sensitivity band classification (low / medium / high) compares your cm/360 against the CS2 pro distribution rather than a flat universal scale. CS2's medium band sits roughly between 25 and 50 cm/360 (the range where most prosettings.net-tracked pros cluster). Anything above 50 cm is low sens; anything below 25 cm is high sens. Use the band as a sanity check, not a prescription — s1mple at 33.6 cm and NiKo at 57.7 cm are both world-class with very different feel.

CS2 eDPI calculator examples

ZywOo — 400 DPI / 2.0 sens (the AWPer-and-rifler benchmark)

Plug 400 DPI and 2.0 sensitivity into the calculator: eDPI 800, cm/360 51.95, inches/360 20.45. ZywOo at 51.95 cm sits just inside CS2's low-sens band — only 1.95 cm above the 50 cm threshold the engine uses to split low from medium. ZywOo runs a Zoom Sensitivity Multiplier of 0.818, which keeps his scoped AWP movement proportional to his unscoped rifle movement — a detail many community converters skip. If you currently play around 50 cm/360 in CS2, your eDPI is already on ZywOo's number.

donk — 800 DPI / 1.25 sens (the modern aggressive rifler)

Set DPI 800 and sens 1.25: eDPI 1000, cm/360 41.56, inches/360 16.36. donk plays Team Spirit and runs above the pro median for a reason — he relies on fast first-bullet flicks and tight spray angles, both of which favour a quicker turn. 1000 eDPI in CS2 sits firmly in the medium band but trends toward the aggressive end. Players coming from Valorant or Apex often find donk's setup feels native because cm/360 around 40 cm is the modal target across all three titles.

s1mple — 400 DPI / 3.09 sens (the high-eDPI AWP outlier)

Plug in 400 DPI and 3.09 sens: eDPI 1236, cm/360 33.62, inches/360 13.24. s1mple has run this exact pair publicly since the late CS:GO era and migrated 1:1 into CS2 (yaw is identical between the games). 33.62 cm sits in the lower half of CS2's medium band — a fast medium, with 8.6 cm of headroom before crossing the 25 cm cutoff into high-sens territory. The closest-pro panel will surface s1mple for any user whose CS2 eDPI lands between roughly 1100 and 1350.

Closest CS2 pro by eDPI band — quick-reference table

Six pros, six distinct cm/360 targets at CS2 yaw 0.022 (verified prosettings.net 2026-05-05): NiKo 720 eDPI / 57.72 cm (low band, arm-aim AWP-rifle hybrid), ZywOo 800 eDPI / 51.95 cm (low band, just over the 50 cm threshold), m0NESY 920 eDPI / 45.18 cm (medium), device 920 eDPI / 45.18 cm (medium), donk 1000 eDPI / 41.56 cm (medium), s1mple 1236 eDPI / 33.62 cm (medium band, fast end). Pick the row whose cm/360 is closest to yours, then commit to that target for two weeks of aim training before tweaking again. Constant adjustment is the single most common reason CS2 aim plateaus.

Tips for using your CS2 eDPI and cm/360

  • Lock your DPI at 400 or 800 — together they account for ~94% of the prosettings.net CS2 roster (66% at 400 DPI, 28% at 800 DPI). Both sit comfortably above sensor-skip thresholds while still allowing 1:1 movement in CS2's UI scaling. Modern sensors (HERO 2, PMW3950, Focus Pro 30K) are pixel-perfect from 100 to 32,000 DPI, so neither value is a hardware limit — they are the community conventions that make pro settings directly comparable. 400 is the modal pro choice; 800 is the second-most-common and the safest starting point if you want finer slider granularity.
  • Match cm/360 to a pro, not eDPI to a pro. eDPI 800 in CS2 is great; eDPI 800 in Valorant is wildly slow. If you ever play Valorant, Apex, Overwatch 2, or Fortnite, write down your CS2 cm/360 and match that number across games using a yaw-aware converter. cm/360 is the only sensitivity metric that transfers between FPS titles because each game has its own yaw constant.
  • If you are migrating from CS:GO to CS2, your sensitivity transfers 1:1. CS2 inherited yaw 0.022 from CS:GO and Source 1, so the exact same DPI and sensitivity produces the exact same cm/360 in both titles. The only thing that changed is feel — CS2's smoother sub-tick mouse handling and slightly different viewmodel can make a 1:1 setup feel a touch lighter on day one. Give it a week before adjusting.
  • Disable Windows Enhance Pointer Precision. CS2's eDPI math assumes a linear cursor response. Windows acceleration breaks that assumption and makes your effective sens drift with hand speed, which is the fastest route to inconsistent flicks. Toggle it off in Settings → Bluetooth & Devices → Mouse → Additional mouse settings → Pointer Options.
  • Set Zoom Sensitivity Ratio to 0.818 if you AWP. The default 1.0 keeps your scoped sens equal to unscoped, but 0.818 makes scoped crosshair movement physically proportional to unscoped — most CS2 AWPers (ZywOo runs this exact value) prefer it because flicks at a 1× scope match the muscle memory of unscoped rifling. The trade-off is a slower scope turn, which most pros consider acceptable for the tracking gain.
  • Treat the sensitivity band as a sanity check, not a prescription. CS2's medium band of roughly 25–50 cm/360 covers nearly every active pro on prosettings.net, but the optimum is whichever cm/360 you can hold steady when shooting under pressure — not the highest or lowest you can tolerate. NiKo at 57 cm and s1mple at 33 cm are both world-class; the difference is years of muscle memory at that exact value, not the value itself.

Frequently asked questions about CS2 eDPI and sensitivity

What is eDPI in CS2?

eDPI in CS2 is your mouse DPI multiplied by your CS2 in-game sensitivity slider. The formula is eDPI = DPI × sens. It is the standard way to compare aim speed against any other CS2 player regardless of which hardware DPI they run.

What is a good eDPI for CS2?

The CS2 pro median is 830 eDPI, with the inter-quartile range from roughly 600 to 1200 eDPI (prosettings.net data, May 2026). 800 eDPI sits just below the median and corresponds to about 52 cm/360 — comfortable for most rifling and AWP play. Anything between 600 and 1200 is well within the competitive range; pick the value where your cm/360 feels stable under pressure.

What eDPI do CS2 pros use?

Verified against prosettings.net 2026-05-05: ZywOo 800 eDPI (400 DPI × 2.0), s1mple 1236 (400 × 3.09), NiKo 720 (800 × 0.9), donk 1000 (800 × 1.25), m0NESY 920 (400 × 2.3), and device 920 (800 × 1.15). The roster median is 830 eDPI (prosettings.net guide, May 2026); 800 sits just below the median and is what most users land on with the canonical 800 DPI × 1.0 sensitivity setup.

What is cm/360 in CS2?

cm/360 is the physical distance your mouse must travel for the camera to complete one full 360-degree turn in CS2. It is calculated as 360 / (0.022 × DPI × sens) × 2.54, where 0.022 is CS2's yaw constant. cm/360 is the only sensitivity metric that transfers cleanly between different FPS games because each game has its own yaw.

What is a good cm/360 for CS2?

Most CS2 pros sit between 25 and 55 cm/360, with the cluster between 30 and 45 cm. Below 25 cm is high sens (s1mple territory at 33 cm sits at the threshold); above 50 cm is low sens (NiKo at 58 cm is well into low). Aim trainers and competitive coaches typically recommend 35–45 cm as a balanced starting point for new players.

Does my CS:GO sensitivity transfer to CS2?

Yes, 1:1. CS2 inherited the 0.022 yaw constant unchanged from CS:GO and Source 1, so the exact same DPI and sensitivity produce the exact same cm/360 in both titles. Some players notice a slightly lighter feel on day one because of CS2's smoother sub-tick mouse handling, but no numeric conversion is needed.

Does my CS2 sensitivity transfer to Valorant?

No — Valorant's yaw (0.07) is 3.18 times higher than CS2's (0.022), so the same eDPI is over three times faster in Valorant. To match the feel, divide your CS2 sensitivity by 3.18 at the same DPI: a 1.0 CS2 sens becomes 0.314 in Valorant. The clean way to think about it is to match cm/360 between the two games using our cross-game eDPI calculator, not to copy the slider number.

Is this CS2 eDPI calculator free?

Yes. The calculator runs entirely in your browser, requires no signup, and stores no personal data. Your DPI and sensitivity persist locally so the page reloads with your last setup, but nothing is sent to a server.

How accurate are the cm/360 values for CS2?

Accurate to 0.01 cm against the canonical formula. CS2's yaw of 0.022 deg/count was re-verified on 2026-05-05 against recharge.com's 2024–2025 yaw table, mouse-sensitivity.com's CS2 converter, and rawaccel.co. The values match what prosettings.net publishes for each pro on their player pages.

Should I copy a pro's CS2 sensitivity?

Use the closest-pro match as a starting point only. A pro's cm/360 is a credible target — most CS2 pros sit in the medium band (25–50 cm/360) for a reason — but their exact value rests on thousands of hours of muscle memory at that number. Land in the right neighbourhood, then commit for at least two weeks of aim training before adjusting. Constant tweaking is the most common cause of stagnant CS2 aim.

Is higher eDPI better for CS2?

No. Higher eDPI gives faster turns and quicker target acquisition but punishes precision; lower eDPI rewards precise headshot aim but requires more arm space. CS2 pros span 400 to 2400 eDPI, with the bulk between 600 and 1200. The optimum for you is the cm/360 you can hold steady when shooting under pressure, not the highest or lowest you can tolerate.

Why do CS2 pros use 400 or 800 DPI instead of higher values?

Tradition and comparability rather than hardware necessity. Modern sensors are pixel-perfect to 30,000+ DPI, so 1600 or 3200 DPI is technically clean. Pros stay at 400 or 800 because the community publishes pro cards at those values, because Windows pointer scaling can introduce sub-count rounding above 1600 DPI on older OS builds, and because lower DPI gives more counts per millimetre of mouse travel — which translates to finer micro-adjustments at the same eDPI.

CS2 mouse sensitivity glossary

eDPI

Effective dots per inch. eDPI = DPI × CS2 in-game sensitivity. A single number that compares aim speed against any other CS2 player regardless of hardware DPI.

DPI

Dots per inch — a hardware setting on the mouse itself that defines how many sensor counts are reported per inch of physical movement. CS2 pros overwhelmingly use 400, 800, or 1600 DPI.

CS2 sensitivity

The Mouse Sensitivity slider in CS2's Settings → Mouse menu. Multiplied by DPI and CS2's 0.022 yaw constant to determine on-screen turn speed.

cm/360

Centimetres of physical mouse travel needed to complete one full 360-degree turn in CS2. The metric pros publish for cross-game comparison because it is independent of yaw.

inches/360

The imperial equivalent of cm/360. inches/360 = cm/360 ÷ 2.54. Common in US, UK and Australian community discussion and on prosettings.net cards.

Yaw constant

The number of degrees the camera turns per mouse count, baked into the game engine. CS2's yaw is 0.022 deg/count — inherited unchanged from CS:GO and the original Source engine.

Sensitivity band

A low / medium / high classification of your cm/360 relative to the CS2 pro distribution. CS2 medium ≈ 25–50 cm/360; below 25 is high sens, above 50 is low sens.

Closest pro match

The CS2 pro from a curated, prosettings.net-verified roster (ZywOo, s1mple, NiKo, donk, m0NESY, device) whose published DPI × sensitivity is mathematically nearest to the user's eDPI.

Zoom Sensitivity Ratio

A CS2 setting that scales mouse sensitivity while scoped (AWP, Scout). Default is 1.0 (no change); 0.818 keeps scoped crosshair movement physically proportional to unscoped, the value most CS2 AWPers prefer.

Polling rate

How many times per second the mouse reports its position to the PC, measured in Hz. Standard CS2 values are 1000, 2000, 4000, and 8000 Hz. Polling rate does not affect eDPI or cm/360 — only motion smoothness.

Raw input

In CS2, raw input is forced on at the engine level — the CS:GO `m_rawinput` toggle was removed when CS2 launched. The engine reads the mouse sensor directly and ignores Windows pointer-precision processing, with no user action required. This is what keeps eDPI a stable metric across machines.

Content verified by the Smart Calculators Team