FPS to Frame Time Calculator

How this is calculated

FRAME TIME IS THE HONEST UNIT AND FPS IS THE MISLEADING ONE. Frame rate is frames per second; frame time is milliseconds per frame, and they are reciprocals - 1000 divided by one gives the other. That reciprocal relationship is why equal-sounding FPS gains are worth wildly different amounts. ⚠️ THE SAME +30 FPS IS NOT THE SAME UPGRADE. Going from 30 to 60 fps cuts frame time from 33.3 ms to 16.7 ms - a saving of 16.7 ms per frame. Going from 120 to 150 cuts it from 8.3 ms to 6.7 ms, a saving of 1.7 ms. Identical on the FPS counter, and the first is ten times the improvement. This is the single most useful thing frame time tells you, and it is invisible in the unit most benchmarks report. THAT IS ALSO WHY DIMINISHING RETURNS ARE REAL RATHER THAN IMAGINED. Every doubling of frame rate halves frame time, so the absolute gain shrinks with each step: 30 to 60 saves 16.7 ms, 60 to 120 saves 8.3 ms, 120 to 240 saves 4.2 ms. Whether the last of those is worth anything to you is a judgement, but the shrinking is arithmetic. ⚠️ AVERAGE FPS HIDES STUTTER, AND STUTTER IS WHAT YOU FEEL. A game averaging 60 fps with 1% lows at 30 delivers occasional frames taking twice as long as normal, and that inconsistency reads as worse than a steady lower frame rate. Putting the lows in milliseconds shows the size of the hitch directly - a jump from 16.7 ms to 33.3 ms is a 16.7 ms pause, which is well above the threshold at which people notice something went wrong. Chasing a higher average while the lows stay bad is a common and unsatisfying way to spend money. REFRESH RATE IS A SEPARATE CEILING. A display shows a new image at its own fixed rate, so frames rendered beyond it are not displayed as extra motion - though they can still reduce input latency slightly, which is why competitive players run above their refresh rate deliberately. The frames-per-refresh figure shows where you sit relative to the panel. THIS IS ARITHMETIC, NOT A BENCHMARK. It converts between units and compares them. What frame rate you get from a given setting, resolution or hardware combination is a measurement, and only your own machine running your own game can tell you that.

Common questions

Why does frame time matter more than FPS?

Because frame rate and frame time are reciprocals, so equal-sounding FPS gains are worth wildly different amounts. Going from 30 to 60 fps saves 16.7 milliseconds per frame. Going from 120 to 150 fps - the same +30 on the counter - saves 1.7 milliseconds. The first is ten times the improvement, and nothing about the FPS numbers tells you that. Frame time is linear in the thing you actually perceive, which is how long you wait for the next image, so it is the unit that makes two upgrades comparable.

So are diminishing returns real or just an excuse?

Entirely real, and they are arithmetic rather than opinion. Every doubling of frame rate halves frame time, so each doubling delivers half the absolute saving of the one before: 30 to 60 saves 16.7 ms, 60 to 120 saves 8.3 ms, 120 to 240 saves 4.2 ms. Whether 4.2 ms is worth money to you is a genuine judgement and depends on what you play - competitive shooters are a different case from single-player games. But the shrinking itself is not a matter of opinion, and it is why the jump from 30 to 60 changes an experience while the jump from 200 to 240 mostly changes a number.

What do the 1% lows actually tell me?

How bad it gets, and that is usually what you feel rather than the average. A game averaging 60 fps with 1% lows at 45 is delivering occasional frames that take 22.2 ms against a normal 16.7 - a 5.6 ms hitch. Put the lows at 30 instead and those frames take 33.3 ms, doubling the normal frame time, which reads as a stutter rather than a slightly slower moment. Inconsistency is more noticeable than a lower steady rate, which is why a locked 60 often feels better than an unlocked 80 that dips.

Should I aim for frames beyond my refresh rate?

It depends what you play. A display shows a new image at its own fixed rate, so frames rendered beyond that are not displayed as extra motion - the frames-per-refresh figure shows where you sit. But rendering faster does slightly reduce input latency, because the frame being shown is more recent, and that is why competitive players deliberately run well above their panel's refresh. For single-player games the usual better answer is to cap slightly below your refresh and spend the headroom on settings or on frame time consistency.

What is the monitor's frame budget for?

It is how long the panel gives each frame, and it is the deadline your machine is trying to meet. A 144 Hz display refreshes every 6.94 ms, so a frame taking longer than that misses its slot. Comparing your frame time against that budget tells you immediately whether you are filling the panel: under it and you are, over it and you are not, regardless of what the average FPS suggests. It is also the figure that makes variable refresh rate technologies easier to reason about, since their job is to move the deadline to meet your frames rather than the other way round.

Does this tell me what settings to use?

No - it converts between units and compares them, which is arithmetic. What frame rate you get from a given combination of settings, resolution and hardware is a measurement, and only your own machine running your own game can produce it. The useful workflow is to measure first with an overlay that reports averages and 1% lows, then bring those numbers here to work out what a change is actually worth before spending time or money on it.

My frame rate is above my refresh but it still feels bad. Why?

Almost always the lows rather than the average. A high average with poor 1% lows means frames are arriving unevenly, and uneven delivery reads as worse than a lower steady rate - the eye notices the change more than the level. Put your lows into this tool and look at the hitch size in milliseconds: anything approaching the length of a normal frame is a visible stutter. Fixing consistency, by capping the frame rate or reducing a setting that spikes, often improves the experience more than adding average frames.

Take it further with AI

Copy this into ChatGPT or Claude with your own numbers filled in. It hands over the figures this calculator worked out, so the answer is built on real arithmetic instead of a guess.

I used the FPS to Frame Time Calculator at https://www.bfcbrilliance.com/tools/fps-frame-time-calculator.

What I entered:
- Your frame rate now (fps): ___
- Frame rate you are aiming at (fps): ___
- Your 1% low (fps): ___
- Monitor refresh rate (Hz): ___

What it calculated:
- Frame time now: ___
- Frame time at your target: ___
- What the upgrade actually saves: ___
- Frame time on your worst frames: ___
- How long a bad frame hangs for: ___

Use those figures as given — they are already worked out, so please don't recalculate or estimate your own. Help me turn them into a plan: what to buy or do, in what order, roughly what it should cost, and the mistakes people most often make with this job.

More screens & media tools