Mouse Sensitivity Converter

To convert mouse sensitivity between two games you keep the cm/360 constant, and that is exactly what the converter above does: pick the game you come from, the game you go to, type your sensitivity and DPI, and read the converted value. One full 360 degree turn will take the same hand movement in both games.

The reason you cannot simply copy a number from one game to another is that each game multiplies mouse input by its own hidden constant. A sensitivity of 1 in Valorant turns your view 0.07 degrees for every count the mouse sends; in Counter-Strike 2 the same count turns 0.022 degrees. Same number in the menu, more than three times the speed on screen.

How to use the mouse sensitivity converter

The converter has a From panel on the left, a To panel on the right and a swap button between them.

1. In the From panel, choose the game you already play under Game, enter your sensitivity under In-game sensitivity and your mouse DPI under Mouse DPI. The DPI field starts at 800.
2. In the To panel, choose the game you want a sensitivity for. The converted value appears in large type under In-game sensitivity.
3. If the new game will be played at a different DPI, type it under New DPI (optional). Leave it empty to keep the same DPI.
4. Check the three boxes below the panels: cm/360, in/360 and eDPI (from game). The first two are the distance you move for a full turn, the third is your eDPI in the original game.
5. Open Same cm/360 in every game to see the equivalent sensitivity in all 14 supported games at once, computed for the DPI on the To side.

The Swap games button reverses the direction and carries the converted value into the input, which is handy when you want to check that a conversion round-trips cleanly. If you are unsure what DPI the mouse is actually running, measure it with the DPI analyzer before you convert, because an error in DPI shifts everything else.

The output uses the number of decimals each game accepts: three for CS2 and Valorant, two for Overwatch 2 and Call of Duty, and one for Fortnite, which is entered and shown as a percentage. Enter the number exactly as shown and the game will round the rest away.

How does sensitivity conversion work?

Every game turns mouse counts into degrees with the same shape of formula:

degrees per count = yaw × in-game sensitivity

Your mouse sends DPI counts per inch, so the distance for a full turn is 360 divided by yaw × sensitivity × DPI, in inches, and multiplied by 2.54 for centimetres. That is the cm/360 figure in the converter. To convert, the tool computes your cm/360 in the source game, then solves the same equation for sensitivity in the target game.

Because DPI appears in the formula, a sensitivity is only meaningful together with a DPI. A CS2 sensitivity of 1.1 is 47.2 cm per turn at 800 DPI and 94.5 cm at 400 DPI. The converter always carries DPI through the calculation, which is why it asks for it on both sides.

Yaw values and equivalent sensitivities

The yaw column is the constant each game uses. The right-hand column is the in-game sensitivity that gives 40 cm per turn at 800 DPI, a middling setting that many players in tactical shooters would recognise.

Game	Yaw (degrees per count)	Sensitivity for 40 cm/360 at 800 DPI
Counter-Strike 2	0.022	1.299
CS:GO	0.022	1.299
Apex Legends	0.022	1.299
Deadlock	0.022	1.299
Team Fortress 2	0.022	1.299
Quake Champions / Live	0.022	1.299
KovaaK's	0.022	1.299
Valorant	0.07	0.408
Aim Lab	0.05	0.572
Overwatch 2	0.0066	4.33
Call of Duty (MW / Warzone)	0.0066	4.33
Marvel Rivals	0.0066	4.33
Fortnite	0.5555 per 100%	5.1%
Rainbow Six Siege	0.00573 × slider (unit 0.02)	5
The Finals	0.001	29
PUBG (FOV 103)	0.001 × 10^(slider/50) × FOV/36	50

Games that share a yaw share a sensitivity: a CS2 value works unchanged in Apex Legends, Deadlock, Team Fortress 2, Quake and KovaaK's, and an Overwatch 2 value works unchanged in Call of Duty and Marvel Rivals. Fortnite is entered as the percentage the game shows, so its row is on a different scale from the rest of the table, but the converter handles the conversion in both directions.

Common conversions

These are the pairs people search for most. All examples keep DPI at 800; the converter will adjust them if you type a different DPI on either side.

CS2 to Valorant sens. Multiply by 0.022 ÷ 0.07, which is about 0.314. A CS2 sensitivity of 1.1 (47.2 cm per turn) becomes 0.346 in Valorant.

Valorant to CS2 sens. Multiply by 0.07 ÷ 0.022, about 3.18. A Valorant sensitivity of 0.35 (46.7 cm per turn) becomes 1.114 in CS2. Switch the DPI to 400 at the same time and the CS2 value doubles to 2.227.

CS2 to Overwatch 2. Multiply by 0.022 ÷ 0.0066, which is exactly 3.333. A CS2 sensitivity of 1.1 becomes 3.67 in Overwatch 2. The same multiplier takes you to Call of Duty and Marvel Rivals.

CS2 to Apex Legends. No change. Both games use 0.022, so 1.1 stays 1.1.

CS2 to Aim Lab. Multiply by 0.022 ÷ 0.05, which is 0.44. A CS2 sensitivity of 1.1 becomes 0.484 in Aim Lab. KovaaK's uses the CS2 scale directly, so no conversion is needed there.

You can check any of these by comparing the cm/360 box before and after the conversion. It should not move.

Should you keep the same sensitivity in every game?

Matching cm/360 is the right way to move your muscle memory across games, and it is the setting to start with. But the games themselves differ. A CS2 player at 47 cm per turn will feel stuck in Apex Legends, where most pros play closer to 26 cm because the game involves far more tracking and turning. The reverse player, going from Apex to CS2, will find small flicks overshoot.

A sensible approach is to convert, play a few sessions, and then move in steps of about 10 percent in cm/360 until the game feels right. Keep notes of the cm/360 rather than the sensitivity, because that is the number you can carry to the next game or the next mouse. The eDPI calculator shows how your resulting eDPI compares with the usual pro range in each game if you want a sanity check.

Converting when you change mouse or DPI

A new mouse often means a new DPI, and the converter handles that in the same pass. Enter the old DPI on the From side, the new DPI under New DPI (optional) and leave both games set to the same title. The output is the sensitivity that gives the same cm/360 at the new DPI.

If you only want the DPI change and a few extra options, such as working from a cm/360 target, the DPI calculator is built for that. And if you are choosing between DPI and sensitivity as the thing to change, read DPI vs sensitivity first.

Limits of the conversion

The converter handles hipfire sensitivity only. Scoped sensitivity, ADS multipliers and per-zoom settings vary by game and are not part of the yaw formula, so match hipfire first and tune scopes inside each game.

It also assumes raw input with no acceleration. If Windows pointer acceleration or a game's own acceleration is on, the relationship between hand movement and rotation is no longer linear and cm/360 stops being a single number. Turn acceleration off in both the operating system and the game before you convert.

Finally, the conversion is only as good as the DPI you type. Many mice are not running the DPI you think, either because a DPI button was pressed or because the sensor is a few percent off. A quick run on the DPI analyzer confirms it.

Related

• DPI analyzer measures the actual DPI of your mouse so the conversion starts from a correct value.
• eDPI calculator compares your eDPI with the usual pro range inside one game.
• DPI calculator finds the matching sensitivity when you change DPI or target a cm/360.
• DPI vs sensitivity explains which setting to change and why.