Mouse sensitivity converter
Keep the same 360° turn when you switch FPS games. Yaw-accurate hipfire conversion with cm/360°, eDPI, dual DPI, and a link you can send to a teammate.
Settings → Sensitivity: Aim
Settings → Keyboard / Mouse → Sensitivity
Converted CS2 sensitivity
1.273
360° distance
Tactical
The band most CS2 and Valorant players sit in.
- cm / 360°
- 40.82 cm
- in / 360°
- 16.07 in
- Valorant eDPI
- 320
- CS2 eDPI
- 1018
cm/360° is the real match — it is identical on both sides after conversion. eDPI is only comparable inside the same game (or games that share a yaw).
Built like a tool, not a landing page
Live, both directions
Type a sens on either side. No extra calculate step, no sign-up wall.
cm/360° is the source of truth
The physical turn distance is shown first. eDPI is labeled so it is not compared across games by mistake.
Share the exact setup
The URL stores games, sens, and DPI. Copy the link and the other person sees the same conversion.
One formula, every game
Games do not share a sensitivity scale. Valorant 1.0 and CS2 1.0 are not the same turn. What they share is physics: counts × yaw = degrees. Match the degrees for a 360, and the mouse path matches.
360° distance
cm/360 = 914.4 / (DPI × sens × yaw)
Convert
toSens = fromSens × (fromYaw / toYaw) × (fromDPI / toDPI)
Example: Valorant 0.4 at 800 DPI → CS2 1.273 — both are 40.82 cm/360°.
Sensitivity questions
How does the conversion work?
Each game turns a different number of degrees per mouse count — that constant is called yaw. The converter matches 360° distance: how far your mouse travels on the pad for a full turn. If cm/360° is the same, the physical motion is the same, even when the in-game number looks completely different.
Do I need to change DPI?
No. Leave both DPI fields on the DPI you already play at. Only split them if you actually use a different DPI in the second game or on a second mouse.
Why does aim still feel different after converting?
360° match does not change FOV, aspect ratio, movement speed, or ADS multipliers. A 90 FOV game and a 103 FOV game can share the same cm/360° and still look faster or slower at the crosshair. Hipfire conversion is still the right starting point — then tweak ADS/scoped sliders in that game.
What is cm/360°?
Centimeters of mouse movement needed to rotate 360° in-game. It is the only number that compares fairly across titles. Most CS2 and Valorant players sit around 40–55 cm. Tracking-heavy games often sit lower.
What is eDPI?
eDPI is DPI × in-game sensitivity. It is useful for comparing two Valorant players, or two CS2 players. It is not useful across games, because yaw is different — 800 eDPI in Valorant is not 800 eDPI in CS2. Trust cm/360° for that.
Is this 100% accurate?
Hipfire 360° match is accurate when you type the real in-game number and the real DPI. Fortnite in particular: use the 0–100 X/Y slider value, not the 0.xx config file value. Siege: use Mouse Yaw Sensitivity with the default 0.02 multiplier. Scoped / ADS feels are a separate slider and are not baked into this result.
Converted. Now take a test.
The number is only useful if the flicks still land. Run a drill on Aim Precision with the new sens before you queue.