CS:GO / CS2 Sensitivity Calculator

Mouse sensitivity in Counter-Strike 2 (and its predecessor CS:GO) controls exactly how many degrees your crosshair rotates for every inch or centimeter you move your mouse. Getting this setting right is one of the most impactful decisions a competitive player can make — a misconfigured sensitivity forces your muscle memory to constantly compensate, costing you accuracy under pressure.

CS2 stores your sensitivity as a single decimal number in the sensitivity console variable, typically ranging from 0.5 to 5.0 for competitive play. Unlike many other games, CS2 does not separate horizontal and vertical sensitivity, keeping the feel consistent across all axes. This simplicity is part of why Counter-Strike settings transfer so cleanly across gear changes when you use a sensitivity calculator.

Professional players spend months — sometimes years — locked onto a specific sensitivity value because of how deeply muscle memory encodes micro-movements. Changing your raw sensitivity without recalculating your eDPI can completely invalidate that muscle memory, which is why understanding the relationship between DPI, in-game sensitivity, and real-world mouse distance is essential for anyone serious about improving.

This CS:GO / CS2 sensitivity calculator lets you compute your effective DPI (eDPI), the centimeters your mouse must travel for a full 360-degree turn, and your AWP zoom sensitivity — all derived from the exact formulas the game uses internally. It also converts sensitivities from Valorant, Apex Legends, Overwatch 2, Fortnite, and Rainbow Six Siege so you can keep your muscle memory intact when switching games.

Effective DPI (eDPI) is the single number that lets you compare mouse sensitivity across different hardware setups. A player at 400 DPI with sensitivity 2.0 and another at 800 DPI with sensitivity 1.0 have identical eDPI — and identical in-game feel — even though their hardware settings look different.

eDPI became the standard comparison metric in the professional CS:GO and CS2 community because raw in-game sensitivity alone is meaningless without knowing the underlying mouse DPI. When pro player databases list settings, eDPI is always the apples-to-apples number. According to compiled data from pro settings trackers, the average CS2 professional plays between 700 and 900 eDPI, with AWPers typically landing in the 600–750 range for greater precision.

The eDPI speed categories used by this calculator are:

• Below 600: Very Low — AWPer Style, extremely precise, slow flicks
• 600–799: Low — Pro Average, favored by most top-tier professionals
• 800–999: Medium — Balanced, suits riflers and entry fraggers alike
• 1000–1399: High — Entry Fragger style, fast tracking, smaller mousepad
• 1400+: Very High — Aggressive, heavy reliance on aim punch recovery

While eDPI tells you how sensitive your setup is on paper, cm/360 translates that number into the physical distance your mouse must travel to rotate your view a full 360 degrees. This is the most practical metric for matching sensitivity across different games or after a hardware change, because it anchors your feel to actual physical space rather than arbitrary in-game numbers.

CS2 uses a yaw value of 3.18 — this is the degrees-per-unit constant baked into the Source 2 engine. The cm/360 formula accounts for your DPI and in-game sensitivity alongside this engine constant to compute the real-world distance. Most professional CS2 players prefer a cm/360 range of 30–60 cm, which gives enough precision for pixel-perfect micro-adjustments while still allowing fast 180-degree flicks.

Knowing your cm/360 is also essential when sizing a mousepad. If your cm/360 is 80 cm, a standard 40 cm × 45 cm mousepad means you physically cannot complete a full 360 without lifting your mouse — and that gap will manifest as a flick-shot problem during real gameplay.

The zoom_sensitivity_ratio console variable controls how much your in-game sensitivity scales when you zoom in with scoped weapons like the AWP, SSG 08, SCAR-20, and G3SG1. The default value is 1.0, meaning your scoped sensitivity numerically matches your hipfire sensitivity. However, this does not mean your actual angular speed is the same — zooming in narrows your field of view, so the same sensitivity value covers fewer degrees.

Most CS2 professionals prefer a zoom_sensitivity_ratio of 0.818, which compensates for the FOV change and keeps the angular rotation speed consistent between hipfire and scoped views. Setting it to 0.818 means your mouse covers the same number of real-world degrees per centimeter whether you are scoped in or not — a major advantage for players who switch frequently between rifles and the AWP.

The calculator also outputs effective sensitivities for AWP Zoom 1 (first scope click, 40° FOV, multiplied by 0.444) and AWP Zoom 2 (second scope click, 15° FOV, multiplied by 0.222). These multipliers represent the angular compression at each zoom level relative to the base 90° FOV, giving you the actual sensitivity number the game applies when you are fully scoped in at maximum magnification.

• AWP Zoom 1 Effective Sens = Sensitivity × ZoomSensRatio × 0.444
• AWP Zoom 2 Effective Sens = Sensitivity × ZoomSensRatio × 0.222

If you play both rifle and AWP regularly, setting your zoom_sensitivity_ratio to 0.818 is the single highest-impact config change you can make for scope consistency.

Each major FPS title uses a different internal yaw constant — the number of degrees your view rotates per mouse count. To match your cm/360 when moving between games, you must scale your sensitivity by the ratio of the two games' yaw constants. This calculator handles the conversion for five popular titles: Valorant, Overwatch 2, Apex Legends, Fortnite, and Rainbow Six Siege.

The underlying multipliers are derived from each game's engine yaw value divided by CS2's yaw of 3.18:

The conversion formula is: CS2 Sensitivity = Source Sensitivity × (Source Yaw / 3.18). This guarantees that your cm/360 — and therefore your physical muscle memory — stays identical in both games. Note that after converting, your CS2 sensitivity number may look very different from your source game value; what matters is that the real-world mouse distance is preserved.

The most common mistake new competitive players make is changing their sensitivity too frequently. Once you have chosen a sensitivity based on your mousepad size and playstyle, the most important thing is to commit to it for at least three to four weeks of deliberate practice. Muscle memory builds through repetition, and constant resets prevent that learning from accumulating.

A practical approach: start by identifying your mousepad's usable area. Measure the width in centimeters. Your cm/360 should ideally be between 50% and 100% of that width — this allows comfortable flick shots across the full range of motion without lifting the mouse on every 180. For a standard large mousepad of 45 cm, target a cm/360 of 25–45 cm for a balanced setup.

DPI choice matters less than many players believe. 400 DPI and 800 DPI are equally valid if the resulting eDPI is the same — the difference is that higher DPI at lower sensitivity gives smoother cursor movement due to sub-pixel interpolation, but modern gaming mice at 400 DPI already exceed the resolution the game can use. The majority of CS2 professionals use 400 or 800 DPI purely by convention and personal preference.

Once you have set your sensitivity, use aim-training software such as Aimlabs or KovaaK's at the same sensitivity to build your mechanics outside the game. Tracking exercises, flick training, and gridshot all reinforce your chosen sensitivity faster than pure in-game practice.