To change your mouse DPI while keeping the same in-game turning sensitivity, use this formula:
New sensitivity = Old sensitivity × Old DPI ÷ New DPI
For example, switching from 800 DPI at 0.35 sensitivity to 1600 DPI requires 0.175 sensitivity. The sensitivity number changes, but the intended physical mouse distance needed to turn stays the same.
This calculation assumes a linear sensitivity setting, the same game and aiming mode, and unchanged input modifiers. It is not a universal conversion for nonlinear sliders or accelerated mouse input. Valve’s public mouse-input implementation provides an example of ordinary sensitivity multiplication alongside separate acceleration behavior.
Changing games as well as DPI? Use GamingStation’s mouse sensitivity converter for supported conversions, and check the selected games’ assumptions before applying the result.
The DPI-to-Sensitivity Formula
You need three numbers: your current mouse DPI, your current in-game sensitivity, and the DPI you want to use.
The calculation is
New sensitivity = Current sensitivity × Current DPI ÷ Target DPI
The direction of the adjustment matters:
When DPI increases, in-game sensitivity must decrease. When DPI decreases, in-game sensitivity must increase.
Doubling DPI means halving sensitivity. Halving DPI means doubling sensitivity.
Why the formula works
Under the linear model, preserving the same product of DPI and sensitivity preserves the same nominal turning response:
Old DPI × Old sensitivity = New DPI × New sensitivity
Rearranging that equation gives the conversion formula.
For decimal sensitivity values, the product of mouse DPI and in-game sensitivity is commonly called effective DPI, or eDPI.
| Configuration | Calculation | eDPI |
|---|---|---|
| Original settings | 800 × 0.35 | 280 |
| Adjusted settings | 1600 × 0.175 | 280 |
Both combinations produce the same mathematical baseline within the same game, with the same relevant settings.
However, eDPI is not a universal cross-game measurement. Games can use different input-to-rotation scales. KovaaK’s sensitivity-matching explanation describes how a game’s yaw factor affects the rotation produced by mouse input.
DPI Conversion Table: 400, 800, 1600, and 3200
Use the multiplier column with your own sensitivity. The example values below demonstrate the calculation; they are not recommended settings for a specific game.
| DPI change | Multiply your sensitivity by | Example of old sensitivity | Matching new sensitivity |
|---|---|---|---|
| 400 → 800 | 0.5 | 1.6 | 0.8 |
| 800 → 400 | 2 | 0.8 | 1.6 |
| 800 → 1600 | 0.5 | 0.35 | 0.175 |
| 1600 → 800 | 2 | 0.175 | 0.35 |
| 400 → 1600 | 0.25 | 1.4 | 0.35 |
| 1600 → 400 | 4 | 0.35 | 1.4 |
| 800 → 1000 | 0.8 | 0.35 | 0.28 |
| 800 → 3200 | 0.25 | 0.35 | 0.0875 |
Every row follows the same formula. These are calculated examples, not independent measurements from individual mice or game builds.
Example: Changing from 800 to 1600 DPI
Your current mouse DPI is 800, and your in-game sensitivity is 0.35.
Calculate:
0.35 × 800 ÷ 1600 = 0.175
Set your mouse to 1600 DPI and your in-game sensitivity to 0.175.
Under the linear model, leaving sensitivity at 0.35 after doubling DPI would double the rotation produced by the same physical mouse movement.
Example: Changing from 1600 to 800 DPI
Your current mouse DPI is 1600, and your sensitivity is 0.175.
Calculate:
0.175 × 1600 ÷ 800 = 0.35
Set your mouse to 800 DPI and your in-game sensitivity to 0.35.
This reverses the previous example.
Example: Changing from 800 to 1000 DPI
You do not need to double or halve DPI for the formula to work.
Starting with 800 DPI at 0.35 sensitivity:
0.35 × 800 ÷ 1000 = 0.28
The matching setting is 1000 DPI at 0.28 sensitivity, subject to the same assumptions.
How to Change DPI and Keep the Same Turning Distance
1. Record your current settings.
Before making changes, record your active mouse DPI and in-game sensitivity. Note any separate horizontal, vertical, ADS, or scope settings that you plan to leave unchanged.
Check the profile used while your game is running—not just the desktop profile. Logitech documents that G HUB can store different DPI settings for different profiles.
For a useful before-and-after comparison, also measure your current physical turn distance using the procedure below.
2. Calculate the replacement sensitivity.
Enter your current sensitivity, current DPI, and intended new DPI into the formula:
New sensitivity = Old sensitivity × Old DPI ÷ New DPI
Keep the full result until you know how much precision the game accepts.
For example, the result of switching from 800 DPI at 0.35 sensitivity to 1200 DPI is
0.35 × 800 ÷ 1200 = 0.233333…
Do not round that to 0.2 when the game supports a more precise value.
3. Change DPI using your mouse’s supported controls.
The steps depend on your mouse and its configuration software.
For compatible Logitech mice, select the intended profile in G HUB, choose your mouse, and open Sensitivity (DPI). Follow Logitech’s official G HUB DPI instructions to configure the relevant stage.
For compatible Razer mice, select your mouse in Synapse and open Performance. Depending on the available controls, select a sensitivity stage or enter the required DPI value. See Razer’s official DPI adjustment guide for the supported procedure.
For other brands, use the manufacturer’s instructions for your specific model.
Confirm that the intended DPI remains active when you return to the game.
4. Enter the calculated in-game sensitivity.
Replace the old sensitivity with the calculated value.
For the 800 DPI, 0.35 → 1600 DPI example, enter 0.175 when the game supports that precision.
After saving, reopen the settings menu to check that the value was retained.
Keep other settings unchanged for the first comparison. Changing FOV, scope settings, acceleration, and DPI together makes it harder to identify the cause of a mismatch.
5. Verify the result before playing a match.
Compare physical turning distance in a practice environment before deciding whether to make further adjustments.
A familiar flick is not a controlled measurement. Use a stationary reference point and a ruler or tape measure to compare how far you move the mouse for the same camera rotation.
How to Verify the Match With cm/360
For a repeatable measurement process, follow our guide to measuring your cm/360 with a ruler.
cm/360 is the distance your mouse travels, in centimeters, to rotate the in-game camera through one complete horizontal turn.
For this task, matching the before-and-after distance is the goal. A repeatable full turn is also central to the verification method described in KovaaK’s sensitivity-matching documentation.
Use this measurement procedure:
- Stand still in a practice area and align your crosshair with a clear, stationary reference point.
- Mark the mouse’s starting position using a consistent point on the mouse body.
- Move the mouse horizontally, without lifting or rotating it, until the camera completes one full turn and returns to the reference point.
- Measure the physical travel and repeat the process to check consistency.
- Apply the new DPI and calculated sensitivity, then repeat under the same conditions.
For example, a setup measuring approximately 40 cm/360 before the change should remain close to 40 cm/360 afterward, allowing for measurement error and the precision of the available settings.
Repeated measurements are more useful than a single sweep. Use the same mouse, surface, reference point, and measurement technique for both configurations.
If your mousepad is too small for a full turn, use a clearly identifiable 180-degree rotation. Doubling that travel distance estimates cm/360 under the same linear conditions.
Do not assume that moving between two arbitrary objects represents exactly 180 degrees.
What to Do When the Game Rounds Your Sensitivity
The mathematical result may contain more decimal places than the game accepts.
Consider an 800 to 1200 DPI change at 0.35 sensitivity:
0.35 × 800 ÷ 1200 = 0.233333…
The following comparison shows the effect of rounding:
| Entered sensitivity | Difference from the ideal sensitivity |
|---|---|
| 0.23 | Approximately 1.43% lower |
| 0.233 | Approximately 0.14% lower |
| 0.2333 | Approximately 0.014% lower |
These percentages describe the difference in the sensitivity multiplier and, under the linear model, rotation per unit of mouse travel. They are not measured differences in aim quality.
Use the closest value the game supports.
If the game only accepts whole-number steps or a restricted slider range, an exact match may not be available at your chosen DPI. You can either use the closest supported setting and verify the result or choose a different supported DPI that produces a representable sensitivity value.
Do not assume that undocumented configuration edits are supported or safe for every game.
Why Your Sensitivity May Still Feel Different
The wrong DPI profile or stage is active.
A conversion calculated for 1600 DPI will not match if the mouse is actually using 800 DPI.
Check the active game profile, selected DPI stage, and any DPI-shift control. Profile-specific DPI settings are a documented feature of Logitech G HUB, so confirming the active profile is a practical first troubleshooting step.
Mouse acceleration changes the response.
A fixed DPI ratio assumes a fixed relationship between physical mouse travel and camera rotation.
Acceleration can make the response depend on movement speed or input magnitude. Valve’s public Source SDK includes acceleration calculations that differ from its ordinary sensitivity-scaling path. Matching an accelerated setup may therefore require more than the simple ratio used in this guide.
Compare like-for-like settings. Do not switch acceleration on or off between measurements and interpret the difference as a formula error.
You are comparing desktop cursor speed with in-game turning.
The desktop pointer and the in-game camera are not interchangeable measurements.
Microsoft’s RAWMOUSE documentation states that raw input mouse events are not affected by the mouse-speed setting in the Windows Control Panel.
For a game using that input path for aiming, changing Windows pointer speed is not a substitute for setting the correct in-game sensitivity.
Keep the Windows setting unchanged during your initial comparison. Check desktop cursor comfort separately.
The game’s slider is not linear.
The formula requires a sensitivity value that scales input proportionally.
If a displayed slider uses a nonlinear mapping, halving the displayed number does not necessarily halve the underlying response. In that case, use a documented game-specific method or compare measured turn distances.
A percentage label alone does not prove that a slider is linear.
You changed games, FOV, or aiming modes.
This guide covers DPI adjustments inside the same sensitivity system.
A different game can use a different yaw factor, and some input implementations have FOV-related behavior. Matching a sensitivity number does not automatically match every aspect of aiming.
For a specific game-to-game change, follow the appropriate conversion method. For example, see GamingStation’s Valorant to CS2 sensitivity guide rather than applying only the same-game DPI ratio.
Should You Change ADS Sensitivity Too?
Do not automatically halve every ADS or scope value just because you doubled DPI.
Consider a system that calculates a scoped response using:
DPI × Base sensitivity × ADS multiplier × Other unchanged factors
If DPI doubles and base sensitivity halves, those first two factors already cancel each other out. Leaving the ADS multiplier unchanged preserves that part of the calculation.
Halving the ADS multiplier as well would apply another reduction.
This is a conditional mathematical example—not a claim that every game handles ADS in the same way.
A game might use independent scope settings or a different input model. Check the relevant documentation and compare the same weapon, optic, and zoom level before changing additional values.
Does the Formula Work With Percentage Sensitivity?
Yes, when the percentage represents a linear sensitivity setting.
For example, changing from 800 DPI at 6% sensitivity to 1600 DPI gives:
6% × 800 ÷ 1600 = 3%
Keep the input format consistent.
A game menu displaying 6% is not asking you to enter 0.06%. When a calculator expects a decimal fraction, 6% corresponds to 0.06.
For percentage-based eDPI calculations using that normalized fraction:
eDPI = DPI × Percentage ÷ 100
Therefore:
800 × 6 ÷ 100 = 48
And after the DPI change:
1600 × 3 ÷ 100 = 48
The unchanged product confirms the calculation under the stated model. Follow the game or calculator’s input labels rather than assuming that every interface uses the same convention.
Frequently Asked Questions
Can I change DPI without changing the sensitivity number?
Not while preserving the same response in the ordinary linear model with every other setting unchanged.
Changing DPI changes one multiplier. Another multiplier must compensate, and the usual adjustment is the in-game sensitivity value.
Is 800 DPI at 0.35 the same as 1600 DPI at 0.175?
Both equal 280 eDPI.
They provide the same nominal turning sensitivity within the same linear game configuration, assuming the mouse response follows the selected DPI ratio and the relevant modifiers remain unchanged.
Verify the result with a physical turn-distance measurement.
What if the calculated sensitivity is outside the game’s range?
Choose a different supported DPI or use the closest valid sensitivity value, then measure the result.
The formula cannot make a game accept a value outside its supported range.
What if I use different horizontal and vertical DPI?
Where the mouse and game expose the corresponding controls, calculate each axis separately:
New X sensitivity = Old X sensitivity × Old X DPI ÷ New X DPI
New Y sensitivity = Old Y sensitivity × Old Y DPI ÷ New Y DPI
Razer documents independent X/Y DPI controls for compatible configurations in its Synapse adjustment guide.
If the game provides only one shared sensitivity value and you change the X and Y DPI by different ratios, that single value cannot exactly compensate for both axes.
Does matching eDPI guarantee identical aiming feel?
No. Within the stated linear model, matching eDPI provides a mathematical baseline for turning sensitivity.
It does not establish that different games, aiming modes, or hardware configurations will feel identical. Compare physical turn distance first, and investigate other variables separately.
The Bottom Line
To change mouse DPI while keeping the same nominal in-game turning sensitivity:
Multiply your current sensitivity by your current DPI, then divide by your new DPI.
Apply the result in the same game and aiming mode, keep the relevant settings unchanged, and verify it with a repeatable turn-distance measurement.
For the common 800 to 1600 DPI change, halve your sensitivity. For 1600 to 800 DPI, double it.
The calculation provides the baseline. The measurement confirms how closely your setup matches it.
References
| Source | What it supports |
|---|---|
| Valve—Source SDK mouse-input implementation | A public example of sensitivity scaling, yaw factors, and separate acceleration calculations. This is implementation evidence, not proof of every current game’s behavior. |
| KovaaK — Sensitivity Matcher | Game-specific yaw factors, sensitivity-matching principles, and repeatable rotation checks. |
| Logitech — G HUB DPI configuration | Profile-specific DPI settings and configuring DPI stages in G HUB. |
| Razer — Adjusting DPI through Synapse | DPI stages, manual DPI entry, and independent X/Y controls on compatible configurations. |
| Microsoft — RAWMOUSE documentation | The distinction between Raw Input mouse events and Windows Control Panel mouse-speed settings. |
Method note: The numerical examples are calculated using a linear sensitivity model. They are not independent hardware measurements or current-build calibration results for every game. Source documentation and the arithmetic examples were reviewed on September 8, 2026.
