Mouse Sensitivity Converter
Convert a PC hip-fire setting with visible yaw assumptions, then compare the exact model value with a practical rounded setting.
Model estimate—verify in game. These are community reference models, not verified current game settings. Distances and rounding differences are estimates under the displayed yaw values.
Conditional result
Suggested target setting
at decimals
Model exact value under the shown assumptions:
Assumption and source receipt
Not a game-verification certificate- Source
- Target
- Yaw assumptions
- degrees/count at sensitivity 1
- Conditional formula
= model exact value- Source provenance
- Game verification
- currentGameVerified=falseBuild: none · physicalCheck=not_performed
- eDPI
- Game-specific; not cross-game equivalence
Scope: PC hip-fire linear yaw model. ADS, scope, aim assist, mouse acceleration, controller curves, FOV matching, and console input are excluded.
Check this setting in your game. “Exact” means exact arithmetic under the displayed assumptions—not exact physical matching or better aim.
Automatic copy was blocked. Select and copy this current receipt manually; CSV remains available.
Private calculation: sensitivity, DPI, custom yaw, results, copied text, and CSV stay on your device. They are not placed in URLs, site storage, cookies, requests, analytics, or error reports. Copy uses your system clipboard; Download CSV saves a local file. After this page loads, new inputs continue to calculate and export offline.
A conditional yaw model, not a game calibration
This calculator has two deliberately narrow reference choices. The CS2 community reference assumes 0.022 degrees per count at sensitivity 1, and the VALORANT community reference assumes 0.07. Both are visibly marked unverified in game. They identify the context of a public community record; they are not supported-game badges, current-build measurements, or promises of physical equivalence.
The bundled records point to one immutable public dataset commit, preserve its file checksum and source-check date, and keep currentGameVerified=false, no game build, and physicalCheck=not_performed. A Custom yaw is your own assumption and is never promoted to verified evidence. If a bundled value loses its provenance, is contradicted, or moves beyond its 90-day source-check window, the page disables that reference instead of silently substituting another value.
Formula and the frozen example
For source sensitivity S, source and target DPI Ds and Dt, and assumed yaw values Ys and Yt, the conditional target is S × Ds × Ys ÷ (Dt × Yt). Modelled cm/360 is 360 × 2.54 ÷ (DPI × sensitivity × yaw).
With the CS2 reference at sensitivity 2 and 800 DPI going to the VALORANT reference at 800 DPI, the model exact target is 0.628571428…. At three decimals the suggested setting is 0.629. The modelled source distance is 25.98 cm/360, while the modelled target distance at 0.629 is 25.96 cm/360. The displayed −0.0176997 cm / −0.068135% is only the rounding difference inside this model; real-game calibration error is unknown.
Why the receipt matters
Different converters can show slightly different settings or distances when their yaw assumptions, profile versions, input precision, or rounding conventions differ. A difference alone does not prove that another result is wrong. ToolNeko instead exposes both assumed yaw values, the conditional formula, source version and date, exact model value, suggested input, and the source-versus-rounded-target distance labels.
The copy receipt and CSV preserve the same qualifications. “Exact” means exact arithmetic under the displayed assumptions. It does not mean exact aim feel or physical matching. eDPI is shown for reference but remains game-specific and is not a cross-game equivalence measure.
How to use the result safely
- Choose the source and target reference models, or choose Custom and enter yaw values you understand.
- Enter source sensitivity and both DPI values. Keep the supported scope on PC hip-fire.
- Choose the decimal precision you can practically enter, then convert.
- Read the exact model value, suggested setting, paired modelled distances, and rounding-only difference.
- Try the suggestion in your current game and adjust from there. Do not treat this page as an installed-game inspection or calibration certificate.
Private and browser-only
The two reference records ship with the static page. All decimal parsing, rational arithmetic, copy text, and CSV creation run in your browser; there is no account, backend calculation, game server, remote coefficient lookup, or paid data API. Sensitivity, DPI, custom yaw, formula results, clipboard text, and CSV contents are not sent to ToolNeko or analytics. Once required static assets have loaded, disconnecting the network does not stop a new calculation or local CSV export.
Frequently asked questions
Is the CS2 or VALORANT yaw value verified in the current game?
No. This page labels both choices as unverified community reference models. The bundled 0.022 and 0.07 values are versioned assumptions from a public community dataset, not current-game measurements or publisher-certified settings. Check the suggested setting in your game.
How does the sensitivity conversion work?
The conditional model multiplies source sensitivity, source DPI, and source yaw, then divides by target DPI and target yaw. It also estimates cm/360 from the same disclosed yaw values. Those distances are model calculations, not physical measurements.
Why are exact and suggested sensitivity different?
The model exact value may repeat beyond the decimal places accepted or convenient in a settings field. Suggested precision rounds that value half up. The result shows the modelled source distance, the modelled distance at the rounded suggestion, and their rounding-only difference.
Why can two sensitivity converter sites disagree?
They can use different hidden yaw assumptions, profile versions, input precision, or rounding conventions. ToolNeko shows its two yaw assumptions, immutable source version, formula, exact value, and rounded-value distance separately. That transparency does not prove another site is wrong.
Does matching eDPI mean the games feel the same?
No. eDPI is DPI multiplied by in-game sensitivity and is game-specific. It does not account for different yaw scales, FOV, acceleration, ADS, response curves, input handling, or personal perception.
Can I convert ADS, scopes, controllers, or console sensitivity?
No. This version is limited to a linear PC hip-fire yaw model with acceleration excluded. ADS multipliers, scopes, aim assist, controller curves, FOV matching, nonlinear sliders, and console input need separate evidence and models.
Are my sensitivity and DPI uploaded?
No. Calculation, copy receipt, and CSV creation happen in your browser. Inputs and results are not placed in the URL or site storage and are not sent in requests or analytics. After the static page loads, fresh calculations and CSV exports continue offline.
Sources and method
- Sens Manager — immutable two-value community dataset at commit 332453d
- Sens Manager — conditional DPI/yaw calculation formulas at the same commit
- Valve Half-Life input source — legacy m_yaw context, not current CS2 verification
- unisense — optional physical 360-degree measurement method, not a measurement used here