Sensitivity Converter

Sensitivity Converter

A free game sensitivity converter for CS2, VALORANT, Fortnite, Apex Legends and Overwatch 2. Convert your mouse aim sensitivity, match cm/360 and adjust for a new DPI.

Different game.
Familiar movement.

Convert your mouse sensitivity

From Current setupExample
Source game

Default m_yaw, hipfire. Use an override if you changed m_yaw.

To New setup
Target game
Your sensitivityLive result
0.31429
Same physical turn distance
Target cm / 360°
51.955cm
Target in / 360°
20.455in
Target eDPI
251.429DPI × sens

Apply to VAL hipfire. Hipfire reference scale 0.07. Some tools use 0.06996; verify in your game. See the instructions below for the field and rounding.

Where to enter this result in VAL

Sensitivity: Aim — Settings → General → Mouse. Enter the result as a number, not a percentage.

Scoped Sensitivity Multiplier and ADS Sensitivity Multiplier are separate settings.

The sensitivity converter display precision is not a guarantee of the game’s accepted precision. Apply your setting, reopen the menu, then enter the number it retained below.

At 0.31429: 51.95384 cm/360 · distance error -0.00136% against the exact result.

A positive distance error means a slower turn. This checks rounding, not measurement accuracy.
Profile evidence & version status

Check the range and precision retained by your game.

Reference recorded 2026-10-14. Current game version and physical turn have not been independently verified by this site.

Read the reference ↗
ADS / scope: match a measured turn distance

This sensitivity converter helper uses your own measurements for one optic. Keep DPI, hipfire sensitivity, FOV and optic unchanged. Measure a full 360° while fully scoped in, away from zoom transitions. All distances below use centimeters.

Enter positive finite settings and distances.

Use only where the ADS setting scales angular speed proportionally. Test this by doubling the setting: turn distance should halve. Capped, nonlinear or FOV-dependent responses need another measurement. Apply in game and remeasure; repeat for each optic. This estimate is independent of saved/shared converter settings and does not automatically set a game-specific ADS profile.

Physical turn distance51.95 cm in your source game
5 cm · faster turn100 cm · slower turn
Advanced matching & custom yawFOV · coefficients · reverse input
FOV conversion & measured-game calibration

Convert your FOV convention

Use a perspective camera model to translate vertical, diagonal or 4:3-based menu values into actual horizontal degrees.

Horizontal 106.2602°
Vertical 73.7398° · Diagonal 113.65618°

Applying a value enables horizontal monitor matching. Aspect ratio describes the rendered view, including any letterboxing. Camera reference ↗

Calibrate an unlisted linear scale

Measure one complete turn at a known sensitivity and DPI. The sensitivity converter can derive the yaw instead of guessing a game factor.

Measured yaw 0.022°/count

yaw = 914.4 ÷ (sensitivity × DPI × cm/360). Repeat at another sensitivity to check linearity. A single measurement does not establish a nonlinear game's curve or automatic ADS rule.

0.0220000 ° / count

Profile reference ↗

0.0700000 ° / count

Profile reference ↗

Profiles describe linear PC hipfire scales. FOV-dependent and nonlinear sliders require a measured custom yaw for the exact setup. eDPI compares values within the same game, not across games.

See your calculation Full precision · every input

Source: Counter-Strike 2, sensitivity 1, 800 DPI, yaw 0.022. Target: VALORANT, 800 DPI, yaw 0.07.

Target sens = source sens × source yaw × source DPI ÷ (target yaw × target DPI) × matching factor

1 × 0.022 × 800 ÷ (0.07 × 800) × 1 = 0.3142857142857142

Source cm/360 = 914.4 ÷ (1 × 0.022 × 800) = 51.95454545454546. Target cm/360 = 51.95454545454546. Inches = cm ÷ 2.54.

Source eDPI: 800. Target eDPI: 251.4285714285714. Source counts/360: 16363.636363636364. Target counts/360: 16363.636363636364. Display rounding never changes the calculation.

