VALORANT Crosshair and Settings: Finding Your Aim Profile

What You'll Be Able to Do After Reading This

By the end of this article you should be able to compute your own centimetres-per-360 from your DPI and sensitivity, know which band that places you in, and know whether that band suits the mousepad you actually own. You should be able to build a crosshair from parameters rather than from a copied profile code, and explain why each number is what it is. And you should be able to run a genuine A/B test on a settings change — one variable, a real sample, an objective metric — instead of the twenty-minute honeymoon that passes for testing in most lobbies.

The wrong mental model is that a correct sensitivity exists and you find it by copying a professional. Pros cluster in a range, not on a number, and it is wide enough that two players at opposite ends play visibly different games. A pro's settings give you a starting hypothesis, not an answer. The second wrong model is that the crosshair is cosmetic. It is an instrument: the only thing on screen telling you where your first bullet goes, whether you are currently accurate, and whether your placement was at head height when you swung. Players spend hundreds of hours tuning sensitivity by tenths and then aim with a crosshair whose gap is wider than the head they are shooting at.

The third wrong model is the one that wastes the most time: that changing a setting is how you get better. Settings remove obstacles. They do not add skill. A player with a badly wrong sensitivity is fighting their own hardware, and fixing it produces a genuine jump. A player with a reasonable sensitivity and bad aim has a crosshair-placement and movement problem, and no amount of tuning will fix it. Knowing which of those two players you are is most of the value of this article.

The Maths: Sensitivity, Resolution and Latency

VALORANT converts mouse counts into view angle at a fixed rate. At sensitivity 1.0, one count of mouse movement rotates your view by roughly 0.07 degrees. That single constant is enough to derive everything you need.

A full turn is 360 degrees, so at sensitivity 1.0 you need about 360 divided by 0.07, which is roughly 5143 counts, to spin once. Your mouse reports one count per DPI-step of physical movement, so the physical distance for a 360 is 5143 divided by your DPI, in inches, divided further by your sensitivity. Converting to centimetres gives the formula worth memorising:

cm per 360 is approximately 13063 divided by eDPI, where eDPI equals your mouse DPI multiplied by your in-game sensitivity.

Check it against reality. A player at 800 DPI and 0.4 sensitivity has an eDPI of 320, and 13063 divided by 320 is about 41 centimetres — roughly sixteen inches — for a full turn. That is squarely inside the range most professional players use. A player at 800 DPI and 0.25 has an eDPI of 200 and about 65 centimetres per turn, which is slow, arm-heavy aim. A player at 800 DPI and 0.6 has an eDPI of 480 and about 27 centimetres, which is fast, wrist-heavy aim. All three are playable. They are different games.

This formula is also how you convert from other shooters. If you are coming from Counter-Strike, the community conversion factor is roughly dividing your CS sensitivity by about 3.2 to get VALORANT sensitivity — and you can verify that against the formula rather than trusting the number, because the constant 0.07 degrees per count is what produces that factor.

DPI versus sensitivity is a real tradeoff, though a smaller one than internet arguments suggest. Lower DPI with higher sensitivity gives you finer granularity per sensitivity step, because each 0.001 change moves your eDPI less. Higher DPI with lower sensitivity gives you more counts per centimetre of movement, which some players report as smoother tracking, at the cost of coarser sensitivity steps and, on some sensors, interpolation or smoothing at non-native values. The safe practical answer is to use a native DPI step — 400, 800 or 1600 — and pick 800 unless you have a reason not to. Also make sure Windows is not interfering: disable pointer acceleration entirely, and leave the Windows pointer speed slider at the middle notch so the operating system is not scaling your counts.

Resolution is the second lever, and it interacts with sensitivity in a way that confuses people. Stretching a narrower aspect ratio across a widescreen panel does not change your centimetres per 360 at all — the angle per centimetre of mouse movement is untouched. What changes is the perceived speed: the same angular motion now sweeps more screen pixels horizontally, so horizontal movement feels roughly a third faster on a stretched four-by-three image than it does at native sixteen-by-nine. That is why players who switch to stretched often lower their sensitivity slightly afterward; they are not imagining the difference, they are compensating for a real change in visual velocity. The other resolution tradeoff is information versus target size. A stretched or letterboxed narrower ratio makes enemy models wider on screen, which genuinely helps at long range, at the cost of peripheral awareness — you simply see less of the sides. There is no correct answer here, only a preference you should arrive at by testing rather than by copying.

