Convert your mouse sensitivity between CS2, Valorant, Apex, Overwatch and 10+ other FPS games instantly.
Mouse sensitivity determines how far you need to move your mouse to rotate 360° in-game. Lower sensitivity means more physical mouse movement for the same rotation, which gives better precision for long-range aiming but requires more desk space.
The cm/360 metric — centimetres of physical mouse movement needed for a full in-game rotation — is the universal benchmark for comparing sensitivity across games. It accounts for both in-game sensitivity and mouse DPI, so 'Valorant 0.35 at 800 DPI' and 'CS2 0.97 at 800 DPI' both produce roughly the same cm/360.
DPI (dots per inch) is a hardware setting on your mouse. In-game sensitivity is a software multiplier. A low DPI with high in-game sensitivity is generally worse than a higher DPI with lower in-game sensitivity, because low DPI can cause 'pixel skipping' at high speeds.
Most professional FPS players use between 30 cm/360 and 80 cm/360. Pros in tactical shooters like CS2 and Valorant tend to sit at 40–60 cm/360. Pros in faster-paced games like Fortnite or Apex sometimes use 20–35 cm/360.
Changing your sensitivity frequently is one of the biggest hindrances to improvement. Once you find a comfortable range, commit to it for at least 30–60 days of consistent play before deciding if it needs adjusting. Muscle memory takes weeks to form.
Convert your mouse sensitivity between any two FPS games while keeping the same physical feel. Enter your DPI, source game and sensitivity, then see the exact equivalent in every other game.
CS2 sensitivity 2.0 at 800 DPI
Valorant: 0.629 | Apex: 2.0 | Overwatch: 6.73
Valorant 0.4 at 1600 DPI
CS2: 1.273 | Apex: 3.195 | OW2: 21.5
s1mple, widely considered one of the greatest CS:GO/CS2 players of all time, uses 400 DPI with an in-game sensitivity of 3.09 — giving him a cm/360 of approximately 26 cm, which is on the lower end even for pros.
Begin with the decision or task you want this page to support. Convert your mouse sensitivity between CS2, Valorant, Apex, Overwatch and 10+ other FPS games instantly. Write down the expected kind of answer before entering values, so you can notice if a default, unit, or mode does not fit your situation. If more than one input could change the result, hold the others steady while you test one value at a time. This makes it easier to understand what the tool is responding to instead of treating the first number on screen as a complete recommendation.
Follow the page instructions in order and check the labels as you go. The first step is: Enter your mouse DPI (check your mouse software or manufacturer specs).. Next, select the game you currently play and enter your current in-game sensitivity. Use consistent units and a consistent time period, and avoid replacing an unknown value with zero unless the tool explicitly treats zero as a valid input.
The page's worked example is a reference point, not a forecast for every situation. It shows how the inputs lead to an output: Valorant: 0.629 | Apex: 2.0 | Overwatch: 6.73 Compare the assumptions in that example with your own values, then check the units, rounding, and any optional settings before comparing results. If your scenario differs, describe that difference explicitly rather than expecting the example's answer to transfer unchanged.
Use the result as one part of a decision rather than a substitute for the context around it. If you are comparing alternatives, run each one with the same definitions and change only the factor you want to compare. For repeated tasks, save a short note of the inputs and date; this makes later results easier to reproduce and helps distinguish a real change from a difference in how the values were entered.
A useful final check is to compare the answer with a second route: a hand calculation, a known example, an official reference, or the instructions for the service that will receive the result. One point worth checking on this page is “What does a sensitivity conversion preserve?” A close match on a simple case can confirm the basic method; it does not prove that every complex case is covered.
For low-consequence tasks, a quick spot check may be enough. For anything that affects money, health, safety, access, or a deadline, verify the result against an authoritative source or the system that will use it. The tool can make routine work faster, but you remain responsible for confirming that the inputs and intended use are appropriate.
A conversion aims to preserve a consistent mouse movement relationship between supported games, usually expressed as a similar distance for a 360-degree turn. It cannot make different games feel perfectly identical because field of view, aiming mechanics, input processing, acceleration, and scoped multipliers can differ.
cm/360 is the physical distance you move the mouse to rotate 360 degrees in a game. It gives you a cross-game reference that is less tied to a particular sensitivity number. Measure your own setup after conversion and fine-tune in a practice range, because grip, mouse pad, polling, and FOV still influence perceived control.
Keep your DPI, in-game sensitivity, and operating-system pointer settings consistent while comparing a conversion. Changing DPI and compensating with sensitivity can preserve a similar total scale in some games, but filtering and implementation details may change the feel. Make one change at a time and test tracking, flicks, and target switching.
Use the same mouse DPI and input settings, then test the converted value in a practice range rather than judging it from one match. Compare a 360-degree turn, tracking, flicks, and scoped aim at the distances you normally play. Adjust in small steps only after identifying whether the issue is sensitivity, FOV, acceleration, or another game setting.