Save a profile ↓

Settings are saved in this browser. Share links include your setup. File exports send the selected values to this site to generate a download. How your data is handled

Sensitivity Converter report

SENSITIVITY CONVERTER

Counter-Strike 2 → VALORANT
Mode: sens; matching: rotation
Source input: 1
Source sensitivity: 1
Source DPI: 800
Target DPI: 800
Source yaw: 0.022
Target yaw: 0.07
Target sensitivity (full precision): 0.3142857142857142
Source cm/360: 51.95454545454546
Target cm/360: 51.95454545454546
Target inches/360: 20.454545454545457
Source eDPI: 800
Target eDPI: 251.4285714285714
Matching factor: 1

Formula: target sens = source sens × source yaw × source DPI ÷ (target yaw × target DPI) × matching factor
Substitution: 1 × 0.022 × 800 ÷ (0.07 × 800) × 1

Linear PC mouse reference profiles. Check the selected profile notes and verify the result in your game. No controller, automatic ADS or acceleration conversion.
POPULAR PAIRS
Practice rangePut your settings to the test.

Try a 60-second FPS practice check, compare rounds, and refine your setup.

Compare games

Reference hipfire values at your target DPI. This table always uses 360° matching.

GameSensitivityAction
Counter-Strike 21
VALORANT0.31429
Apex Legends1
Overwatch 23.33333
Fortnite3.9604
Call of Duty / Warzone3.33333
Counter-Strike: Global Offensive1
Team Fortress 21
Quake Live / Quake III1
Quake Champions1
Titanfall 21
Garry's Mod1
Left 4 Dead 21
KovaaK's (Quake/Source profile)1
Diabotical1.32
Reflex Arena3.83972
Rainbow Six Siege (default multiplier)3.83972

Saved setups

Save up to 20 profiles on this device. No account or cloud sync.

Your saved setups will appear here.

JSON files · up to 50 KB

Restore from pasted backup
Know what you’re matching.

These are documented reference scales, not direct measurements of your game. Use the source links, check your settings, and verify a full turn on your mousepad.

Understand the formula ↗

Guide updated .

How to use the sensitivity converter

Enter your current setup

Choose both games and enter your source sensitivity and actual DPI. The sensitivity converter updates immediately; set target DPI separately when changing mouse settings.

Apply and verify your result

Copy the sensitivity converter result into the target hipfire field. Reopen the game settings to check rounding, then verify one full turn on your mousepad.

Start from a measured distance

Select cm/360 or in/360 to start from a measured turn distance. The sensitivity converter calculates the corresponding setting using your target profile and DPI.

Games supported by the sensitivity converter

This free mouse sensitivity converter includes 17 named reference profiles plus a measured-yaw custom option. Available profiles: Counter-Strike 2, VALORANT, Apex Legends, Overwatch 2, Fortnite, Call of Duty / Warzone, Counter-Strike: Global Offensive, Team Fortress 2, Quake Live / Quake III, Quake Champions, Titanfall 2, Garry's Mod, Left 4 Dead 2, KovaaK's (Quake/Source profile), Diabotical, Reflex Arena, Rainbow Six Siege (default multiplier). Check each sensitivity converter profile’s assumptions before using the result.

CS2 and VALORANT sensitivity converter

The CS2 sensitivity converter assumes default m_yaw 0.022; VALORANT uses 0.07. Enter each setup’s DPI and use Swap to check the reverse direction.

Fortnite sensitivity converter inputs

Enter 4 for a displayed 4%, not 0.04. The Fortnite sensitivity converter covers PC mouse hipfire; building multipliers, controller input and weapon-specific ADS are separate.

Apex and Overwatch 2 sensitivity converter

Use the Apex sensitivity converter for default hipfire or choose Overwatch 2 as either game. Compare cm/360: equal eDPI across these scales does not mean equal movement.

