Should I use zoom_sensitivity_ratio_mouse 1.0 or 0.8189?

Both are valid, and the right choice depends on how your brain maps scoped aim. At 1.0, the scoped sensitivity is faster than a true 1:1 match — your on-screen flick distance requires less physical mouse movement when scoped because the game applies sensitivity scaling to compensate for visual magnification. Many AWPers prefer this because a scoped shot is usually a small-angle correction and the faster sensitivity helps with quick micro-flicks. At 0.8189, your scoped sensitivity is mathematically 1:1 at the screen center — the same on-screen distance requires the same mouse movement scoped or unscoped. This is preferred by players who want their muscle memory to transfer perfectly between rifle and AWP without any mental adjustment. Test both: play two AWP deathmatch sessions, one with each setting, and trust whichever one produces better results. The difference is small enough that preference outweighs mathematics.

Does my CS:GO sensitivity work the same in CS2?

Yes, completely. CS2 uses the exact same yaw multiplier (0.022) and sensitivity system as CS:GO. Your CS:GO sensitivity value, eDPI, and cm/360 transfer to CS2 without any conversion. All console commands related to mouse input (m_rawinput, m_customaccel, m_mousespeed, zoom_sensitivity_ratio_mouse) function identically. The only difference is CS2's subtick system, which registers shots at the sub-tick level rather than on the next tick boundary — this can make your flicks feel slightly more responsive, but it does not change the underlying sensitivity mechanics. If you backed up your CS:GO config, your sensitivity and mouse settings will carry over seamlessly.

What FOV does CS2 use and how does it affect sensitivity?

CS2 uses a horizontal FOV of approximately 90 degrees at 16:9 aspect ratio. However, CS2's FOV scales with aspect ratio: 4:3 stretched displays a narrower horizontal FOV (approximately 74 degrees), while 16:9 displays the full 90 degrees. Ultrawide aspect ratios (21:9, 32:9) show more than 90 degrees horizontally. The vertical FOV remains constant across all aspect ratios. This FOV behavior has no effect on your mathematical sensitivity (cm/360 remains identical regardless of aspect ratio), but it significantly affects perceived sensitivity. On 4:3 stretched, targets appear wider and your crosshair appears to move faster horizontally because fewer degrees of the game world are displayed across the same screen width. On 16:9, your sensitivity feels slightly slower because more degrees are visible. This is purely a visual perception effect — your physical mouse movement for a given rotation angle is unchanged.

What mouse polling rate should I use for CS2?

1000Hz (1ms report interval) is the standard and fully sufficient for 99.9% of players, including professionals. At 1000Hz, your mouse reports its position 1000 times per second, which at typical CS2 sensitivities translates to a new position report for every pixel or two of crosshair movement. 2000Hz and 4000Hz polling offer marginally reduced input latency (0.5-0.75ms theoretical reduction) but at the cost of higher CPU usage that can cause frame time inconsistency on systems that are already CPU-limited by CS2. The only scenario where above-1000Hz polling provides a meaningful benefit is if you use a very high sensitivity combined with a very high refresh rate monitor (240Hz+) — the finer temporal granularity of mouse reports can reduce micro-stutter in crosshair movement when making very fast flicks. For everyone else, 1000Hz is the sweet spot of responsiveness, stability, and compatibility.

How do I set my CS2 sensitivity from another game like Valorant?

To convert Valorant sensitivity to CS2: multiply your Valorant sensitivity by approximately 3.18. For example, Valorant 0.35 at 800 DPI (280 eDPI) converts to roughly CS2 1.11 at 800 DPI (~888 eDPI). The exact conversion uses the yaw ratio: Valorant yaw (~0.07) divided by CS2 yaw (0.022) = ~3.18. Our universal converter handles this automatically — select Valorant as your source, CS2 as your target, enter your DPI and Valorant sensitivity, and the converter outputs the exact CS2 value. You can also calculate manually: multiply Valorant sens by 3.18, but the converter provides a more precise result by matching cm/360 directly rather than using the rounded yaw ratio.

Gaming Tools2026-05-10

CS2 Sensitivity Converter: Match Your Aim with eDPI and cm/360

