AimFinder

Find your real Valorant sensitivity

A free in-browser sensitivity test on Valorant’s exact camera math, per-kill analysis of your .vrf replays, aim drills with Valorant movement and a CS2 → Valorant converter. No download, no overlay: Vanguard has nothing to see.

Analyze a replayFind my Valorant sensitivityTrain with drills
Replay analysis

Your .vrf replays, kill by kill

Upload a replay straight from %LOCALAPPDATA%\VALORANT\Saved\Demos. The analyzer decodes it, rebuilds every kill you got (how many degrees the fight required, how far your first ballistic movement carried, how long you spent correcting) and turns a systematic overshoot or undershoot into a concrete sensitivity proposal.

  • Per-kill breakdown: weapon, headshot, flick size, overshoot and time to first shot.
  • 128 Hz view angles: twice the resolution of a CS2 demo.
  • Your flick bias across all your replays turns into sensitivity propositions, with a confidence tier.
  • The file is deleted after parsing; only the per-kill numbers are kept.
Analyze my replays

Example: what a report extracts from your shot history

WeaponFlick sizeOvershootEngage time
Vandal31°+12%0.39 s
Sheriff19°+8%0.46 s
Phantom13°+5%0.34 s
Operator26°−4%0.52 s
Ghost9°+10%0.31 s

Median overshoot +9% across 47 kills in 3 replays → 0.39 is a touch high; proposed 0.36 (−8%).

Illustrative sample data — upload a replay to see your own numbers.

One kill, read at 128 Hz

For every kill the analyzer finds where your flick started, measures how far the first ballistic movement carried your crosshair against the angle the fight actually required, and times the correction that followed. The dashed line is that required angle: a curve that climbs past it is overshoot, one that stalls below it is undershoot.

Example: one Vandal flick, tick by tick

flick start0°target 31.0°kill
Flick size
31.0°
Overshoot
+12%
Correction time
211 ms
Peak speed
361°/s

First movement stopped at 34.7° for a 31.0° target: +12% overshoot, then 211 ms of correction before the kill.

Illustrative sample data — upload a replay to see your own numbers.

Example: a finder run converging round by round

38R154R245R349R446R547R6cm/360bias 0

Settled after 6 rounds: 46.7 cm/360 → Valorant sensitivity 0.35 @ 800 DPI (280 eDPI).

Illustrative sample data — run the finder to trace your own curve.

The Valorant sensitivity finder

A guided ~10 minute test: adaptive rounds of wide and micro flicks read whether your first movement flies past the target (sensitivity too high) or stops short (too low), close in on the value where your flicks land, then a blind A/B round against a decoy protects the result from placebo. Output: a Valorant sensitivity for your DPI, its eDPI and cm/360.

Find my Valorant sensitivity

Focused drills

17 scored drills for tracking, wide flicks, micro precision, reaction shots and counter-strafe one-taps. With realistic Valorant movement on, targets run at 6.75 m/s, stop almost instantly and jiggle-peek like agents do. Every run is saved to your history, so you can see whether a week of practice moved your numbers.

Train with drills
Follow the Ball

Mean recoil paths: a fixed start, then a random-side tail

Vandal25 · 585 rpm6 protected bullets, then random driftPhantom30 · 660 rpm8 protected bullets, then random driftSpectre30 · 800 rpm5 protected bullets, then random drift

Spray control, the Valorant way

Valorant recoil is only fixed for the first bullets of a spray, the protected window. After that the drift picks a side at random and every bullet carries the gun’s spread. The spray trainer reproduces both: pull down through the protected bullets, then react to the drift instead of memorizing a shape.

Open the spray trainer

Train with your own crosshair

Paste any Valorant profile code (0;P;…) into the crosshair generator to preview it, tweak it and copy it back into the game. Apply it to the trainer and every drill and test round is played with the crosshair you use in matches.

Open the crosshair generator

Example profile codes, drawn at rest

