How to Convert Sensitivity When Changing DPI

How to Convert Sensitivity When Changing DPI

To keep the same effective sensitivity after changing DPI, use this formula: new sensitivity = old DPI x old sensitivity / new DPI. This works in games that scale mouse input linearly, meaning a proportional sensitivity change preserves the same basic movement.

Example: if you move from 800 DPI at 0.5 sensitivity to 1600 DPI, the new sensitivity is 0.25. You doubled the DPI, so you halve the in-game sensitivity.

For the full conversion process, read the mouse sensitivity conversion guide. You may also want how to measure cm/360 manually, what yaw means, and eDPI vs cm/360.

Key Takeaways

  • Use new sensitivity = old DPI x old sensitivity / new DPI.
  • Doubling DPI means halving sensitivity, if the game scales linearly.
  • DPI conversion is not the same as full game-to-game conversion.
  • Verify the result with cm/360 if the setting feels off.

Before You Begin

You need three values before converting: your old DPI, your old in-game sensitivity, and your new DPI. You also need to know whether you are staying in the same game or moving to another game.

Use this guide for same-game DPI changes. If you are changing games, use how mouse sensitivity conversion works and convert through cm/360.

In 2026, the Steam Hardware & Software Survey for June 2026 reports Windows at 94.10% among participating Steam users and Windows 11 64-bit at 70.44% among Windows users (Valve, Steam Hardware & Software Survey June 2026, 2026). That context matters because many PC players adjust DPI in mouse software or Windows-adjacent setups before testing in game.

Step 1: Write Down Your Current DPI and Sensitivity

By the end of this step, you should have the two old values that define your current setup. Do not rely on memory if you recently changed mouse software profiles.

Record:

  1. Current mouse DPI.
  2. Current in-game sensitivity.
  3. Game name.
  4. Raw input or acceleration setting, if visible.

Example:

old DPI = 800
old sensitivity = 0.5
game = current FPS

The sneaky error is having multiple DPI stages on the mouse. A player may think they are using 800 DPI while the active hardware stage is 1200. Check the mouse software or DPI indicator before doing any math.

Step 2: Choose the New DPI

Choose the new DPI you actually plan to use on the mouse. Common reasons include using a cleaner desktop cursor speed, matching another setup, or reducing the need for a very high or very low in-game sensitivity number.

The formula only works if the new DPI is real. If your mouse software saves the setting per profile, make sure the correct profile loads while the game is running.

Example:

new DPI = 1600

If you double DPI, the mouse reports twice as many counts over the same physical distance. To preserve the same game movement, the in-game sensitivity should drop by half.

Step 3: Apply the DPI Conversion Formula

The conversion formula is direct: multiply the old DPI by the old sensitivity, then divide by the new DPI. In plain English, you keep the same effective input by balancing the hardware increase or decrease with the game setting.

Formula:

new sensitivity = old DPI x old sensitivity / new DPI

Example:

new sensitivity = 800 x 0.5 / 1600
new sensitivity = 400 / 1600
new sensitivity = 0.25

So the converted setting is 0.25. If the game accepts decimals, enter that value. If the game uses a slider or rounded values, choose the closest available value and test it.

DPI conversion keeps the same effective input by offsetting a hardware DPI change with an inverse sensitivity change. In a linear game scale, doubling DPI means halving in-game sensitivity, while halving DPI means doubling in-game sensitivity.

Step 4: Check the eDPI Result

eDPI is a quick way to confirm the math. eDPI = mouse DPI x in-game sensitivity. If the old and new eDPI match, the same-game DPI conversion is consistent.

Old setup:

800 DPI x 0.5 sensitivity = 400 eDPI

New setup:

1600 DPI x 0.25 sensitivity = 400 eDPI

The eDPI stayed the same. That is what you want for a same-game DPI change.

This is the correct place to use eDPI. It is not a universal cross-game unit, but it is useful for checking DPI-to-sensitivity changes inside one game. For the unit comparison, read eDPI vs cm/360.

Step 5: Test Your cm/360

The final check is physical. If your old setting was 40 cm/360, your new DPI-adjusted setting should still be close to 40 cm/360 in the same game.

Use a simple test:

  1. Face a fixed point in game.
  2. Put your mouse at a marked start point.
  3. Move until the view completes one full turn.
  4. Measure the mouse travel.
  5. Repeat and compare the average.

If the distance changes a lot, recheck the DPI stage, the entered sensitivity, and any acceleration options. The formula is simple, but the setup around it can still be wrong.

For a detailed ruler method, follow how to measure cm/360 manually.

Step 6: Watch for Input and Acceleration Changes

A DPI conversion can be mathematically correct while the mouse still feels different. Higher DPI may change desktop cursor behavior. Mouse software may switch profiles. A game may use raw input, OS input, or its own filtering.

In 2026, MDN's Pointer Lock API documentation says Pointer Lock is useful for first-person 3D games because it provides access to raw mouse movement. It also notes that operating-system mouse acceleration is enabled by default and unadjustedMovement can request raw input (MDN, Pointer Lock API, 2026).

In 2026, Microsoft's Raw Input overview says Raw Input provides direct data from the device and can distinguish devices. It also notes buffered reads are useful for high-frequency devices such as mice at 1000Hz (Microsoft Learn, Raw Input Overview, 2026).

The practical point: if a DPI change feels strange, check the whole input path. The formula preserves effective input only when the game is receiving and scaling movement as expected.

Common Mistakes to Avoid

Using the wrong active DPI. Mouse software often has several DPI stages. Confirm the active stage before converting.

Treating DPI conversion as cross-game conversion. DPI conversion keeps one game's effective input the same after a DPI change. Cross-game conversion should use cm/360 and game-specific scale.

Ignoring slider rounding. Some games cannot accept the exact converted number. Use the nearest available value, then measure the result.

Leaving acceleration on by accident. Acceleration can make distance depend on movement speed. That breaks the simple expectation that the same mouse distance always creates the same turn distance.

If the new value feels slightly off but the cm/360 test is close, give yourself a short adjustment window before changing again. The cursor may feel different outside the game even when in-game turn distance is preserved.

Frequently Asked Questions

How do I keep the same sensitivity after changing DPI?

Use new sensitivity = old DPI x old sensitivity / new DPI when the game scales linearly.

What happens if I double or halve DPI?

If you double DPI, halve the in-game sensitivity to keep the same effective input. For example, 800 DPI at 0.5 becomes 1600 DPI at 0.25. If you halve DPI, double your in-game sensitivity. For example, 1600 DPI at 0.25 becomes 800 DPI at 0.5. The eDPI remains 400 in both cases.

Does DPI conversion work across games?

DPI conversion preserves same-game effective input. Cross-game conversion should use cm/360.

Does this formula work for every game?

It works as a practical rule for games that scale sensitivity linearly. It may not cover unusual input systems, coarse sliders, acceleration, or separate ADS behavior. Use cm/360 measurement to verify.

Sources