Frame Rate Calculator

This frame rate calculator works the four directions of the same triangle: frames per second from a frame count and a duration, frame time in milliseconds from an FPS value, total frames from a rate and a duration, and duration from a frame count and a rate. It is a video and animation tool first, with gaming, streaming, broadcast and VR readings built into its performance verdict. It does not measure the frame rate your hardware is actually achieving right now: for that you need a benchmark or an FPS counter running on the machine, not an arithmetic tool.

Quick Answer

How to use the frame rate calculator: four modes, one job each

Choose a mode first, because the mode decides which two fields the tool reads. The format preset sets the frame rate (see the presets section), the resolution feeds the true uncompressed data rate, and the application selector sets the performance thresholds.

1. Calculate Frame Rate (FPS): enter total frames and duration in seconds. Use this to identify the true rate of a render, an export or an image sequence.
2. Calculate Frame Time: enter a frame rate and read its frame time in milliseconds, for render budgets and input-lag estimates. Total frames and duration report 0 in this mode, because neither is known.
3. Calculate Total Frames: enter a frame rate and a duration. Use it to size a render before you start: the answer is rounded to a whole frame, because half frames do not exist.
4. Calculate Duration: enter total frames and a frame rate to learn how long a sequence runs, for edit timing and slow motion planning.
5. Set the context selectors: the format preset enters its standard frame rate (picking Custom leaves your numbers untouched), the resolution (if set) produces the true uncompressed data rate, and the application picks the performance thresholds described below.

Every mode validates its two inputs the same way: a zero, negative or blank value stops the calculation with a message naming the pair it needs, such as “Please enter valid total frames and duration.” Decimal frame counts are truncated to whole frames, which matches how frames exist in the real world.

The four frame rate formulas

All four modes rearrange one relationship: the frame count equals the rate multiplied by the time.

Frame time deserves one extra line, because it is where the calculator is most often misread. A second holds 1000 milliseconds, so dividing 1000 by the rate spreads the second evenly across the frames. Game engines expose the same relationship from the other side: the Unity documentation for Application.targetFrameRate caps a game’s rate directly, and the frame budget that results is 1000 divided by that cap. Renderers and engines think in frame budgets; players and viewers think in FPS. This tool converts between the two dialects.

Worked example: 7,200 frames over 240 seconds

The FPS mode is pre-filled with 7,200 frames and 240 seconds, a four minute clip. Running it returns 30.00 FPS with a frame time of 33.333 ms and the duration shown back as 4:00 min, rated Good for video production, where the tool’s Good band starts at 24 FPS.

Four more real runs of this calculator, covering the other three modes:

Standard frame rates, their frame times, and what the presets really do

The seven named standards in the format selector are the rates the industry actually ships, and each one fixes a frame time you can plan around:

Choosing a preset now does the work its name promises: selecting a format enters its standard rate into the Frame rate field. If you are in Calculate Frame Rate mode, which derives FPS from a frame count and a duration, the tool switches you to Calculate Frame Time mode so the preset rate is the one that drives the result; in the other modes the preset simply replaces the frame rate value. Picking Custom leaves every value exactly as you typed it. You can still type any rate yourself afterwards, including 29.97 and 23.976, which the tool handles exactly, as the NTSC hour in the checks table shows. If you change the numbers manually after picking a preset, the information note under the result says so instead of claiming the standard rate beside a different result. That hour is also why 29.97 exists: as the Steinberg reference on timecode standards sets out, NTSC timecode counts 30 frames per second of counter while the video itself runs at 29.97 in real time, a 1000/1001 shift inherited from colour television. Platforms accept the whole family: the YouTube upload encoding guidelines list supported frame rates from 24 to 60 FPS, which is why exports at 23.976, 29.97 and 59.94 all upload cleanly. Creators weighing those export choices against channel income can run the audience side of the maths in the YouTube earning calculator.

Frame time and pacing: the average is not the experience

An FPS figure is an average over a second, and averages hide stutter. Two renders can both average 60 FPS while one delivers a frame every 16.667 ms and the other alternates 8 ms frames with 25 ms frames; the second one judders on camera moves, and no headline FPS number will tell you. Frame time is the metric that exposes it, which is why this calculator reports it beside every result.

