What Is the Video Frame Count Calculator?
This tool tells you exactly how many frames a video clip contains, based on its length and frame rate. A video is just a sequence of still images (frames) shown rapidly to create the illusion of motion. The frame rate — measured in frames per second (fps) — defines how many of those images appear each second. Common rates include 24 fps (cinema), 25 fps (PAL), 30 fps (broadcast), and 60 fps (smooth gaming or sports footage).
How to Use It
Enter the clip's duration as minutes and seconds, then enter the frame rate in fps. The calculator converts the duration into total seconds, multiplies by the frame rate, and rounds to the nearest whole frame. Use it to estimate render counts, plan keyframe budgets, check timeline lengths, or convert between time and frame-based editing.
The Formula Explained
The math is simple: $$\text{Total Frames} = \text{Duration in seconds} \times \text{fps}$$ First the duration is normalized to seconds with \(\text{Minutes} \times 60 + \text{Seconds}\). Then that value is multiplied by the frame rate. Because partial frames are not displayed, the result is rounded to the nearest integer.
Worked Example
Suppose you have a 2-minute 30-second clip at 24 fps. The total duration is \(2 \times 60 + 30 = 150\) seconds. Multiply by 24 fps: $$150 \times 24 = 3{,}600 \text{ frames}$$ At 60 fps the same clip would contain \(150 \times 60 = 9{,}000\) frames.
Standard Frame Rates and Where They Are Used
Frame rate (fps, frames per second) is the second input this calculator needs, alongside duration. Several broadcast frame rates are not whole numbers: when NTSC colour television was introduced in the United States, the black-and-white 30 fps rate was slowed by a factor of 1000/1001 to avoid interference between the colour subcarrier and the audio carrier. That is why 29.97 and 23.976 are shorthand for the exact fractions 30000/1001 and 24000/1001.
| fps (nominal) | Exact value | Region / standard | Typical use | Frames per minute |
|---|---|---|---|---|
| 23.976 | 24000/1001 ≈ 23.976024 | NTSC territories (North America, Japan) | Film transferred to NTSC video; "24p" delivery for US broadcast and many streaming masters | ≈ 1,438.56 |
| 24 | Exactly 24 | DCI / cinema, worldwide | Theatrical features, digital cinema packages, film-look projects | 1,440 |
| 25 | Exactly 25 | PAL / SECAM territories (Europe, Australia, much of Asia and Africa) | European broadcast television, EBU-region commercials and news | 1,500 |
| 29.97 | 30000/1001 ≈ 29.970030 | NTSC broadcast | Standard-definition and HD broadcast video in NTSC countries; legacy camcorder footage | ≈ 1,798.20 |
| 30 | Exactly 30 | Web / digital video, no broadcast standard tied to it | Online video, screen recordings, social platforms, mobile capture | 1,800 |
| 50 | Exactly 50 | PAL-region high-frame-rate broadcast | European sports and live production (1080p50, UHD 50p) | 3,000 |
| 59.94 | 60000/1001 ≈ 59.940060 | NTSC 60p | US/Japanese HD broadcast, 1080i59.94 and 720p59.94 sports feeds | ≈ 3,596.40 |
| 60 | Exactly 60 | Web / gaming, region-neutral | Game capture, smooth-motion online video, action cameras | 3,600 |
| 120 | Exactly 120 | High-frame-rate capture | Slow motion: 120 fps played at 30 fps gives 4× slowdown | 7,200 |
| 240 | Exactly 240 | High-speed capture | Slow motion: 240 fps played at 30 fps gives 8× slowdown | 14,400 |
Enter the fps value your project actually uses. If your timeline is 23.976 or 29.97, typing the rounded 24 or 30 will overstate the frame count by roughly one frame in every thousand — about 1.8 frames per minute at 29.97 versus 30.
Frame Counts for Common Clip Lengths and Frame Rates
Total frames follow directly from the formula
$$\text{Total frames} = (60 \times \text{Minutes} + \text{Seconds}) \times \text{fps}$$The grid below crosses realistic delivery lengths with the five most common frame rates. Values in the 29.97 fps column are shown rounded to the nearest whole frame; cells marked with an asterisk are not whole numbers before rounding.
| Clip | Duration (s) | 24 fps | 25 fps | 29.97 fps | 30 fps | 60 fps |
|---|---|---|---|---|---|---|
| Social ad | 15 | 360 | 375 | 450* | 450 | 900 |
| TV commercial | 30 | 720 | 750 | 899* | 900 | 1,800 |
| Explainer video | 60 (1 min) | 1,440 | 1,500 | 1,798* | 1,800 | 3,600 |
| YouTube segment | 300 (5 min) | 7,200 | 7,500 | 8,991 | 9,000 | 18,000 |
| TV episode body | 1,320 (22 min) | 31,680 | 33,000 | 39,560* | 39,600 | 79,200 |
| Feature film | 5,400 (90 min) | 129,600 | 135,000 | 161,838 | 162,000 | 324,000 |
Worked example — the 30-second commercial at 29.97 fps:
$$(60 \times 0 + 30) \times 29.97 = 30 \times 29.97 = 899.1 \text{ frames}$$A video cannot contain a fractional frame, so the clip holds 899 complete frames and the last frame is displayed a fraction of a frame-period short of the nominal 30.000 s. Put another way, 899 frames at 29.97 fps last 29.997 s, and 900 frames last 30.030 s — which is why an exactly 30-second NTSC spot is normally cut to 899 frames and timed against 30000/1001.
Note the pattern in the 29.97 column: durations that are multiples of 100 seconds (300 s, 5,400 s) give whole numbers because 29.97 × 100 = 2,997 exactly, while 15 s, 30 s, 60 s and 1,320 s do not.
Timecode, Seconds and Frames Conversion
Every duration-to-frames conversion is a single multiplication by the frame rate; going the other way is a division.
$$\text{Frames} = \text{Seconds} \times \text{fps} \qquad \text{Seconds} = \frac{\text{Frames}}{\text{fps}}$$| Input duration | Multiplier | 24 fps | 25 fps | 30 fps |
|---|---|---|---|---|
| 1 second | × fps | 24 | 25 | 30 |
| 10 seconds | × 10 × fps | 240 | 250 | 300 |
| 1 minute | × 60 × fps | 1,440 | 1,500 | 1,800 |
| 10 minutes | × 600 × fps | 14,400 | 15,000 | 18,000 |
| 1 hour | × 3600 × fps | 86,400 | 90,000 | 108,000 |
Frames back to seconds
| Frames | ÷ 24 fps | ÷ 25 fps | ÷ 30 fps |
|---|---|---|---|
| 100 | 4.167 s | 4.000 s | 3.333 s |
| 500 | 20.833 s | 20.000 s | 16.667 s |
| 1,000 | 41.667 s | 40.000 s | 33.333 s |
| 10,000 | 416.667 s (6 min 56.67 s) | 400.000 s (6 min 40 s) | 333.333 s (5 min 33.33 s) |
Reading HH:MM:SS:FF timecode
SMPTE timecode labels each frame as HH:MM:SS:FF, where the frame field FF counts from 0 up to fps − 1 and then rolls over, incrementing the seconds field. So at 24 fps the frame field runs 00–23, at 25 fps it runs 00–24, and at 30 fps it runs 00–29. Converting a timecode position to a frame index:
$$\text{Frames} = (3600 \times HH + 60 \times MM + SS) \times \text{fps} + FF$$Example at 24 fps, timecode 00:00:02:12:
$$(3600 \times 0 + 60 \times 0 + 2) \times 24 + 12 = 48 + 12 = 60 \text{ frames}$$That position is 60 frames from the start, i.e. 2.5 seconds in. Note the off-by-one convention: 00:00:02:12 is frame index 60 counting from zero, and the 61st frame counting from one.
A note on drop-frame timecode
At 29.97 and 59.94 fps, real time runs slightly slower than the timecode clock — about 3.6 seconds of drift per hour. Drop-frame timecode (written with semicolons, e.g. 00;01;00;02) compensates by skipping two frame labels at the start of every minute except minutes divisible by ten. No picture is removed: the video still contains every frame it recorded. Only the numbering changes, so the total from the formula on this page is unaffected by whether your project is set to drop-frame or non-drop-frame. This convention comes from the NTSC broadcast standard used in North America, Japan and other 59.94 Hz territories; PAL/SECAM regions at 25 fps have no equivalent, because 25 fps is an exact integer rate.
FAQ
Does this support fractional frame rates like 23.976? Yes — enter 23.976 in the fps field and the calculator handles the decimal correctly, rounding the final frame total.
Why is the result rounded? A display device can only show whole frames, so the total is rounded to the nearest integer for a realistic count.
Can I work backwards from frames to duration? Yes: divide the frame count by the fps to get the duration in seconds (e.g. \(3{,}600 \div 24 = 150\) s).