donk plays at 1000 eDPI, ZywOo at 760 and NiKo at 652. Three very different mouse speeds, all used at the top level. This guide puts their CS2 settings beside those of nine other pros so you can pick a setup to try, rather than assume there’s one number everyone agrees on.
You’ll need both columns when copying mouse speed: DPI and sensitivity. A 2.0 sensitivity on an 800-DPI mouse is twice as fast as 2.0 at 400 DPI. If you’d rather leave your mouse’s DPI alone, divide the player’s eDPI by your DPI to find the equivalent game sensitivity.
A full config import changes a lot at once. If it’s only the stretched picture or the slower mouse speed you’re curious about, try that part first. You’ll have fewer changes to undo if you dislike it.
Sensitivity and resolution are only part of a useful CS2 settings baseline. Stable performance, readable visuals and consistent audio matter too.
CS2 Pro Settings at a Glance
The short version: 400 DPI and 1280×960 are the most common choices among these twelve players. The table underneath has each player’s mouse, DPI, sensitivity and display settings if you’re looking for a particular name.
We’ve used the players’ ProSettings profiles for these entries. Players do change their setups, so the profile links are included with the numbers. Our calculation is the same throughout: eDPI = mouse DPI × in-game sensitivity.
| Setting | Most common value | Share of tracked pros | Reading |
|---|---|---|---|
| Mouse DPI | 400 DPI | 7 of 12, 58% | The five other mice are set to 800, though the faster DPI need not mean faster aim. |
| In-game sensitivity | 2.30 | 3 of 12, 25% | 0.815 at the bottom of the column, 3.09 at the top. Read the DPI column too. |
| eDPI band | 700 to 1000 | 8 of 12, 67% | Looking at the middle of the sorted list gives a median of 876. |
| Resolution | 1280×960 | 9 of 12, 75% | For 1024×768, see ZywOo or XANTARES. For 1920×1080, see ropz. |
| Aspect ratio | 4:3 | 11 of 12, 92% | Native widescreen is represented by ropz alone here. |
| Monitor refresh | 240 Hz or higher | 12 of 12 profiles with monitor data | No reason to copy a rate your own panel cannot display. |
| Raw mouse input | Built into CS2 | Game behavior | CS2 reads raw mouse movement, not an optional old CS:GO toggle. |
| Mouse acceleration | Windows pointer acceleration does not set CS2 aim speed | Game behavior | DPI and in-game sensitivity are the relevant base-speed inputs. |
One important limit on those percentages: our sample has twelve players. Seven use 400 DPI, which makes 58% of this table, not 58% of all professional players.
CS2 Settings for Top Pros
| Player | Team | Role | Mouse | DPI | Sensitivity | eDPI | Resolution | Aspect ratio | Source |
|---|---|---|---|---|---|---|---|---|---|
| donk | Team Spirit | Rifler | ZOWIE x donk Mouse (Unreleased) | 800 | 1.25 | 1000 | 1280×960 | 4:3 | ProSettings profile |
| ZywOo | Vitality | AWPer | Pulsar ZywOo The Chosen Mouse Gen.2 | 400 | 1.9 | 760 | 1024×768 | 4:3 | ProSettings profile |
| m0NESY | Falcons | AWPer | Logitech G Pro X Superlight 2 | 400 | 2.3 | 920 | 1280×960 | 4:3 | ProSettings profile |
| NiKo | Falcons | Rifler | Razer Viper V4 Pro | 800 | 0.815 | 652 | 1280×960 | 4:3 | ProSettings profile |
| ropz | Vitality | Rifler | Razer DeathAdder V3 HyperSpeed | 400 | 1.77 | 708 | 1920×1080 | 16:9 | ProSettings profile |
| s1mple | BC.Game | AWPer | Logitech G Pro X Superlight 2 | 400 | 3.09 | 1236 | 1280×960 | 4:3 | ProSettings profile |
| sh1ro | Team Spirit | AWPer | Logitech G Pro X Superlight 2 | 800 | 1.04 | 832 | 1280×960 | 4:3 | ProSettings profile |
| b1t | NAVI | Rifler | Logitech G Pro X Superlight 2 | 800 | 0.825 | 660 | 1280×960 | 4:3 | ProSettings profile |
| XANTARES | Aurora | Rifler | ZOWIE FK1-C | 400 | 2.3 | 920 | 1024×768 | 4:3 | ProSettings profile |
| KSCERATO | FURIA | Rifler | Logitech G Pro X3 SUPERSTRIKE | 800 | 1.45 | 1160 | 1280×960 | 4:3 | ProSettings profile |
| malbsMd | Team Liquid | Rifler | Logitech G Pro X2 SUPERSTRIKE | 400 | 2.3 | 920 | 1280×960 | 4:3 | ProSettings profile |
| apEX | Vitality | Rifler / IGL | ZOWIE EC2-EW (Unreleased) | 400 | 1.91 | 764 | 1280×960 | 4:3 | ProSettings profile |
A new mouse doesn’t necessarily mean new sensitivity. When checking a player’s latest equipment entry, look at the DPI and sensitivity too, rather than assume both changed with the hardware.
Mouse Settings: DPI, Sensitivity, and eDPI
Start with the slowest and fastest entries: NiKo at 652, s1mple at 1236 eDPI. There’s room for quite different preferences between them. Eight of the twelve fall in the 700 to 1000 band. The midpoint of the sorted list works out to 876 eDPI, while adding all twelve and dividing by twelve gives 877.7. Those are descriptions of the sample, not ideal settings to chase.
Mouse DPI, Sensitivity and eDPI
Seven mice are set to 400 DPI here, the other five to 800. You don’t have to switch between those DPI settings to copy someone. For example, ZywOo uses 1.9 at 400 DPI. On an 800-DPI mouse, 0.95 gives the same 760 eDPI. m0NESY’s 2.3 at 400 DPI becomes 1.15 at 800.
Try a full turn before settling on the slower values. NiKo’s setting needs more mouse travel than s1mple’s for that turn, and the edge of your pad is a real limit. Running out of space isn’t something copying another pro’s name will fix. You need more room or more speed.
Resolution and Aspect Ratio
1280×960 accounts for nine entries. ZywOo and XANTARES use 1024×768 instead, while ropz is the lone 1920×1080, 16:9 player in this group. That’s eleven 4:3 choices out of twelve.
Why stretched? You’re filling a widescreen panel with a 4:3 image, so everything widens, including the player models. The cost is a narrower horizontal view than 16:9. It won’t make a missed shot count as a hit: hitboxes, weapon accuracy and movement on the server don’t change with your CS2 resolution.
Video and Graphics Settings
Don’t stop at the average FPS reading. Watch what happens when several players, smoke and fire are on screen. A high average can hide an awkward stutter. Check that important shadows remain visible too before leaving every setting on Low.
For Reflex, check that your NVIDIA hardware supports it, then compare input latency with it on and off. The GPU and its workload affect the benefit. Keep one CS2 settings baseline for that check, with no other changes between runs.
When comparing anti-aliasing, don’t also switch the NVIDIA driver settings. You’d have two possible explanations for any difference. Return to the same scene at your usual resolution, change the game option, and compare the edges and frame rate there.
Crosshair, Viewmodel, and Audio
Before an import, copy your current crosshair code somewhere safe. It takes little effort and saves rebuilding the old shape if you dislike the replacement. The imported crosshair can look different from a screenshot: CS2 rescales pixel dimensions for resolution, while any stretching of the display also changes the proportions you see.
Viewmodel offsets are there to move the weapon on screen, so try them if the gun covers an area you’d like clear. With CS2 audio settings, listen for where sounds come from and keep the volume comfortable. If extra processing makes footsteps harder to pick out, undo it.
Test it with your normal weapons and finishes so visibility stays consistent in real matches.
Browse CS2 SkinsPro Settings by Role
| Role sample | Players | Average eDPI | Common resolution | Useful takeaway |
|---|---|---|---|---|
| Riflers | donk, NiKo, ropz, XANTARES, KSCERATO, b1t, malbsMd | 860 | 1280×960; XANTARES uses 1024×768 and ropz uses 1920×1080 | NiKo and KSCERATO use very different speeds despite both being riflers. |
| AWPers | ZywOo, m0NESY, s1mple, sh1ro | 937 | 1280×960; ZywOo uses 1024×768 | Some AWPers are slower than some riflers; role doesn’t separate the ranges. |
| IGL example | apEX | 764 | 1280×960 | A single IGL entry cannot establish a role-wide average. |
Player-by-Player Context
donk’s setup comes to 1000 eDPI: 800 on the mouse, 1.25 in CS2. That’s above the median of this table. On a 400-DPI mouse you’d enter 2.5 to get that speed. Try the mouse change first if you like; his stretched 1280×960 picture doesn’t have to come with it.
For ZywOo’s mouse speed, the numbers to copy are 400 DPI and 1.9 sensitivity, or 0.95 if your mouse is set to 800 DPI. Either gives 760 eDPI. His stretched resolution is 1024×768. Be careful with monitor listings here: the resolution of the panel isn’t necessarily the resolution selected inside CS2.
m0NESY’s 2.3 sensitivity goes with 400 DPI and a stretched 1280×960 picture. Work out the mouse speed and you get 920 eDPI, 160 more than ZywOo. The same unscoped mouse movement will therefore turn farther, though we aren’t comparing their zoom settings, mouse shapes or pads.
At the slow end of our list is NiKo: 652 eDPI, from 800 DPI and 0.815 sensitivity, paired with 1280×960 at 4:3. Halving the DPI to 400 means doubling his game value to 1.63. Try a broad turn across a site entrance with it; that tells you more about the room it needs than a few tiny aim adjustments.
Here’s the widescreen option in the table: 1920×1080, 16:9. ropz combines it with 400 DPI and 1.77 sensitivity, giving 708 eDPI. His mouse speed is fairly close to NiKo’s, even though one uses a native widescreen picture and the other stretched 4:3.
At 400 DPI and 3.09 sensitivity, s1mple’s 1236 eDPI is the fastest in this selection. It takes less hand movement to turn than any of the other eleven entries. That may be worth trying if you like a fast mouse, but being an AWPer doesn’t oblige you to play at that speed.
Don’t let the 1.04 sensitivity mislead you. With 800 DPI behind it, sh1ro’s setup comes to 832 eDPI, faster than ZywOo’s 760 at 1.9 sensitivity. His selected resolution is 1280×960.
800 DPI and 0.825 sensitivity put b1t at 660 eDPI, only eight above NiKo. If your mouse stays on 400 DPI, you’d enter 1.65 to match b1t. There’s little reason to chase those last few eDPI points if the larger issue is running out of mousepad.
The mouse numbers are familiar: 400 DPI, 2.3 sensitivity, 920 eDPI. m0NESY and malbsMd use that speed too. XANTARES differs in resolution, playing at 1024×768 stretched rather than their 1280×960.
KSCERATO has the fastest mouse among our riflers. His 800 DPI and 1.45 sensitivity work out to 1160 eDPI. Compare that with NiKo’s 652 before assuming riflers all favour much the same speed.
For malbsMd, enter 2.3 at 400 DPI to reproduce his reported 920 eDPI. His resolution is 1280×960 stretched. You can copy both without buying his equipment, although mouse shape, weight and the pad will still affect how the setup feels.
apEX is just four eDPI above ZywOo: 400 DPI multiplied by 1.91 gives 764. The resolution differs, at 1280×960 stretched. He’s our one IGL example, so these numbers tell us about apEX, not an average for all callers.
Crosshair and viewmodel choices can change independently of mouse speed. Save each preset before experimenting, and keep sensitivity steady while comparing the visual options.
Launch Options and Autoexec Commands Pros Use
A long launch string can look more useful than it is. -console, for instance, opens the console. It doesn’t add FPS. Some shared configs still contain old CS:GO options, so check what each flag does before pasting the lot into Steam.
| Entry | Current use | Practical guidance |
|---|---|---|
| Blank field | A simple baseline before adding any specific flag | The safest baseline. Add only a flag you can explain and test. |
-console | Opens the developer console at launch | Convenient, but not a performance boost. |
-refresh 360 or -freq 360 | Refresh-rate override in some older configs | The number must match a rate your monitor actually supports. |
-allow_third_party_software | Third-party capture/overlay compatibility | For a tool that requires the allowance, not extra FPS. |
+exec autoexec.cfg | Loads a named config at startup | Useful when the file is maintained and commands are current. |
-novid | Still appears in inherited profile strings | Legacy CS:GO habit. Do not treat it as an FPS optimization. |
-tickrate 128 | A leftover in older launch strings | Your launch options cannot change an official matchmaking server to 128 tick. |
Leaving the launch field blank is fine. Add a flag when you have a reason for it, such as loading a named config. A small CS2 autoexec file with commands you understand is easier to maintain than an old bundle whose purpose isn’t clear.
How to Copy and Adapt Pro Settings
- Pick a setup you can use. A similar role can help you narrow the table down, but check the mouse speed against the space on your desk.
- Match the speed, not just the sensitivity. Either copy the DPI too or calculate the equivalent value. The CS2 eDPI calculator handles that conversion between DPI settings.
- Leave the other settings alone. If sensitivity is the thing you’re trying, keep DPI, resolution and crosshair unchanged for now. You’ll have one change to judge.
- Do more than one drill. Try deathmatch, recoil control, transfers between targets and scoped flicks, then play normal matches with it. One empty-map test won’t show every awkward moment.
Say you’re moving from donk’s 1000 eDPI to NiKo’s 652. Expect the same turn to take more physical travel. If the mouse reaches the edge first, the copied setting doesn’t fit your current space. Mouse weight and pad resistance matter to the feel as well, even though neither appears in the eDPI calculation.
Write down your old DPI, sensitivity, eDPI and resolution before starting. You might like the slower mouse but dislike stretched 4:3. With the originals noted down, restoring the picture doesn’t mean giving up the mouse change too.
How to Calculate and Compare CS2 eDPI
Multiply the two numbers first. ZywOo’s 400 × 1.9 equals 760 eDPI. Want that speed at 800 DPI? Divide 760 by 800, which gives 0.95 sensitivity. Your Windows cursor can still move differently; you’re matching the aim speed in CS2.
Matching DPI alone isn’t enough. Both donk and NiKo use 800 DPI, but donk’s 1.25 gives 1000 eDPI and NiKo’s 0.815 gives 652. It’s the multiplication that exposes the difference.
This comparison is for CS2 base sensitivity. It leaves out zoom sensitivity and any separate acceleration software, as well as mouse weight, polling rate, grip and pad friction. Equal eDPI doesn’t promise that two mice will feel identical under your hand.
Comparison rule: Changing to 1600 DPI but wanting to keep 800 eDPI? The calculation is 800 ÷ 1600 = 0.50 sensitivity. Use the same division with your own target eDPI and new DPI.
FAQ
How often do professional CS2 players change their settings?
There’s no fixed schedule. A new mouse can arrive with the old DPI and sensitivity, and a crosshair can change without anything happening to the mouse. Check the actual entry you want to copy rather than assume a hardware update means every setting changed.
Should AWPers use a different eDPI from riflers?
Not necessarily. Our table has an AWPer, m0NESY, at the same 920 eDPI as riflers XANTARES and malbsMd. Base sensitivity isn’t the whole of AWP aim anyway: zoom sensitivity changes the scoped comparison, and positioning and control still matter.
Do CS2 pros use 400 DPI or 800 DPI more often?
400 DPI leads this particular table, seven players to five. We haven’t counted the whole pro scene. If you like 800 DPI for everyday use, keep it: half of a 400-DPI player’s game sensitivity will reproduce that player’s eDPI at 800 DPI.
Why do many professionals still use 4:3?
Stretched 4:3 gives the picture wider-looking models. Some players prefer that, despite losing horizontal view compared with 16:9. It doesn’t enlarge the hitboxes. ropz is a useful counterexample to the idea that you must play stretched: his entry is native widescreen.
Do professional players use NVIDIA Reflex in CS2?
Some do. There isn’t one Reflex choice shared by every pro, and their result won’t necessarily match yours. On supported hardware, compare latency with your normal game settings and workload to see what it does for your machine.
Can I copy a pro’s config without copying their hardware?
Yes. Your own 800-DPI mouse at 1.25 sensitivity will give donk’s 1000 eDPI. You don’t need his mouse to try the speed. Shape, weight and the pad still affect the feel, so the copied numbers aren’t a promise of an identical experience.
Which CS2 settings should I avoid changing too often?
Leave settings alone when they aren’t part of the problem. A crosshair disappearing on a pale wall calls for a color or outline change, not new sensitivity. Running off the mousepad calls for a look at speed and desk space, not a complete replacement of the video settings.
What launch options do CS2 pros typically use?
They vary by player. -console simply opens the console, refresh-rate flags need to suit the monitor, and the third-party-software flag is a compatibility allowance. None of that makes an old CS:GO bundle a required FPS tweak. Read each entry before copying it.
Do pros use raw input or Windows sensitivity?
CS2 uses raw mouse movement. The Windows pointer slider is about the desktop cursor, not the sensitivity in our table. To compare base aim speeds, use mouse DPI multiplied by CS2 sensitivity; don’t put the Windows setting into that calculation.
How much does mousepad size affect sensitivity choice?
It can rule out a copied low sensitivity pretty quickly. From your usual resting position, try a turn left and a turn right. A tiny adjustment onto one target won’t reveal the space problem. If you keep reaching an edge, you’ll need more usable pad space or higher sensitivity.