That framing comes straight from engine practice. Unreal Engine’s documentation treats hitting a target frame rate as a per-frame time budget problem, as its frame rate in Unreal Engine guide explains, and web animation lives under the same budget: a browser aiming for 60 FPS has the same 16.667 ms per frame to do its work. For planning, use this tool’s frame time mode to turn a target rate into a budget, then treat consistency as the goal: a locked 30 FPS with even 33.333 ms frames looks smoother in video than a wandering 45 FPS average. Animators planning long sequences at these rates face the cost side of the same coin, since every added frame is another render; the animation cost calculator prices that side of the decision.

The performance reading and the data rate: two lines to read with care

The coloured performance band is a rule, not a measurement, and here is the whole rule. The reading compares your computed rate with thresholds set by the application selector:

Below Good, the band reads Poor. That produces one verdict worth knowing in advance: a true cinema rate of 23.976 FPS scores Poor for video and animation, because Good starts at exactly 24 and 23.976 falls a hair under it. The film is fine; the rule is blunt. Streamers get the mirror-image warning, since a 24 FPS stream scores Poor under streaming rules that start Good at 30; the money side of streaming at any rate is covered by the streaming cost calculator.

The data rate line is now a true uncompressed rate, worked out from real pixel dimensions: width × height × your frame rate × 24 bits per pixel, divided by 1,000,000 to give megabits per second. Uncompressed 1080p at 30 FPS therefore reports 1,493 Mbps (1920 × 1080 × 30 × 24), and at 60 FPS it reports 2,986 Mbps. Read it as the raw rate before any compression: real delivery rates sit far below uncompressed because codecs compress, which is why platforms publish their own recommended bitrates rather than a formula.

Frame rate is not refresh rate

Frame rate counts the frames a source produces each second; refresh rate, in hertz, counts how often a display can redraw. The two meet at the screen and are otherwise independent, which is why a 240 FPS game on a 60 Hz monitor shows at most 60 fresh frames a second while a 24 FPS film on a 144 Hz panel simply repeats each frame six times.

Modern displays blur the line with variable refresh, letting the panel wait for the game instead of the other way round; Microsoft’s documentation on variable refresh rate displays covers how Windows handles that handoff. For the arithmetic here the distinction has one practical consequence: enter the content’s rate, not your monitor’s. A screen’s 144 Hz is not a frame rate, and typing it into a duration calculation will invent frames your video never had.

What competing calculators miss

Frame rate tools cluster at two extremes, a single bare formula or a live benchmark, and both leave gaps this page is built to close:

• One-direction tools: most rival calculators (CalculatorsHub, BraveCalculator, CalculatorDoc) solve only FPS = frames ÷ time. Frame time, total frames and duration are separate page hunts there; here all four rearrangements live in one mode switch.
• Benchmark confusion: FPS tester sites measure whatever your browser happens to render during the test and present it as a frame rate reference. That number says something about one machine on one day and nothing about your clip, render or timeline. This tool does the deterministic arithmetic instead, and says so.
• No fractional-rate honesty: rivals round broadcast work to 30 FPS in their examples. A 29.97 timeline drifts about 3.6 seconds per hour against a 30 FPS assumption, which is a real sync problem in long edits; this tool accepts 29.97 and 23.976 as first-class inputs and its checks table proves the NTSC hour lands on exactly 3,600 seconds.
• Hidden verdict rules: tools that grade your rate rarely publish their thresholds. The full threshold table is printed above, blunt edges included, so a Poor verdict can be argued with instead of wondered at.
• Silent dead controls: rival pages (and the old version of this one) carry selectors that look functional while doing nothing to the numbers, plus a frame time field no formula ever read. Here the presets genuinely set the frame rate, the dead frame time field is removed, and the exact behaviour is disclosed in the tooltip, in its own section and in the FAQs.

Honest limits of this tool

Four limits, all verified against the tool’s own code and behaviour. First, there is no frame time input: frame time is strictly an output here (1000 ÷ FPS). An earlier version of this page carried a frame time field that no mode read; it has been removed rather than left as a dead control. Second, durations are formatted loosely: under an hour they show as minutes and seconds (4:00 min), and the seconds are rounded in a way that can print 1:60 min for a 119.9 second duration; at an hour and beyond the format switches to a bare 1:00:00 with no unit word. The underlying seconds figure is always exact; only the label is loose. Third, the frame time mode reports total frames and duration as 0 rather than hiding those rows, so read them as “not applicable”, not as answers. Fourth, the format name is echoed with basic capitalisation, so NTSC appears as “Ntsc” in the results; the number beside it is unaffected.

Frequently asked questions

Add This Calculator to Your Website

References