SENS CONVERTER / GAME SETTINGS

Mouse sensitivity converter.

Get a horizontal hip-fire starting setting, see the exact profile math, then correct it from one measured in-game turn.

“Sens converter” means sensitivity converter. This page keeps calculated cm/360 constant under the selected reference or custom yaw profiles. It does not find your best sensitivity or match ADS, FOV and perceived speed.

CALCULATESHip-fire cm/360 match
SUPPORTSSeparate target DPI
SHOWSRounding error + exact math
DOES NOT CLAIMIdentical feel or optimal aim

CHOOSE A STARTING TASK

One converter, three practical paths.

The same transparent model handles cross-game conversion and a DPI change. A physical turn check can then correct the number you actually entered in the target game.

MEASURED RESULTCorrect a real turnUse observed cm/360

THE CONVERTER

Convert one known setting.

01 From your current game
Use the active mouse profile. Where to find DPI →
02 To your target game
Enter it even when it stays the same.
Mode used by this page

Horizontal, linear, hip-fire rotation. ADS/scopes and acceleration are outside this result.

No mouse detection. Enter the values shown in your mouse software and game.

YOUR RESULT

The setting, evidence and rounding choices appear here.

Nothing has been calculated yet. Load the example or enter your own profile, sensitivity and DPI.

VERIFY AND CORRECT

Measured a different turn distance?

Use one slow, repeatable 360° turn in the target game's same hip-fire mode. The correction works from your measurement, so it can recover from profile drift, actual CPI difference or target rounding.

1

Mark the mouse start point and an in-game direction.

2

Move slowly until the view completes one full 360° turn.

3

Measure the mouse travel and enter it below. Repeat to confirm.

PROFILE LEDGER

The preset values are visible—and editable through Custom.

These are reference profiles reviewed on 2026-09-28, not publisher-certified current-game constants. They agree with the cited community table and the operated converter examples; verify in game when precision matters.

ProfileYaw usedScopeEvidence status
CS2 reference0.022° / count at sens 1Horizontal linear hip-fireCommunity reference + live converter agreement; publisher/version unverified
VALORANT reference0.07° / count at sens 1Horizontal linear hip-fireCommunity reference + live converter agreement; publisher/version unverified
Apex Legends reference0.022° / count at sens 1Horizontal linear hip-fire; acceleration offCommunity reference + live converter agreement; publisher/version unverified
Custom linear yawValue you enterOnly the mode represented by that valueUser-supplied; this page checks positivity, not provenance

READ THE OUTPUT

What each number can—and cannot—tell you.

CM/360

Physical turn distance

Calculated centimeters of mouse travel for one horizontal 360° turn under the chosen model. It is the cross-profile matching basis used here.

EDPI

Useful inside one game scale

DPI × in-game sensitivity. Equal eDPI across profiles with different yaw values does not mean equal cm/360.

COUNTS/360

Input counts for a full turn

360 ÷ (sensitivity × yaw). DPI converts those counts into a theoretical physical distance.

FEEL

Not guaranteed by one distance

FOV, ADS/zoom, acceleration, frame behavior and game pacing can make equal hip-fire cm/360 feel different.

WHEN THE RESULT DOES NOT FEEL RIGHT

Check the cause before changing random settings.

Turn distance is measurably wrong

Use the correction above.

Keep the same target mode and trial setting, measure cm/360, calculate the correction, then repeat.

Correct a measured result ↑
Only ADS or a scope is wrong

Use the game's mode-specific controls.

Do not alter the hip-fire result to fix a separate zoom multiplier. This version does not convert ADS.

Distance matches but feels faster

Compare FOV and visual context.

Equal physical rotation does not equal equal monitor-distance motion or perception. Decide which matching method the task needs.

You want the best sensitivity

Use practice and performance evidence.

A converter preserves a chosen relationship. It cannot decide the setting that best fits your aim, desk space or play style.

METHOD, SOURCES AND DATA

Treat the first number as a transparent starting point.

Target sensitivity = source sensitivity × source DPI × source yaw ÷ (target DPI × target yaw). cm/360 = 914.4 ÷ (DPI × sensitivity × yaw). The correction uses trial setting × observed distance ÷ desired distance. All require a positive linear relationship in the exact mode being tested.

The three presets use the reference values shown above. They are not game-publisher certified; game updates, actual mouse CPI, custom yaw, acceleration, ADS/scopes and FOV/perception can change the practical result. Unsupported games are not guessed—use Custom only with a documented value, or measure and correct manually.

Inputs and the current result stay in this open page. Editing an input clears the result; reload clears everything. Copy occurs only when you press Copy result. No account or mouse access is used by this page.

Sources and cross-checks: Aimlabs conversion and verification guide · EA Apex settings/test guidance · community profile table. Live arithmetic was cross-checked against Aimlabs, sensitivityconverter.com and siutil; agreement does not turn the presets into official constants.