/
/
Settings & Config
Settings & Config
CS2 Pro Settings 2026: 30 Players, Full Table
Thirty players, one table. Then the reason you should not copy any row of it.
WHAT YOU’LL LEARN

Here is the table you came for, and then the part that makes it useful rather than just a list.
Every player, full settings
Sensitivity, DPI, the resulting eDPI, and how many centimetres of mousepad each player needs to turn a full circle.
Player | Team | Sens | DPI | eDPI | cm/360 |
|---|---|---|---|---|---|
s1mple | BC.Game | 3.09 | 400 | 1236 | 33.6 |
Ax1Le | 1WIN | 1.5 | 800 | 1200 | 34.6 |
EliGE | Team Liquid | 0.74 | 1600 | 1184 | 35.1 |
w0nderful | NAVI | 1.27 | 800 | 1016 | 40.9 |
donk | Team Spirit | 1.25 | 800 | 1000 | 41.6 |
huNter- | G2 | 1.25 | 800 | 1000 | 41.6 |
stavn | NIP | 2.5 | 400 | 1000 | 41.6 |
iM | NAVI | 1.2 | 800 | 960 | 43.3 |
Perfecto | No team | 1.2 | 800 | 960 | 43.3 |
m0NESY | Team Falcons | 2.3 | 400 | 920 | 45.2 |
device | 100 Thieves | 1.15 | 800 | 920 | 45.2 |
Brollan | HEROIC | 1.15 | 800 | 920 | 45.2 |
cadiaN | OG | 2.3 | 400 | 920 | 45.2 |
headtr1ck | Inner Circle | 2.3 | 400 | 920 | 45.2 |
electronic | No team | 2.2 | 400 | 880 | 47.2 |
aleksib | NAVI | 1.06 | 800 | 848 | 49.0 |
sh1ro | Team Spirit | 1.04 | 800 | 832 | 50.0 |
ZywOo | Vitality | 2.0 | 400 | 800 | 52.0 |
jL | No team | 1.0 | 800 | 800 | 52.0 |
frozen | FaZe | 2.0 | 400 | 800 | 52.0 |
Magisk | BC.Game | 1.0 | 800 | 800 | 52.0 |
FalleN | FURIA | 1.95 | 400 | 780 | 53.3 |
broky | No team | 1.9 | 400 | 760 | 54.7 |
NiKo | Team Falcons | 0.9 | 800 | 720 | 57.7 |
rain | 100 Thieves | 0.9 | 800 | 720 | 57.7 |
karrigan | Team Falcons | 0.9 | 800 | 720 | 57.7 |
ropz | Vitality | 1.77 | 400 | 708 | 58.7 |
dupreeh | Retired | 1.77 | 400 | 708 | 58.7 |
Twistzz | FaZe | 1.7 | 400 | 680 | 61.1 |
b1t | NAVI | 0.825 | 800 | 660 | 63.0 |
Sorted highest to lowest. The eDPI column is the one worth reading, because sensitivity on its own is meaningless without the DPI next to it.
The whole field fits in one band

Plot all thirty and the spread collapses.
The median is 864. The middle half sits between 760 and 960. Twenty four of the thirty, four in five, are between 700 and 1000.
That is a band three hundred points wide containing almost the entire list. The lowest player is b1t at 660 and the highest is s1mple at 1236, and almost nobody is near either edge.
The median cm/360 is 48.1 centimetres, which is roughly the width of a large mousepad. That is the physical fact behind every number in the table.
So the honest summary of thirty professional configs is: they are all playing more or less the same sensitivity, and the differences between them are smaller than the differences you would get from changing your grip.
If you want your own number in the same terms, the eDPI calculator gives you both figures in about ten seconds.
DPI is a preference, not a setting
Sixteen of these players use 800 DPI, thirteen use 400, and one uses 1600.
That tells you DPI is not what they are optimising. ZywOo on 400 and 2.0 and jL on 800 and 1.0 both land at exactly 800 eDPI, and their mouse travels the same 52 centimetres for a full turn. They are playing the same sensitivity written two different ways.
EliGE is the interesting outlier at 1600 DPI and 0.74 sensitivity, which still lands at 1184. Same logic, different arithmetic.
Pick whichever DPI your mouse is comfortable at, then set the in-game number so the product lands where you want it. The full breakdown of what the professional distribution looks like across 820 players is here.
Why you should not copy any of these rows

Here is the problem with every pro settings page, including the table above.
During 2026, three published settings sources gave NiKo three different configurations: 800 and 0.9, 400 and 1.58, and 800 and 0.8. Those work out to 720, 632 and 640 eDPI. A spread of 88 points on the same player in the same year.
Nobody is lying. Professionals change settings between events, and settings pages are snapshots taken on different days and then left alone.
This is the same failure as pro crosshair codes, where two major sites published completely different codes for the same four players in the same month.
So when you copy a row from a table like this, you are not adopting a professional’s settings. You are adopting what somebody recorded about them at some point, which may be a year out of date.
And even if it were current, it was calibrated to their desk, their mousepad, their grip and their role.
What to do with the table instead

The table is useful as a map, not as an instruction.
Work out your own eDPI and cm/360. That is your position on the map. Until you know it, nothing else in this article applies to you.
Check whether you are inside 700 to 1000. If you are, you are in the same band as four fifths of this list and your sensitivity is not what is costing you rounds.
Find who you already match. With thirty players spread across a narrow band, there is almost certainly a professional sitting on or near your exact number already. That is a more useful fact than any config you could paste, because it tells you your number is viable at the top level. The pro comparison tool does this directly.
Build a crosshair instead of copying one. Crosshair codes go stale faster than sensitivity does. The crosshair generator gives you a code you can actually keep.
Frequently asked
What eDPI do CS2 pros use? The median across these thirty is 864, with four in five between 700 and 1000.
What sensitivity does s1mple use? 3.09 at 400 DPI, which is 1236 eDPI and 33.6 cm per 360. The highest on this list by a clear margin.
What sensitivity does donk use? 1.25 at 800 DPI, which is 1000 eDPI and 41.6 cm per 360.
What DPI do most pros use? 800 slightly more often than 400 in this sample, 16 to 13. The DPI is not the setting that matters.
Should I copy a pro’s settings? No. Published lists contradict each other and go out of date, and the number was calibrated to someone else’s setup.
Why do settings sites disagree? Because pros change settings between tournaments and the lists do not get rechecked.
These settings are dated snapshots reviewed in June 2026, not live configurations. The eDPI column is DPI multiplied by in-game sensitivity. The cm/360 column is 41563.6 divided by eDPI, which comes from CS2 turning 0.022 degrees per mouse count, and you can verify any row of it with a calculator. Professional settings change, so treat this as a picture of a moment.
KEEP IMPROVING
Want someone to look at your own games? Book CS2 coaching and get your demos reviewed, or join the CS2 Rank Up Society for a structured 20-day plan and weekly accountability.

Brian Sirbu
CS2 COACH // GAMESENSELAB
MORE CS2 GUIDES


