Cm/360 Calculator

Ask a competitive FPS player for their sensitivity and you will rarely hear a single number. Instead you will hear something like "I play on 52 centimeters per 360." That figure — the physical distance your mouse must travel to spin your character a full circle — is the universal language of aim. It works across games, across mice, and across DPI settings, because it describes what your hand actually does rather than what a slider says.

The problem is that games do not show you this number. They show DPI on your mouse and a sensitivity slider in the settings menu, and the relationship between those two numbers and your real-world mouse movement is anything but obvious. Change your mouse, change your DPI, switch games — and your carefully tuned aim feels foreign overnight. A Cm/360 Calculator converts DPI and in-game sensitivity into the physical measurement that actually matters.

This page gives you a free Cm/360 Calculator. Enter your mouse DPI, your in-game sensitivity, and the game's yaw value (0.022 is the standard default used by Counter-Strike-style games), and it returns your cm per 360, inches per 360, eDPI, and total mouse counts per turn. Use it to replicate your aim exactly on any setup, in any game.

What Is Cm/360?

Cm/360 is the distance, in centimeters, that you must move your physical mouse to rotate your in-game view a full 360 degrees. A low value like 25 cm/360 means high sensitivity — a short flick spins you around — while a high value like 60 cm/360 means low sensitivity, requiring a long arm sweep for the same turn.

Three inputs determine it. DPI (dots per inch) is your mouse's hardware resolution: how many movement counts it reports per inch of physical travel. In-game sensitivity is the game's multiplier applied to those counts. Yaw (sometimes called m_yaw) is the degrees of rotation the game applies per mouse count at sensitivity 1.0 — most Source-engine-style games use 0.022 degrees per count.

The related term eDPI (effective DPI) is simply DPI multiplied by in-game sensitivity. Two players with 400 DPI at 2.0 sensitivity and 800 DPI at 1.0 sensitivity both have 800 eDPI and — in the same game — identical cm/360 values. That is why eDPI, not raw DPI, is the number worth comparing when someone shares their settings.

Why Cm/360 Matters

Sensitivity expressed as cm/360 is hardware-independent. If your mouse dies the night before a tournament and the replacement only supports different DPI steps, you can recalculate the in-game sensitivity that reproduces your exact cm/360 and your muscle memory survives intact. Without the conversion, you would spend days relearning your aim by feel.

It is also game-independent, with one caveat. Different games use different yaw values and sensitivity scales, so "sensitivity 1.0" means different things in different titles. But 40 cm/360 is 40 cm/360 everywhere — the calculator lets you translate your aim from one game to another by solving for the sensitivity that yields the same physical distance.

Finally, cm/360 makes aim discussions meaningful. Saying "I use 800 DPI" tells another player almost nothing, because the in-game slider could be anything. Saying "I use 45 cm/360" tells them exactly how your aim feels. Most professional FPS players cluster between roughly 25 and 55 cm/360, with tactical shooters skewing lower-sensitivity and fast arena shooters skewing higher.

How to Use the Cm/360 Calculator

Follow these steps to measure your sensitivity.

Step 1: Enter your mouse DPI. Type your mouse's DPI setting into the "Mouse DPI" field. Check your mouse software if you are unsure — common values are 400, 800, 1600, and 3200. For example, enter 800.

Step 2: Enter your in-game sensitivity. Type the sensitivity value from the game's settings menu into the "In-Game Sensitivity" field. For example, enter 1.0. Decimal values like 0.75 are fine.

Step 3: Enter the yaw value. The "Degrees Per Count" field defaults to 0.022, which is correct for Counter-Strike, Valorant-style conversion tools, and most Source-engine games. Change it only if your specific game documents a different yaw.

Step 4: Click Calculate. Press the Calculate button. You will see four results: cm per 360, inches per 360, your eDPI, and the total mouse counts in one full turn.

Step 5: Reset to compare. Press Reset and enter a different game's settings to find the sensitivity that matches your cm/360 there.

Worked Example 1: 800 DPI at 1.0 Sensitivity

A Counter-Strike player uses 800 DPI with an in-game sensitivity of 1.0 and the default yaw of 0.022. What is her cm/360?

Inputs: DPI = 800, sensitivity = 1.0, yaw = 0.022.

Step 1 — Counts per 360. Each count rotates the view by yaw x sensitivity = 0.022 x 1.0 = 0.022 degrees. Counts needed for a full turn: 360 / 0.022 = 16,363.6 counts.

