ReflexTimer

Aim Trainer Settings Guide: DPI, Sensitivity, and Accuracy

By oogwaaay (ReflexTimer operator) · Last updated: November 7, 2026

Most aim trainer score changes come from setup and technique, not from talent. This guide explains which settings actually matter, how to compare them without fooling yourself, and how to build a repeatable practice routine.

Aim trainer scores are sensitive to settings; if you want a separate simple-response baseline, use the reaction time test. Change your sensitivity, DPI, or mouse acceleration and the same hand movement produces a different cursor movement; change your grip or seating position and the same target may feel harder. The problem is that most players change several settings at once, play a few rounds, and conclude that the new setup is better. This guide is about avoiding that mistake.

What actually affects an aim score

Four groups of variables matter. Measurement conditions: display refresh, mouse polling, browser, and the aim trainer's target size and distance. Input mapping: DPI, sensitivity, and acceleration. Physical setup: grip, hand position, mousepad, chair, and desk height. State: sleep, fatigue, warm-up, and attention. A score change can come from any of these, so a useful comparison changes one group at a time.

Of these, the input mapping and physical setup are the ones most under your control in a short session. They are also the ones most often changed all at once.

DPI and sensitivity are not the same thing

DPI (dots per inch) describes how far the cursor moves for a given physical mouse movement. Sensitivity is a software multiplier applied on top. You can change one and compensate with the other to keep the same effective cursor movement. That is why comparing raw DPI numbers is not very meaningful: 800 DPI with one sensitivity can produce the same cursor travel as 1600 DPI with half the sensitivity.

The useful concept is the combined mapping — often described as eDPI (DPI × sensitivity) or as the physical distance needed for a 360-degree turn. Those descriptions stay comparable when you change one number and adjust the other. For this aim trainer, what matters is the cursor distance per hand movement, because that determines how much movement each target requires.

Mouse acceleration

Mouse acceleration changes the cursor distance depending on how fast you move. When it is on, the same hand displacement produces different cursor travel at different speeds, which makes target acquisition harder to learn. If you want a stable, comparable aim score, turn acceleration off and keep it off across sessions. This is not a universal law of aiming, but it removes a variable that makes practice less repeatable.

Some players use acceleration deliberately; that is a choice. The point is to know whether it is on and to keep it consistent if you are comparing scores.

Polling rate and display

Mouse polling determines how often the device reports its position: 125 Hz every 8 ms, 500 Hz every 2 ms, 1,000 Hz every 1 ms. Higher polling can reduce input delay slightly, but it also increases CPU load and may be less stable on some systems. A wired connection removes one source of variability; a wireless mouse can be excellent, but interference and battery state can add noise.

Display refresh affects when a new frame is visible. A higher refresh rate reduces the waiting time between frames, which can make targeting feel more responsive and reduce score variance. It does not change your hand speed; it changes the information flow. Keep the display mode and refresh setting consistent across sessions.

Grip, posture, and comfort

Grip and posture are not soft factors. A tense grip tires the forearm quickly; a desk that is too high or a chair that is too low changes the angle of your wrist and the range of motion available. A neutral wrist, a supported forearm, and a comfortable reach usually produce more consistent movement than a strained setup.

Change one physical variable at a time. If you move your chair and change your grip in the same session, you will not know which one helped. Give each change a few rounds before deciding.

A controlled A/B routine

Use the aim trainer as the measuring instrument:

  1. Baseline. Run three rounds with your current setup and record the median average time and accuracy.
  2. Change one setting. For example, turn acceleration off, or adjust sensitivity by a small amount.
  3. Re-test. Run three rounds under the new setting, under the same conditions.
  4. Compare medians. A difference smaller than your normal variation is not evidence; repeat on another day before keeping the change.

This is a small experiment, not a laboratory study. Its value comes from controlling the obvious variables: same device, same browser, same time, one change at a time. If you change sensitivity, DPI, grip, and sleep in one day, you will not know what mattered.

What not to change mid-session

Do not change sensitivity between rounds while chasing a score. Each sensitivity change resets part of your motor calibration, and the resulting score reflects the adjustment period rather than your skill. Do not change the aim trainer's viewport or browser zoom between rounds either; both change the effective target size and distance.

If you are testing a new setup, accept that the first round or two may be worse while you adapt. Compare the settled rounds, not the first attempt after a change.

A worked example: changing sensitivity

Suppose your aim average is 520 ms per target with a sensitivity you have used for months. You halve the sensitivity and play three rounds. The first round is worse, the second is closer, and the third is roughly equal to your baseline. It is tempting to say the new sensitivity is neutral, but the experiment has not settled: you may still be adapting, and the target positions are not identical across rounds.

A cleaner version keeps the same test conditions and gives the new setting a full session, then repeats the comparison on another day. If the median is still worse after adaptation, the change is probably not helping. If it is consistently better across sessions, it might be — but the difference must be larger than your normal round-to-round variation to be meaningful.

Mousepad and desk space

The physical space available shapes your effective sensitivity. A large mousepad allows low-sensitivity arm aiming; a small pad may force you into a higher sensitivity or into lifting the mouse repeatedly. Neither is inherently better, but the setup should let you reach the targets without running out of pad mid-movement.

If you change the pad or the available space, treat it as a setup change and re-baseline. The same hand movement now produces a different cursor travel if the sensitivity is unchanged but the usable area shrinks; you may unconsciously start lifting or shortening your movements, which shows up as a change in the score.

What to record

Record the settings that define the measurement: DPI, sensitivity or eDPI, acceleration on/off, polling rate, display refresh, browser viewport, and the aim trainer's target size/distance if the page exposes them. Add the date and a note about sleep and warm-up. This is enough to make next week's comparison meaningful. Keep the note short — a few lines per session is enough — and update it only when something material changes, so the history stays readable.

A practical ten-minute routine

For practice rather than testing:

  1. Warm up with one slow round. Aim for the centre of each target; do not chase the timer.
  2. Run three scored rounds with your current settings and record the median.
  3. Practise one skill — for example, moving the cursor in a straight line to the target rather than overshooting.
  4. Run two more rounds and compare with the earlier median.
  5. Stop while fresh. A short, focused session is more useful than a long, tired one.

Record the setup alongside the score: DPI, sensitivity, acceleration, polling rate, display refresh, and accuracy. Without that context, a saved score is not comparable to next week's.

Common mistakes

Chasing a high DPI because it sounds faster. DPI is a mapping, not a skill. What matters is the cursor distance per hand movement and your control over it.

Changing sensitivity every round. You are measuring adaptation, not skill.

Comparing aim scores across devices or viewports. Target size and distance change with the layout; the score is not comparable.

Ignoring accuracy. A fast average with many misses is not necessarily better than a slightly slower, clean run. Track both.

Limits

This page is a practical guide, not a prescription for a particular game or a guarantee of improvement. The best settings are the ones you can reproduce and control, and the most useful comparison is your own median across several rounds under the same conditions. A setting that makes your scores more consistent is often more useful than one that produces a single lucky fast round. Small sensitivity differences are usually not worth chasing; consistency and comfort matter more than finding a perfect number. For the measurement chain behind input and display latency, see reaction time test accuracy and the latency calibration guide.

A setup checklist

Before you change another setting, write down the current DPI, in-game sensitivity, acceleration state, and display refresh rate. Change one item, run three rounds, and keep the rounds only if accuracy stays comparable. If a change feels faster but accuracy drops, you have moved along the speed–accuracy curve rather than improved the setup. Return to the previous configuration if the new one is not repeatable across two sessions.

For the scoring side of aim training, see the reaction time guides.

Sources