Skip to tool content
Toolioz logoToolioz

Mouse Sensitivity Converter with eDPI

A mouse sensitivity converter with eDPI matches hipfire turn speed between FPS games by comparing yaw constants. CS2, Valorant, Apex, Overwatch 2, Fortnite, Siege, and Warzone use fixed yaw values, so the conversion does not change when a patch ships new weapons.

Quick Summary & Direct Answer
FPS

How is mouse sensitivity converted between games?

Hipfire sensitivity in the destination game is source sensitivity × (source yaw / destination yaw) × (source DPI / destination DPI). eDPI is sensitivity × DPI. cm/360 uses the source yaw so the physical mouse distance for a full turn stays matched.

Key Takeaways

  • Same DPI: multiply by source yaw divided by destination yaw.
  • eDPI = sensitivity × DPI. It is not comparable across games unless yaw also matches.
  • cm/360 is the figure that should match when the conversion is correct.
  • ADS, zoom, and relative-aim sliders are not part of hipfire yaw.

Scoped zoom uses zoom_sensitivity_ratio_mouse and is not part of this hipfire conversion. ADS and scoped rifles use a separate multiplier in settings. This page converts hipfire only.

Valorant sensitivity

0.47143

Factor0.314286
Source eDPI1200
Dest eDPI377
cm / 360°34.64

CS2 to Valorant sens and other game pair pages

Each pair page locks one yaw ratio and shows a worked eDPI example. The main converter above accepts any two games from the table.

Frequently asked questions

Hipfire conversion multiplies the source sensitivity by (source yaw / destination yaw) and by (source DPI / destination DPI). eDPI is sensitivity times DPI. cm/360 is 360 / (yaw × sensitivity × DPI) × 2.54.

Publisher notes · reviewed 29 October 2026

Hipfire conversion is a yaw ratio, not a copied sensitivity number

Each FPS stores a yaw constant: degrees turned per mouse count at sensitivity 1. Matching turn speed is source sensitivity × (source yaw / destination yaw) × (source DPI / destination DPI). eDPI is sensitivity × DPI and is only comparable inside one yaw. cm/360 is the figure that should match across games.

Why CS2 to Valorant sens is about 0.314

CS2 and CS:GO use Source m_yaw 0.022. Valorant uses 0.07. 0.022 / 0.07 ≈ 0.314286. CS2 1.5 at 800 DPI is Valorant 0.47143 at 800 DPI, eDPI 1,200, about 34.6 cm per 360°. Pair pages lock one ratio so a search such as CS2 to Valorant sens lands on a worked example instead of a generic two-dropdown tool.

Apex hipfire uses the same 0.022 yaw as CS2, so Apex 1.0 matches CS2 1.0. Apex ADS optics are extra sliders. Overwatch 2 and modern Call of Duty hipfire use 0.0066. Fortnite uses 0.005555…. Rainbow Six Siege uses 0.00572958. Those constants are engine yaw, not a patch note.

Worked examples

  • Same cm/360, different numbers

    Valorant 0.5 at 800 DPI is CS2 1.59091 at 800 DPI. Both are about 32.7 cm/360. The larger CS2 number is the smaller yaw, not a faster swipe.

Limits of this page

  • ADS, zoom, relative aim, and scoped ratios are not converted.
  • FOV and aspect-ratio differences can still make two matched cm/360 settings feel slightly unlike.

Sources