FPS → Refresh Rate Calculator
Raw FPS means little without the refresh rate context. See how your frame rate matches your monitor, whether frames repeat, and where stutter lives.
On a 144 Hz monitor, 60 FPS shows roughly one new frame per 2.4 refreshes — smooth-looking but effectively 60 Hz. Matching FPS multiples to refresh rate (or capping 2× refresh) gives the cleanest frame pacing.
How it works
The ratio fps ÷ hz shows how many refresh cycles each frame spans:
- <1× — frames repeat multiple times; effective smoothness ≈ fps, not hz.
- 1–1.9× — variable pacing; this band causes the most visible micro-stutter.
- ≥2× — each monitor refresh can get a fresh frame; clean pacing and minimal input lag.
Example
90 FPS on 144 Hz = 0.625× — badly mismatched; frames repeat 1–2 times unpredictably. Bumping to 144 FPS (1.0×) or a stable 288 (2×) would fix the stutter.
The math behind it
ratio = fps ÷ hz · recommend fps ≥ hz, ideally 2× hz
Frequently Asked Questions
Should I cap FPS at 2× refresh?
If you can sustain it, a 2× cap (e.g. 288 on 144 Hz) gives the best frame pacing plus a small input-lag edge. If not, cap exactly at refresh + keeping headroom with V-Sync off is common.
Does screen tearing come from FPS above refresh?
Tearing appears when new frames arrive mid-refresh. V-Sync stops it but adds latency; G-Sync/FreeSync (within the hz window) eliminate tearing without the lag penalty.
Is 1% low FPS in the formula?
Averages hide dips. If your 1% lows (see the FPS counter tool) fall below your monitor hz, you will stutter even with a high average — the verdict above assumes stable FPS.