Why do sensitivity numbers differ so much between games?

Every game engine uses a unique yaw multiplier — a constant that defines how many degrees of camera rotation result from one mouse input count. CS2 uses a yaw of 0.022 degrees per count, Valorant uses approximately 0.07, Overwatch 2 uses 0.0066, and Apex Legends uses 0.022 (same as CS2 since both are Source-derived). This means the same sensitivity number produces wildly different physical rotation speeds across games: sensitivity 2.0 in CS2 rotates your view by 0.044 degrees per count, while sensitivity 2.0 in Valorant rotates by 0.14 degrees per count — more than three times faster. Game developers choose yaw multipliers based on what sensitivity range they want their slider to produce. Valorant's larger yaw means players use smaller numbers (0.2-0.5) for a natural-feeling sensitivity range, while Overwatch 2's tiny yaw means players use larger numbers (4-10). The numbers look different but can represent identical physical mouse-to-rotation relationships.

How do I measure my cm/360 accurately?

To measure cm/360: enter any game or practice range, find a corner or distinct visual marker, and aim your crosshair at a specific point on it. Place a ruler or measuring tape flat on your mousepad, aligned with the side of your mouse. Slowly and steadily move your mouse in one direction until your character completes a full 360-degree rotation and your crosshair returns to the exact same marker point. The distance traveled in centimeters is your cm/360. For accuracy, repeat the measurement three times and average the results. If your mousepad is not long enough for a full 360 (common with sensitivities above 35 cm/360), measure a 180-degree turn instead and multiply by two. This direct physical measurement is immune to any engine quirk, yaw rounding error, or setting mismatch — it is your true sensitivity, period.

Should I use the same sensitivity for all games?

Most competitive players who play multiple FPS titles maintain the same cm/360 across all their games to preserve a single, unified muscle memory map. Your brain builds motor patterns that associate a specific eye-to-target distance with a specific hand movement distance — splitting these across multiple sensitivity values means you are constantly relearning rather than refining those patterns. However, there are valid exceptions: some players use a slightly faster sensitivity (lower cm/360) for games with more verticality and 360-degree threats (Apex Legends, Overwatch) and a slower sensitivity (higher cm/360) for games focused on horizontal angle holding (CS2, Valorant). If you choose to use different sensitivities per game, limit the difference to no more than 20% in cm/360 terms, and spend 10-15 minutes in a practice range after switching to recalibrate.

What is the difference between 400 DPI and 800 DPI?

At the same eDPI (e.g., 400 DPI × 2.0 sens = 800 eDPI vs 800 DPI × 1.0 sens = 800 eDPI), both configurations produce identical cm/360 and identical physical mouse movement requirements. The difference is in angular granularity: at 400 DPI, your mouse reports 400 counts per inch, so each individual count rotates your view by a specific angle. At 800 DPI, you get twice as many counts per inch, meaning each count produces half the rotation — your aim is twice as "fine" at the smallest possible movement level. At typical tactical shooter sensitivities, 400 DPI can produce noticeable pixel skipping at 1080p resolution, where the smallest possible mouse movement jumps over 1-2 pixels. 800 DPI eliminates this issue for most sensitivity ranges. 1600 DPI provides even finer granularity with no meaningful downside on modern sensors. Most pros have migrated from 400 to 800 or 1600 DPI for the reduced input latency (higher DPI sensors report faster at the same physical speed) and finer angular resolution.

Does the sensitivity converter account for different FOVs?

Our converter calculates the exact in-game sensitivity required to match your cm/360 between games — this is the mathematically correct translation that preserves the physical mouse-to-rotation relationship. It does not apply FOV-based sensitivity scaling because FOV and sensitivity are independent variables. Some sensitivity philosophies (like Viewspeed or Monitor Distance Matching at a specific percentage) incorporate FOV into the calculation, but these methods change your cm/360, which changes your muscle memory. The standard approach — matching cm/360 — preserves your trained motor patterns exactly. Any perceptual difference caused by FOV mismatch is a visual adaptation issue that resolves naturally after a few hours of play, while changing your cm/360 to compensate for FOV creates a permanent mismatch in your physical muscle memory.

