Frames to Timecode Converter

Enter a frame count and frame rate to get the SMPTE timecode and duration in seconds.

How it is calculated

The frame count must be a whole number (a decimal such as 100.5 gives no result) and the frame rate is rounded to the nearest integer, R. Then: FF = frames mod R, total seconds = frames div R, SS = total seconds mod 60, MM = (total seconds div 60) mod 60, HH = (total seconds div 3600) mod 24: Recommendation ITU-R BR.780-2 gives the time address as a 24-hour clock from 00:00:00 to 23:59:59, so a count past a day wraps to 00, and a note says how many whole days were dropped. At 50 and 60 fps (and 59.94) the standard counts every second frame (§ 4.1, the rate exceeds the code's frame capacity): the tool halves the frame count and counts at 25 or 30, so FF runs 0 to 24 or 0 to 29, and it says whether the frame is the first or second of its pair. The timecode is printed as HH:MM:SS:FF with leading zeros. The second result, duration in seconds, uses the unrounded rate: frames ÷ fps. This is non-drop-frame counting only. At 29.97 fps the timecode counts at 30 per second while the seconds line uses 29.97, so the two drift apart: 107,892 frames shows 00:59:56:12 but lasts 3,600.00 seconds. Negative frames or a rate of zero give no result.

Worked example

90,137 frames at 25 fps. Whole seconds: 90,137 div 25 = 3,605, with a remainder of 90,137 − 3,605 × 25 = 12 frames, so FF = 12. Seconds 3,605 = 60 × 60 + 5, so HH = 1, MM = 0, SS = 5. Timecode: 01:00:05:12. Duration: 90,137 ÷ 25 = 3,605.48 seconds. Because 25 is a whole number, the timecode and the duration agree exactly: 12 frames is 0.48 s at 25 fps.

Try this example →

Common mistakes

  • Using the result as drop-frame timecode for 29.97 fps material: this tool counts at 30 per second without dropping any numbers, so it can differ from the clock by seconds over an hour.
  • Typing 29.97 and expecting the frame field to count to 29.97: the frame rate is rounded to 30 for the counting, so FF runs from 0 to 29.
  • Expecting FF to reach 59 at 60 fps: the address holds one number per pair of frames, so FF stops at 29 and the pair line tells the two frames apart.
  • Reading the last field as hundredths of a second: FF is a frame number, from 0 to the rate minus one, not a decimal.
  • Entering a time in seconds instead of frames: 3605 means 3,605 frames, which is under 2.5 minutes at 25 fps.
  • Starting the count at frame 1 instead of 0: frame 0 is 00:00:00:00, so the 25th frame of video is frame number 24, shown as 00:00:00:24.

Sources

About this calculator

SMPTE timecode labels every frame of video with an HH:MM:SS:FF address, letting editors, colorists and broadcast engineers reference an exact frame instead of a rough time. This calculator converts a raw frame count into that timecode at the frame rate the project uses — 24, 25, 29.97 or 60 fps, among others — rounding the rate to a whole number for counting, so 29.97 fps counts as 30. It follows Recommendation ITU-R BR.780-2: the hours run on a 24-hour clock, so a count past 23:59:59 starts again at 00, and at 50 and 60 fps each pair of progressive frames shares one address, because those rates exceed the frame count the code can carry; the tool says whether a frame is the first or second of its pair.

At fractional NTSC rates like 29.97 fps, plain frame counting drifts from wall-clock time, which is why drop-frame timecode exists: it skips certain frame numbers on a schedule so the displayed timecode stays aligned with real elapsed time. This calculator always produces non-drop-frame timecode, which keeps every frame number but slowly diverges from the clock at 29.97 fps; the real elapsed time (frames ÷ exact frame rate) is shown next to it as seconds. Knowing which mode your delivery spec requires is essential for matching cut lists, syncing audio, and hitting broadcast specs frame-accurately.

Was this helpful?

You can pick up to 3 reactions.

Note from the editors

At 29.97 fps, 107,892 frames last exactly 3,600.00 seconds on the tool's duration line, yet the timecode reads 00:59:56:12 because the counter runs at a flat 30 per second and never drops numbers. That is a lag of 3.6 seconds on a one-hour program. For broadcast delivery on 29.97 material, use a drop-frame tool or check your editor's setting. Which frame rate do your clips use?

Comments

  • Be the first to comment.

Popular calculators

All Calculators