Drop-frame timecode skips frame numbers, not frames. Video at 29.97 frames per second runs slightly slower than a clock that counts 30 frames a second, so ordinary timecode falls behind real time by 3.6 seconds every hour. Drop-frame timecode leaves out two frame numbers at the start of most minutes so that the timecode stays in step with the clock. Every picture is still there.

You meet it in broadcast work, in NTSC-region cameras and in editing software that offers "29.97 DF" and "29.97 NDF". It matters whenever a programme has to last an exact length, or when timecodes from different tools must agree.

How timecode works

Timecode names every frame as hours:minutes:seconds:frames. The last part counts frames within the second: 00 to 24 at 25 fps, 00 to 29 at 30 fps. At 25 fps, one hour is 3,600 × 25 = 90,000 frames, and 01:00:00:00 is exactly one hour of real time.

Why 29.97 needs a correction

North American colour television (NTSC) runs at 30000/1001 frames per second, which is about 29.97 rather than 30. Timecode still counts 30 frame numbers per second. After one real hour, the video has played 107,892 frames, but a count of 30 per second needs 108,000 to reach 01:00:00:00. Counted the plain way, one hour of video reads 00:59:56:12: 108 frames, or 3.6 seconds, short.

The drop-frame rule

  • At the start of every minute, the frame numbers 00 and 01 are skipped: after 00:00:59;29 comes 00:01:00;02.
  • Except every tenth minute (00, 10, 20, 30, 40, 50), which keeps all its numbers.
  • That removes 2 × 54 = 108 numbers an hour: exactly the shortfall.
  • At 59.94 fps the same rule skips four numbers (00 to 03).

Drop-frame timecode is written with a semicolon before the frames, 01:00:00;00, so it cannot be confused with non-drop timecode.

Frame number (29.97 DF) Timecode
1,799 00:00:59;29
1,800 00:01:00;02
17,982 00:10:00;00
107,892 01:00:00;00

Drop-frame or non-drop: which should you use?

  • Drop-frame when timecode must match clock time: broadcast programmes, commercials with a fixed length, anything delivered "to the second".
  • Non-drop when every frame number must exist and simple arithmetic matters more than clock time, for example in many editing, VFX and subtitling workflows.
  • Only 29.97 and 59.94 have a drop-frame form. 23.976 fps is also 0.1% slower than its count of 24, but it has no drop-frame timecode, so it drifts from clock time by the same 3.6 seconds an hour.

Whichever you use, keep it the same from camera to edit to delivery, and say which one it is.

Converting timecode, frames and real time

The free Timecode Calculator converts any timecode to a frame number and real time, handles 29.97 and 59.94 drop-frame exactly, shows the same moment at 23.976, 24, 25, 30, 50 and 60 fps, and gives the duration between two timecodes. It runs in your browser.

For subtitles made at one frame rate and played at another, the Subtitle Shifter converts their timing between 23.976, 24, 25 and 29.97 fps.

Cutting on the exact frame

Once you know where a cut belongs, CreatorCut cuts video, removes silent parts and adds captions on your Windows PC.

Get CreatorCut on Microsoft Store

Frequently asked questions

Does drop-frame timecode delete frames from my video?

No. Every frame is kept and played. Only the numbering skips, the way a calendar skips 29 February in most years.

Why does my editor show a semicolon in the timecode?

The semicolon (or sometimes a period) before the frames marks drop-frame timecode. A colon marks non-drop.

Is 30 fps the same as 29.97 fps?

No. True 30 fps needs no correction: 30 frames are 30 frame numbers, and timecode matches the clock. 29.97 fps is 0.1% slower, which is why drop-frame exists.

References

Try it free in your browser

Continue reading