Gaming Tools2026-05-10

Gaming Mouse Sensitivity Converter: Match Your Aim Across Every Game

If you play more than one FPS game, you need a sensitivity of roughly 30-45 cm/360 for tactical shooters and 20-35 cm/360 for faster-paced titles — and our universal sensitivity converter bridges the gap between every game engine so you never have to guess. The numbers that appear in each game's sensitivity setting — 2.0 in CS2, 0.3 in Valorant, 5.0 in Overwatch 2 — are meaningless on their own because every game engine uses a different internal multiplier (yaw) to convert mouse input into degrees of camera rotation. The only measurement that holds constant across every game, engine, and platform is cm/360: the physical distance your mouse must travel to complete one full 360-degree turn. Our converter works by taking your known sensitivity and DPI from any supported game, calculating your cm/360, then reverse-calculating the correct in-game sensitivity value to produce that same cm/360 in any other game. This article explains the universal principles behind sensitivity conversion — eDPI, yaw multipliers, FOV effects, and cm/360 measurement — so you understand not just the result but the why behind it.

settings_input_component

Game Sensitivity Converter

Free · No registration

Try this tool for free →open_in_new

Step-by-Step Guide

Enter Your Source Game Settings and Measure Your cm/360

Start by selecting your source game — the game where your sensitivity already feels perfect. Enter your in-game sensitivity value and your mouse DPI (found in your mouse software like Logitech G Hub, Razer Synapse, or SteelSeries GG). The converter immediately calculates your cm/360. If you have never measured your cm/360 manually, it is worth doing once as verification: open your game, stand facing a specific landmark or corner, place a ruler flat on your mousepad next to your mouse, and slowly drag your mouse horizontally until your character completes one full 360 and faces the exact same landmark again. The distance in centimeters is your cm/360. This one number is your universal sensitivity fingerprint — write it down, remember it, and use it as your reference point for every future sensitivity change or game swap. The most common cm/360 ranges are 25-35cm (fast, typical for MOBAs and arena shooters), 35-50cm (medium, typical for tactical FPS), and 50-70cm (slow, typical for ultra-precision roles like dedicated AWPers).

Understand eDPI — Your True Sensitivity Metric

eDPI (effective DPI) is calculated by multiplying your mouse DPI by your in-game sensitivity. For example, 800 DPI × 2.0 sensitivity = 1600 eDPI in CS2. This number represents your true sensitivity independent of individual DPI choices — two players running 400 DPI at 3.0 sensitivity and 800 DPI at 1.5 sensitivity both have 1200 eDPI and experience identical physical mouse-to-rotation relationships, though the 800 DPI player benefits from finer angular granularity (less pixel skipping). Professional eDPI ranges differ dramatically by genre. Tactical shooters (CS2, Valorant) see pros clustered at 200-400 eDPI in Valorant and 800-1600 eDPI in CS2 — the numbers differ because of different yaw multipliers, but the underlying cm/360 is similar at 35-55cm. Arena FPS (Overwatch 2, Quake) pros run 2400-8000 eDPI with cm/360 of 20-35cm. MOBA and BR players spread across 800-2000 eDPI depending on their aim style. Your eDPI is personal — there is no universally correct value, only what produces the cm/360 that feels natural to your hand and wrist coordination.

Convert to Your Target Game and Account for FOV Differences

Select your target game and the converter outputs the exact in-game sensitivity value needed to match your cm/360. The conversion is mathematically precise because it uses each game's known yaw multiplier — the internal constant that translates mouse counts to degrees of rotation. However, a perfect cm/360 match still may not feel identical because FOV (field of view) changes your perception of rotation speed. A wider FOV (110 in Apex Legends) makes the same cm/360 feel subjectively slower than a narrower FOV (90 in CS2) because more of the game world moves across your screen during the same physical mouse movement. This is perceptual, not mathematical — your muscle memory for how far to move the mouse to rotate 30 degrees is correct, but the visual feedback differs. The solution is to either match FOVs where possible (unify around 103 if the game supports it), or to spend 30-60 minutes adjusting to the new FOV without changing sensitivity. Your brain adapts to the new visual frame within a few play sessions, and your underlying motor patterns remain intact because the cm/360 relationship is unchanged.

