Timecode Generator

Build HH:MM:SS:FF labels for edits, captions, and sync—pick frame rate carefully.

Timecode Settings

Configure timecode format and timing parameters

Add Timecode Entry

Create individual timecode entries with precise timing

0.00s

Formats that matter

SMPTE-style timecode is usually HH:MM:SS:FF. The last field is a frame count at your project frame rate (24, 25, 29.97, 30, 50, 60, and friends). Wrong frame rate = labels that look fine and land on the wrong picture.

Drop-frame (common for NTSC 29.97) skips certain frame numbers so clock time stays honest over long programs. It does not drop actual frames. Non-drop counts every number in sequence and can drift from wall-clock time. Use what your NLE and delivery spec expect—mixing DF and NDF is a classic gotcha.

Practical workflow tips

  • Match the sequence frame rate before generating a list of marks
  • For subtitles, prefer formats your player accepts (SRT/WebVTT often want milliseconds)
  • Keep captions on screen long enough to read—rough floor around two seconds; avoid parking one line for many seconds
  • Convert frame rates with math, then spot-check playback; automatic remapping is rarely perfect
  • Accessibility rules care about sync and reading time, not fancy timecode aesthetics

Related Tools and Resources

Frequently Asked Questions

Drop-frame vs non-drop-frame?

Drop-frame skips frame numbers on a schedule so 29.97 fps stays aligned with real clocks. Non-drop never skips numbers and can drift. Broadcast NTSC often wants DF; film and many digital workflows do not.

How do I keep subtitle timing stable across devices?

Export a standard caption format, match the master frame rate, and test on the target player. Millisecond-based cues travel more cleanly than frame labels when platforms disagree on fps.

Can I convert between frame rates automatically?

You can remap by ratio, then fix by eye. Large fps jumps and variable frame rate sources need manual cleanup.

How long should a subtitle stay up?

Long enough to read without blocking the next line. Many editors use a short minimum (around two seconds) and avoid multi-line walls of text. Adjust for dense dialogue and audience.

Related tools

Related tools