Drop-frame vs non-drop timecode checker and frame calculator

It handles the skipped frame-number labels used by NTSC-derived drop-frame formats instead of treating every labeled minute as identical. The result also reports the nominal counting rate, effective playback rate, number of labels removed before the timecode, and elapsed seconds, making it useful for edit decisions, metadata validation, and automated media pipelines.

Understand what drop-frame timecode actually drops

Drop-frame timecode does not remove video pictures, shorten a clip, or change its playback speed. It removes selected frame numbers from the clock label so that the displayed time stays close to real elapsed time at NTSC-derived fractional rates. At 29.97 fps, counting as if the stream were exactly 30 fps makes the label drift by roughly 3.6 seconds per hour. The drop-frame convention corrects that mismatch by skipping labels 00 and 01 at the start of every minute except each tenth minute. At 59.94 fps it skips four labels, and at 119.88 fps it skips eight. This checker recognizes a semicolon or period before the frame field as drop-frame notation, while a colon means non-drop. It then reports both the selected convention and whether the supplied rate supports drop-frame counting. Nothing is removed from the underlying sequence: the corrected frame count simply subtracts the labels that should never have existed before the requested point. That distinction matters whenever an editor, asset manager, or automation script must translate a human-readable timecode into a precise zero-based frame position.

How the frame-count calculation is made

The calculator first maps the supplied playback rate to its nominal integer counting base. For example, 29.97 uses 30 frame labels per nominal second, while 23.976 uses 24. It validates the minutes, seconds, and frame field against that base. For non-drop notation, the calculation is direct: hours, minutes, and seconds are converted at the nominal rate and the final frame field is added. For drop-frame notation, the checker counts every completed minute before the label, excludes every tenth minute from the correction, and subtracts two, four, or eight skipped labels per corrected minute according to the rate. It also rejects impossible labels such as 00:01:00;00 at 29.97, because the first valid label in that minute is 00:01:00;02. The returned elapsed seconds divide the corrected frame count by the exact fractional playback rate, such as 30000/1001, rather than by the rounded display value. This preserves the practical relationship between frame position and running time while keeping all frame-count arithmetic deterministic and integral.

Choose the convention from the source, not by guesswork

A fractional rate does not automatically prove that a particular timecode is drop-frame. A 29.97 or 59.94 project can carry either drop-frame or non-drop labels, depending on the production requirement and equipment settings. That is why this tool reads the final separator instead of silently forcing one convention: use a semicolon or period when the source specifies drop-frame, and a colon when it specifies non-drop. Rates such as 23.976, 24, and 25 do not use the standard dropped-label correction supported here, so drop-frame punctuation at those rates returns an error instead of a plausible but misleading number. In a media pipeline, preserve the original rate and complete timecode string together; stripping punctuation can erase the convention. Use the reported frame count as a position from a zero origin, then add any separate source start offset only if your workflow requires it. For long-form programs, broadcast logs, caption cues, and conform lists, checking the convention before comparing positions prevents small hourly drift from becoming a visible synchronization or edit-placement error.