CS2 eDPI Explained: What Sensitivity Do Pros Use?

Ask three pros their sensitivity and you’ll get three different-looking answers - one runs 800 DPI at sens 1.0, another 400 DPI at sens 2.0, a third 1600 DPI at sens 0.5. They are all aiming at the same speed.

The number that makes that visible is eDPI, and across cs2pedia’s dataset of pro profiles the typical pro eDPI is 800 median pro eDPI - low, and tightly clustered.

That clustering is the whole story of this page: pro CS2 sensitivity is not a matter of taste spread evenly across a wide range. It’s a narrow band, and the data below shows exactly where it sits.

What Is eDPI?

eDPI (“effective DPI”) is the one number that lets you compare two players’ sensitivity fairly. It’s just a multiplication:

eDPI = mouse DPI × in-game sensitivity

DPI (dots per inch) is how far the cursor travels per inch of physical mouse movement, set in your mouse driver or on the mouse itself. In-game sensitivity is the multiplier CS2 applies on top of that. Neither number alone tells you how fast someone actually turns, because they trade off against each other.

A player at 400 DPI and sensitivity 2.0 moves their crosshair exactly as fast as a player at 800 DPI and sensitivity 1.0 - both land at an eDPI of 800. That’s why “I play on 1.5 sens” is meaningless on its own: without the DPI it tells you nothing.

eDPI collapses the two into a single comparable figure, which is why it’s the only sensitivity unit worth quoting across players. Everything on this page is in eDPI for that reason.

CS2 Pro eDPI Distribution

Here’s where the pro field actually lands. This is computed at build time from every profile in the dataset that has both a DPI and an in-game sensitivity recorded - eDPI is derived per player from those raw fields, not from a scraped summary number.

Value

Pros

Share

<500

19

1.9%

500–799

344

35.2%

800–999

392

40.1%

1000–1199

133

13.6%

1200+

89

9.1%

The shape matters more than any single figure. The center of gravity is the 500–999 band: the two middle buckets together hold the clear majority of the field, and the median sits right at 800 median eDPI .

The mean is slightly higher, at 860 mean eDPI - that gap between median and mean is the signature of a right-skewed distribution, where a thin tail of high-sensitivity outliers drags the average up without moving the typical value. That’s exactly why the median is the number to anchor on: it’s where pros actually sit, not an average distorted by a handful of fast-flickers.

Two reads come straight off the table. First, low sensitivity dominates - the bottom three buckets (everything under 1000 eDPI) make up the bulk of the field, so if your eDPI is well above 1000 you are playing faster than most of the pro scene. Second, the high end is real but thin: the 1200+ bucket exists, it’s just small. High-sens pros are a genuine minority, not a myth, and we’ll come back to who they tend to be.

One honest caveat on the denominator: a small number of profiles don’t have both DPI and sensitivity on record, and those are excluded from the curve entirely rather than guessed at - the caption above states exactly how many of the profiles contributed. The distribution describes the pros who reported both settings, which is nearly the whole roster but not literally all of it.

DPI: 400 vs 800

Once you’ve fixed your eDPI, the DPI half of the equation is close to a coin flip - and the dataset shows the field splitting almost exactly that way.

Value

Pros

Share

400

497

50.9%

800

410

42.0%

1600

47

4.8%

3200

5

0.5%

Two values own the field: 400 and 800, with 400 holding a slim edge over 800 among the pros who reported a DPI. Almost everything else is a rounding error.

And here’s the thing that trips up newer players: it does not matter which of the two you pick, as long as you set your in-game sensitivity to hit the same eDPI. 400 DPI at sens 2.0 and 800 DPI at sens 1.0 are mechanically identical movements.

Modern flagship sensors - the Hero and Focus Pro families that the current pro mice run - track both 400 and 800 natively with no interpolation or accuracy penalty, so there’s no sensor-quality reason to prefer one. (Those sensors are also why the old “always use 400” advice has softened; it was a real concern on cheaper sensors a decade ago, not on current hardware.)

The practical rule: pick 400 or 800, set sensitivity to land on your target eDPI, and never think about DPI again. If you genuinely have no preference, 400 is the marginally more common pro choice and a fine default. For the rest of the mouse config that should stay locked alongside it, see our CS2 mouse settings guide.

Why Most Pros Run Low Sensitivity

