Non-drop-frame timecode
108,000 frames at 30 fps.
Share links include only numbers and choices. Local saves remain in this browser until you delete them.
Saved on this device0 of 6 saved
Save a fresh result to compare or reuse it later on this device.
Formula or method
Timecode and total frames are converted using the selected integer frame rateAssumptions
- This utility uses non-drop-frame timecode.
- For 29.97/59.94 broadcast drop-frame workflows, use dedicated editorial software.
How to use the frames and timecode
Convert an integer frame count to non-drop-frame SMPTE-style timecode or convert a valid timecode back to frames. The tool is designed for deterministic edit notes, turnovers, and duration checks where a one-frame error can create the wrong cut.
Match the frame rate used by the timeline
At 30 frames per second, 108,000 frames equals 01:00:00:00. At 24 frames per second, the same frame count represents 01:15:00:00. Always confirm the timeline rate before converting, and keep source, proxy, sequence, and export rates documented when they differ.
Timecode frame components must stay below the selected frame rate. A value ending in :30 is invalid at 30 fps because valid frame numbers run from 00 through 29. The tool rejects out-of-range minute, second, and frame components instead of silently rolling them over.
Know when drop-frame rules are required
This converter uses non-drop-frame arithmetic. Broadcast workflows using 29.97 or 59.94 fps may require drop-frame timecode so the displayed clock remains aligned with real elapsed time. Do not substitute a rounded 30 fps calculation for a delivery specification that explicitly requires drop-frame notation.
Record whether an edit note is a source timecode, sequence timecode, or simple elapsed duration. Camera restarts, multicamera synchronization, and time-of-day code can create identical-looking values that refer to different frames.
Questions about this tool
Does this support drop-frame timecode?
No. It currently performs non-drop-frame conversion at the selected integer frame rate. Use a drop-frame-aware workflow when the specification requires it.
Why is the frame field limited by frame rate?
The last timecode component counts frames within one second, so it runs from zero to one less than the selected frames-per-second value.
Can I use this for variable-frame-rate footage?
Use caution. Variable-frame-rate sources should usually be conformed or interpreted in a fixed-rate editing timeline before frame-accurate timecode decisions are made.