Quick Settings Checklist
Apply these five changes before adjusting anything else:
- Set DPI to 400 or 800 in your mouse software
- Set polling rate to 1000Hz (or 4000Hz if you have a 240Hz+ monitor and a modern CPU)
- Disable Enhance Pointer Precision in Windows mouse settings
- Enable Raw Input in your FPS game (usually under Mouse or Advanced settings)
- Set Windows pointer speed to the 6th notch out of 11 — the exact center
The rest of this guide explains the mechanism behind each setting and how to dial in the fine details for your game and playstyle.
DPI: Why the Number Itself Doesn’t Matter (But Your eDPI Does)
Here is what most settings guides get backwards: your DPI number is almost meaningless on its own. What determines how far your crosshair moves for a given hand movement is your eDPI — effective DPI — which is your hardware DPI multiplied by your in-game sensitivity.
800 DPI with 0.35 sensitivity gives you 280 eDPI. 400 DPI with 0.70 sensitivity also gives you 280 eDPI. Both setups move the crosshair the same distance for the same physical mouse movement. Same 360-degree rotation distance. Same flick arc. Mathematically identical.
So why do 66% of professional CS2 players use 400 DPI instead of spreading evenly across the range? Two reasons that the simple math does not capture:
- Sensor noise amplification. Modern sensors produce tiny tracking jitter at rest — vibrations from typing, a fan, a desk wobble. At 1600 DPI, a 0.01mm desk vibration registers as a visible crosshair twitch. At 400 DPI, the same vibration falls below the tracking threshold. Lower DPI makes your crosshair more stable during the moments you are not intentionally moving.
- Physical movement range and arm engagement. A low-eDPI setup requires larger hand movement to achieve the same crosshair rotation. Larger movement means your arm muscles are doing the work rather than your wrist alone — and arm muscles are more precise over extended play. This is why the average CS2 professional moves their mouse 47 cm to complete a full 360-degree turn [1].
The data from 878 tracked CS2 professionals: 66% use 400 DPI, 28% use 800 DPI, and only 5% use 1600 DPI or higher [1]. There is no competitive reason to exceed 800 DPI for FPS games.
eDPI Ranges by Game Type
Your eDPI target varies by game. Tactical shooters punish overshooting and reward micro-adjustments, so pros run lower. Movement-heavy games are slightly more forgiving:
| Game | Pro eDPI Range | Notes |
|---|---|---|
| Valorant | 200–450 | Median 256 among pros; one-tap headshots reward low sens [2] |
| CS2 | 700–1200 | Median 830; recoil control rewards lower sensitivity [1] |
| Apex Legends | 800–1600 | Movement-heavy game; slightly higher eDPI is viable |
| Call of Duty (MP) | 600–1200 | Faster TTK; quicker target acquisition matters more |

