Mouse Sensitivity Converter

Every FPS game assigns an arbitrary number to the in-game sensitivity slider. A sensitivity of 2.0 in CS2 moves your crosshair at a completely different speed than a 2.0 in Overwatch 2 because each game applies its own internal multiplier — called a game coefficient — to translate that number into actual degrees-per-second of camera rotation.

The mouse sensitivity converter bridges this gap by converting your source game sensitivity into a universal physical measurement — centimeters per 360 degrees (cm/360) — and then back into the matching sensitivity number for the target game. This guarantees your muscle memory transfers perfectly, because the physical amount of mouse movement needed for a full rotation stays identical.

The first step calculates your cm/360:

cm/360 = (2.54 × 360) / (sensitivity × gameCoefficient × (DPI ÷ 400))

The constant 2.54 converts inches to centimeters, and DPI is normalized against the baseline of 400 DPI. Once cm/360 is known, the target sensitivity is found by reversing the formula for the target game's coefficient. Because both steps use the same DPI and the same 2.54 × 360 constant, these factors cancel out, leaving the elegant simplified form:

targetSens = sourceSens × (sourceCoefficient ÷ targetCoefficient)

This means the DPI of your mouse does not change the converted sensitivity value — it only affects how fast the physical movement translates into pixels on screen. Two players with identical cm/360 but different DPI settings will use different in-game sensitivity numbers, but their hands will move exactly the same amount per 360-degree turn.

The calculator also computes eDPI (effective DPI), which is simply sensitivity × DPI. eDPI is a single number that captures the combined effect of both your hardware and software settings, making it easy to compare sensitivity across players regardless of their individual DPI choices.

Each supported game has a hardcoded coefficient that represents how aggressively the game engine responds to a unit change in your in-game sensitivity slider. Understanding these coefficients helps you predict how your sensitivity will feel when you switch titles.

Notice that CS2 and Valorant share the exact same coefficient of 3.18. This is not a coincidence — Valorant's designers intended to make it trivially easy for CS players to transition, so the sensitivity scale was deliberately matched. If you play both games, you can use the exact same sensitivity number in each.

The cm/360 metric is the gold standard for comparing mouse sensitivity across different games, mice, and players. It measures the physical distance in centimeters that you must slide your mouse on the desk to rotate your in-game view by exactly 360 degrees. Because it is a physical measurement, it is entirely independent of game engine, DPI setting, or sensitivity number — a player with 40 cm/360 in CS2 and one with 40 cm/360 in Apex Legends will move their hands the exact same amount per full rotation.

Professional players typically cluster between 25 cm/360 and 80 cm/360, though there is significant variation by role and personal preference. High-sensitivity players (under 25 cm/360) use quick wrist flicks and excel at tracking fast close-range targets. Low-sensitivity players (above 60 cm/360) use full arm sweeping motions, which often leads to more precise long-range flick shots but requires a large mouse pad.

eDPI (effective DPI) is a related metric calculated simply as your in-game sensitivity multiplied by your mouse DPI. For example, a sensitivity of 2.0 at 800 DPI gives an eDPI of 1600. This single number lets you compare your overall speed setting against other players without needing to know their individual hardware configurations. Common competitive eDPI ranges fall between 400 and 1600 for tactical shooters, with the sweet spot for most CS2 professionals sitting around 800–1000 eDPI.

Unlike cm/360, eDPI does depend on the game's coefficient, so it is most useful for comparing players within the same game. When comparing across games, always use cm/360 as the universal reference.

Sensitivity selection is one of the most personal decisions in competitive gaming. There is no universally optimal value — the right choice depends on your aiming style, mouse pad size, the type of game you play, and whether you prioritize micro-adjustment tracking or large snap flicks.

Wrist aimers typically prefer higher sensitivity settings (shorter cm/360) because wrist range of motion is limited compared to full arm movement. A wrist aimer with a 30 cm/360 can comfortably reach all targets without repositioning their elbow, which keeps their technique fast and consistent. Arm aimers generally favor lower sensitivity (longer cm/360) because larger movements carry more muscle memory precision — the shoulder and elbow joints have better fine motor control over wide arcs than the wrist does over tiny ones.

Game genre also matters. In tactical shooters like CS2 and Valorant, where precise micro-corrections at long range are critical, players often prefer lower sensitivity. In battle royale games or hero shooters with lots of close-range engagement and 180-degree snap turns, slightly higher sensitivity can be advantageous. Movement-heavy games like Quake and Apex Legends see more variance, with both very high and very low sensitivity players succeeding at the top level.

When switching games, the primary goal of this sensitivity converter calculator is to preserve your existing muscle memory. By matching your cm/360 exactly, you ensure your brain's learned movement patterns carry over without retraining. After converting, give yourself a few sessions before tweaking further — your aim may feel slightly off initially simply because of visual and environmental differences between titles, not because the sensitivity is wrong.

DPI (dots per inch) is a hardware specification describing how many individual steps your mouse sensor reports for every inch of physical movement. A mouse at 800 DPI sends 800 position updates per inch; at 1600 DPI, it sends 1600. Higher DPI is not inherently better — it simply means smaller physical movements can be detected, which is useful at very low in-game sensitivities but makes no difference otherwise.

Most competitive FPS players settle on 400 DPI or 800 DPI with a corresponding in-game sensitivity that produces their preferred cm/360. Using a moderate DPI avoids sensor jitter issues that can appear at extremely high DPI settings, and keeps in-game sensitivity numbers in a comfortable mid-range rather than tiny decimals like 0.003 or large values like 45.

Polling rate — measured in Hz — determines how frequently your mouse reports its position to your computer. A 1000 Hz polling rate means 1000 position reports per second (every 1 ms). Higher polling rates reduce input latency and produce smoother cursor movement, but they have no effect on the sensitivity conversion formula. Whether you use 125 Hz or 8000 Hz, your converted sensitivity value from this calculator remains exactly the same.

The key takeaway for using this cross-game sensitivity calculator is straightforward: enter the DPI you actually play at in the DPI field, input your current game sensitivity, select your source and target games, and the calculator produces the exact number to enter in your new game. Your cm/360 stays locked, your muscle memory transfers, and you can focus on learning the new game's mechanics rather than re-learning how to aim.