eDPI (effective DPI) is your mouse DPI multiplied by your in-game sensitivity. For example, 400 DPI × 1.80 sensitivity = 720 eDPI. That number is just arithmetic, not a recommended target.
The value of mouse eDPI tuning is consistency inside one game. If you change DPI, you can work out the sensitivity that keeps the same eDPI. A matching number in a different game is only a starting point, so you still need to test how it actually feels there.
Calculate eDPI and Adjust Sensitivity When DPI Changes
Two formulas cover almost every eDPI task. According to the eDPI calculation guide, eDPI equals DPI × sensitivity, and you can rearrange it to find sensitivity by dividing eDPI by DPI.
Here is what each term means:
- Mouse DPI is the setting on your mouse or its software. It sets how many counts the mouse reports per inch of movement.
- In-game sensitivity is the slider value inside the game. Keep it in that game's own notation, such as 1.80 or 0.5.
- eDPI is the product of the two. It lets you compare setups that use different DPI and sensitivity mixes.
| Task | Formula | Illustrative example |
|---|---|---|
| Find your eDPI | DPI × in-game sensitivity | 400 DPI × 1.80 = 720 eDPI |
| Keep eDPI after a DPI change | Chosen eDPI ÷ new DPI | 800 eDPI ÷ 500 DPI = 1.6 sensitivity |
Neither example is a suggested setting. They only show how the numbers move. The second formula works within the same game's sensitivity scale. If your current eDPI is 800 and you switch your mouse to 500 DPI, setting that game's slider to 1.6 keeps the calculated value the same. When picking the new DPI, our guide to native DPI steps explains how a mouse's DPI steps differ from scaling sensitivity in software.
Build a Repeatable Sensitivity Baseline
A baseline is a set of recorded, tested values that work for you in one game. You build it by changing one thing at a time and comparing results on the same task. Nobody has proven a single ideal eDPI, so the goal is a number you have tested yourself.
- Record your starting point. Write down the game, mouse DPI, in-game sensitivity, and the eDPI you calculate from them.
- Pick one repeatable in-game task. Use the same drill every time, such as a training map, a fixed set of targets, or a target-grid drill. Keep the same mouse and mousepad surface so the only variable is your setting.
- Change one value deliberately. Adjust sensitivity or DPI in a small step, then recalculate and record the new eDPI.
- Compare on the same task. Note whether the drill feels easier or harder to control. Look for overshooting past targets, stopping short, or needing extra correction strokes.
- Keep the earlier values on file. If a trial feels worse, go back to the last recorded setting instead of guessing.
- Save the winner as that game's baseline. Label it with the game name, and start your next tuning session from those numbers.
Use eDPI Across Games Without Assuming the Same Feel
You can carry an eDPI number into another game, but it does not guarantee the same aim. eDPI works best for comparing DPI and sensitivity combinations within one game. The reason is that games use different sensitivity scales and parameters, so 720 eDPI in one title may turn your view a different amount in another.
Game code adds its own step between your hand and the screen. In Microsoft's relative mouse example, the game multiplies mouse movement by a rotation gain to scale control sensitivity. That is one implementation, not a rule every game follows. Still, it shows why your DPI and slider value do not tell the whole story.
For a physical comparison between games, measure cm/360. This is how far your mouse travels to turn a full 360 degrees in-game. Aim at a visual reference point, move the mouse without lifting it until you complete one full turn, and measure the distance on your desk with a ruler. Then repeat in the other game. Matching cm/360 means your hand travels the same distance for a full turn. Differences in field of view or game handling can still make it feel different, though.
If you want to skip the ruler, our sensitivity converter can match DPI, cm/360, and eDPI between titles. Our walkthrough on cross-game cm/360 conversion covers converting from a reference game. Whatever method you use, treat the converted value as a first trial. Run it through the baseline steps above and save it under the new game's name.
Does eDPI Tuning Prevent Pixel Skipping?
No reliable evidence shows that eDPI tuning prevents or eliminates pixel skipping. Matching eDPI keeps your calculated sensitivity steady. It is not a demonstrated fix for skipped pixels in games.
The relevant technical detail is narrower. Windows documents that WM_MOUSEMOVE is limited to screen resolution. A tiny mouse movement that is too small to move the pointer to the next pixel generates no WM_MOUSEMOVE message. By contrast, WM_INPUT messages carry high-definition mouse data. That difference applies to those Windows input paths. It does not tell you which path a particular game uses or how eDPI changes the result.
A stronger claim would need game-specific testing. That testing would have to define pixel skipping, name the input path, and state the DPI and sensitivity conditions tested. That kind of evidence is not available for eDPI today. So pick your settings for control and consistency, not as a pixel-skipping cure.
FAQs
Is 720 eDPI a good setting to aim for?
No. The 720 figure is simply what 400 DPI times 1.80 sensitivity produces. It shows how the math works. The right value is whatever you test and find controllable on your own drill in a specific game.
What can comparing eDPI with a friend tell me?
If you both play the same game, eDPI shows whether your overall sensitivity is higher or lower than theirs, even with different DPI settings. It is a reference point, not a ranking. A higher or lower number does not mean better aim.
What should I do if the same eDPI feels different in another game?
Treat the carried-over number as a draft. Measure cm/360 or use a converter for a closer physical match. Then adjust in small steps on a repeatable task and record a separate baseline for that game.
Do I need to recalculate eDPI when I only change in-game sensitivity?
Yes. eDPI changes whenever either input changes. Multiply your unchanged DPI by the new sensitivity value and update your notes, so your recorded baseline always matches what is actually in the game.
