CM per 360 Calculator for FPS Sensitivity

🎯 CM per 360 Calculator

Calculate FPS mouse sensitivity from DPI, in-game sens, yaw coefficient, FOV scaling, ADS multiplier, target cm/360, eDPI, mousepad width, and same-distance game conversion.

🔫Real FPS sensitivity presets
Formula note: hipfire cm/360 uses 360 divided by DPI, sensitivity, and yaw coefficient, then converts inches to centimeters. ADS and FOV scaling are applied as separate sensitivity multipliers.
46.7 cm
Current hipfire turn
280 eDPI
DPI times sensitivity
0.070
Yaw coefficient in use
0.96 turns
Mousepad 360 coverage
DPI, sensitivity, yaw, ADS, and target inputs
Chooses the reference yaw coefficient and conversion label.
Equivalent sensitivity is calculated from yaw ratio.
Use your mouse driver DPI or raw hardware stage.
For percent games, enter the visible number such as 7.0.
Degrees per count per sensitivity unit. Advanced users can override it.
Use 1.00 for hipfire-only games or raw ADS matching.
Enter the FOV used by the view you want to model.
The hipfire or monitor-match reference FOV.
0 ignores FOV, 100 applies full tangent FOV ratio.
Used to solve the in-game sensitivity for your DPI and yaw.
Measure the real swipe distance, not the advertised pad size.
Affects displayed converted sensitivity only.
FPS sensitivity result
Hipfire cm/360
-
physical mouse travel for one turn
ADS cm/360
-
after ADS and FOV scaling
eDPI
-
DPI multiplied by source sensitivity
Target sensitivity
-
to hit target cm/360 in source game
Calculation breakdown
🔁Game conversion comparison grid
Selected Target
-

Equivalent target game sensitivity appears here.

Yaw-
Valorant
-

Same hipfire cm/360 using Valorant's yaw coefficient.

Yaw0.0700
CS2 / Apex
-

Source-engine style yaw used by CS2, Apex, and many legacy configs.

Yaw0.0220
Overwatch 2
-

Same-distance conversion into Overwatch's lower per-unit yaw.

Yaw0.0066
Tip: Convert hipfire first, then tune ADS separately. Different games can apply zoom sensitivity, FOV matching, and scope multipliers in different layers.
Tip: A mousepad should cover at least one comfortable 180-degree swipe. If it barely covers a full 360, your reset space may be too tight for tracking fights.
📊CM/360, yaw, and sensitivity reference tables
Common cm/360 ranges
RangeFeelCommon useMousepad note
15-25 cmVery fastArena shooters, close tracking, small desksEasy turns, harder micro correction
25-35 cmFast balancedBattle royale, movement-heavy FPSOne 360 fits most medium pads
35-50 cmControl balancedValorant, CS2, Apex, Overwatch hitscanNeeds a wider pad for full resets
50-70 cmLow controlTactical rifling, sniper-heavy rolesLarge arm swipes required
70+ cmVery lowSpecialized tac aim or raw aim trainingDesk-sized pad recommended

Ranges are practical aiming bands, not skill tiers. Comfort, desk space, and game pace matter as much as the number.

Yaw coefficient quick reference
Game profileYaw usedInput styleConversion note
Counter-Strike 20.0220Decimal sensitivityClassic Source-style m_yaw baseline
Valorant0.0700Decimal sensitivityLower menu numbers than Source games
Apex Legends0.0220Decimal sensitivityVery close to Source conversion math
Overwatch 20.0066Menu numberHigher menu number for the same turn distance
Rainbow Six Siege0.0200Menu numberAdvanced ADS sliders can change scoped feel
Fortnite0.005715Percent menu numberEnter 7.0 for seven percent style input

Yaw values are practical conversion coefficients for this calculator. Always check unusual config files or custom sensitivity multipliers.

Preset profile reference
PresetDPISensitivityApprox role
CS2 Rifler4002.00Tactical rifling around 41 cm/360
Valorant Duelist8000.35Control-heavy entry aim around 47 cm/360
Apex Tracking8001.20Tracking and armor-swap movement around 43 cm/360
Overwatch Hitscan8004.00Hitscan tracking around 43 cm/360
Call of Duty Ranked8005.50Faster centering around 31 cm/360
PUBG Arm Aim40040.00Percent-style scoped shooter baseline

The presets are editable examples. Use them to load sane starting values, then replace them with your exact config.

Formula reference
MetricFormulaMain inputsWhy it matters
Hipfire cm/360360 / (DPI x sens x yaw) x 2.54DPI, sensitivity, yawBase physical turn distance
eDPIDPI x sensitivityDPI, sensitivityGood inside one game, weak across yaw changes
Target sensitivity360 x 2.54 / (DPI x target cm x yaw)DPI, target cm, yawSolves the setting needed for a target
Game conversionsource sens x source yaw / target yawTwo yaw valuesKeeps the same cm/360 across games
ADS cm/360hip cm / ADS effective multiplierADS, FOV scaleShows scoped turn distance after multipliers