CS2 professionals cluster between 800 and 1600 eDPI, with most running 800 DPI at a sensitivity of 1.0-2.5 — giving them a cm/360 range of roughly 25-52cm. This wide range exists because CS2 accommodates multiple playstyles: aggressive riflers like m0NESY favor higher sensitivity (around 2.0 at 800 DPI, ~832 eDPI, ~25cm/360) for fast target switching and flicking, while AWPers like ZywOo prefer lower sensitivity (1.95 at 400 DPI equivalent, roughly 780 eDPI, ~27cm/360) for long-range precision. CS2 runs on the Source 2 engine, which uses a yaw multiplier of 0.022 degrees per mouse count — the same yaw value CS:GO used, making sensitivity settings fully backward compatible. Our CS2 sensitivity converter takes your settings from any game and calculates the exact CS2 sensitivity that preserves your cm/360, including the zoom sensitivity ratio for AWP double-scoping and Aug/SG 553 scoped modes. This guide covers the CS2 sensitivity ecosystem in depth: how the Source 2 engine processes mouse input, the professional sensitivity meta after the CS2 transition, the zoom_sensitivity_ratio_mouse command and its popular values, and the Windows and NVIDIA settings that affect input feel.

settings_input_component

CS2 Sensitivity Converter

Free · No registration

Try this tool for free →open_in_new

Step-by-Step Guide

Calculate Your CS2 eDPI and Find Your Sensitivity Archetype

Enter your DPI and CS2 sensitivity. Your eDPI = DPI × sensitivity. For example, 800 DPI × 1.5 sens = 1200 eDPI (~35 cm/360). CS2 pros divide loosely into three archetypes: low sensitivity (600-900 eDPI) players like ZywOo (400 DPI × 1.95 = 780 eDPI) and dev1ce (400 DPI × 2.0 = 800 eDPI) prioritize long-range precision and AWP stability, using their whole arm for large movements. Medium sensitivity (900-1200 eDPI) players like NiKo (400 DPI × 2.5 = 1000 eDPI) and ropz (800 DPI × 1.27 = 1016 eDPI) balance flick speed with precision — this is the most populated range in Tier 1. High sensitivity (1200-2000 eDPI) players like m0NESY (800 DPI × 2.0 = 1600 eDPI) and woxic (1600 DPI × 1.5 = 2400 eDPI, an outlier) prioritize raw speed and use wrist-dominant aim styles. If you are unsure where to start, set 800 DPI at 1.3 sensitivity (1040 eDPI, ~40 cm/360) — a middle-ground value that allows both precise rifle aim and manageable 180-degree turns on a standard 45cm mousepad.

Configure CS2 Mouse Settings for Maximum Consistency

Open CS2 Settings → Keyboard/Mouse and set Mouse Sensitivity to your calculated value. Below it, ensure Raw Input is set to On — this bypasses Windows mouse processing and reads mouse data directly, eliminating any acceleration or pointer speed distortion. The Mouse Acceleration setting should be Off (this is the default). In the console (enable it in Settings → Game → Enable Developer Console), the command m_rawinput 1 confirms raw input is active. Also verify m_mousespeed 0 and m_customaccel 0 in the console to ensure no residual acceleration profiles are active. For your Windows settings: Control Panel → Mouse → Pointer Options → pointer speed at 6/11 (exact center), and uncheck Enhance Pointer Precision. These Windows settings matter because, even with raw input, some mouse drivers reference the Windows pointer speed for sensor behavior. Additionally, in your NVIDIA Control Panel or AMD Adrenalin software, set Low Latency Mode to On or Ultra (or use Reflex in-game via the nvidia_reflex_low_latency setting) and ensure VSync is off to minimize the render queue latency that affects the perceived responsiveness of your mouse movements.

Set Your Zoom Sensitivity Ratio for Scoped Weapons

CS2 handles scoped sensitivity through the console command zoom_sensitivity_ratio_mouse (default value: 1.0). At 1.0, your scoped sensitivity in the first zoom level (both AWP and SSG 08) uses a sensitivity scaled by the zoom factor — the AWP at 1.0 zoom sensitivity produces roughly 47% of your hipfire cm/360, which compensates for the visual magnification to make the crosshair feel consistent between scoped and unscoped views. The most debated value in CS history is 0.818933..., which mathematically produces a true 1:1 monitor distance match for the AWP's first zoom level (2.5x magnification) — meaning a flick of a certain distance on screen requires the same mouse movement whether scoped or unscoped. Many pros including s1mple use 1.0 (the default). NiKo uses 0.8. ropz uses 1.0. If you are an AWPer, test 1.0 and 0.8189 side by side in a deathmatch session and commit to whichever feels more natural — both are valid, and the difference comes down to whether you want your scoped aim to feel slightly faster (1.0) or mathematically matched (0.8189). The AUG and SG 553 scoped sensitivity is controlled by the same cvar value.

Tips & Best Practices

check_circle

CS2 uses the same yaw multiplier as CS:GO (0.022), meaning all CS:GO sensitivity settings, muscle memory, and cm/360 values transfer directly to CS2 without any conversion. If you had 2.0 sensitivity at 800 DPI in CS:GO, use exactly 2.0 at 800 DPI in CS2. The subtick update system in CS2 changes when your shots are registered relative to server ticks, but it does not change how mouse input translates to view rotation.

