Device Bench

Device test · Input

Mouse Sensitivity Converter

Move a sensitivity from one title to another and keep the same arm movement. Enter what you play at now, pick or type the yaw for each title, and the page returns the matching setting along with eDPI and centimetres per 360 degrees. Every formula is printed underneath its result, so you can check the arithmetic by hand. Nothing is uploaded and nothing is stored.

Converting from

eDPI—
cm / 360°—
in / 360°—

Converting to

eDPI—
cm / 360°—
in / 360°—
Matching sens— Source cm/360°— Target cm/360°— Source eDPI— Target eDPI—

Your sensitivity across the listed titles

TitleYawSensitivityeDPIcm / 360°

Preset yaw values as recorded on this page: last verified 2026-08-22. A game patch can change a yaw, and a stale constant produces a wrong answer rather than merely old text — so treat the presets as a convenience, check anything that looks off against the measurement below, and use the custom field to override.

Changing mouse DPI, same title

Raising DPI without changing the in-game number changes your arc. This keeps the arc and moves the setting.

New sensitivity—

Measure a yaw from a physical 360

The one number no table can go stale on, because it comes from the build you are actually running. Line the mouse against a ruler, turn exactly one full circle in game, and enter the distance you moved.

Derived yaw—

Paste that number into either "Enter yaw directly" field above and every result on this page is computed from your own measurement.

How this converter works

Nothing here is hidden behind a lookup. Given a yaw y — the degrees a title turns per mouse count at sensitivity 1 — a sensitivity s, and a mouse resolution d in counts per inch, effective DPI is d × s; a full turn takes 360 ÷ (y × s) counts; that distance is counts ÷ d inches, or × 2.54 for centimetres. Every figure this page prints comes from those four lines and from numbers you typed. There is no server, no lookup call and no stored profile.

Two settings feel the same when the mouse travels the same distance for one turn, so matching aim means holding centimetres per 360 degrees constant across the two titles. Setting the two distances equal gives y1s1d1 = y2s2d2, and solving for the unknown side gives the converter its single line: s2 = (y1 × s1 × d1) ÷ (y2 × d2). The result is printed underneath every readout with the actual numbers substituted, so the arithmetic can be checked by hand.

The limit worth stating plainly is the yaw constant. It is a property of a specific build, not of the world, and a patch can move it — which makes a stale table a wrong answer rather than merely old text. That is why the presets carry a verification date, why every result names the yaw it used, and why the physical-360 measurement above exists: a yaw derived from your own turn cannot go stale. This page reports measurements and conversions only. It does not recommend a sensitivity, because that is preference and no arithmetic settles it.

Frequently asked questions

What is eDPI?
Effective DPI: mouse DPI multiplied by in-game sensitivity. It lets two people compare settings when their mice are set to different DPI, but it only compares within one title — eDPI 800 does not mean the same arm movement in two games, because each game turns a different number of degrees per mouse count.
What is cm per 360, and why does this page lead with it?
The distance the mouse travels for one full turn. Unlike eDPI it is comparable across titles and across mice, because it is a physical measurement rather than a setting. That is the number this page holds constant when it converts.
What is yaw?
Degrees of rotation per mouse count at sensitivity 1. It is the constant that makes conversion possible, and it belongs to a specific build of a specific title — a patch can change it. That is why every result on this page states the yaw it used, and why you can type your own instead.
How do I check a yaw value myself?
Measure a physical 360. Line the mouse up against a ruler, turn exactly one full circle in the game, and note the distance travelled. Enter that distance with the sensitivity and DPI you used and the page derives the yaw from your own measurement — a number that cannot be stale, because it came from your build. The on-screen ruler on this site is calibrated for exactly that kind of measurement.
Why does the converted sensitivity have so many decimals?
Because an exact match usually is not a round number. Most titles accept several decimal places; if yours truncates the value, the arc changes very slightly and the printed cm per 360 tells you by how much.

Related tools