Drop Frame vs Non-Drop Frame Timecode, Explained Simply
If you’ve ever seen a timecode written 01:00:00;02 with a semicolon and wondered what’s going on, this guide is for you. Drop frame timecode is one of the most misunderstood concepts in post-production — mostly because its name suggests something it absolutely doesn’t do.
First, the one thing to remember
Drop frame timecode never drops frames. Not one. Every frame of your video is still there. What gets skipped is frame numbers — labels, not pictures. The name refers to dropping numbers from the counting sequence.
Why the problem exists at all
In 1953, US television engineers needed to add color to the black-and-white NTSC standard without breaking existing TV sets. Their solution required slowing the frame rate by exactly 0.1% — from 30 fps to 30 ÷ 1.001 ≈ 29.97 fps.
That tiny slowdown created a bookkeeping headache. Timecode counts frames: at “30 fps” numbering, one hour of timecode assumes 108,000 frames. But at 29.97 fps, playing 108,000 frames takes one hour plus about 3.6 seconds. Let a program run all day and the timecode clock drifts minutes away from the wall clock.
For broadcasters, that’s a real problem. Program durations are contractual; ad breaks are scheduled to the second. Timecode needed to match real time.
How drop frame fixes it
The fix is elegantly ugly: skip frame numbers 00 and 01 at the start of every minute, except minutes ending in 0 (00, 10, 20, 30, 40, 50).
So the counter goes:
00:00:59;28 → 00:00:59;29 → 00:01:00;02 → 00:01:00;03 ...Numbers 00:01:00;00 and 00:01:00;01 simply never exist. Over one hour this skips 108 numbers — almost exactly the 3.6-second drift. Drop frame timecode stays within 3 frames of real time per 24 hours.
When you must use which
| Situation | Timecode |
|---|---|
| US/NTSC broadcast delivery at 29.97/59.94 | Drop frame (almost always required by spec) |
| Film, streaming, web at 23.976/24/25 | Non-drop (DF doesn’t exist at these rates) |
| PAL countries (25 fps) | Non-drop — 25 divides evenly, no drift, no problem |
| Post-production working timecode | Whatever your pipeline specifies; many facilities cut in NDF and conform on output |
Two spotting rules: a semicolon before the frames field (;02) means drop frame; a colon (:02) means non-drop. And drop frame only exists at 29.97 and 59.94 fps — if someone asks for “24 fps drop frame,” the correct answer is that there is no such thing.
What happens if you get it wrong
Deliver an NDF master against a DF spec and your program appears to run long: an hour-long show measured in NDF timecode is 3.6 seconds more than an hour of real time. QC will bounce it. In the edit suite, mixing DF and NDF sources without conforming causes sync and duration mismatches that surface at the worst possible moment — final output.
Do the math automatically
Adding and subtracting timecodes across drop frame boundaries by hand is genuinely error-prone (the skipped numbers make naive arithmetic wrong). Our timecode calculator implements the SMPTE drop frame algorithm — add, subtract and convert frames to timecode at every professional rate, and it will show you the real running time alongside.