check_circle

s1mple uses 400 DPI × 3.09 = 1236 eDPI (~34 cm/360) with zoom sensitivity 1.0. NiKo uses 400 DPI × 2.5 = 1000 eDPI. m0NESY uses 800 DPI × 2.0 = 1600 eDPI (~26 cm/360) with zoom sensitivity 1.0. These three players represent the spectrum: s1mple is on the higher end for rifle play, NiKo is in the center of the pro distribution, and m0NESY is at the upper end, using his exceptional wrist control to handle the higher speed.

check_circle

The CS2 pro eDPI distribution has shifted slightly higher compared to the CS:GO era. More young pros entering Tier 1 (like m0NESY, Jimpphat, donk) use sensitivities in the 1200-1600 eDPI range, while the old guard (karrigan, apEX, Snappi) tend toward 800-1000 eDPI. This trend reflects an evolving meta that values faster target switching and more aggressive peeking, enabled by lighter modern gaming mice and higher polling rates.

check_circle

The zoom_sensitivity_ratio_mouse value of 0.818933... comes from the formula: zoom_sensitivity_ratio = tan(hipfire_FOV_internal / 2) / tan(scope_FOV_internal / 2) for the AWP's first zoom level. This produces a mathematically exact 1:1 match at the center of the screen between scoped and unscoped flick distances. At default 1.0, your scope flicks require less mouse movement than equivalent unscoped flicks because Riot/Valve scales the sensitivity to compensate for the magnified view. The 0.8189 value unscales it completely.

check_circle

CS2 supports a maximum mouse polling rate of 8000Hz for compatible mice (Razer Viper 8K, Razer DeathAdder V3, etc.). At 8000Hz, the mouse reports its position every 0.125ms, compared to 1ms at 1000Hz. In theory, this reduces input latency by up to 0.875ms. In practice, the difference is extremely subtle and only detectable by players already competing at the highest level. Most pros still use 1000Hz or 2000Hz — the stability and compatibility benefits outweigh the theoretical latency advantage of 4000-8000Hz for now.

check_circle

Your mousepad matters enormously for CS2 sensitivity. A control pad (ZOWIE G-SR, SteelSeries QcK Heavy) provides higher static friction that helps stop flicks on target, favoring lower sensitivities. A speed pad (Artisan Hien, Razer Strider) provides lower friction for fast, fluid movements, favoring higher sensitivities. Match your pad to your sensitivity: if you use lower eDPI (600-1000), a speed pad helps with the larger arm movements. If you use higher eDPI (1200-2000), a control pad helps prevent over-flicking with small wrist movements.

check_circle

CS2's subtick system decouples mouse input timing from the 64-tick server update rate. Your shots register at the exact moment you click, not at the next available tick. This means your flick timing is more precisely represented than in CS:GO, but it also means that sensitivity inconsistencies (e.g., from mouse acceleration or an inconsistent grip) are more sharply punished because the game is more faithfully representing exactly where your crosshair was when you clicked.

check_circle

To test whether your CS2 sensitivity is correct: join a deathmatch server or workshop map like Aim Botz, close off all angles behind you, and practice flicking between two static bot heads placed at roughly 30 degrees apart. If you consistently overshoot, your sensitivity is too high. If you consistently undershoot, your sensitivity is too low. If you sometimes over- and sometimes under-shoot by roughly equal amounts, your sensitivity is in the right ballpark and the inconsistency is in your aim execution, not your settings.

Frequently Asked Questions

The statistically safest starting point is 800 DPI at 1.3 sensitivity (1040 eDPI, ~40 cm/360). This sits near the center of the professional distribution, allows precise rifle aim at all ranges, and requires roughly 40cm of mousepad for a 360-degree turn. From this baseline, adjust based on your natural tendencies: if you find yourself running out of mousepad space during wide-angle peeks or if 180-degree turns feel labored, increase sensitivity by 0.1 per week until comfort improves. If you find your crosshair is jittery at long range or you over-flick consistently in pistol rounds, decrease by 0.1 per week. The ideal CS2 sensitivity is the one you forget about — it should not require conscious management of your mouse movement to be accurate. Most players settle between 800-1200 eDPI, and the most important thing is staying within a range that allows both precise micro-adjustments and practical utility movements like 90-degree angle clears.

CS2 sensitivity is built on the mature, well-understood Source engine input system. Find your eDPI in the 800-1600 range, set Raw Input to On, choose your zoom sensitivity ratio (1.0 or 0.8189), and invest your practice time in the workshop maps and deathmatch servers that build the muscle memory no converter can give you. Your settings are the foundation — your practice is the building.

Try this tool for free →open_in_new