What is drop frame timecode?

It is timecode that skips certain frame numbers, not actual frames, so the timecode value stays aligned with real clock time at 29.97 and 59.94 frames per second. It drops two frame numbers each minute except every tenth minute, which brings the error close to zero over an hour.

Should I use drop frame or non-drop frame?

Drop frame when broadcast running time matters, because the timecode then matches wall clock duration. Non-drop when frame counting matters and you want every number to exist in sequence. Neither is wrong, and what causes real problems is mixing them within a project, so decide once and stay consistent.

How much does non-drop timecode drift from real time?

About 3.6 seconds per hour at 29.97 frames per second, because timecode counts 30 frames per second while the video actually runs at 29.97. Over a two hour programme that is more than seven seconds, which is why broadcasters specify drop frame for anything where the stated duration has to be accurate.

Do I need timecode for single camera work?

Not if the audio is recorded in the camera, since picture and sound already share a clock. It becomes worth having when a separate audio recorder is used on long takes, when several cameras must cut together, and when the volume of material makes manual syncing a significant part of the schedule.

What frame rate should I shoot at?

Decide the delivery frame rate before you shoot and capture to match, unless you specifically want slow motion. Mixing capture rates in one timeline forces frames to be dropped or blended, and both look wrong on motion. Twenty four is the cinema standard, 25 suits 50 Hz broadcast regions and 30 suits North American broadcast.

Timecode and Frame Rate Calculator

Short answer

Non-drop frame timecode at 29.97 frames per second drifts about 3.6 seconds ahead of real clock time every hour, because it counts 30 frames per second while the video runs slightly slower. Drop frame timecode skips frame numbers to correct that, which is why broadcast deliverables specify it.

Timecode arithmetic is the kind of thing that is simple until 29.97 appears, at which point it stops being intuitive. This calculator converts between timecode and frames, shows the drift between drop frame and non-drop frame, and gives the running time for a frame count. On the hardware side, a Deity TC-1 Timecode Box at around $135 is what puts the same clock on every device.

Calculator

Runs in your browser

Enter a timecode value and a frame rate. The readout gives the total frame count, the real elapsed time, and how far non-drop frame timecode has drifted from the clock at that point.

Timecode, hh:mm:ss:ff

Frame rate

Total frames

non-drop count

Real elapsed time

at the actual frame rate

Non-drop drift

0 s

against wall clock

What this means for your project

The arithmetic

A timecode value converts to frames with frames = hh x 3600 x rate + mm x 60 x rate + ss x rate + ff, where the rate used for counting is the nominal integer rate. Timecode always counts in whole frames, so 29.97 fps material is counted at 30 frames per second even though it does not play at exactly that speed.

That gap is the entire source of the drop frame problem. Real elapsed time is frames / actual rate, and with an actual rate of 29.97 against a counting rate of 30, real time runs about 0.1 percent longer than the timecode suggests. Over an hour that is roughly 3.6 seconds.

Why 29.97 exists

When colour was added to black and white television in North America, the frame rate had to shift very slightly to prevent interference between the colour subcarrier and the audio carrier. Thirty frames per second became 30 multiplied by 1000 over 1001, which is 29.97. The same adjustment produced 23.976 from 24 and 59.94 from 60.

Every one of those rates has persisted through every subsequent format, which is why a modern camera in 2026 still offers 23.976 alongside 24. It is not a technical necessity any more and it is a compatibility requirement, because a great deal of delivery infrastructure still expects it.

Drop frame, explained properly

Drop frame timecode does not drop frames. It drops frame numbers, skipping two numbers at the start of every minute except every tenth minute. No picture is lost; only the labelling changes, so the timecode value stays aligned with real clock time.

Mode	Counts	Matches wall clock?	Use it when
Non-drop frame	Every number in sequence	No, drifts about 3.6 s per hour at 29.97	Frame counting matters more than duration
Drop frame	Skips two numbers per minute, except every tenth	Yes, near enough to zero error	Broadcast running time has to be accurate
25 fps	Every number in sequence	Yes, because 25 is exactly 25	Any 50 Hz broadcast region. No drop frame needed
24 fps exactly	Every number in sequence	Yes, because 24 is exactly 24	Cinema delivery. No drop frame needed

Note that only the 29.97 and 59.94 families need drop frame at all. Twenty five and a true 24 are exact rates and their timecode matches the clock without correction. If you shoot 25 fps you never have to think about any of this, which is a small and genuine advantage of working in a 50 Hz region.

Jam syncing and drift in hardware

Timecode arithmetic is one problem and keeping devices agreed is another. A timecode box like the Deity TC-1 Timecode Box is jammed to a master at the start of the day and then free-runs on its own crystal, holding roughly one frame of drift per twenty four hours. That accuracy is what makes a single jam sync each morning sufficient.

