Mouse DPI is the foundation every other aiming decision sits on top of. Whether you're grinding ranked in Valorant, holding angles in CS2, or chasing movement-heavy fights in Apex Legends and Fortnite, getting it right means your aim behaves predictably from session to session. This guide breaks down what DPI actually does, how it relates to in-game sensitivity, why the overwhelming majority of professionals settle on the same small range of values, and how to lock in a number you can trust and stop thinking about.
What DPI Actually Is
DPI stands for dots per inch, and it describes how many counts your mouse sensor reports for every inch you physically move it across your pad. A higher DPI means more reported counts per inch, so your view travels farther for the same physical hand motion. A lower DPI means the same hand motion moves the view less. Manufacturers sometimes use the term CPI, counts per inch, which is technically more accurate, but the two terms are used interchangeably in gaming.
The important part: DPI on its own doesn't define how fast your aim feels. It's only half the equation. The actual on-screen speed you experience is the product of your DPI and your in-game sensitivity slider working together. This is why two players can run the identical DPI and still have wildly different aim, and why copying someone's DPI number without their sensitivity tells you almost nothing useful.
DPI vs Sensitivity: Understanding eDPI
This is the single most misunderstood part of aim setup. Players obsess over the DPI number printed on the mouse box while ignoring that the in-game sensitivity multiplier matters just as much. The way to combine both into one meaningful number is called eDPI, or effective DPI.
The formula: eDPI = mouse DPI × in-game sensitivity.
eDPI represents your true on-screen turning speed regardless of how you split the two values. A player on 1600 DPI with 0.25 sensitivity has the exact same effective aim speed as a player on 800 DPI with 0.5 sensitivity, because both produce an eDPI of 400. This is the only fair way to compare aim speed between players, or even between your own past settings.
| Mouse DPI | In-game sensitivity | eDPI | Resulting feel |
|---|---|---|---|
| 400 | 1.0 | 400 | Low / precise |
| 800 | 0.5 | 400 | Low / precise (identical to above) |
| 800 | 1.0 | 800 | Medium |
| 1600 | 0.5 | 800 | Medium (identical to above) |
| 800 | 2.0 | 1600 | High / fast |
Notice the 400-eDPI rows feel identical even though one runs 400 DPI and the other 800. That equivalence is the whole reason the specific DPI number matters less than people assume, and why you should treat DPI as a fixed base rather than a dial you constantly twist. For a deeper walkthrough and a calculator, see our Sensitivity and eDPI Calculator guide.
400 vs 800: The Two Values That Dominate
If you want the short answer, the right DPI for the vast majority of FPS players is either 400 or 800. These two values dominate competitive play for practical reasons, and you rarely need to look beyond them.
Why 800 is the modern default
For years, 800 DPI has been the most common recommendation for new and experienced players alike. It sits in the sweet spot for modern sensors and high-refresh monitors, giving smooth, granular movement without forcing your in-game sensitivity down to values that can feel mushy. It also pairs cleanly with 1440p and higher resolutions, where slightly more reported counts help aim feel responsive across more pixels.
Why 400 still has a following
Plenty of professionals, especially long-time Counter-Strike players, still swear by 400 DPI. The reasoning is largely historical: older sensors were optimized and tested heavily around 400, and many veterans simply never had a reason to change. At 400 DPI you typically run a higher in-game sensitivity value to reach the same eDPI, which some players find gives a clearer mental model of their setup. For most people today, 400 and 800 are functionally equivalent once eDPI is matched.
What pros actually run
The honest pattern is that the large majority of professionals cluster at 400 or 800 DPI and then tune sensitivity to hit a comfortable eDPI. Tactical shooter pros tend to run lower effective speeds for precise tap-firing, while pros in faster, movement-heavy titles run higher effective speeds for quick turns. You will essentially never see a serious competitor playing on 6400 DPI, which alone should tell you that chasing a high number is the wrong goal.
Why Higher DPI Doesn't Mean Better Aim
Marketing has convinced a lot of players that a mouse advertising 20,000 or 30,000 DPI will somehow make them aim better. It won't, for a few concrete reasons:
- You compensate with lower sensitivity anyway. Raise your DPI and you have to drop in-game sensitivity to keep the same eDPI. The net feel is identical, so nothing was gained.
- Extremely high DPI can introduce jitter. At very high counts, tiny hand tremors and sensor noise become more visible, which can make precise micro-adjustments harder rather than easier.
- It doesn't add real information. Past a certain point, more counts per inch don't give finer control than your monitor's pixel grid can actually display at normal sensitivities.
The practical takeaway: DPI should be set high enough to feel smooth and low enough to stay stable, then left alone. For nearly everyone, that means 400 or 800.
Sensor Considerations and Native DPI Steps
Modern gaming sensors are excellent, but they still have characteristics worth knowing. Most quality sensors have native DPI steps, the values the sensor is designed to report most cleanly. Common native steps include 400, 800, 1600, and 3200. Choosing a native step rather than an arbitrary value like 750 or 1100 ensures your sensor isn't interpolating, which keeps tracking accurate and avoids subtle inconsistencies.
- Stick to clean, native steps. 400 and 800 are native on essentially every gaming mouse made in the last decade.
- Avoid software-interpolated values that fall between native steps; they can introduce minor inaccuracy without any benefit.
- Trust modern sensors. The flagship sensors in current mice are accurate enough that DPI choice within the native range is about feel and habit, not raw tracking quality.
Polling Rate: The Other Setting That Matters
While configuring your mouse, set your polling rate correctly too. Polling rate, measured in hertz, is how often your mouse reports its position to the computer each second. A 1000 Hz rate reports once every millisecond and has been the competitive standard for years. Some newer mice offer 4000 Hz or 8000 Hz, which can reduce latency further but demand more from your CPU and offer diminishing returns for most players.
For the vast majority of setups, 1000 Hz is the right choice: smooth, low-latency, and stable on virtually any system. Only consider higher polling rates if you have a powerful CPU and a high-refresh monitor, and even then, verify it doesn't cause stutters or frame drops. Polling rate and DPI are independent settings, so configure both deliberately rather than assuming a single "gaming mode" preset handles everything for you.
Set DPI Once, Then Tune Sensitivity Only
The most important workflow lesson in this guide: set your DPI once and never touch it again. Use your in-game sensitivity slider for all future adjustments instead. A few concrete reasons this wins:
- Consistency across games. A fixed DPI gives you a stable base, so you can match eDPI across Valorant, CS2, Apex, and Fortnite and let muscle memory transfer instead of resetting every time you switch titles.
- Finer control. In-game sensitivity sliders usually offer far more granular adjustment than DPI steps, letting you dial in exactly the feel you want.
- Easier troubleshooting. When your aim feels off, you only have one variable to think about. A moving DPI plus a moving sensitivity is a recipe for never finding a setting that sticks.
Pick 800 DPI if you're unsure, leave it there permanently, and make every future change through sensitivity. If you're still deciding how fast that sensitivity should be, our comparison of Low vs High Sensitivity in FPS Games walks through the tradeoffs in detail.
How to Test Your Setting in an Aim Trainer
Numbers on a config screen mean nothing until your hand confirms them. The fastest way to validate a DPI and sensitivity combination is to test it deliberately in an aim trainer before taking it into ranked. A browser-based trainer lets you isolate mechanics and feel small changes immediately.
- Check your 180 turn. Measure how much physical desk space a full turn takes. You want to flick 180 degrees without lifting the mouse, while still landing precise small adjustments.
- Run a flicking scenario. Spawn static targets and snap to them. Consistently overshooting means your effective speed is too high; consistently falling short means it's too low.
- Run a tracking scenario. Follow a moving target and watch whether your crosshair stays glued or wobbles. Jittery tracking can indicate your eDPI is too fast for fine control.
- Test target switching. Move between multiple targets to confirm your setting holds up when you need both speed and precision in the same motion.
Give any new setting at least a few sessions before judging it, since your brain needs reps to adapt and first impressions are unreliable. A clean, high-contrast crosshair makes it easier to see exactly where your shots land while you tune; our sister site valocrossdb.site has a large library of Valorant crosshair codes if you want to dial that in at the same time. For a complete training framework to pair with your new settings, see our complete guide to improving FPS aim.
Start Tuning Your Settings
Your DPI is the stable foundation under every flick, track, and micro-adjustment you'll ever make. Set it to 800, or 400 if you prefer, lock in 1000 Hz polling, match your eDPI across your games, and make all future changes through sensitivity alone. The fastest way to confirm your choice actually feels right is to test it. Open the free aim trainer and start dialing in a setup you can trust in every match.