How to Change Mouse DPI Without Changing In-Game Sensitivity

If you double DPI and leave the game's sensitivity unchanged, you change the movement scale. To keep the same intended rotation, reduce the in-game multiplier proportionally.

This is a same-game calculation. Switching between two games requires their respective scaling conventions, so use a game-aware converter instead of copying the result directly.

The formula and its assumptions

Let the original DPI be D1, the original sensitivity be S1 and the new DPI be D2. To keep the product unchanged:

D1 × S1 = D2 × S2

Therefore:

S2 = D1 × S1 / D2

This works as intended when the relevant camera input is linear and the other scaling factors remain unchanged. Acceleration, a different camera mode, a separate ADS multiplier or a changed profile can break the simple comparison.

Worked examples

These are mathematical examples, not recommended settings for a particular game or player. The first three preserve a product of 240, but that product is not a universal cross-game speed.

The DCPROSENS DPI calculator helps check the arithmetic. If you are changing games too, use the sensitivity converter and verify the result in the destination game.

Apply the change in a controlled order

1. Save the original configuration. Record the DPI stage, game sensitivity and any separate scoped settings.
2. Calculate before editing. Write the target value down so you do not confuse the old and new profiles.
3. Change the mouse DPI. Confirm the stage that is active when the game runs.
4. Enter the new sensitivity. Use the most precise input the game officially supports.
5. Check a physical turn. Compare the same landmark-to-landmark rotation with the original setup.
6. Check ADS separately. Do not assume every game's scoped implementation follows the hip-fire relationship without qualification.

If you also change polling rate, pad, resolution or FOV, you lose a clean comparison. Keep those fixed until the DPI transfer is verified.

What if the game rounds the number?

Suppose the calculation gives 0.225 but the game only accepts two decimal places. Selecting 0.23 creates a different product from 0.225. In this example, 0.23 / 0.225 - 1 is about 2.22%, so the angular scale is slightly higher under the same linear assumptions.

That is a rounding example, not evidence that your game has that input limit. Check its supported interface. Do not edit unknown configuration files or use unsupported tools simply to force extra precision.

If exact entry is unavailable, compare the accepted neighboring values in practice and record the actual setting used.

Why can the desktop feel different afterward?

Desktop cursor behavior and in-game camera behavior can follow different input paths. Microsoft documents the distinction between pointer messages and raw mouse input.

Preserving the game's sensitivity product does not automatically preserve desktop cursor speed. Adjusting the desktop pointer is a separate preference; confirm whether your game uses that path before assuming it affects the camera.

If the game itself still differs, check profile switching first. Then use the new-mouse troubleshooting workflow to distinguish physical scaling from handling or measurement uncertainty.