Rainbow Six Siege sensitivity converter

The Siege sensitivity converter assumes MouseSensitivityMultiplierUnit 0.02 and an integer horizontal slider from 1–100. Check rounding; a modified multiplier requires a yaw override.

Call of Duty / Warzone sensitivity converter

Choose the listed PC hipfire reference in the sensitivity converter. Verify it against your installed game; this profile does not cover every release, ADS mode or input curve.

KovaaK’s sensitivity converter profile

Select Quake/Source in KovaaK’s before applying the sensitivity converter result. Other named profiles include CS:GO, TF2, Titanfall 2 and Quake; shared engines do not establish unlisted support.

Sensitivity converter formulas: DPI, eDPI and cm/360

Understand yaw and physical turn distance

Yaw measures degrees per mouse count at sensitivity 1. The sensitivity converter combines yaw, sensitivity and DPI to match rotation; displayed decimals do not change internal precision.

Sensitivity converter reference equations

s₂ = s₁ × y₁ × DPI₁ ÷ (y₂ × DPI₂)

cm/360 = 914.4 ÷ (s × y × DPI)

s = 914.4 ÷ (cm/360 × y × DPI)

in/360 = cm/360 ÷ 2.54 · eDPI = s × DPI

Sensitivity converter calibration and ADS equations

measured yaw = 914.4 ÷ (s × DPI × measured cm/360)

new ADS = current ADS × measured scoped cm/360 ÷ desired cm/360

Repeat yaw measurements to check consistency. The ADS estimate assumes proportional response with unchanged DPI, hipfire and optic. For example, a multiplier of 1 at 80 cm/360 becomes 2 for 40 cm/360. Apply it in game and remeasure.

Sensitivity converter monitor-distance factor

factor = atan(p × tan(FOV₂/2)) ÷ atan(p × tan(FOV₁/2))

Multiply s₂ by this factor for horizontal screen matching. p is the match percentage divided by 100. At p = 0 use tan(FOV₂/2) ÷ tan(FOV₁/2). Use radians inside trigonometric functions; inputs are horizontal degrees. y is degrees per count at sensitivity 1. These equations assume linear mouse input without acceleration.

Sensitivity converter worked examples

CS2 to VALORANT sensitivity converter example

At 800 DPI, the sensitivity converter maps CS2 1 to VALORANT 0.3142857143: 1 × 0.022 ÷ 0.07. Both measure 51.9545 cm/360. Target DPI 1600 halves the result.

VALORANT to CS2 sensitivity converter example

At 800 DPI, the sensitivity converter maps VALORANT 0.35 to CS2 1.1136363636, or 46.6531 cm/360. Doubling only source DPI doubles the CS2 result to 2.2272727273.

Fortnite sensitivity converter example

At 800 DPI, the sensitivity converter maps Fortnite 4% to Overwatch 2 3.3666666667 or Apex 1.01. Each corresponds to 51.4401 cm/360. Enter 4 as the source.

Overwatch to Apex sensitivity converter example

At 800 DPI, the sensitivity converter maps Overwatch 2 sensitivity 5 to Apex 1.5: 5 × 0.0066 ÷ 0.022. Both give approximately 34.6364 cm/360.

DPI sensitivity converter example

Select CS2 on both sides. The DPI sensitivity converter maps 1.2 at 800 DPI to 0.6 at 1600 DPI, preserving 960 eDPI and 43.2955 cm/360.

Distance-based sensitivity converter example

Enter 40 cm/360. With Quake/Source yaw 0.022, the sensitivity converter returns 1.2988636364 at 800 DPI, or 0.6494318182 at 1600 DPI.

Choose your sensitivity converter matching method

Rotation-based sensitivity converter matching

Use the sensitivity converter’s rotation mode to preserve a full turn’s physical distance. FOV, movement and frame timing can still change how aiming feels.

FOV-aware sensitivity converter matching

