Change Mouse Sensitivity
Adjust your mouse sensitivity across Windows, macOS, and Linux. Convert sensitivity values between platforms and games with precise mathematical formulas.
How Mouse Sensitivity Works Across Platforms
Mouse sensitivity has 3 layers: hardware DPI, operating system multiplier, and application-specific sensitivity. Each platform handles these layers differently.
Hardware DPI (Layer 1)
The mouse sensor generates raw counts per inch of physical travel. This is constant across all platforms — 800 DPI produces 800 counts whether connected to Windows, Mac, or Linux. Hardware DPI is set through manufacturer software or the mouse's DPI button.
OS Sensitivity Multiplier (Layer 2)
Each operating system applies a software multiplier to the raw counts. Windows uses an 11-notch pointer speed slider. macOS uses a continuous tracking speed slider with an acceleration curve. Linux uses libinput speed values ranging from -1.0 to 1.0.
Application Sensitivity (Layer 3)
Games and creative software apply an additional multiplier. In CS2, the in-game sensitivity value multiplies the OS-processed counts. In Photoshop, the brush speed follows OS cursor speed. Some games override the OS layer entirely with raw input.
DPI vs In-Game Sensitivity vs OS Multiplier
Understanding how these 3 values interact is the foundation for consistent mouse control.
DPI (Dots Per Inch) is fixed at the hardware level. In-game sensitivity is a multiplier applied by the game engine. eDPI (Effective DPI) = Hardware DPI × In-Game Sensitivity. The OS multiplier sits between these two — unless the game uses raw input, which bypasses the OS layer entirely.
eDPI (Raw Input) = DPI × Game Sensitivity
Effective Sensitivity (No Raw Input) = DPI × OS Multiplier × Game SensitivityWith Raw Input Enabled
eDPI = Hardware DPI × In-Game Sensitivity. The OS pointer speed and acceleration have zero effect. This is how CS2, Valorant, Apex Legends, and Overwatch 2 handle input when raw input is enabled.
Without Raw Input
Effective Sensitivity = Hardware DPI × OS Multiplier × In-Game Sensitivity. Older games, browser games, and some indie titles read the OS cursor position instead of raw sensor data. The OS multiplier affects the final cursor speed.
Calculating Your True Sensitivity
Two universally comparable metrics define your true sensitivity: eDPI and cm/360°.
eDPI (Effective DPI)
eDPI = Mouse DPI × In-Game Sensitivity. An 800 DPI mouse with 1.0 sensitivity = 800 eDPI. A 400 DPI mouse with 2.0 sensitivity = 800 eDPI. Both settings produce identical cursor behavior. eDPI is the standard metric used on ProSettings.net for comparing player sensitivities.
cm/360° (Physical Turn Distance)
The number of centimeters of physical mouse travel needed to complete one full 360° turn in a game. Calculated as: cm/360° = (360 ÷ (DPI × In-Game Sensitivity × Game Yaw)) × 2.54. Lower cm/360° means faster turning. Professional CS2 players average 40–55 cm/360°.
in/360° (Imperial Equivalent)
Same concept as cm/360° but measured in inches. cm/360° ÷ 2.54 = in/360°. Used primarily by North American gaming communities.
Matching Sensitivity Between Two Computers
Moving your exact sensitivity to a different computer requires matching 3 specific values.
Step 1: Record Your Source Configuration
Note your hardware DPI (from mouse software), OS pointer speed setting (Windows notch or macOS slider position), and in-game sensitivity value. Calculate your eDPI.
Step 2: Set Hardware DPI on the New Computer
Install your mouse manufacturer software and set the same hardware DPI. If the mouse stores DPI in onboard memory, this step is automatic.
Step 3: Match the OS Pointer Speed
Set Windows pointer speed to the same notch (6/11 recommended) or macOS tracking speed to the same position. Disable acceleration on both computers.
Step 4: Enter the Same In-Game Sensitivity
Open the game and set the exact same sensitivity value. If the game supports raw input, enable it on both computers. Your cm/360° should now be identical.
Sensitivity Settings for Different Tasks
Optimal sensitivity varies by application. Here are 5 common use cases and their recommended ranges.
Competitive FPS Aiming
eDPI: 200–400 (CS2), 200–320 (Valorant). cm/360°: 35–55 cm. Low sensitivity for maximum crosshair precision. Requires large mousepad (45+ cm wide) and arm aiming technique.
Fast-Paced Shooters
eDPI: 800–1600 (Apex Legends), 4000–8000 (Overwatch 2). cm/360°: 15–30 cm. Medium sensitivity balances tracking speed and flick accuracy.
Desktop Navigation
800–1600 DPI with default OS multiplier. Cursor should cross the full screen width with a comfortable wrist movement — approximately 8–12 cm of travel for a 24" monitor.
Photo and Video Editing
1200–2400 DPI for 1080p, 1600–3200 DPI for 4K. Precision cursor placement for selection tools, masking, and timeline scrubbing. Low acceleration or flat profile preferred.
CAD and 3D Modeling
1600–3200 DPI with orbit and pan mapped to mouse buttons. CAD software uses cursor position for snapping — pixel-accurate placement needs higher DPI with low OS sensitivity.
Why Raw Input Overrides OS Sensitivity
Modern games bypass the operating system to read mouse data directly from the hardware driver.
Raw input reads the mouse sensor's unprocessed delta values — the exact number of counts the sensor reported in each movement packet. This data skips the OS pointer speed multiplier, acceleration curve, and DPI scaling layer. The game engine applies only its own sensitivity multiplier to the raw counts.
Games that support raw input include CS2 (m_rawinput 1), Valorant (always on), Apex Legends (always on), Overwatch 2 (m_rawinput 1), Fortnite (settings menu toggle), and most modern Unreal Engine and Unity titles. When raw input is enabled, changing Windows pointer speed or macOS tracking speed has zero effect on in-game cursor behavior.
Enable raw input in every game that supports it. Raw input ensures your sensitivity stays identical regardless of OS pointer speed settings, making your configuration portable between computers.
Frequently Asked Questions
Common questions about mouse sensitivity, eDPI calculations, and cross-platform sensitivity conversion.
01What is the difference between mouse DPI and mouse sensitivity?
DPI (Dots Per Inch) is the hardware sensor resolution — how many counts the sensor reports per inch of physical travel. Sensitivity is a software multiplier applied by the OS or a game to those raw counts. DPI is fixed in hardware; sensitivity is adjustable in software. Both affect cursor speed.
02How do I convert sensitivity between two games?
Calculate your cm/360° in the source game using: cm/360° = (360 ÷ (DPI × Sensitivity × Yaw)) × 2.54. Then solve for the sensitivity in the target game using the target game's yaw value. Each game engine has a different yaw constant — CS2 uses 0.022, Valorant uses 0.07, Overwatch 2 uses 0.0066.
03Does changing sensitivity affect mouse accuracy?
Changing software sensitivity does not affect the hardware sensor's accuracy. The sensor continues reporting the same number of raw counts per inch. Increasing sensitivity amplifies those counts, which makes the cursor faster but does not add precision — unlike increasing hardware DPI, which actually resolves more physical position data.
04What sensitivity do pro gamers use?
Professional CS2 players average 800 DPI with 0.8–1.2 in-game sensitivity (eDPI 640–960). Professional Valorant players average 800 DPI with 0.25–0.45 sensitivity (eDPI 200–360). Professional Apex Legends players average 800 DPI with 1.2–2.0 sensitivity (eDPI 960–1600). Source: ProSettings.net.
05Should I use high DPI with low sensitivity or low DPI with high sensitivity?
Both produce identical eDPI and cursor speed. 800 DPI × 2.0 sensitivity = 400 DPI × 4.0 sensitivity = 1600 eDPI. The practical difference: higher hardware DPI provides smoother sensor sampling and lower initial pixel latency. Most competitive guides recommend 800 or 1600 DPI with adjusted in-game sensitivity.
06Can I change mouse sensitivity without installing software?
Yes. On Windows: Control Panel → Mouse → Pointer Options → Pointer Speed slider. On macOS: System Settings → Mouse → Tracking Speed slider. On Linux: 'xinput set-prop <id> "libinput Accel Speed" <value>' in terminal. These change OS-level sensitivity without manufacturer software.
07Why does my sensitivity feel different after a Windows update?
Major Windows updates can reset the pointer speed slider to the default 6th notch and re-enable 'Enhance pointer precision' (acceleration). If your previous setting was different from the default, the update effectively changed your OS sensitivity multiplier. Re-check Control Panel → Mouse → Pointer Options after every major update.
08Does raw input bypass OS sensitivity settings?
Yes. When a game enables raw input, it reads mouse data directly from the hardware driver, bypassing the OS pointer speed multiplier and acceleration curve. Changing Windows pointer speed or macOS tracking speed has zero effect on in-game cursor behavior when raw input is active.