Polling Rate: Match It to Your Monitor, Not Your Marketing Budget
Polling rate sets how often your mouse reports its position to your PC. At 1000Hz, the mouse sends an update every 1ms. At 4000Hz, every 0.25ms. At 8000Hz, every 0.125ms.
Those smaller intervals only improve your aim if your monitor can actually display the difference — and only if your CPU can handle the extra interrupts without slowing the game down.
| Polling Rate | Report Interval | Recommended For | CPU Overhead |
|---|---|---|---|
| 500Hz | 2.0ms | Older hardware, budget builds | <1% |
| 1000Hz | 1.0ms | Most gamers; up to 240Hz monitors | <1% |
| 4000Hz | 0.25ms | 240Hz+ monitors; modern CPU required | 2–5% |
| 8000Hz | 0.125ms | 360Hz+ displays; high-end CPUs only | 5–10% |
The 8000Hz reality check: moving from 1000Hz to 8000Hz recovers less than 0.9ms of latency total. On a mid-range CPU already running near capacity during demanding scenes, that change can drop CS2 frame rates by 3–4% and introduce stutter during fast 180-degree turns. On a Ryzen 7 7800X3D or Intel 13th gen equivalent, the same change is imperceptible [4]. The CPU overhead at 4000Hz sits at 2–5% — meaningful but manageable. At 8000Hz it rises to 5–10% [4].
For most competitive players: 1000Hz is the correct setting. Upgrade to 4000Hz only if you have a 240Hz+ monitor, a modern CPU, and you are maintaining 240+ FPS consistently. The 8000Hz marketing push from mouse brands is aimed at a very narrow slice of setups where it actually helps. For everyone else it is a downgrade disguised as an upgrade.
For more on optimising your full system for frame rate consistency, see our guide on how to optimise your PC for better FPS.
In-Game Sensitivity: Finding Your Starting eDPI
Once you have set your hardware DPI, calculate your in-game sensitivity target using this formula:
In-game sensitivity = Target eDPI ÷ Your DPI
For Valorant at 400 DPI targeting 280 eDPI: 280 ÷ 400 = 0.70 sensitivity. For CS2 at 800 DPI targeting 800 eDPI: 800 ÷ 800 = 1.0 sensitivity. Start at the lower end of your game’s pro range. Give it two to three days before deciding the sensitivity feels wrong — adjustments take time to settle into muscle memory, and the first day always feels too slow.
Zoom and scope sensitivity is one setting almost every guide omits. In CS2, a Zoom Sensitivity Multiplier of 0.818819 keeps your scoped crosshair movement proportional to your unscoped movement. Without this correction, your scoped aim runs at a different effective sensitivity, meaning your brain builds two separate sets of muscle memory — one for rifles, one for scopes. The 0.818819 value matches the field-of-view change from the default scope zoom level.
In Valorant, set Scoped Sensitivity Multiplier to 1.0. In Apex Legends, set ADS Mouse Sensitivity Multiplier to 1.0. In Overwatch 2, Relative Aim Sensitivity While Zoomed at 100% achieves the same result. Set it once, verify it feels consistent, and never change it again.
Mouse Acceleration: The Setting That Breaks Muscle Memory
Muscle memory works by internalising a fixed relationship: this much hand movement equals this much crosshair rotation. Mouse acceleration breaks that relationship because the cursor travels a different distance depending on how fast you move the mouse. Move quickly and you overshoot. Move carefully and the crosshair barely responds. After a year of practice, you are still relearning the curve every session rather than building on a stable foundation.
Every professional FPS player has mouse acceleration disabled — both in Windows and in-game [3].
Windows (Enhance Pointer Precision):
Settings → Bluetooth & Devices → Mouse → Additional Mouse Settings → Pointer Options tab → uncheck “Enhance Pointer Precision.”
In-game Raw Input:
Enable the Raw Input toggle in your game’s mouse settings. This bypasses Windows cursor scaling entirely and reads directly from the mouse driver. Without Raw Input enabled, some games continue applying Windows pointer acceleration even after you disable Enhance Pointer Precision at the OS level. Raw Input closes that gap. In CS2 it is called “Raw Input” under Keyboard / Mouse settings. In Valorant it is enabled by default. In Apex Legends, disable “Mouse Acceleration” under Mouse settings.
To understand how all your settings interact with in-game frame time, our game settings explained guide covers the full input pipeline from hardware to render.
Three Settings Most Players Completely Ignore
Lift-Off Distance (LOD)
When you lift your mouse to reposition, does your crosshair drift? That is your lift-off distance (LOD) causing the problem. LOD sets the height at which your sensor stops tracking after you lift the mouse from the pad. Set it too high and the sensor keeps reading movement as you slide the mouse back to centre position, pushing your crosshair off target before you have even moved intentionally.
For arm aimers who regularly lift and reposition during low-sensitivity play, a high LOD means every repositioning stroke introduces a small crosshair deviation that needs a correction micro-adjustment. The competitive sweet spot is 1–2mm. Most gaming mice allow LOD adjustment in their companion software under labels like “Low” and “High” or specific millimetre values. Set it to the lowest stable option for your mousepad surface and verify that tracking does not cut out during normal movement.
Windows Pointer Speed
Leave Windows pointer speed at exactly the 6th notch out of 11 — the exact centre. At this position, Windows applies a clean 1:1 multiplier with no scaling. Any other position applies a curve that stacks on top of your DPI and in-game sensitivity, making your eDPI calculation invalid and introducing a hidden sensitivity variable that changes how your aim feels between Windows updates. It looks inconsequential. It is not.
Angle Snapping and Mouse Prediction
Some mice offer an “angle snapping” or “prediction” feature that smooths diagonal movements into straighter lines. It sounds helpful for tracking targets. It is not — the smoothing introduces a few milliseconds of input lag and subtly alters your actual movement path relative to your physical hand movement. Disable it in your mouse’s companion software (Logitech G Hub, Razer Synapse, SteelSeries GG). The feature exists for office productivity use, not gaming.
Settings by Player Type
What works for a dedicated CS2 ranked player does not work for someone who games two evenings a week. Use this table to find your starting configuration:
| Player Type | DPI | Polling Rate | eDPI Target | First Priority |
|---|---|---|---|---|
| New to FPS | 800 | 1000Hz | 500–800 | Disable Enhance Pointer Precision — do this first |
| Casual (under 5h/week) | 800 | 1000Hz | 600–1200 | Comfort over precision; higher eDPI reduces fatigue |
| Competitive (ranked, 10h+/week) | 400 or 800 | 1000Hz | 250–800 (game-specific) | Match eDPI to your game’s pro range; set zoom sensitivity |
| Pro-style (daily aim training) | 400 | 1000–4000Hz | 200–500 | Low LOD, 6/11 pointer speed, Raw Input, no angle snapping |
New players: resist copying pro settings directly. A 280 eDPI setup that requires 47 cm of mouse movement per full rotation only builds consistent muscle memory if you have the desk space and play enough hours to internalise it. Start in the 600–800 eDPI range, lower gradually as your aim stabilises, and never change your sensitivity mid-ranked-session.
Frequently Asked Questions
Does higher DPI mean better aim?
No — and this is the most common misconception in gaming peripherals marketing. Higher DPI increases your cursor speed at the same in-game sensitivity, but sensitivity is adjustable. A 3200 DPI mouse at 0.1 sensitivity and a 400 DPI mouse at 0.8 sensitivity produce identical crosshair movement per inch. The only advantage of higher DPI is a marginally higher theoretical resolution ceiling, which matters below 400 DPI but is irrelevant above it. What determines aim quality is consistent muscle memory built on a stable, fixed eDPI — not the hardware DPI number itself.
Should I upgrade from 1000Hz to 4000Hz or 8000Hz polling rate?
At 1000Hz you already get 1ms position updates — fast enough for any monitor up to 240Hz. Upgrading to 4000Hz recovers 0.75ms on a 240Hz+ setup with a modern CPU. Upgrading to 8000Hz recovers another 0.125ms while increasing CPU overhead by 5–10%. The trade-off is only worth it if you are on a 360Hz+ display, maintaining 360+ FPS consistently, and running a Ryzen 5000 series or Intel 12th gen CPU or newer. For everyone else, 1000Hz is the correct setting and higher polling rates introduce more risk than they remove [4].
How long does it take to adjust to a new sensitivity?
Expect three to five days of uncomfortable play before the new setting starts to feel natural, and two to four weeks before it is fully internalised. The common mistake is abandoning a new sensitivity after the first day because flick shots feel imprecise. That imprecision is the old muscle memory misfiring, not evidence the new sensitivity is wrong. Track your stats over two weeks — accuracy and first-shot reliability are better adjustment metrics than how the sensitivity feels in the first session.
Sources
[1] CS2 Best Settings & Options Guide — ProSettings.net
[2] eDPI Calculation Method for FPS Games — ZOWIE BenQ
[3] Enhance Pointer Precision for Gaming: On or Off? — Esports.net
[4] Gaming Polling Rate Explained: 125Hz to 8000Hz — Kordu Tools
