Masked Trial

Mouse sensitivity FAQ

Last updated 6 October 2026

Answers to the questions players ask most about sensitivity: how our blind test works, what cm/360 and eDPI actually measure, how to carry a sensitivity from one game to another, and how to pick one in the first place.

How the test works

What does the test actually do?

You enter your game, the sensitivity you play on and your mouse DPI. The test turns that into a physical distance (your cm/360) and builds five settings around it: 30% slower, 15% slower, your own, 20% faster and 45% faster. You then flick to targets on each of them, and at the end it tells you which one you aimed best on, written back as your game's own number.

Why are the sensitivities hidden behind letters?

Because knowing changes how you play. If you know you are on a faster setting, you tense up and aim the way you expect fast sensitivity to feel. If you know you are on your own setting, it feels like home before you have fired a shot. Each setting gets a random letter instead, shuffled fresh every session, so the only thing being measured is your hand.

Why does it keep switching between settings?

Your aim changes over a session: you warm up, then you start to tire. If the test ran all of one setting and then all of the next, the first would collect your cold-hands trials and the last your tired ones, and that difference would look exactly like one setting being better. So the test runs short blocks and cycles through every setting in a new random order each round, which spreads warm-up and fatigue evenly across all five. The first block is a warm-up on the middle setting and is never scored.

How is my aim scored?

Each flick is scored by throughput, a measure from pointing research (Fitts' law). It combines how far the target was, how small it was and how long you took into one number, so a quick flick to a near, large target and a slower flick to a far, small one can be compared fairly. Flicks you never landed are dropped rather than counted as infinitely slow, and freak results far from the rest are trimmed before averaging.

How does it decide the winner?

It fits a curve through your scores across the five settings, allowing for your aim drifting over the session, and estimates how confident it can be in the result. A few rules keep the answer honest:

How long does it take?

About 4 minutes if you already have a sensitivity. If you don't, the beginner test searches the whole range players use and takes about 10 minutes.

cm/360 and eDPI explained

What is cm/360?

It is how many centimetres you move your mouse to turn a full 360° in game. A player on 40 cm/360 sweeps 40 cm across the pad to turn around; a player on 20 cm/360 needs half that. Higher means slower. Because it describes a physical hand movement, it is the same thing in every game, with any mouse, at any DPI. That makes it the only number you can compare directly between two players or two games. (Some people use inches/360 instead; divide cm by 2.54.)

How do I measure my cm/360?

The quick way is to enter your game, sensitivity and DPI into Masked Trial, which works it out from each game's known turn rate. To measure it by hand: put a ruler next to your mousepad, line your crosshair up with something distinctive, move the mouse slowly until you have turned exactly once around, and read off the distance. Turn off mouse acceleration first, or the number depends on how fast you move.

What is eDPI?

eDPI is your in-game sensitivity multiplied by your mouse DPI. A Valorant player on 0.4 at 800 DPI has an eDPI of 320, the same as one on 0.2 at 1600 DPI, and both turn exactly the same amount for the same hand movement.

Why not just use eDPI?

eDPI only works within one game. Every game multiplies your sensitivity by its own turn rate, so 320 eDPI in Valorant and 320 eDPI in CS2 feel nothing alike. A few games also use sliders that are not linear, where doubling the number does not double the speed, and eDPI means nothing there at all. cm/360 has neither problem, which is why Masked Trial works in it internally and shows eDPI only where it is meaningful.

Does DPI on its own matter?

For how far you turn, no: only the combination does. 400 DPI with a high in-game number and 1600 DPI with a low one can give the same cm/360. Higher DPI does give the game finer steps to work with, which matters most at very low in-game values, but it does not make you faster or slower by itself.

Converting sensitivity between games

How do I keep the same sensitivity in a new game?

Work out your cm/360 in the old game, then find the setting in the new game that gives the same cm/360 at your DPI. Masked Trial does this for every game it supports: your result shows the matching number in each of them.

Why can't I just copy the number across?

Because each game decides how far one unit of sensitivity turns you. A sensitivity of 1 is a different turn speed in nearly every game, so the same number can be several times faster or slower. Copying across only works between games built on the same engine and scale.

I matched my cm/360 but it still feels different. Why?

Usually field of view. Matching cm/360 guarantees that a full turn takes the same hand movement, but a game with a wider FOV squeezes more of the world onto your screen, so everything in front of you moves past faster for the same mouse movement. Small aim adjustments near the crosshair can feel faster or slower even though turning around feels identical. The sensible fix is to give it a few sessions before changing anything: the feel usually settles once you stop comparing. Masked Trial renders its targets at your game's field of view so what you test on matches what you play on.

Does this cover scoped or ADS sensitivity?

No. The conversions are for hip-fire, the sensitivity you turn and flick with. Scoped and aim-down-sights multipliers work differently in every game and are best tuned inside the game itself once hip-fire is right.

What if my game isn't listed?

Pick the option to enter your cm/360 directly. Measure it by hand as described above and the test works the same way.

Choosing a sensitivity

Is low sensitivity better than high?

Neither is better in general. Lower sensitivity makes small corrections easier, because a given mistake in your hand becomes a smaller mistake on screen, but it costs you on big turns and tracking fast targets. Higher sensitivity is the reverse. Where the balance sits depends on your hand, your arm, your mousepad and the game. That is the reason the test exists: the right answer is personal and is easier to measure than to argue about.

Arm aiming or wrist aiming?

Low sensitivities make you move from the elbow and shoulder for large movements; high ones let you aim with the wrist and fingers. Arm aiming needs a large mousepad and room on your desk; wrist aiming suits a small space but asks for finer control. If you keep running off the edge of your pad, your sensitivity is probably too low for your setup, whatever the test says.

Should I copy a pro player's sensitivity?

It is a reasonable place to start, especially if you have no idea where to begin. But a pro's setting suits their hand, their setup and thousands of hours on it. Copying it does not copy the aim. Use it as a starting point, then test around it.

How often should I change my sensitivity?

Rarely. Muscle memory takes time to build, and switching often keeps resetting it. Changes under a few percent are not worth making. If the test recommends a change, make it, play on it for a week or two, then test again from there to confirm.

Why does the test sometimes tell me to keep my sensitivity?

Because often the honest answer is that your current setting is already as good as anything nearby. That is a useful result: it means you can stop second-guessing it and spend the time on practice instead.

Take the test