Cyan cross
0;P;c;5;h;0;0l;4;0o;2;0a;1;0f;0;1b;0
Green dot
0;P;c;1;o;1;d;1;z;3;0b;0;1b;0
Custom red plus
0;P;c;8;u;FF4655FF;h;0;f;0;0l;4;0o;0;0a;1;0f;0;1b;0

CS2 → Valorant at 800 DPI

CS2 sensValorant senscm/360 @ 800 DPI
1.000.31452.0 cm
1.250.39341.6 cm
1.500.47134.6 cm
1.800.56628.9 cm
2.000.62926.0 cm
2.500.78620.8 cm
3.000.94317.3 cm

Valorant = CS2 × 0.3143 at the same DPI.

Exact conversions, not sample data. Other DPIs and the reverse direction are in the converter.

Coming from CS2? Same cm/360, different number

Valorant turns the camera 0.07° per mouse count at sensitivity 1, CS2 0.022°. Multiply your CS2 sensitivity by 0.3143 at the same DPI and a full turn takes exactly the same mousepad distance, so your muscle memory carries over.

Open the sensitivity converter

Built on Valorant’s numbers, not CS2’s

0.07° per count

Valorant turns the camera 0.07° per mouse count at sensitivity 1 — more than three times CS2’s 0.022°. The test scene uses that constant, so a 180° flick here is the same hand movement as in-game.

103° field of view

Valorant locks 70.53° vertical FOV (103° horizontal at 16:9); the scene renders the same projection, so target sizes and flick distances look like the game.

Vanguard has nothing to see

The trainer runs in your browser tab: nothing to install, no overlay, nothing running alongside the game, no game files touched. Replays are analyzed from the file you upload, never read from the game client.

Valorant sensitivity FAQ

What is a good sensitivity for Valorant?

Most professional Valorant players sit between 0.25 and 0.5 at 800 DPI (roughly 200–400 eDPI, or 33–65 cm/360), but there is no single best value. If your first ballistic movement systematically flies past heads your sensitivity is too high; if it always stops short it is too low. AimFinder measures that bias from your flicks and recommends the value where they land.

How do I convert my CS2 sensitivity to Valorant?

Multiply the CS2 value by 0.3143 (0.022 ÷ 0.07) at the same DPI: CS2 1.6 becomes Valorant 0.503, CS2 2.0 becomes 0.629. The physical cm/360 stays identical, so your muscle memory carries over — only the number changes. The sensitivity converter handles both directions and DPI changes.

What is eDPI in Valorant?

eDPI is your mouse DPI multiplied by your in-game sensitivity: 800 DPI × 0.35 = 280 eDPI. It compares Valorant players regardless of DPI, but it is not comparable across games — 280 Valorant eDPI is the same hand speed as about 890 CS2 eDPI, because Valorant turns 0.07° per mouse count and CS2 0.022°.

What is cm/360 in Valorant?

cm/360 is how many centimeters your mouse travels for one full turn — the most physical way to express sensitivity. In Valorant, cm/360 = 13062.86 ÷ (DPI × sensitivity): 0.35 at 800 DPI is 46.7 cm. Lower cm/360 means a faster sensitivity; most pros land between 30 and 70 cm/360.

How does AimFinder find my Valorant sensitivity?

You play short flick rounds in a 3D scene that reproduces Valorant's camera exactly — 0.07° per mouse count, the 103° horizontal field of view at 16:9, raw mouse input. An adaptive staircase 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 and outputs a Valorant sensitivity for your DPI.

Is AimFinder safe with Vanguard?

Yes. Everything runs in the browser: nothing to download or install, no overlay, no game files touched, so Vanguard has nothing to object to. The optional replay analysis parses the .vrf file you upload on our server, keeps only the per-kill numbers and deletes the file.

Where are Valorant replay files?

Valorant records every competitive, unrated and premier match automatically as a .vrf file under VALORANT/Saved/Demos (on Windows: %LOCALAPPDATA%\VALORANT\Saved\Demos), typically 50–80 MB each. Upload the file as it is; the analyzer reconstructs every kill and derives your flick bias from it.

Valorant guides & tools