The sensitivity converter’s horizontal monitor mode matches near the crosshair at 0% or the screen edge at 100%. Enter actual horizontal FOV; different FOVs change cm/360.

Measured ADS in the sensitivity converter

Enter your current ADS multiplier, measured scoped cm/360 and desired distance. The sensitivity converter estimates a proportional adjustment. Keep DPI, hipfire and optic unchanged, then remeasure.

Sensitivity converter profiles and verification

Check the reference scale

Sensitivity Converter includes 17 named profiles and a custom option. These are documented coefficients, not measurements of your installation. Follow the references and check your game settings.

Check the value your game retains

The sensitivity converter’s retained-value helper reports distance error after rounding. Check your exact mode: KovaaK’s uses Quake/Source, while Siege assumes its default multiplier and integer slider.

Calibrate an unlisted linear game

Measure a full turn at known sensitivity and DPI. The sensitivity converter derives yaw; repeat at another sensitivity to check linearity. One measurement cannot characterize a nonlinear curve.

Save and share your sensitivity converter setup

Keep your settings

Sensitivity Converter saves up to 20 named profiles locally. Rename, update or export a JSON backup. Share links restore inputs on another device; profiles do not sync automatically.

Take the calculation with you

Download the sensitivity converter report as TXT or print it. CSV comparisons always use rotation matching. File exports send selected values to this site to generate attachments.

Try the practice range

Open the sensitivity converter’s practice range for precision, tracking, switching and turns. Trials affect the conversion only when applied. Round comparisons last for this page session; verify physical movement in game.

A FEW THINGS WORTH CHECKING

Sensitivity converter questions

How does the sensitivity converter match VALORANT to CS2?

At equal DPI, the sensitivity converter multiplies by 0.07 ÷ 0.022: VALORANT 0.35 becomes CS2 1.1136363636. Enter both DPI values if they differ.

Can the sensitivity converter handle 800 to 1600 DPI?

Yes. Within one linear game profile, the sensitivity converter halves sensitivity when DPI doubles: 1.2 at 800 DPI becomes 0.6 at 1600 DPI.

Why can a sensitivity converter result feel different?

A sensitivity converter matches a chosen measurement. Equal cm/360 does not preserve FOV, zoom, recoil or frame timing; verify the result in your game.

Will this aim sensitivity converter preserve my aim?

The aim sensitivity converter provides a repeatable starting point, not identical gameplay. Check your DPI, input settings and FOV before adjusting the result.

Does the sensitivity converter change mouse DPI?

No. Set DPI in your mouse software. The sensitivity converter uses the value you enter to calculate the required in-game setting.

Why might another sensitivity converter give a different answer?

Compare coefficients and rounding. This sensitivity converter uses VALORANT yaw 0.07; some tools use 0.06996. Different reference assumptions produce different answers.

Can I use the sensitivity converter for ADS?

The sensitivity converter includes a measured-distance ADS helper. It estimates proportional adjustments for one optic; it cannot automatically translate every weapon or zoom multiplier.

Is this a controller sensitivity converter?

No. This PC mouse sensitivity converter does not model analog-stick dead zones, acceleration or response curves. Controller settings have no universal mouse conversion ratio.

Where does Sensitivity Converter save my settings?

Sensitivity Converter stores settings, favorites and profiles in this browser. There is no cloud sync. Download a backup before clearing browser data.

How accurate is the sensitivity converter?

The sensitivity converter retains full calculation precision. Real accuracy depends on DPI, yaw and game settings. Check the value your game retains after rounding.

Can the sensitivity converter handle an unlisted game?

Choose the custom option in the sensitivity converter only after measuring a linear yaw for your setup. An arbitrary coefficient cannot establish accurate support.

Sensitivity converter sources and assumptions

Sensitivity converter profiles were reviewed on October 14, 2026. Game coefficients are documented reference values from original engine code and aim-training developers, not direct measurements made by this site. Follow the profile link in the tool for scope; verify the value against your current game.