numvana

SMPTE Timecode Calculator

Convert an HH:MM:SS:FF video timecode to a total frame count and real elapsed duration, with correct NTSC drop-frame (29.97/59.94fps) handling.

Total elapsed frames
107,892
Real elapsed duration
0:59:59.996
Literal HH:MM:SS:FF duration
1:00:00.000
Drift (literal minus real)
0.0036 s

How it works

SMPTE timecode counts frames as HH:MM:SS:FF. At an exact integer frame rate (24, 25, or 30fps), that count matches real elapsed time exactly. NTSC video, though, actually runs at 30÷1.001 (≈29.97) or 60÷1.001 (≈59.94) fps — not the round 30/60 the timecode digits count in — so the raw HH:MM:SS:FF numbers drift behind real-world elapsed time by about 3.6 seconds per hour at 29.97fps if left uncorrected. Verified via web search against Wikipedia's SMPTE timecode reference rather than relied on from memory.

Drop-frame notation (DF) fixes this by skipping the frame numbers 0 and 1 (0-3 at 59.94fps) at the start of every minute except every tenth minute, which removes almost exactly the right count of frame numbers to keep the displayed timecode in sync with the wall clock — no video frames are ever actually dropped, only some of the numbers used to label them. This reproduces the standard reference example that a drop-frame count at 29.97fps advances directly from 01:22:59:29 to 01:23:00:02 (skipping the labels 01:23:00:00 and 01:23:00:01), and that exactly 108 frame numbers are dropped over a full drop-frame hour (108,000 nominal 30fps frames minus 108 dropped = the well-known 107,892 real frames per hour at 29.97fps).

The result shows the drop-frame-corrected total frame count, the real elapsed duration computed from the true (non-round) frame rate, and — for comparison — the 'literal' duration you'd get by naively reading the HH:MM:SS:FF digits as if the frame rate were an exact round number. The difference between those two is the drift that drop-frame notation exists to correct.

FAQ

Does drop-frame timecode actually delete video frames?

No. Every recorded frame is kept and played back — drop-frame only skips certain frame-number labels (like a digital odometer skipping from 00:59 to 01:02) so the displayed clock stays in sync with real elapsed time. Non-drop-frame timecode keeps every consecutive number but slowly drifts from wall-clock time over a long recording.

Which should I use, drop-frame or non-drop-frame?

Broadcast television in NTSC regions conventionally uses drop-frame so on-air duration matches the timecode exactly (critical for hitting exact program lengths), while non-drop-frame is common in post-production for its simpler, gap-free frame numbering. Match whatever convention your delivery format or broadcaster requires — this calculator supports checking either.

Related calculators