Step 2 — Inches per 360. The mouse reports 800 counts per inch: 16,363.6 / 800 = 20.45 inches.

Step 3 — Centimeters per 360. 20.45 x 2.54 = 51.95 cm.

Step 4 — eDPI. 800 x 1.0 = 800 eDPI.

Final result: Her sensitivity is 51.95 cm/360 — a fairly low sensitivity typical of tactical shooter players who value precise long-range aiming. If she switches to a 1600 DPI mouse, she can keep the identical feel by halving her in-game sensitivity to 0.5 (eDPI stays 800).

Worked Example 2: 400 DPI at 2.5 Sensitivity

An arena shooter player uses 400 DPI at 2.5 sensitivity with the same 0.022 yaw. How does his aim compare?

Inputs: DPI = 400, sensitivity = 2.5, yaw = 0.022.

Step 1 — Counts per 360. Degrees per count: 0.022 x 2.5 = 0.055. Counts per turn: 360 / 0.055 = 6,545.5 counts.

Step 2 — Inches per 360. 6,545.5 / 400 = 16.36 inches.

Step 3 — Centimeters per 360. 16.36 x 2.54 = 41.56 cm.

Step 4 — eDPI. 400 x 2.5 = 1,000 eDPI.

Final result: His sensitivity is 41.56 cm/360 — noticeably faster than the first player's 51.95, suiting the rapid 180-degree turns of arena gameplay. Note the eDPI of 1,000 versus 800: eDPI alone would not reveal the full picture, but cm/360 makes the comparison exact.

Understanding the Cm/360 Formula

The formula chains together the three stages of the input pipeline. First, the game converts mouse counts into degrees: degrees per count = yaw x sensitivity. Second, it figures out how many counts make a full rotation: counts per 360 = 360 / (yaw x sensitivity). Third, it converts counts back into physical distance using the mouse hardware: inches per 360 = counts per 360 / DPI, then cm per 360 = inches x 2.54.

In one line: cm/360 = 360 / (yaw x sensitivity x DPI) x 2.54. Every term matters. Doubling your DPI halves your cm/360 (faster aim). Doubling your sensitivity halves it too. And a game with a different yaw value shifts everything, which is why the calculator exposes yaw as an input rather than hiding it.

The concept of pixel skipping falls out of the same math. At very low DPI combined with high sensitivity, the game may rotate more than one pixel per mouse count, making aim feel steppy. Keeping DPI at 400 or above with moderate in-game sensitivity avoids this — one reason 400-800 DPI remains the professional standard despite mice offering 20,000+ DPI.

Choosing the Right Sensitivity for Your Game

There is no universally best cm/360 — only trade-offs matched to the game. Tactical shooters (Counter-Strike, Valorant) reward pixel-precise crosshair placement at long range, so professionals typically sit between 35 and 55 cm/360, using large mousepads and arm aiming. Fast-paced arena and battle royale games with frequent close-range 180-degree turns favor 25-40 cm/360, trading some precision for speed.

Your physical setup constrains the choice too. A 30 cm/360 sensitivity on a tiny 25 cm-wide mousepad means you will constantly run out of space mid-fight. As a rule of thumb, your mousepad should be at least as wide as your cm/360 value so a full turn fits in one uninterrupted swipe — another reason the number is worth knowing precisely.

When changing sensitivity, change it deliberately and rarely. Aim is motor memory built over hundreds of hours; switching from 50 to 30 cm/360 overnight will wreck your performance for weeks. If you want to go lower, step down 10-15% at a time and give each step at least a week. Many players who chase a pro's exact number end up worse — the right sensitivity is the one your arm has actually practiced.

Tips for Dialing In Your Aim

1. Know your current cm/360 first. You cannot improve what you have not measured — calculate it before changing anything.
2. Keep eDPI constant when switching DPI. If you move from 400 to 800 DPI, halve your in-game sensitivity to preserve your exact aim feel.
3. Match sensitivity across games by cm/360. Use the calculator in reverse: enter your target cm/360 and solve for the new game's sensitivity setting.
4. Use a mousepad wider than your cm/360. One full turn should fit in a single swipe without lifting the mouse.
5. Disable mouse acceleration. Turn off "enhance pointer precision" in Windows and any in-game acceleration so equal hand movements always equal equal rotation.
6. Set Windows sensitivity to 6/11. The middle notch is the only one with no scaling; anything else distorts your true DPI.
7. Change sensitivity in small steps. Adjust by 10-15% at a time and practice for at least a week before judging the change.
8. Warm up before judging. Test a new sensitivity after a proper aim warm-up, not cold — fatigue masquerades as a bad setting.
9. Keep one sensitivity per game genre. Tactical and arena shooters can differ, but avoid a different setting for every single title.
10. Write your settings down. Record DPI, sensitivity, yaw, and cm/360 somewhere safe so a reinstall or new PC never costs you your aim.

