Category
Gaming Tools & Calculators
Calibrate your mouse tracking across game engines with verified yaw constants. Compute frame display timings in milliseconds and calculate FOV geometry accurately.
Gaming tools here convert the numbers players actually trade: mouse sensitivity (cm/360°), eDPI, FOV across games with different projection math, and frame time at a given refresh rate. Conversions use each game’s yaw constant where it is publicly known, so results match what you experience in-game rather than a generic formula.
Most used in Gaming
All Gaming
Mouse Sensitivity & cm/360 Converter
Convert your exact mouse sensitivity across game engines using verified angular yaw constants with cm/360 rotation metrics.
Field of View (FOV) Converter
Convert between Horizontal and Vertical Field of View across display aspect ratios.
FPS & Refresh Rate Calculator
Calculate exact frame presentation intervals in milliseconds for any framerate (FPS) or Hz.
Screen Resolution & Aspect Ratio Calculator
Analyze display resolutions, calculate lowest-term aspect ratios via GCD, and scale dimensions.
Which tool for which job
- Mouse Sensitivity Converter — moving between games while keeping your muscle memory (same cm/360°).
- eDPI Calculator — comparing setups in games where eDPI (DPI × in-game sensitivity) is the community standard, like CS2.
- FOV Converter — translating a horizontal FOV preference between games that measure vertically or use different aspect ratios.
- Frame Time — seeing that 60 FPS equals 16.67 ms per frame, and why a 144 Hz display rewards consistent frametimes more than peak FPS.
Why cm/360° is the honest metric
Sensitivity sliders are arbitrary per game. The physical distance your mouse travels to turn a full 360° is game-agnostic: if it is 30 cm in one title, matching 30 cm in another reproduces your aim. This is why converters target cm/360° rather than copying slider values. Monitor distance matching for FOV is a related but separate choice — it preserves how large targets appear at screen center.
Common mistakes
- Converting sensitivity without matching the same measurement (horizontal vs vertical FOV) — the aim will feel close but not identical.
- Chasing raw FPS while ignoring 1% lows; a stable 140 FPS beats an unstable 200.
- Assuming eDPI is comparable across games — it is only meaningful within a single game’s own scale.