Latency is the third lever and the one most players ignore. Everything between your hand and the pixel costs time: mouse polling, the operating system's input queue, the simulation, the render queue and the panel's refresh. The practical steps are straightforward. Keep the mouse at 1000 Hz polling unless you have a specific reason and a strong CPU for higher. Leave raw input enabled so the game reads the device directly rather than through Windows' scaling. Enable the low-latency mode your GPU vendor offers if the game exposes it. And treat framerate as a latency setting rather than a graphics setting: lowering detail raises framerate, and higher framerate reduces the time between your input and the frame you see. Do not lower settings so far that distant enemy silhouettes lose definition — model detail and at least some anti-aliasing are worth keeping, because an enemy you cannot resolve is an enemy you cannot shoot.

Sensitivity Bands

Two rules fall out of this table. The first is the pad rule: your usable pad width should be at least about seventy-five percent of your 360 distance. If your 360 is 45 centimetres, you want roughly 34 centimetres of unobstructed run, because a 180 from the centre of the pad is 22.5 centimetres and you need margin on both sides. Players who complain about "running out of mouse" are almost always at a sensitivity their pad cannot serve. The second is the range rule: most people who have never thought about it are too fast. If you are coming from a game with low time-to-kill and a lot of turning, or if you grew up on a laptop trackpad, your instinct will be to set sensitivity high. VALORANT punishes that because first-shot accuracy is everything and precision is cheaper to gain by slowing down than by practising.

If you have no idea where to start, take your 360 distance, and if it is under 30 centimetres, add roughly twenty percent. If it is over 60, subtract roughly fifteen percent. Then leave it alone for a month.

Three Build Walkthroughs

Build One: Starting From Zero

Step one: measure your mousepad's usable width with a ruler, not by eye. Step two: multiply that by about 1.3 to get the 360 distance your pad comfortably serves; if your pad gives you 34 centimetres, target a 360 of about 45 centimetres. Step three: convert that to eDPI using 13063 divided by the target — 45 centimetres gives an eDPI of roughly 290. Step four: choose a native DPI, 800 by default, and divide to get sensitivity: 290 divided by 800 is about 0.36. Step five: enter it, then do the pad test — start at the centre, swing a comfortable 180, and check that you did not hit an edge. Step six: build a crosshair before you play a single match: colour green or cyan, outline on at thickness 1 and full opacity, inner lines length 4, thickness 2, offset 2, centre dot on at thickness 1, movement error on, firing error on. Step seven: play fifty deathmatches before changing anything.

Build Two: Converting From Another Tactical Shooter

Step one: do not use a raw multiplier you found on a forum without checking it. Compute instead. Take your old sensitivity, convert it to a 360 distance using that game's known constant, then convert that distance back into VALORANT eDPI with 13063 divided by the distance. Step two: once you have the number, spend ten minutes in the range doing slow, deliberate flicks between two fixed targets at roughly the distance of a mid-length lane. Step three: check the overshoot direction. If your flicks consistently land past the target, drop eDPI by about eight percent. If they land short and you need a second correction, raise it by about eight percent. Step four: do not import your old crosshair. Different games have different palettes and different enemy outline colours; build a new one. Step five: accept two weeks of feeling worse. Conversion always feels wrong for a while, and switching back mid-way resets the adaptation clock.

Build Three: Rebuilding After Five Hundred Hours on a Bad Setup

This is the hardest case, because your muscle memory is calibrated to the wrong thing and every session will feel worse before it feels better.

Step one: identify what is actually broken. If your problem is long-range precision, go slower. If your problem is turning on close targets, go faster. If your problem is shakiness during slow tracking, go slower and work on grip. Do not change both sensitivity and crosshair and resolution in the same week. Step two: make one change of about fifteen percent, in one direction. Step three: commit to three weeks. Neural adaptation to a new sensitivity is measured in days of consistent play, not minutes, and the standard failure is changing back on day two because a deathmatch went badly. Step four: rebuild crosshair placement deliberately during this period. Because your flick calibration is gone, you will be forced to rely on pre-aiming, which is the habit you should have had anyway. Many players come out of a sensitivity rebuild with better aim than before, entirely because of this forced re-learn. Step five: at the end of week three, evaluate with the numbers from the practice plan below, not with feelings.

Crosshair Parameters, Ranged

Colour deserves more than a table cell. The correct colour maximises contrast against two things: the map's palette and the enemy highlight colour you selected. VALORANT's maps lean on desaturated greys, tans and blues with bright skyboxes, which is why white crosshairs wash out exactly when you need them. The enemy outline defaults to a warm colour, so warm crosshairs blend into the thing you are shooting. Green and cyan are the standard answers and are also rare in the environment. Change your highlight colour and re-check the crosshair against it — the most common unforced error in crosshair setup.

