How to use the converter
- Choose whether the value is a zero-based frame number or a timecode label.
- Select the project frame rate and NDF or 29.97 DF counting.
- Enter one value, then select Convert. Editing it clears the old result; after a successful conversion, changing a selector recalculates valid input immediately.
- Copy the converted label or frame number. The elapsed-time line is a reference, not another editable timeline.
Frame numbers, timecode and drop-frame counting
Frame number 0 is the first frame and maps to 00:00:00:00. At integer rates, NDF splits the continuous frame count into hours, minutes, seconds and FF using that many frames per second.
29.97 fps is exactly 30000/1001 frames per second. NDF still labels frames on a nominal 30-count clock, so its displayed minute is slightly longer than one real minute.
29.97 DF does not remove video frames. It skips labels ;00 and ;01 at the start of every minute except each tenth minute, bringing the label clock close to elapsed time.
Boundary examples
At 29.97 NDF, frame 1800 is 00:01:00:00 but starts at about 00:01:00.060 of playback. This is why timecode labels and elapsed time must not be treated as the same value.
At 29.97 DF, frame 1799 is 00:00:59;29 and frame 1800 is 00:01:00;02. Labels 00:01:00;00 and 00:01:00;01 do not exist.
The tenth-minute exception keeps 00:10:00;00 valid. Frame 17982 maps to it, and frame 107892 maps to 01:00:00;00.
Supported range and limits
- Supported NDF rates are 24, 25, 29.97, 30, 50 and 60 fps. DF is limited to 29.97 fps.
- Frame numbers must be non-negative integers. Decimal and negative frame numbers are rejected.
- Timecode uses two-digit hours from 00 through 99, minutes and seconds from 00 through 59, and FF from 00 to one less than the nominal rate. There is no hidden 24-hour wrap.
- This page does not read video files, change frame rates, edit timelines, create EDLs, or support 59.94 DF.
Frequently asked questions
Does drop-frame discard pictures?
No. Only selected timecode numbers are omitted; every recorded frame remains present.
Why is 00:01:00;00 rejected?
In 29.97 DF, ;00 and ;01 are skipped at most minute boundaries. Use 00:01:00;02. Multiples of ten minutes are exceptions.
Why can elapsed time differ from timecode?
Timecode is a frame-labeling system. At 29.97 NDF it counts nominal 30-frame seconds while playback runs at exactly 30000/1001 fps.
Can I use a 24-hour broadcast wrap?
No. This page accepts explicit 00–99 hours and never wraps a result silently.