How do you convert frames to seconds and minutes?
Seconds = frames ÷ frame rate, and minutes = seconds ÷ 60. Going the other way, frames = seconds × frame rate. The only trap is the 1000/1001 rates: 29.97 fps is really 30000/1001, so 1,800 frames is 60.06 seconds, not 60. The calculator above does it for any rate; here are common frame counts worked out:
| Frames | at 23.976 fps | at 24 fps | at 25 fps | at 29.97 fps | at 30 fps | at 60 fps |
|---|---|---|---|---|---|---|
| 24 | 1.001 s | 1 s | 0.96 s | 0.801 s | 0.8 s | 0.4 s |
| 100 | 4.171 s | 4.167 s | 4 s | 3.337 s | 3.333 s | 1.667 s |
| 1,000 | 41.708 s | 41.667 s | 40 s | 33.367 s | 33.333 s | 16.667 s |
| 1,440 | 1 min 0.06 s | 1 min 0.00 s | 57.6 s | 48.048 s | 48 s | 24 s |
| 1,800 | 1 min 15.08 s | 1 min 15.00 s | 1 min 12.00 s | 1 min 0.06 s | 1 min 0.00 s | 30 s |
| 3,600 | 2 min 30.15 s | 2 min 30.00 s | 2 min 24.00 s | 2 min 0.12 s | 2 min 0.00 s | 1 min 0.00 s |
| 10,000 | 6 min 57.08 s | 6 min 56.67 s | 6 min 40.00 s | 5 min 33.67 s | 5 min 33.33 s | 2 min 46.67 s |
Arithmetic from the exact frame rates (23.976 = 24000/1001, 29.97 = 30000/1001).
What is the difference between 24, 30 and 60 fps?
Frame rate is how many still pictures the video shows each second. More frames means each one is on screen for less time, so motion looks smoother, and the file needs more data to stay sharp. How each family is usually used:
| Frame rate | Each frame lasts | Usually used for | How it looks |
|---|---|---|---|
| 24 / 23.976 fps | 41.667 ms / 41.708 ms | Cinema and most scripted film and TV. 24 is the cinema rate; 23.976 is the version used when the footage is delivered for 60 Hz video systems. | The "film look": each frame holds more motion blur, so movement looks softer. |
| 25 / 50 fps | 40 ms / 20 ms | TV and video in 50 Hz regions such as Europe; EBU Tech 3299 defines 720p/50, 1080i/25, 1080p/25 and 1080p/50. | 25 looks close to 24; 50 is the smooth, high-frame-rate option there. |
| 30 / 29.97 fps | 33.333 ms / 33.367 ms | Online video, phones, TV in 60 Hz regions such as North America and Japan. ATSC lists both 29.97 and 30. | The everyday video look: a little crisper than 24. |
| 60 / 59.94 fps | 16.667 ms / 16.683 ms | Sports, gaming, screen recordings and footage you plan to slow down by half. | Very smooth motion; fast pans and scrolling stay sharp. |
Frame durations are arithmetic (1,000 ÷ fps). "Usually used for" describes common practice; the standards behind the 50 Hz and ATSC rates are linked below.
Higher frame rates cost bit rate. YouTube recommends 8 Mbps for 1080p at 24 to 30 fps and 12 Mbps at 48 to 60 fps, and 35 to 45 against 53 to 68 Mbps at 4K (YouTube Help, checked November 10, 2026). It also says to upload at the frame rate the video was recorded at. The video file size calculator shows what those bit rates mean in megabytes, and video bitrate explains the numbers.
Which looks better, 24, 30 or 60 fps?
The two most compared, frame time, shutter and platform rules worked out side by side: 24fps vs 30fps.
- 24 fps for anything that should feel like film: brand pieces, narrative, interviews shot with a cinematic look. Fast pans can stutter, so move the camera slowly.
- 30 fps for most online video: talking heads, tutorials, product demos, social posts. It is what phones and screen recorders usually default to, and every platform below accepts it.
- 60 fps for fast motion and anything you'll slow down: sports, gaming, UI with lots of scrolling. Check the platform first: X's web limit is 40 fps and App Store previews allow 30.
Why do 23.976, 29.97 and 59.94 fps exist?
They are the whole-number rates slowed by a factor of 1000/1001, a holdover from colour NTSC television. ITU-R BT.709, the HDTV standard, specifies picture rates of 60, 50, 30, 25 and 24 Hz, and says that "for the 60, 30 and 24 Hz systems, picture rates having those values divided by 1.001 are also specified" (ITU-R BT.709-6, section 1). So 29.97 is really 30000/1001, and 23.976 is 24000/1001. The 50 Hz rates, 25 and 50, have no 1.001 version.
US digital broadcasting lists the same family. ATSC A/53 Part 4, Table 6.2, allows frame rates of 23.976, 24, 29.97, 30, 59.94 and 60 Hz. In that table, 1920×1080 is progressive only at 23.976 to 30 (and interlaced at 29.97 and 30 frames, 59.94 and 60 fields); 1280×720 is progressive at every rate up to 60 (ATSC A/53 Part 4:2009). Europe's 50 Hz HD formats are 720p/50, 1080i/25, 1080p/25 and 1080p/50 (EBU Tech 3299).
What are the exact frame rates?
| Rate | Exact value | Decimal | Frame lasts | Frames per minute | Timecode counted at | Non-drop timecode drift per hour |
|---|---|---|---|---|---|---|
| 23.976 fps | 24000/1001 | 23.976024 | 41.708 ms | 1,438.56 | 24, non-drop | 3.6 s behind |
| 24 fps | 24 | 24 | 41.667 ms | 1,440 | 24, non-drop | none |
| 25 fps | 25 | 25 | 40 ms | 1,500 | 25, non-drop | none |
| 29.97 fps | 30000/1001 | 29.970030 | 33.367 ms | 1,798.20 | 30, non-drop or drop-frame | 3.6 s behind |
| 30 fps | 30 | 30 | 33.333 ms | 1,800 | 30, non-drop | none |
| 50 fps | 50 | 50 | 20 ms | 3,000 | 50, non-drop | none |
| 59.94 fps | 60000/1001 | 59.940060 | 16.683 ms | 3,596.40 | 60, non-drop or drop-frame | 3.6 s behind |
| 60 fps | 60 | 60 | 16.667 ms | 3,600 | 60, non-drop | none |
All values are arithmetic from the exact fractions. Drift is how far non-drop timecode falls behind a wall clock in one hour of real time (3600 ÷ 1001 = 3.6 seconds).
What is drop-frame timecode, and how is it calculated?
Timecode labels each frame as hours:minutes:seconds:frames. At 29.97 fps it still counts 30 frame numbers per timecode second, so with plain (non-drop-frame) counting the timecode falls behind real time: one real hour reads 00:59:56:12. Drop-frame timecode fixes this by skipping the frame numbers 00 and 01 at the start of every minute, except minutes 00, 10, 20, 30, 40 and 50. That removes 108 numbers an hour, so one hour of drop-frame timecode is within 3.6 ms of a real hour. At 59.94 fps the same scheme skips four numbers (00 to 03).
- No picture is dropped. Only labels are skipped; every frame is still there.
- It is written with a semicolon before the frames, like 00:01:00;02, while non-drop uses colons throughout.
- Only 29.97 and 59.94 use it. 23.976 is normally counted non-drop at 24, so its timecode also runs 3.6 seconds an hour slow.
- Use it when timecode must match the clock, such as broadcast programme lengths. For web video, either works; just keep one setting through the edit.
As a drop-frame timecode calculator, the tool above works both ways: tick "Drop-frame timecode" at 29.97 or 59.94, then type a frame count to get the timecode, or type a timecode (with a semicolon, like 00:10:00;00) to get frames and seconds. The arithmetic it uses at 29.97: every 10 minutes holds 17,982 frames (10 × 60 × 30 − 9 × 2). Split the frame count into whole 10-minute blocks and a remainder; add back 18 skipped numbers per block, plus 2 for each started minute after the first in the remainder; then count the result as plain 30-frame timecode. At 59.94 the numbers double (35,964 frames per 10 minutes, 4 skipped per minute).
What frame rate does each platform accept?
| Platform | Published frame-rate rule | 24 fps | 30 fps | 60 fps |
|---|---|---|---|---|
| 10 to 60 fps (source) | Yes | Yes | Yes | |
| X | up to 40 fps (web) (source) | Yes | Yes | Above the maximum |
| Instagram Reels | at least 30 fps (source) | Below the minimum | Yes | Yes |
| YouTube | the rate it was recorded at (source) | Yes | Yes | Yes |
| 24 to 60 fps recommended (source) | Yes | Yes | Yes | |
| Threads (API docs) | 23 to 60 fps (source) | Yes | Yes | Yes |
| Vimeo | native and constant; over 60 fps is reduced (source) | Yes | Yes | Yes |
| App Store app previews | 30 fps maximum (source) | Yes | Yes | Above the maximum |
From each platform's own help pages (Threads: Meta's API docs), checked November 4 and 10, 2026; App Store from Apple's app preview specifications. YouTube says to upload at the recorded rate and names 24, 25, 30, 48, 50 and 60 as common. Vimeo reduces anything above 60 fps. YouTube Shorts, Bluesky, Pinterest, Snapchat, Reddit and WhatsApp publish no frame-rate rule; TikTok is left out because we couldn't verify its help pages. Full limits on social media video sizes, or check a file with the video specs checker.
The surprises: Instagram Reels lists 30 fps as a minimum, so a 24 fps export is below it, and X's web upload stops at 40 fps, so 60 fps is above it. A 30 fps export clears every published rule here.
What frame rate should a launch video use?
30 fps. A launch or product video is mostly UI, type and motion graphics; 30 fps keeps scrolling and animation clean, fits every rule in the table above (including the App Store's 30 fps maximum and Instagram's 30 fps minimum), and needs less bit rate than 60. Record screen captures at 30 too, or at 60 if you'll make a separate cut for YouTube, which accepts the rate it was recorded at. Pair it with a 1920×1080 master (see video aspect ratio) and YouTube's 8 Mbps for 1080p. Per-platform recipes: YouTube, LinkedIn, X, Instagram Reels, App Store previews.
How do you convert between frame rates?
A video's frame count and duration are tied by its rate (frames = seconds × fps), so changing the rate means either changing the speed or adding and removing frames. Playing 24 fps footage at 25 makes it about 4% faster; turning 24 into 30 means repeating some frames, which can make motion look uneven. Where you can, shoot or render at the rate you'll deliver. The converter above does the arithmetic: enter a frame count at one rate and the table shows how many frames the same length takes at the others.