How the conversion works
CS2 turns you 0.022° per mouse count at sens 1; Deadlock turns 0.044°. To keep the same physical movement, the sens scales by the ratio of those yaws: 0.022 ÷ 0.044 = 0.5000. Your DPI stays out of it as long as it's the same in both games.
Deadlock is the conversion people get wrong most. Because both games run on Source 2, a widespread claim says the sensitivity is 1:1 with CS2. It is not: measured data puts Deadlock's yaw at 0.044, exactly double CS2's 0.022, so the same number turns you twice as far. Halve your CS2 sens for Deadlock (or double it coming the other way) and your cm/360 carries over exactly.
Assumes the same DPI in both games; the number that transfers between games is the physical distance (cm/360). Most pros land between 25 and 55 cm.
Quick reference (at 800 DPI)
| CS2 sens | Deadlock sens | cm/360 |
|---|---|---|
| 0.64 | 0.320 | 81.2 cm |
| 1.12 | 0.560 | 46.4 cm |
| 1.60 | 0.800 | 32.5 cm |
| 2.24 | 1.120 | 23.2 cm |
| 3.20 | 1.600 | 16.2 cm |
Why the same engine does not mean the same number
An engine does not decide how far one mouse count turns you. Each game sets that for itself, and the setting is called yaw. CS2 kept the 0.022 degrees per count that CS:GO used before it. Deadlock measures at 0.044, twice as far per count, and sharing Source 2 does nothing to make the two agree.
The myth lasts because it fails quietly. Aim at double speed is still playable, so a CS2 player who types in the same number can spend weeks thinking Deadlock just feels twitchy without ever tracing it back to the setting.
Check it yourself in five minutes
You do not have to take a converter's word for this, including this one. Keep the same DPI in both games, mark a spot on your mousepad, and turn one slow, complete circle in CS2. Then type the same number into Deadlock and do it again. At CS2 1.6 and 800 DPI the circle takes 32.5 cm of mousepad. The same 1.6 in Deadlock takes 16.2 cm, half the distance. Set Deadlock to 0.8 and the two turns match.
Use the config file, and recheck after big patches
The 0.044 figure comes from mouse-sensitivity.com, whose measurements most converters are built on. Their measurer notes that Deadlock's in-game slider is not exact and recommends the config file for accuracy, so put the value in autoexec.cfg under citadel/cfg instead of dragging the slider toward it. Deadlock's sensitivity has also changed in a patch before, and the measurements were redone afterwards. After a large update, the five-minute test above is worth repeating.
The camera is the other thing you will notice. Deadlock is third person, with the view over your hero's right shoulder, so part of the screen is your hero and everything sits slightly off to one side. That changes what a fight looks like, not how far a count turns you, so it is no reason to change the number. Give it a few sessions first.
What changes between CS2 and Deadlock
CS2 reads sensitivity from the console or autoexec.cfg with up to five decimals, and raw input is always on. Scoped weapons use zoom_sensitivity_ratio_mouse (default 1.0). Pros mostly sit between 0.8 and 1.3 at 800 DPI, or double that at 400.
Deadlock is Source 2 like CS2 and reads sensitivity from its own autoexec.cfg under citadel/cfg, but its yaw is exactly double CS2's, so identical numbers are not identical aim.
Same engine, same console, half the number. Paste the converted value into Deadlock's autoexec exactly as you would in CS2; the config syntax is identical. If it feels slow at first, that is the myth talking: check the cm/360 readout above and trust it over the familiar-looking number.
Questions
How do I convert CS2 sensitivity to Deadlock?
Multiply your CS2 sens by 0.5000 (the ratio of the games' yaw values, 0.022 / 0.044). At the same DPI this keeps your physical mouse movement identical: 1.6 in CS2 becomes 0.800 in Deadlock.
Does my CS2 scoped or ADS sensitivity carry over to Deadlock?
Not by itself. In CS2, scoped weapons use zoom_sensitivity_ratio_mouse, also a factor on hipfire (default 1.0). In Deadlock, the hipfire sensitivity cvar is the number that matters for nearly every weapon. Convert hipfire with the multiplier above, then set Deadlock's scoped value so it matches how you have CS2 set up.
Do I need the same DPI in both games?
The simple multiplier assumes the same DPI. If you change DPI too, use the full formula: target sens = (source DPI × source sens × source yaw) ÷ (target DPI × target yaw). The converter above handles this automatically.
A converted number is a starting point; your hands confirm it. Run a couple of free rounds and feel whether the distance is right.
Test It Free in the TrainerMore conversions
All conversions live on the sensitivity converter. For finding a sens from scratch rather than porting one, read How to Find Your Ideal Mouse Sensitivity.