Drop-Frame Timecode: The Decisions That Matter
A timecode counting method for 29.97 frames per second video that keeps timecode aligned with real clock time.
Tomas Lindqvist
Why does it matter?
Using the wrong timecode type causes program lengths to drift from real time, which matters for broadcast delivery.
What are the numbers?
- Frame rate NTSC-based video runs at 29.97 frames per second
- Method frame numbers 00 and 01 are skipped each minute except every tenth minute
- No frames lost only frame numbers are skipped, not images
- Notation drop-frame timecode is often shown with semicolons
What should I do?
- Confirm timecode type in delivery specs
- Keep one timecode type per project
- Check program length against clock time
- Label files with timecode settings
- Test conforms with the delivery format
What should I avoid?
Avoid:
- Mixing drop-frame and non-drop-frame
- Assuming timecode matches clock time
- Ignoring broadcast specifications
- Changing timecode types mid-project
When should I get help?
Short answer Bring in help when delivering to US broadcasters.
Where this comes from
The figures and practices above come from the sources listed.
Working on something like this?
We take on Video Editing & Production work for teams who want it done once, properly. Tell us what you are building and we will tell you honestly whether we are the right studio for it. Start a project.
Where to go next
Spotted something wrong? Report an error on this page. We correct on the page and say what changed.