FOV scaling here uses a tangent-ratio model so the ADS multiplier can be blended between raw and FOV-matched behavior.

Conversion sanity check table
SourceExample settingSame cm in ValorantSame cm in CS2 / ApexSame cm in Overwatch
CS2 / Apex1.00 at yaw 0.0220.3141.0003.333
Valorant0.35 at yaw 0.0700.3501.1143.712
Overwatch4.00 at yaw 0.00660.3771.2004.000
Rainbow Six8.00 at yaw 0.0202.2867.27324.242
Fortnite7.00 at yaw 0.0057150.5721.8196.061

This grid demonstrates yaw-ratio conversion only. Games with special ADS systems, acceleration, scoped multipliers, or non-linear sliders may require extra in-game matching.

Ever played a fast paced arena game after spending time playing a tactical shooter? Your aim seem out of sync for a while. You land headshots one minute and wild swings the next.

Your mechanics probably aren’t at fault. Chances are it’s the math beneath your mouse movement. Players spends a lot of time tweaking their raw sensitivity numbers (DPI), not knowing that they’re meaningless by themselves. Two point zero feels fast in one engine and sluggish in another. You must know what you’re measuring.

Why Sensitivity Calculators Help Your Aim

With that input, the calculator does the work. No more guesswork about whether you’ll be twitchy or too slow if you convert. It’s all about centimeters per three hundred sixty degrees. That removes the need to figure out the different sensitivity multipliers used by each game. It takes you back to thinking about actual physical movement instead of some abstract value from a menu.

Because it lets you think about how far you have to move your mouse to complete a 360 degree rotation, you have something consistent with which to train your muscle memory. Now, it’s not a question of memorizing a number. It’s a question of remembering distance.

What is the secret ingredient that tricks everyone trying to translate settings from one game to another? Yaw coefficients. One degree in sensitivity doesn’t mean the same thing everywhere underneath the hood. Copying your Valorant sensitivity straight over to Counter-Strike won’t make it feel like the same thing at all; instead, your aim will be way off. It’s because the underlying math will scale input different than before.

But the tool automatically adjusts for those yaw differences across games. A turn will feel the exact same when processed by any game engine. And that is where people goes wrong. They think sensitivity is the same thing everywhere. It isn’t.

In this equation, however, physical limits matter just as much as digital ones, with mousepad space being a key constraint. Say you want 45 centimeters for turn distance but all your pad has is thirty. You’re at war with dead desk space and friction each time you have to reposition your aim mid-fight.

This is where the calculator comes into play: it displays how many complete turns will fit onto your usable pad width. Perhaps your dream sensitivity doesn’t even let you make those emergency flicks because you’ve run out of surface area before you can finish turning. Digital limitations aren’t the only thing that matters; physical limitations does too.

On top of all that, there is Aim Down Sights scaling. A lot of people think of hipfire sensitivity and scoped sensitivity as two distinct things, but they’re directly tied together via their relative fields of view. If the game matches your FOVs when you scope in, then your actual effective sensitivity will shift with you as well.

This is what causes that jarring feeling: you set your base sensitivity to “feel good”, yet when you look down the sight the aim seems like it’s heavy. With this you can model out these multipliers and literally see how far off your turn distance gets when looking down sights compared to hipfire. Small thing, but it makes a difference if you want to be precise.

When it comes to sensitivity, pros tend to settle on specific sensitivity bands because they are the best compromise between speed & control. High sensitivity give you the fastest reaction time at the cost of making any micro corrections difficult to make. Low sensitivity will let you be super precise with shots, but requires you to move your whole arm which can strain your shoulders after prolonged gaming.

Your sweet spot isn’t necessarily one exact value, but rather finding the best compromise between how you like to play and the pace of the game. If you’re in a slow paced tactical shooter where each shot matters, you may want lower than normal sensitivity. In faster games though, where you have to track people and adjust direction quickly, a little higher sensitivity tends to help more.

In addition to that, it comes with presets from actual competitors so you have a place to start based off of how they set up their rig. And again, they aren’t rules, but reference points. Load one of those up, adjust some of the variables and experience what little tweaks do to your total turn distance.

Tinker with those inputs and learn why some games seem light, while others seem heavy. This isn’t about reinventing how you aim every time something gets updated. It’s about creating a sensitivity profile that you bring with you from game to game to give you consistent muscle memory instead of chaos. Remove the doubt out of your reaction, that’s what getting your sensitivity “just right” means.

Your physical actions need to match up with the math. At some point, it’s no longer something you think about, it’s something you feel. It goes from a hindrance on the screen to an extension of your intent. It becomes not about the number, it becomes about how you react to the enemy. The calculator lays down the base; the rest is all you. Discover that magic distance where your eye and hand become one, then the rest follows.

CM per 360 Calculator for FPS Sensitivity

Leave a Comment