From (your current game)
- cm / 360°
- —
- inch / 360°
- —
- eDPI (sens × DPI)
- —
- Counts / 360°
- —
To (target game)
Enter your current game, DPI and in-game sensitivity on the left; the matching sensitivity for the target game is solved on the right so your physical cm/360 stays the same. Works for linear-sensitivity FPS — for Fortnite, R6, CoD or PUBG, set Game to Custom and type the yaw. Everything is computed in your browser.
A mouse sensitivity converter that moves your aim between games. Enter the game you currently play, your mouse DPI and your in-game sensitivity, and it works out your cm/360 (how far you physically move the mouse to turn a full 360°), then solves the sensitivity for the target game that keeps the exact same turn distance. Conversion is based on each game's yaw — the degrees turned per mouse count at sensitivity 1.0 — using Valorant = 0.07, Source-engine games (CS2/CS:GO, Apex, TF2, Quake, Deadlock) = 0.022 and Overwatch 2 = 0.0066. You can set a different DPI on each side, so switching DPI (e.g. 800 → 1600) converts correctly too. It also shows eDPI (sens × DPI), inch/360 and counts/360, handy for sharing settings or aim training. Games with non-linear sensitivity such as Fortnite, Rainbow Six, Call of Duty and PUBG can't be converted 1:1 — set the game to Custom and type the yaw. Everything is computed in your browser; the values you enter are never sent to any server or API.
How to use
- On the left (From), pick your current game and enter your mouse DPI and in-game sensitivity — your cm/360 is shown.
- On the right (To), pick the game you're moving to (change the DPI if it differs).
- The equivalent sensitivity is solved on the right, keeping the same cm/360 (eDPI shown; nothing is sent).
FAQ
Are my sensitivity and DPI sent anywhere?
No. The yaw-based cm/360 calculation and the equivalent-sensitivity solve both run entirely in your browser. The values you type are never sent to any server or API — it all stays on your device.
Does it work if I also change DPI?
Yes. You can enter a different DPI on the From and To sides. It keeps the same cm/360 using sens × (from yaw ÷ to yaw) × (from DPI ÷ to DPI), so a DPI change like 800 → 1600 still matches your turn distance.
Can I convert Fortnite, Rainbow Six, CoD or PUBG?
Those use non-linear sensitivity (custom multipliers or percentage settings), so a single yaw value can't represent them for 1:1 conversion. Set the game to Custom and enter a measured yaw, or match the shown cm/360 in-game manually.
What's the difference between cm/360 and eDPI?
cm/360 is how far you physically move the mouse for a full 360°, reflecting both DPI and sensitivity — the real turn distance. eDPI is sens × DPI, useful for comparing within one game. For cross-game comparisons, cm/360 is the accurate measure.