Drop-frame timecode can skip frame numbers while every video picture remains present. At a 29.97 fps timecode boundary, missing labels do not establish a damaged export. Inspect the actual consecutive pictures and the display convention before changing frame rate or regenerating footage. A numbering correction cannot repair a genuinely missing image.
Separate the address from the picture
Timecode gives frames addresses. Its last field is a frame label, not decimal fractions of a second. Drop-frame, abbreviated DF, adjusts numbering for certain fractional rates so that the counter follows elapsed clock time closely. Non-drop-frame, NDF, uses a different counting convention.
Frame.io's timecode guide explains that 29.97 DF omits two labels at each minute except every tenth minute. It does not delete recorded pictures. Adobe's current Premiere sequence-settings documentation separately confirms that changing Display Format does not change the sequence or clip frame rate.
Do not confuse the editor's warning about dropped playback frames with this convention. A computer that cannot display every picture in realtime has a different problem from a counter whose labels intentionally skip.
Try a display-only comparison
Keep the source file and project intact. Record the sequence rate, whether the counter is DF or NDF, and whether you are reading source or sequence timecode. Those counters can also start at different addresses.
- Find visible movement near a minute boundary.
- Advance one actual frame at a time and note both the picture and its address.
- Compare a supported sequential frame-number display for the same interval.
- Change only the display convention on a project copy, where supported.
- Confirm that the media, cut positions and playback duration remain unchanged.
If pictures repeat or jump, inspect source and export separately. A repeated motion state may be part of the source cadence or a conversion. Conversely, smooth movement does not prove the entire file is complete; this test answers the local numbering question.
A hypothetical minute boundary
Imagine a 29.97 DF sequence starting at zero. One picture has the address 00:00:59;29. The immediately following picture is labeled 00:01:00;02. Labels ending in ;00 and ;01 are omitted at that boundary. There are still two adjacent pictures to inspect, rather than a hole requiring invented in-between motion.
This is a planning example, not an inspected export. The rule is specific to this rate and convention; do not apply the same two-label example to every fractional-rate format. A semicolon commonly signals DF, but confirm the editor's actual setting instead of relying on punctuation alone.
Approve the numbering and the handoff
Accept this diagnosis when the observed label jump matches the declared convention and consecutive decoded pictures show no corresponding omission. If the source or export really lacks a required moment, investigate capture, trimming or conversion using the actual images.
Keep the intended media rate. Changing 29.97 to 30 merely to make labels look familiar can change timing or conversion behavior. For review notes, include the filename, counter type, DF/NDF convention and sequence rate with every critical address. A collaborator can then find the same moment without mistaking two different counters for different edits.
Sources
Prepared by Imagild Editorial with AI assistance and reviewed against the linked sources on October 13, 2026. Examples are hypothetical; external procedures do not establish Imagild features or guarantee results.