Find your real CS2 sensitivity
Upload a match demo and AimFinder dissects every kill — flick size, overshoot, correction time, crosshair placement — then derives the sensitivity your aim actually performs best at. Verify it with the in-browser finder and train it with focused drills.
Demo upload & shot analysis
Drop in a .dem file straight from matchmaking: the parser replays your match and measures how you flicked onto every kill. No plugins, no VAC risk — the file is analyzed then deleted, only the per-kill results are stored.
The CS2 sensitivity finder
A guided ~10 minute test in a 3D scene with CS2's exact camera math. An adaptive staircase reads your overshoot and undershoot between rounds and closes in on the value where your flicks land, finishing with a blind A/B check against placebo.
Focused drills
Seven scored drills — tracking, wide flicks, micro precision, counter-strafe one-taps and more — with optional realistic CS2 movement. Every run is saved to your history, so progress is measured, not felt.
Why AimFinder
1:1 with CS2
Same yaw constant (0.022), same field of view, raw mouse input. A 180° flick here is a 180° flick in-game.
Evidence, not vibes
Systematic overshoot means your sens is too high; undershoot means too low. The staircase search reads your ballistic flicks and adjusts between rounds.
Yours to keep
Everything stays in your browser. Export your full trial data as JSON anytime from the history page.
CS2 sensitivity FAQ
What is the best sensitivity for CS2?
There is no single best CS2 sensitivity. Most professional players sit between 1.5 and 2.5 at 400–800 DPI (roughly 600–1400 eDPI), but the right value depends on your grip, your arm mechanics and your mousepad space. AimFinder measures how you actually flick and recommends the sensitivity where your first ballistic movement lands on target.
What is eDPI and how do I calculate it?
eDPI (effective DPI) is your mouse DPI multiplied by your in-game sensitivity. It lets you compare settings between players regardless of DPI: 800 DPI × 1.0 sens = 800 eDPI, exactly the same real speed as 400 DPI × 2.0. AimFinder reports your result as in-game sensitivity, eDPI and cm/360.
What is cm/360 in CS2?
cm/360 is how many centimeters your mouse must travel to turn a full 360° in-game — the most physical way to express sensitivity. In CS2, cm/360 = 41563.64 ÷ (sensitivity × DPI). Lower cm/360 means a faster sensitivity; most pros land between 30 and 70 cm/360.
Should I play CS2 at 400 or 800 DPI?
Either works if the eDPI is the same: 400 DPI × 2.0 feels identical to 800 DPI × 1.0. Higher DPI reduces pixel-skipping slightly and tracks micro-adjustments more smoothly on modern sensors, which is why most current pros run 800 or 1600 DPI with a lower in-game sensitivity. Pick one DPI, then let AimFinder tune the in-game value.
How does AimFinder find my CS2 sensitivity?
You play short flick rounds in a 3D scene that reproduces CS2's camera math exactly — same 0.022 yaw constant, same field of view, raw mouse input. An adaptive staircase algorithm detects whether your ballistic flicks systematically overshoot or undershoot, adjusts the sensitivity between rounds until it converges, and validates the result with a blind A/B check. A session takes about 10 minutes.
Is AimFinder free, and is it VAC safe?
Yes. AimFinder is free and runs entirely in the browser: nothing to download or install, no game files touched, no overlay — so there is no VAC risk. The optional demo analysis parses the .dem file you upload, keeps only the per-kill numbers and then deletes the file.
How do I test my new sensitivity in CS2?
Set it in the console with the sensitivity command (for example sensitivity 1.85) or in Settings → Keyboard & Mouse. Then give it a fair trial: warm up in aim_botz or a Fast Aim map, play a few deathmatches, and keep it for at least a week before judging. Constant switching hurts your aim more than any single value ever will.