Splitgate to Aiming.Pro sensitivity converter
Convert your Splitgate sensitivity to Aiming.Pro instantly. Same hand motion, perfect muscle memory across both games.
Why Splitgate sens doesn't match Aiming.Pro
At 0.4 sens on 800 DPI, Splitgate sweeps 40.82 cm across a full 360°. To reproduce that exact arm motion in Aiming.Pro, you need sens 1.2727 — about 3.18× your Splitgate number. Nothing changed except Aiming.Pro's yaw of 0.022 vs Splitgate's 0.07; the centimeters of mouse travel stay the same.
- Splitgate · Yaw
- 0.07
- Aiming.Pro · Yaw
- 0.022
- Splitgate · Default FOV
- 90
- Aiming.Pro · Default FOV
- 103
How to apply the converted sensitivity in Aiming.Pro
Open Aiming.Pro's settings, paste the converted sensitivity into the sens field and keep your 800 DPI if that matches how you play Splitgate. Run a 360° check on a practice map: the mouse sweep should cover roughly 40.82 cm on your pad — the same distance as in Splitgate. Only start tuning if the sweep feels off, never before the 360° check.
Common mistakes when converting Splitgate to Aiming.Pro
- Copying the sens without matching DPI
A converted Splitgate-to-Aiming.Pro number is tied to the DPI you used during conversion. If your Aiming.Pro mouse profile runs a different DPI, the math no longer holds — use Sens Converter's 'different DPI' toggle instead of eyeballing.
- Trusting eDPI across engines
Matching eDPI between Splitgate and Aiming.Pro does not give matching turn speed, because their yaws are 0.07 and 0.022. Always compare cm/360° (or in/360°), not eDPI, when swapping games.
- Ignoring scoped and ADS overrides
Splitgate and Aiming.Pro each apply their own scoped / ADS multiplier on top of the base sensitivity. Converting the base is step one — confirm the per-zoom multiplier in Aiming.Pro separately, otherwise scoped aim will feel wrong even with a perfect hipfire match.
Splitgate → Aiming.Pro FAQ
Why is my converted Aiming.Pro sens different from my Splitgate number?+
Aiming.Pro has a yaw of 0.022 compared to Splitgate's 0.07. Their ratio is about 3.18×, so Sens Converter multiplies your Splitgate sens by that factor to keep cm/360° identical. The raw number looks different, but the arm motion is the same.
Should I keep the same DPI in Splitgate and Aiming.Pro?+
Yes, when possible. Keeping DPI identical means only the in-game multiplier changes, which is the cleanest switch. If you run different DPI in Aiming.Pro, enable 'different DPI' in the converter and it absorbs the extra math.
How many decimals should I use in Aiming.Pro?+
Aiming.Pro accepts at least 3 decimals; 4-6 is common. Sens Converter outputs enough precision that rounding to 3 decimals keeps the 360° error below one millimetre on a typical 800 DPI setup.
Does FOV affect Splitgate to Aiming.Pro conversion?+
For the base sensitivity, no — sens is independent of FOV in both engines. If you use a 0% MonitorDistance or similar scaling mode in either game, convert at the FOV you actually run in-game.