Camera internal clocks are far worse, commonly drifting several frames per hour, which is why syncing cameras to each other without dedicated boxes fails on long takes. It is also why re-jamming after a large temperature change is worth the minute it costs, since crystal drift varies with temperature.

What keeps everything agreed

A three-box kit for a two-camera shoot with a recorder, a matched pair, and a recorder that accepts timecode directly rather than through an audio channel.

Best value $373

Deity

Deity TC-1 Three-Box Kit

Three boxes covers two cameras and a recorder, which is the actual shape of most small multicam shoots.

Units: 3

The value pick for two-camera interviews.

Check price

Expert choice $399

SUAREA

Tentacle Sync E MKII (Standard Set)

Two units with the cables that actually fit common cameras, which is where most timecode purchases quietly go wrong.

Units: 2

Check your camera's connector before ordering.

Check price

Best value $299.99

Zoom

Zoom F3

Two channels of 32-bit float with no gain to set, which removes the single most common way a solo shooter ruins location audio.

Channels: 2
Format: 32-bit float

The pick for a one-boom documentary rig.

Check price

Frame rate choices and mixing

Decide the delivery frame rate before shooting and capture to match. Footage captured at 30 dropped into a 24 fps timeline has to have frames removed or blended, and both look wrong on motion. This is the single most common frame rate mistake and it is entirely preventable.

The deliberate exception is slow motion. Capturing at 60 or 120 for delivery at 24 gives you the option of slowing a shot smoothly, and following the 180 degree shutter rule at the capture frame rate rather than the delivery rate is correct in that case.

Running time from a frame count

Editors and producers ask for durations in different units, and the conversion is worth keeping straight. A frame count divided by the actual frame rate gives seconds. At 24 fps, 86,400 frames is exactly one hour. At 29.97, 107,892 frames is one hour of real time but reads as 01:00:03:18 in non-drop timecode.

That discrepancy is exactly why broadcast deliverables specify drop frame. A programme slot is measured in clock time, and a timecode system that runs 3.6 seconds fast per hour will report a duration that does not match the slot.

A practical timecode routine

Set the same frame rate and the same drop frame mode on every device, before anything else.
Charge every timecode box the night before, since they free-run continuously and discharge on the shelf.
Jam sync all boxes from one master at the start of the day, and note the time.
Mount each box where its cable does not cross a battery door or a hinge.
Label every box, because three identical black boxes and a sync problem is a miserable afternoon.
Record a camera scratch track regardless, as the fallback when something in the chain fails.

The timecode and sync guide covers how the signal actually reaches each device, including the audio-channel method used on bodies with no timecode input.

Next, from here

Timecode and sync guide
Jam syncing, drift and dual system sound.
Best timecode generators
The boxes, compared.
Shutter angle and frame rate chart
Every shutter conversion.
ND and shutter angle calculator
Holding 180 degrees in daylight.
Best field recorders
Which accept timecode directly.
Media workflow and backup
What happens to synced files afterwards.

Common questions

What is drop frame timecode?: It is timecode that skips certain frame numbers, not actual frames, so the timecode value stays aligned with real clock time at 29.97 and 59.94 frames per second. It drops two frame numbers each minute except every tenth minute, which brings the error close to zero over an hour.
Why does 29.97 fps exist at all?: It is a legacy of adding colour to black and white television in North America. The frame rate was shifted very slightly from 30 to avoid interference between the colour subcarrier and the audio carrier, and the resulting 29.97 rate persisted through every subsequent format. The same reasoning produced 23.976 and 59.94.
Should I use drop frame or non-drop frame?: Drop frame when broadcast running time matters, because the timecode then matches wall clock duration. Non-drop when frame counting matters and you want every number to exist in sequence. Neither is wrong, and what causes real problems is mixing them within a project, so decide once and stay consistent.
How much does non-drop timecode drift from real time?: About 3.6 seconds per hour at 29.97 frames per second, because timecode counts 30 frames per second while the video actually runs at 29.97. Over a two hour programme that is more than seven seconds, which is why broadcasters specify drop frame for anything where the stated duration has to be accurate.
Do I need timecode for single camera work?: Not if the audio is recorded in the camera, since picture and sound already share a clock. It becomes worth having when a separate audio recorder is used on long takes, when several cameras must cut together, and when the volume of material makes manual syncing a significant part of the schedule.
What frame rate should I shoot at?: Decide the delivery frame rate before you shoot and capture to match, unless you specifically want slow motion. Mixing capture rates in one timeline forces frames to be dropped or blended, and both look wrong on motion. Twenty four is the cinema standard, 25 suits 50 Hz broadcast regions and 30 suits North American broadcast.

Totalling your own rig weight against your gimbal payload? The Camera Rig Build Planner is the paid version of these pages: 8 printable worksheets you fill in with your own numbers, plus the full PDF, $29.