The distribution leans low for a physical reason, not a fashion one. At low eDPI, a given on-screen movement requires a larger physical sweep of the mouse, which recruits the arm and shoulder rather than just the wrist. Arm-aiming is slower to whip around but far more repeatable: large muscles make small relative errors, so your shots land where you intended.

High sensitivity is the opposite - tiny wrist twitches cover huge angles, which is fast but amplifies every micro-tremor into a missed shot. For a game decided by precise taps at range, the error tolerance of a low, arm-driven sensitivity wins, and the field has converged on it.

Low sensitivity also leans on good crosshair placement. If you pre-aim corners at head height, you rarely need a big flick - you need a small, accurate correction, which is exactly what low eDPI is best at. The pros in the dense middle of the distribution are playing a positioning game where the mouse mostly makes fine adjustments.

So why does the high-sens tail exist at all? A minority of pros - the 1200+ bucket - run hot on purpose. These tend to be aggressive entry fraggers and some AWPers who value the ability to spin and reposition instantly, trading precision for raw turn speed and accepting that their aim is a touch noisier.

It’s a real, viable style, but it’s a minority style, and it requires the reflexes to control. Picking a high eDPI because two famous players do is the wrong reason; the data says the safe bet is low.

There’s a hardware corollary here worth flagging. Low sensitivity means big physical sweeps, which means you need desk room and a surface you can travel across without lifting constantly. A small pad will sabotage a low-sens setup - see our best mousepad guide for the large sizes the low-sens majority effectively requires.

How to Find Your eDPI

You don’t need to copy a specific pro. You need to land inside the band the distribution describes and then refine. A practical method:

1. Start at the median. Set your eDPI to roughly 800 eDPI . At 800 DPI that’s in-game sensitivity 1.0; at 400 DPI it’s sensitivity 2.0. This drops you straight into the densest part of the pro field - a deliberately unremarkable starting point, which is the point.
2. Live with it for one to two weeks. Play deathmatch and aim-training maps daily. Muscle memory needs reps before you can judge a sensitivity honestly; switching after one bad session tells you nothing.
3. Adjust in small steps. Overshooting flicks consistently? Your eDPI is too high - drop it. Can’t turn fast enough to deal with someone behind you? Nudge it up. Move in increments, not leaps.
4. Recompute, don’t guess. Whenever you change DPI or sensitivity, recheck your eDPI with the formula so you always know your real number and can compare it to the player profiles and the aggregate stats on cs2pedia.

The goal isn’t to find the “correct” eDPI - there isn’t one, and the spread in the distribution proves it. The goal is to find your repeatable eDPI inside the proven low-to-mid band, then stop moving it.

Sensitivity Consistency

That last point deserves its own heading, because it’s the most common self-inflicted wound. Every time you change your sensitivity, you reset a chunk of your muscle memory - the mapping between “this much hand movement” and “this much crosshair movement” has to be relearned. Pros lock a sensitivity and leave it for years precisely to protect that mapping. Chasing a slightly different number every week guarantees you never build stable aim at any of them.

If eDPI doesn’t click for you, an equivalent framing is cm/360: the physical distance, in centimeters, your mouse travels to turn a full 360 degrees in-game. It’s the inverse view of the same thing - low eDPI means a long cm/360 (a big sweep), high eDPI means a short one. Pick whichever framing you find easier to reason about, but pick one and stay consistent.

Consistency also depends on settings outside the game. Windows pointer acceleration must be off, the Windows pointer-speed slider should sit at its neutral middle notch, and CS2 raw input should be on - otherwise the OS distorts your movement and your eDPI no longer means what you think it means. Those are covered in the CS2 mouse settings guide; lock them once and your eDPI stays honest.

A Note on the Data

The eDPI curve and DPI split above are computed at build time from cs2pedia’s dataset of 1,000+ active pro profiles, derived per player from their recorded raw DPI and in-game sensitivity. That’s the point of this page: the numbers come from the same database that powers the rest of the site, recomputed on every deploy, not a hand-typed “most pros use 400–800” claim copied between blogs.

The dataset is a snapshot rather than a live per-event feed, and a small share of profiles don’t list both settings and are excluded from the curve - so read the distribution as the proven shape of pro sensitivity, current but not instant.

To go further: compare your number against individual player profiles, browse the full settings stats, lock in the supporting config with the CS2 mouse settings guide, and if you’re still choosing hardware, see which mice the field runs in the best mouse guide.