GAME SETTINGS / SENS CONVERTER

Mouse sensitivity converter.

Carry a setting between games, choose a turn distance, or keep the same eDPI when you change DPI.

Linear hip-fire · CS2, VALORANT, Apex & Custom references. Verify the result in game.

START WITH A KNOWN VALUE

Calculate a setting.

What do you know?

Enter the setting you use now, then choose the game and DPI you want to use.

01 / Current setting
02 / Setting to calculate

Use the active device DPI, even when it stays the same. Find your active DPI →

Presets are disclosed reference models, not readings from your game or mouse. View values and scope. Use decimal game settings, not percentages.

Calculations run in this page. Editing an input clears the old result.

YOUR SETTING WILL APPEAR HERE

Enter your values or try an example.

You'll get the setting to type, its calculated turn distance and rounding choices.

DEMO INPUTS / NOT RECOMMENDED SETTINGS

Mouse sensitivity conversion examples.

These examples use the reference values listed below. Load a row to see the calculation and rounding choices.

TaskKnown valuesCalculated settingTry it
CS2 → VALORANTCS2 sens 2 · 800 DPI
VALORANT · 800 DPI
0.62857125.9773 cm/360
800 → 1600 DPICS2 sens 2 at 800 DPI
Same CS2 profile at 1600 DPI
1Same 25.9773 cm/360
Choose cm/36040 cm per full turn
CS2 · 800 DPI
1.29886440 cm/360 in the model
Use same-game eDPI320 eDPI in VALORANT
800 DPI
0.440.8214 cm/360
Follow the CS2 → VALORANT example, step by step
  1. Source rotation per inch: 2 × 800 × 0.022 = 35.2 degrees.
  2. Target sensitivity: 35.2 ÷ (800 × 0.07) = 0.6285714286.
  3. Shared modeled distance: 360 ÷ 35.2 × 2.54 = 25.9772727 cm per turn.
  4. Apply a supported precision: 0.629 gives about 25.9596 cm/360, a −0.068% distance change. Verify the physical result in game.

READ THE NUMBERS

cm/360 matches distance. eDPI needs a game scale.

Demo: one turn, different distancesCS2 reference · 800 DPI. Schematic, not a screen ruler.
40 cmsens 1.2989
20 cmsens 2.5977

Both travel distances produce one modeled 360° turn. Halving the distance doubles the setting under the same linear profile.

Equal eDPI can turn different amounts.

At 800 eDPI, the CS2 reference gives 51.9545 cm/360; VALORANT gives 16.3286 cm/360. The yaw values differ.

eDPI
DPI × decimal game sensitivity. Compare inside the same game scale.
cm/360
Calculated mouse travel for one full horizontal turn under the selected yaw model.
Yaw
Degrees turned by one input count at sensitivity 1. This is the profile's scale.

The eDPI definition and same-game limitation explain why eDPI alone cannot convert games.

MEASURE / COMPARE / RETEST

Measure cm/360 and correct your setting.

Use this after a calculation, or on its own when your game isn't listed. You need a trial setting, a desired distance and a repeatable measurement in the same linear hip-fire mode.

  1. Mark a starting point.Use a ruler or tape beside the mouse. Pick a fixed direction or object in game and mark the mouse position.
  2. Make one full horizontal turn.Move the mouse in one direction until the view returns to the same reference. Keep the same hip-fire mode and movement speed.
  3. Repeat before correcting.Measure the mouse travel. If repeated turns differ substantially, check acceleration, mode and the measurement method first.

IF IT DOESN'T FEEL RIGHT

Check which part of the match is wrong.

The physical distance is wrong
Check the active DPI and profile. Repeat a measured turn, then calculate a correction in the same mode.
Only ADS or a scope feels wrong
Use the game's separate ADS or zoom controls. This calculator solves horizontal hip-fire, not scope multipliers.
Distance matches, but motion feels faster
Compare FOV, zoom, acceleration and visual context. Matching cm/360 preserves a turn distance; it cannot guarantee the same perceived speed.
My game isn't in the list
Use Custom only with a documented linear yaw for your exact mode. Otherwise, use the manual measurement and correction path without guessing a coefficient.
I don't know my DPI or best sensitivity
Find the active DPI setting first. Choosing a comfortable sensitivity requires practice and testing; this converter calculates a chosen relationship.

PROFILES / FORMULAS / LIMITS

How this sensitivity calculator works.

The presets below are reference values, not publisher-certified current-game constants. Their disclosed values are retained from the September 28 reference review; this page's arithmetic and new input paths were reviewed on October 15, 2026.

Horizontal linear hip-fire profiles
ProfileYaw at sensitivity 1Evidence and scope
CS2 reference0.022° / countCommunity reference; compare a physical turn.
VALORANT reference0.07° / countCommunity reference; decimal hip-fire setting.
Apex reference0.022° / countCommunity reference; linear hip-fire with acceleration off.
Custom linear yawYour documented valueOnly the mode represented by your value; positivity checks do not verify its source.

The community profile table is a reference, not publisher verification. Check your game after updates. The Aimlabs setup guide explains manual DPI entry and separate ADS/FOV settings.

Calculation formulas and units
Convert games
target sens = source sens × source DPI × source yaw ÷ (target DPI × target yaw)
Calculate cm/360
cm/360 = 914.4 ÷ (DPI × sensitivity × yaw)
Set a target distance
sensitivity = 914.4 ÷ (DPI × yaw × target cm/360)
Use eDPI
eDPI = DPI × sensitivity; sensitivity = eDPI ÷ DPI
Correct a measured turn
new setting = trial setting × measured cm/360 ÷ desired cm/360

The distance formula is 360 degrees × 2.54 cm per inch, divided by degrees turned per inch. Inches/360 = cm/360 ÷ 2.54. Target counts/360 = 360 ÷ (target sensitivity × target yaw).

What happens to your numbers?

Inputs and results are held in this open page. Reset or reload clears them. Copy and .txt download happen only when you choose them; the download stays on your device. Site analytics may count page views, form submissions and link clicks separately. See Privacy for the site's data disclosures.