Your controller setting won't convert into a correct initial mouse sensitivity, so skip the search for an equivalent number. Instead, pick a setting in the PC game you plan to play that feels controllable. Write it down along with your mouse DPI and treat it as a personal starting point.
After that, run the same short aiming task every time you test it. Change one thing at a time, and only when the same miss keeps showing up. That way you can tell which change actually helped.
Set and Test Your First Mouse Sensitivity
Choose and Record a Baseline
On PC, how fast your crosshair moves depends on two settings working together. One is your mouse's DPI (also called CPI), a hardware setting you set in the mouse software. The other is the sensitivity slider in the game. Games also use game-specific sensitivity scales. Aimlabs explains that the game profile you pick sets the scale and formula it uses, so the same number won't always feel the same in two different games.
Start in the game you'll actually play. Pick a value where turning around and making small aim corrections both feel manageable, then write down your setup:
- Target game: the specific PC title you're setting up, since its sensitivity scale is what your number means.
- Mouse DPI/CPI: the exact value set in your mouse software. If you practice in a trainer like Aimlabs, enter that same DPI there too, because the trainer can't use the right setup without it.
- In-game sensitivity: the exact number shown in the game's settings menu.
- Field of view (FOV): worth noting in games that let you change it, because Aimlabs asks for an exact FOV in those games so practice matches play.
If you warm up in a trainer, select your target game's profile and enter these same values. That keeps practice and real matches on one baseline.
Repeat the Same Short Aiming Task
Test your baseline in the game's practice range or an empty map, not in a live match where every fight is different. Start from the same spot each time. Flick between the same fixed targets a few times, then briefly track the same moving target. Keep your DPI, sensitivity, and FOV exactly as recorded while you go through the attempts. This is a personal consistency check, not a standardized test. Its value comes from repeating the same thing, so the only variable left is how your aim behaves.
If you want extra reps outside the game, you can practice a mouse accuracy drill on our site. Still make the final sensitivity call in your target game, since that's where the setting applies. Fortnite players can use our Fortnite sensitivity ladder, which applies the same idea to shotgun flicks and tracking.
Read the Pattern and Adjust Once
One bad shot tells you very little. Look for the same pattern across several runs of the task, then respond to it:
- You overshoot, then bounce back and forth: Aimlabs describes repeated overshooting and correction as a possible sign that sensitivity is too high. Try a small reduction.
- Your flicks keep stopping short, or your crosshair falls behind the moving target: treat this as a hint, not a diagnosis, and try a small increase. Aimlabs says its Sensitivity Finder weighs these same flick and tracking cues, meaning underflicks, overflicks, and how well you match a moving target's speed. Your own check is rougher than that tool, so go slowly.
- After any change: adjust only one setting, write down the new value, and run the same task again. Then decide whether to keep the change or go back.
The same Aimlabs guide advises gradual changes over a dramatic drop. A big jump creates its own adjustment period, which makes it harder to tell whether things are improving. A simple way to keep your record clean is to leave DPI alone and make changes with the in-game slider. If a change feels wrong, you can always return to your last recorded value.
FAQs
Does the same sensitivity number work across every PC game?
Not reliably. Each game has its own sensitivity system, so a value that feels right in one title can feel faster or slower in another. When you move to a second game, look at that game's own setting instead of copying the number. Our Mouse Sensitivity Tool can help you compare mouse settings across games.
What does cm/360 measure?
The cm/360 mouse-distance measure is how far your mouse physically travels to make one full 360-degree turn in the game. For example, 32 cm/360 means 32 centimeters, or about 12.6 inches, of mouse movement for one full spin. A lower number means a higher sensitivity. Because it's based on physical distance, it lets you compare mouse sensitivity between games even when their in-game numbers look different. It compares one mouse setup to another. It is not a way to convert a controller setting.
Can a controller 360 method give me a mouse setting?
No. Aimlabs' controller-to-controller 360 method is a trial-and-error process for matching controller sensitivity across controller games. You time a full-stick 360 turn in a game where your sensitivity feels right, then adjust the second game until the times match. That's useful if you keep playing some games on a controller. It doesn't produce a mouse DPI or in-game mouse value, so your mouse baseline still has to come from the PC game itself.
Why might my mouse feel different even when the in-game number is unchanged?
Check whether your mouse's DPI changed. A press of the DPI button can switch stages without you noticing. Also check whether your trainer is set to a different game profile or FOV. Put everything back to your recorded baseline before you judge the aiming task again. If stray presses keep happening, this guide on how to avoid accidental DPI changes covers when to keep, disable, or remap that button.