Frequently Asked Questions

1. What does cm/360 mean?

It is the centimeters of physical mouse movement required to turn your in-game view a full 360 degrees. Lower values mean higher sensitivity; higher values mean lower sensitivity.

2. What is a good cm/360 for FPS games?

Most players land between 25 and 55 cm/360. Tactical shooters favor 35-55 for precision, while fast arena games favor 25-40 for quick turns. Personal comfort and mousepad size matter more than any specific number.

3. What is eDPI?

Effective DPI — your mouse DPI multiplied by your in-game sensitivity. It lets you compare sensitivity across different DPI settings, since 400 DPI at 2.0 and 800 DPI at 1.0 are identical at 800 eDPI.

4. What is yaw (m_yaw)?

Yaw is the degrees of in-game rotation applied per mouse count at sensitivity 1.0. The default in many games is 0.022. Games with different yaw values need different sensitivity numbers for the same cm/360.

5. How do I convert my sensitivity to a new game?

Calculate your current cm/360, then in the new game adjust its sensitivity until the calculator shows the same cm/360 using that game's yaw value. Your muscle memory will transfer directly.

6. Does higher DPI mean better aim?

Not inherently. DPI only changes the granularity of movement reporting. What matters is the resulting cm/360. Very high DPI with very low in-game sensitivity and very low DPI with high sensitivity can feel identical.

7. What causes pixel skipping?

When sensitivity is so high relative to DPI that one mouse count rotates the view by more than one screen pixel, aim feels jumpy. Using at least 400 DPI with moderate in-game sensitivity prevents it.

8. Should I use the same sensitivity for all games?

Ideally yes, measured in cm/360. Some players keep a slightly faster setting for fast-paced games, but maintaining one consistent aim across titles builds stronger muscle memory.

9. How do I find my mouse DPI?

Check your mouse manufacturer's software (Logitech G Hub, Razer Synapse, and similar). Many gaming mice also have a DPI button that cycles presets, often with an on-screen indicator.

10. Why do pros use low sensitivity?

Lower sensitivity (higher cm/360) makes tiny aiming errors physically larger hand movements, which the arm controls more precisely than the wrist. It trades turning speed for aiming precision.

11. Arm aiming vs. wrist aiming — which is better?

Low sensitivities require arm aiming and suit large mousepads; high sensitivities allow wrist aiming on small pads. Neither is objectively better — it follows from the cm/360 you choose.

12. Does Windows sensitivity affect my cm/360?

Yes, if it is not at the default 6/11 notch. Other notches scale your mouse input before the game sees it, changing your effective DPI. Keep it at 6/11 and disable pointer precision.

13. How often should I change my sensitivity?

As rarely as possible. Aim is built on thousands of hours of motor memory. Change only for a clear reason, in small steps, and give each change at least a week of play.

14. What mousepad size do I need?

At minimum, as wide as your cm/360 so a full turn fits in one swipe. Players under 40 cm/360 usually want large or extended pads; above 50 cm/360, an XL pad is practically mandatory.

15. Can cm/360 be too low or too high?

Extremes cause problems: under about 15 cm/360, precise aiming becomes nearly impossible; over about 80 cm/360, you cannot turn fast enough for close combat. Staying in the 25-55 range keeps both capabilities viable.

CONCLUSION

The Cm/360 Calculator translates the abstract numbers on your mouse and in your settings menu into the one measurement that describes your actual aim: how far your hand moves to turn all the way around. With cm/360, inches per 360, eDPI, and counts per turn in front of you, you can switch mice, switch DPI, or switch games without losing the muscle memory you spent hundreds of hours building.

The single most important takeaway is this: stop thinking in DPI and start thinking in cm/360. Measure where you are, change only in small deliberate steps, and keep your setup consistent. Aim is a physical skill, and like any physical skill, it rewards measurement, patience, and practice far more than it rewards chasing someone else's settings.