Frame Time Calculator

Frequently Asked Questions

How is frame time related to FPS?

Frame time (ms) = 1000 ÷ FPS. 60 FPS is 16.67 ms per frame, 120 FPS is 8.33 ms, 144 FPS is about 6.94 ms. It is the time budget to render one frame.

What is my frame budget for a target FPS?

The budget is the target frame time: to hold 60 FPS every frame must finish within 16.67 ms (CPU + GPU + present). Exceeding it on any frame causes a stutter or dropped frame.

Why watch frame time instead of average FPS?

Average FPS hides stutter. A game averaging 60 FPS with occasional 40 ms spikes feels janky. Consistent frame times (low 1% lows) matter more than a high average number.

What frame time targets common refresh rates?

Match the monitor: 60 Hz = 16.67 ms, 120 Hz = 8.33 ms, 165 Hz ≈ 6.06 ms, 240 Hz ≈ 4.17 ms. Staying under the panel's refresh interval keeps motion smooth and tear-free with sync on.

Provided by AllCalculators.io
Free online calculators for everyday. No registration required.

Estimates for informational purposes only.

Important Disclaimer: Estimates for informational purposes only.

This calculator provides estimates for informational purposes only. Results are based on assumptions and may not reflect actual outcomes. Consult qualified professionals in relevant fields before making important decisions based on these results.

JavaScript is required to use the interactive calculator above. The questions and answers below remain readable without JavaScript.

How This Calculator Works

Frame rate (FPS) and frame time are two views of the same thing. FPS is how many frames render each second; frame time is how many milliseconds each individual frame takes, and it is the more useful number for diagnosing stutter because the human eye notices an inconsistent spacing of frames far more than a slightly lower average. The relationship is a simple reciprocal: frame time (ms) = 1000 ÷ FPS, and inversely FPS = 1000 ÷ frame time. This tool converts either way, compares your frame time against the budget set by a target FPS, and counts how many frames you render over a chosen duration - handy for capture, benchmarking, and tuning a monitor refresh rate.

Formula / Method

frame time_ms = 1000 ÷ FPS. FPS = 1000 ÷ frame time_ms. The per-frame budget for a target rate is 1000 ÷ targetFPS; if your actual frame time is at or below that budget you sustain the target, and the difference (budget − actual) is your headroom in milliseconds. Frames over a duration = FPS × duration in seconds. These are exact because the conversion is purely a reciprocal; what they cannot capture is frame-to-frame variance, which is why a 100 FPS average with occasional 50 ms spikes feels worse than a steady 80 FPS.

Worked Example

At 144 FPS each frame takes 1000 ÷ 144 ≈ 6.94 ms. Targeting 60 FPS gives a budget of 1000 ÷ 60 ≈ 16.67 ms, so you have 16.67 − 6.94 ≈ 9.73 ms of headroom and comfortably meet the target. Over a 10-second clip you render 144 × 10 = 1,440 frames. If instead your frame time were 20 ms (50 FPS) against the same 60 FPS target, the budget difference would be 16.67 − 20 = −3.33 ms - negative, meaning you miss the target and the game runs below 60.

Common Mistakes

Judging smoothness by average FPS alone - 1% and 0.1% low frame times reveal stutter that the average hides.

Confusing frame time with input lag; frame time is one component, but display, USB polling, and render-queue latency add more.

Assuming a 144 Hz monitor shows 144 FPS - the GPU must actually produce frames that fast, and excess frames are dropped without sync.

Forgetting that V-Sync caps FPS to refresh and can double frame time when a frame just misses the scan-out window.

Comparing frame times across resolutions or settings without noting them - the number is only meaningful with context.

Tips & FAQ

Why does my game feel choppy at high FPS? Almost always frame-time variance: a high average with periodic spikes produces visible hitching, so watch the frame-time graph and the 1% / 0.1% lows, not just the FPS counter - a steady 90 FPS line is smoother than a 140 FPS average that repeatedly dips to 40. What frame time should I aim for? Match it to your monitor - 16.7 ms for 60 Hz, 6.94 ms for 144 Hz, 4.17 ms for 240 Hz - and keep it consistently below that budget rather than chasing a higher peak that your panel cannot display anyway. Does more FPS than my refresh rate help? With a variable-refresh display it does little once you exceed the range; on a fixed-refresh panel extra frames are discarded, though uncapped rendering can still shave a little input latency by always presenting the freshest frame. Should I cap my frame rate? A cap a few frames below your refresh ceiling keeps variable-refresh sync engaged and stops the GPU running hot for frames you never see, which often produces a smoother, cooler, quieter experience than an uncapped number. How many frames will I capture? Multiply FPS by the recording length - useful for estimating file size and editing timelines before you hit record, since a 60-second 60 FPS clip is 3,600 frames to scrub through. Is frame time the same as input lag? No - it is one ingredient; total latency also includes peripheral polling, the render queue, and display scan-out, which is why a separate ping-and-tickrate breakdown is worth checking for online play.

Frequently Asked Questions

Related Gaming Calculators