How AimBench works
Every number on the site comes from one of two places: a sourced fact (a spec sheet, a measurement, a player's own setting, each with its link and the date it was checked) or a model we built and describe here. Facts are shown as facts, models are labelled as models.
What the Setup Score measures
How well your hardware is matched for competitive play, on a 0–100 scale: 0 is a stock office build (60 Hz office monitor, 125 Hz office mouse, membrane keyboard, bundled cloth pad; a stock headset off onboard audio if you add audio), and 100 is every domain at the point where more gear stops measurably helping. It is not a rank, a skill rating or a win-rate prediction. It's built from the same flags the diagnostics list, so the score and the bottleneck list can't disagree.
Six domains, weighted by the evidence
Each domain takes its worst flag (the limiting factor) and turns it into points: good 100, info 80, warning 50, critical 20. The headline is the weighted average, remapped so the office build reads 0. Without audio, the four aim domains are re-weighted to fill the whole score (they carry 68% of it when audio is on).
| Domain | Weight | What decides it |
|---|---|---|
| Input chain | 22% | Mouse polling against the 1000 Hz floor and the 2000 Hz sweet spot; the CPU cost of 4K/8K at low FPS. |
| Aim & surface | 10% | How well the pad and skates are built (consistency, build, durability), against the best-built surface for your materials. |
| Display | 24% | Refresh rate against the 144 Hz floor, on a frame-time curve; panel response that can't keep up with the refresh. |
| Keyboard | 12% | Membrane, mechanical, or Hall-effect with rapid trigger. |
| Audio — hear | 20% | Footstep imaging, whether your amp can drive your headphones, bass that masks footsteps, isolation for a loud room. |
| Audio — comms | 12% | Whether your mic chain has enough clean gain, and phantom power where it's needed. |
Curves above the floor
A step score can't tell a 144 Hz panel from a 540 Hz one. So past the floor, Display follows frame time and the input chain follows the polling interval, both in a straight line, flattening where the evidence says the gain stops (360 Hz for refresh, 2000 Hz for polling). Below the floor the warning points apply.
| Refresh | Frame time | Display points |
|---|---|---|
| 60 Hz | 16.7 ms | 20 (critical) |
| 120 Hz | 8.3 ms | 50 (warning) |
| 144 Hz | 6.9 ms | 85 |
| 165 Hz | 6.1 ms | 88 |
| 180 Hz | 5.6 ms | 90 |
| 240 Hz | 4.2 ms | 95 |
| 280 Hz | 3.6 ms | 97 |
| 360 Hz | 2.8 ms | 100 |
| 540 Hz | 1.9 ms | 100 |
| Polling | Report every | Input-chain points |
|---|---|---|
| 125 Hz | 8.0 ms | 50 (below floor) |
| 500 Hz | 2.0 ms | 50 (below floor) |
| 1000 Hz | 1.0 ms | 92 |
| 2000 Hz | 0.500 ms | 100 |
| 4000 Hz | 0.250 ms | 100 |
| 8000 Hz | 0.125 ms | 100 |
Controller mode
A pad has no mouse chain, surface or keyboard, so one Controller domain takes their 44% share and display and audio weigh the same as they do for mouse players. It scores two things. Measured input latency on the connection you use, averaged by an independent tester (a maker's figure never fills the slot, and an unmeasured connection is left out rather than guessed): 2 ms or less scores 100, falling in a straight line to 80 at one 144 Hz frame (6.9 ms); more than a frame is a warning and more than two is critical. Back paddles: without them your right thumb leaves the aim stick every time you jump, crouch or slide, so no paddles is a warning. Stick type (potentiometer sticks drift as they wear) and your deadzone are shown as advice. The 0 point is a stock first-party pad over Bluetooth on a 60 Hz panel.
Some flags are shown but never scored: whether your pad's glide suits your aim style, your sensitivity band, FPS under your refresh rate, mouse weight. They're choices or free settings, not gear quality. Scoring FPS once made a 240 Hz monitor score lower than a 144 Hz one at the same frame rate, which is exactly backwards.
The evidence ladder
The weights and the upgrade order follow how big each effect actually is, from the research summarised in Does gear give a competitive advantage? The short version: gear is a floor, not a booster. Below the floor it holds you back; above it, spending buys feel and consistency.
| Effect | What the engine does with it | |
|---|---|---|
| 1. Escape a sub-144 Hz display | Large | Below 100 Hz is critical, below 144 Hz a warning: the biggest single upgrade. |
| 2. Sensitivity in 20–80 cm/360, held consistently | Large, free | Flagged when outside the band. A setting, so it's a note, not points. |
| 3. System latency (Reflex, a steady FPS cap) | Small but real, free | FPS under your refresh is flagged as a free fix. Never scored: it made faster monitors score lower. |
| 4. Rapid-trigger (Hall-effect) keyboard | Consistency aid | The keyboard's top rung. |
| 5. Positional audio | Real, saturates early | Graded on footsteps only; tops out at a competent mid-priced stereo headphone. |
| 6. 144 → 240 Hz, 1000 → 2000 Hz polling | Small | Scored on the continuous curves below, so the step shows as a small gain. |
| 7. 4K/8K polling, 360 Hz+, pads and skates | Negligible to preference | Curves are flat here. Pad and skate build counts at the lowest weight. |
“Baseline cleared”
When no domain carries a warning or a critical flag, the dashboard says your setup has cleared the competitive baseline. Info flags (small, real headroom such as 144 → 240 Hz) don't block it. That's the honest point to stop upgrading and practise.
Upgrade picks
For each fixable flag the engine swaps every product in that category into your setup, re-scores it, and keeps only the ones that raise your score, best per price class. Ties break on the measured build score, then on price, never on catalog order or popularity. Prices are shown as a class (Budget to Flagship), never a number: your local store has the live price.
Sensitivity and cm/360
cm/360 is how far your mouse travels for one full turn: (360 × 2.54) / (DPI × sens × yaw), where yaw is each game's degrees-per-count constant. It doesn't depend on the game, which is why it can compare players across games and convert a setting from one to another. WARDOGS is the exception to the simple formula: its slider is affine (it has an offset), so it's converted with its own two constants. Each constant was checked against a published reference and against pros' own settings; games whose scale isn't a clean constant are marked approximate.
| Game | Constant | Model |
|---|---|---|
| CS2 / CS:GO | 0.022 | Exact |
| Valorant | 0.07 | Exact |
| Apex Legends | 0.022 | Exact |
| Overwatch 2 | 0.0066 | Exact |
| Fortnite | 0.005555 | Approximate |
| Rainbow Six Siege | 0.0057296 | Approximate |
| Call of Duty | 0.0066 | Exact |
| Battlefield 6 | 0.00075 | Exact |
| Marvel Rivals | 0.0176 | Exact |
| Escape from Tarkov | 0.125 | Approximate |
| The Finals | 0.001008 | Approximate |
| Rust | 0.1125 | Approximate |
| PUBG: BATTLEGROUNDS | 0.002222 | Approximate |
| WARDOGS | 0.03316 + offset 0.00368 | Exact |
Where the pro data comes from
215 tracked players, each with a source link and a check date. The player's own word wins: a chat command, a channel panel or their own video beats an aggregator, and 79 records come straight from one. Values are never inferred. If a source swaps a named product for something unidentifiable (“Custom keyboard”), the field is dropped rather than guessed, and an aggregator whose page hasn't changed in years is dated to when it last changed, not to when we last read it.
| Source | Records | Whose word |
|---|---|---|
| prosettings.net | 111 | Settings aggregator |
| twitch.tv | 38 | The player's own channel (panels / chat) |
| youtube.com | 20 | The player's own video or description |
| nightbot.tv | 13 | The player's own chat command |
| liquipedia.net | 10 | Esports wiki (identity, team) |
| streamelements.com | 7 | The player's own chat command |
| bestsettings.com | 3 | Settings site or wiki |
| gamingcfg.com | 3 | Settings site or wiki |
Where the specs come from
Hard specs come from the manufacturer's page, with independent measurements where a spec sheet hides the real difference: click latency and sensor behaviour from TechPowerUp, monitor response from the maker's published figures, headphone and amp data from RTINGS, Audio Science Review and Crinacle. Friction (glide), drive-match and mic gain are models built on those specs, labelled as models wherever they appear. Mousepad and skate build grades are reviewer consensus, cited per product.
What it can't tell you
Whether a shape fits your hand (that's the hand-size finder's job), how a switch feels, or whether you'll get better. Above the floor, practice beats gear by a distance.