The gap deserves a note too. A gap wider than the target's head gives you less information than a head-sized or smaller one, because you lose the visual signal of the head entering the centre. Players who insist on a wide gap usually fight at very close range, where the head is large on screen; players who hold long angles should shrink it.

Advanced and Edge Cases

Scoped sensitivity is the first edge case. If your client exposes a scoped sensitivity multiplier, leave it at 1.0 until you have real time on the Operator, then consider lowering it slightly if your scoped flicks consistently overshoot. Because the zoom narrows your field of view, the same angular motion covers more screen, and many players find scoped aim too fast even at a multiplier of 1.0. The trap is changing it before you have enough scoped shots logged to know whether you overshoot or under-rotate.

Per-agent sensitivity is the second, and almost nobody should do it. The argument for it is that an entry duelist turns more than an anchor holding a long angle, so the entry player wants a faster setting. The argument against is that motor learning is context-specific and expensive, and two calibrations mean neither is automatic. If you must, keep the difference small.

Refresh rate changes feel. Moving from 60 Hz to 144 Hz or higher changes how smoothly you can track a moving target and how quickly you see an enemy appear from cover; it does not change your sensitivity, but it almost always changes the sensitivity you prefer, because smooth motion makes faster settings controllable. Re-run your evaluation after a monitor upgrade rather than assuming your old number still applies.

Sensor deviation is real and unglamorous. Two mice set to "800 DPI" can differ by a few percent, and switching peripherals silently changes your eDPI. If you switch mice and your aim mysteriously degrades, measure rather than guess: do a ruler test by moving the mouse a fixed physical distance and comparing the count, or simply accept that you need a week to recalibrate.

Physical inputs matter more than most settings menus. Pad friction changes effective sensitivity — a slow cloth pad makes fast flicks harder and a hard pad makes micro-corrections twitchier. If you are at a good eDPI and still cannot stop shaking at long range, the problem is frequently your grip or your arm position, not your number.

Common Mistakes and Their Corrections

A Three-Week Practice Plan and a Real A/B Protocol

The daily routine is short and boring, which is the point. Ten minutes of slow, deliberate flicks between fixed targets, concentrating on landing exactly on the first try rather than on speed. Ten minutes of tracking a moving bot at whatever distance you find hardest, maintaining the crosshair on the head rather than snapping to it. Ten minutes of counter-strafe work — move, stop, shoot, and watch the movement error indicator close before you fire. Then play.

Week one: establish a baseline. Record your score on the game's bot practice at a fixed difficulty with strafing enabled, run it five times, and take the median. Record your headshot percentage over ten deathmatches. These two numbers are your yardstick for everything afterward.

Week two: introduce the single change you want to test, and only that one. Continue the daily routine and log the same two numbers every session. Do not look at the numbers mid-session and do not revert after a bad day.

Week three: compare. If both metrics moved in the same direction by a margin larger than your normal session-to-session noise, keep the change. If they moved in opposite directions or by less than the noise, revert — you have learned that this variable does not matter for you, which is a genuine result.

Self-diagnosis is the part that actually separates players who improve from players who fiddle. Ask where your misses go. Consistent overshoot means your eDPI is too high; consistent undershoot on large turns means it is too low. Ask at what range you lose fights. Losing close-range fights against players who move suggests too slow a setting; losing long-range duels to players who hold still suggests too fast. Ask whether your flicks are good but your follow-up is bad — if you land near the target and then miss, your problem is micro-correction and crosshair placement, and no sensitivity change will help. In that last case, the fix is a practice routine, not a settings menu.

The honest test for whether a change helped: play a session where you deliberately do not think about your settings at all. If the new sensitivity is correct, you stop noticing it within about fifteen minutes. Settings you have to think about are settings that are wrong.

Closing Synthesis

Three numbers decide almost everything: your eDPI, your crosshair gap, and your framerate. Get eDPI into the band your pad can serve, get the gap roughly head-sized at your most common fight distance, and get framerate high enough that latency is not what loses duels. Everything beyond that is preference, worth exactly as much as the testing behind it. The players who improve fastest are not the ones with the most optimised profiles; they are the ones who change one thing, keep it for three weeks, measure twice, and spend the rest of their time on the thing that actually scales — pre-aiming at head height so that when you swing a corner, the only movement left is a small correction instead of a large flick. Sensitivity determines how fast you can make that correction. Crosshair placement determines whether you need to make it at all.