Tips & Best Practices

check_circle

cm/360 is the only truly universal sensitivity measurement. It works across every game engine, every operating system, and every mouse because it measures the physical distance you move your mouse, which is independent of any software setting. Memorize your cm/360 — it is the single most useful number in maintaining consistent aim across multiple games.

check_circle

eDPI is game-specific and should never be compared across different games. A Valorant player with 320 eDPI and a CS2 player with 1000 eDPI may have identical cm/360 values because Valorant's yaw multiplier is approximately 3.18 times larger than CS2's. Compare eDPI only within the same game or within games that share the same engine yaw.

check_circle

Tactical FPS pros (Valorant, CS2) typically use 30-55 cm/360. Arena FPS pros (Overwatch, Quake) use 20-35 cm/360. MOBA pros (LoL, Dota 2) use 20-45 cm/360 but with higher DPI for faster cursor movement on the map. Battle Royale pros (Apex, Warzone) cluster at 25-40 cm/360, balancing precision with the need for rapid 90-180 degree turns.

check_circle

The Windows pointer speed setting must be at 6/11 (the exact middle notch) with Enhance Pointer Precision disabled for raw mouse input to function correctly. Any other setting applies Windows-level acceleration or deceleration that distorts the linear input both the converter and your games expect. This is the most common reason players report that converted sensitivities feel wrong even when the math is correct.

check_circle

Mouse DPI should remain constant across all your games — never change DPI to adjust sensitivity. Changing DPI also changes your desktop cursor speed, Windows navigation, and inventory menu interaction in every game, fragmenting your overall hand-eye coordination. Adjust only the in-game sensitivity value and keep DPI as a fixed hardware constant.

check_circle

Test your converted sensitivity by measuring cm/360 manually in the target game. Even with a perfect mathematical conversion, always verify physically: use a ruler to measure the distance for a 360-degree turn and confirm it matches your source game within 0.5cm. Small deviations can come from rounding errors, aspect ratio differences, or game-specific mouse input processing.

check_circle

When switching between games with different FOV values, do not immediately start tweaking sensitivity. Give your brain at least 3-5 hours of gameplay at the correctly converted sensitivity to adapt to the new FOV. Constant micro-adjustments prevent this adaptation and keep your aim in a permanent state of flux between two sensitivity values.

check_circle

For games with multiple sensitivity settings (hipfire, ADS, scope, vehicle), convert only hipfire sensitivity first. Scope and ADS multipliers should be set to 1.0 (or the game's default that produces 1:1 monitor distance matching) as a starting point, then fine-tuned individually based on comfort with specific zoom levels.

Frequently Asked Questions

There is no single "best" sensitivity — the optimal value is the one that allows you to perform both precise micro-adjustments and comfortable 180-degree turns. That said, data from thousands of professional players across major FPS titles shows clear clustering: tactical shooter pros overwhelmingly use 30-55 cm/360, arena shooter pros use 20-35 cm/360, and battle royale pros fall between 25-45 cm/360. If you are unsure where to start, set your sensitivity to 35 cm/360 as a middle-ground baseline. Play for one week without changing it. If you find yourself under-aiming (crosshair stops short of targets), slightly increase sensitivity (lower cm/360). If you over-aim (crosshair flies past targets), slightly decrease sensitivity (raise cm/360). Adjust by no more than 2cm per session until you settle into a value that feels effortless — the right sensitivity should not require conscious effort to keep your crosshair on target.

Consistent aim comes from consistent sensitivity, and consistent sensitivity comes from knowing your cm/360. Our universal converter does the math so you do not have to — enter your settings once, get the correct sensitivity for every game you play, and build one unified muscle memory that transfers across every title in your library.

Try this tool for free →open_in_new