This Quake to Valorant sensitivity converter takes the sensitivity you use in Quake and returns the Valorant value that produces the same physical turn — the same cm/360 — on the same mouse DPI. Quake runs on a yaw of 0.022 degrees per count and Valorant on 0.07, so the number changes even though your arm movement does not. Example: Quake 1.5 at 800 DPI is 34.64 cm per full turn; the matching Valorant value is 0.47.
1.5 × (0.022 / 0.07) = 0.47. Set Valorant to 0.47 and both games compute to about 34.64 cm per 360.Both games turn your view by a fixed number of degrees for every count the mouse sends, scaled by the sensitivity value you type in. That per-count constant is the yaw: Quake uses 0.022, Valorant uses 0.07. Your DPI stays the same, so the only thing that has to change is the in-game number.
cm/360 = (2.54 × 360) / (DPI × sensitivity × yaw)Quake sens × 0.022 = Valorant sens × 0.07Valorant sens = Quake sens × (0.022 / 0.07) = Quake sens × 0.3143The multiplier is 0.3143, so every Quake value becomes a smaller number in Valorant. The turn itself does not change: Valorant moves more degrees per count, so it needs a smaller multiplier for the same cm/360.
Eight common Quake values, the Valorant value that matches each one, and the shared cm/360 at three DPI settings. Every row is computed with the formula above; the cm/360 columns are the same for both games by construction, because that is the quantity the conversion preserves.
| Quake sens | Valorant sens | cm/360 at 400 DPI | cm/360 at 800 DPI | cm/360 at 1600 DPI |
|---|---|---|---|---|
| 0.8 | 0.25 | 129.89 cm | 64.94 cm | 32.47 cm |
| 1.0 | 0.31 | 103.91 cm | 51.95 cm | 25.98 cm |
| 1.2 | 0.38 | 86.59 cm | 43.30 cm | 21.65 cm |
| 1.5 | 0.47 | 69.27 cm | 34.64 cm | 17.32 cm |
| 1.8 | 0.57 | 57.73 cm | 28.86 cm | 14.43 cm |
| 2.0 | 0.63 | 51.95 cm | 25.98 cm | 12.99 cm |
| 2.5 | 0.79 | 41.56 cm | 20.78 cm | 10.39 cm |
| 3.0 | 0.94 | 34.64 cm | 17.32 cm | 8.66 cm |
Quake Champions gives you direct control over sensitivity as a raw decimal value with no hard upper limit, accessible under Settings > Controls > Mouse. The engine also exposes a Mouse Yaw variable (horizontal coefficient, defaulting to 0.022) and a matching Mouse Pitch for vertical. Most players leave yaw and pitch at defaults and only adjust the main sensitivity number, but the option exists for asymmetric tuning.
FOV in Quake Champions ranges from 80 to 130, and the game is typically played at the higher end of that range. Because the FOV range is significantly wider than most tactical shooters, converting from a game like VALORANT (fixed 103) or Siege (max 90) requires careful FOV-aware calculation. Simply matching cm/360 at different FOVs will feel wrong because the angular size of targets changes dramatically between 90 and 120.
In VALORANT, your aim sensitivity lives under Settings > General > Mouse. The slider labeled Sensitivity: Aim accepts values from 0.1 up to 100 with two-decimal precision, so you can dial in something like 0.35 without rounding issues. VALORANT uses a fixed 103-degree horizontal field of view with no FOV slider at all, which simplifies cross-game conversions because there is no FOV variable to match.
Scoped sensitivity is handled by a separate Scoped Sensitivity Multiplier that scales from 0 to 1. At 1.0 your scoped aim moves at the same speed as hip-fire; lower values slow the reticle while zoomed. When converting from another title, the most common mistake is ignoring this multiplier and only matching the base value. That leaves your Operator or Marshal scope feeling wildly off.
| Game | Setting | Menu range |
|---|---|---|
| Quake | Sensitivity (decimal, no fixed cap); Mouse Yaw default 0.022 | no fixed cap |
| Valorant | Sensitivity: Aim 0.1 - 100 | 0.1 to 100 |
Of the eight Quake values in the table above, 8 convert to a Valorant value inside its menu range. If yours lands outside, keep the cm/360 and move DPI: half the DPI needs double the value, double the DPI needs half.
The reverse direction uses the inverted ratio 0.07 / 0.022 = 3.182. Valorant 0.4 becomes Quake 1.27, and both sit at 40.82 cm/360 at 800 DPI. The Valorant to Quake converter has its own prefilled tool and table.
Keep your DPI the same and multiply your Quake value by 0.022 / 0.07 = 0.3143. Example: Quake 1.5 becomes Valorant 0.47; at 800 DPI both give 34.64 cm per 360-degree turn. The tool above does this and prints both cm/360 values so you can check they match.
No. Quake uses 0.022 and Valorant uses 0.07 degrees per count, so the same number turns your view faster in Valorant: Quake 1.5 at 800 DPI is 34.64 cm/360, while Valorant 1.5 is 10.89 cm/360. The matching Valorant value is 0.47.
There is no hard cap. You can enter any positive decimal. The practical range depends on your DPI and how much mousepad space you have.
Yes, both default to 0.022. If you also match FOV, your cm/360 transfers directly by copying the sensitivity number.
At 130 FOV, more of the world is displayed on screen, so each degree of rotation covers fewer pixels. The actual cm/360 may be identical, but targets move across your screen faster, creating the illusion of higher sensitivity. A FOV-aware converter can compensate for this perceptual difference.
VALORANT locks FOV at 103 degrees. If your source game used a different FOV, the visual speed of camera rotation will feel different even at identical cm/360. Give yourself a few minutes of warm-up to adjust to the visual difference.
Yes. The scoped multiplier only affects zoomed weapons like the Operator and Marshal. If your source game has separate ADS values, convert the zoom sensitivity on its own rather than relying on the base conversion alone.
The in-game slider displays two decimal places, but you can edit the settings config file directly to get finer values. This is useful when a conversion produces a number like 0.3467 that the slider would round.