Carry the same physical aim from one game to another, work out eDPI and rescale for a new DPI — with the constant behind every number written down, and the reason mathematically equal does not always feel identical.
One full turn takes the same centimetres of mouse movement in both games. That is the whole model, and the constant behind it is printed under the result.
Hip-fire only. Matching cm/360 keeps the physical distance identical; it does not promise the two games will feel the same, because field of view, zoom behaviour, acceleration and frame pacing all sit outside this arithmetic. Nothing typed here leaves your browser.
The quick tool above covers the 9 verified models. The converters below carry the documented and community-sourced ones too, each labelled with how well it is established.
A sensitivity converter and sensitivity calculator in one: convert hip-fire sensitivity between 24 games, keep the same physical cm/360 and see the formula behind the result.
02Use four transparent calculators for Minecraft portal coordinates, frame-time budgets, deadzone scaling and touch-target planning.
03Calculate eDPI for any supported game, see where it lands among pro settings, convert it to cm/360 and keep the same feel when you change DPI.
04Turn Overworld X and Z into the Nether coordinates where a linked portal belongs, or the other way round, with the rounding the game actually uses.
05Convert a frame rate into milliseconds per frame, and see how many input reports your polling rate fits into each one.
06See how much a stretched resolution widens everything on screen, and the m_yaw value that makes horizontal aim feel like vertical again.
07Get the geometrically correct field of view for your screen and seat, in the number each racing game actually asks for, with triple-screen angles and wheel rotation.
08Turn an old CS2 crosshair code or old console settings into the new pixel crosshair — as a code the game imports and as console commands — or read a new code back into commands.
09Carry your crosshair between VALORANT and CS2: paste a code from either game and get the other game’s code, pixel for pixel at your resolutions, with everything that could not carry over listed.
10Tap any button on a drawn Xbox, PlayStation or Switch controller and see the same button on the other two, by position or by printed letter, with a full conversion table.
11Type your FOV in one game and get the number that gives the same view in eleven others, for your screen shape, with the scene drawn through both.
12Find the tablet area that moves the cursor as far per centimetre as your mouse did, mapped to the whole screen or the playfield, drawn to scale on your tablet.
The pairs people search for most, each on its own page with a table of the values players actually use.
Game sensitivity values are not a shared unit. A value of two in one engine can represent a completely different angular change than two in another. The converters use documented horizontal yaw constants to preserve the estimated physical distance for a full 360-degree turn.
This makes the conversion testable, but it does not promise identical perception. Field of view, animation, frame pacing, acceleration, zoom behavior and game-specific input processing all influence feel. The converter therefore shows both the output and the limitation beside it.
I answer from this site only — the 28 browser tests, the controls library for 46 games, the sensitivity converters and the two games. I can tell you which page to open, how a tool works and what its result means.
I will not guess. If something is not on the site, I will say so.
Answers come from this site's pages.