Blendpipe homeSend a brief
Menu

Frame and timecode calculator

Frame rate, length and a frame count in, frames, timecode and clock drift out.

Send a brief
You enter
Frame rate, spot length, a frame count
You get
Frames, timecode and real time
Example
1438 frames at 23.976 = 00:00:59:22 non-drop
Runs
In your browser; nothing is sent
A wooden metronome on the closed lid of a black piano, its swinging arm leaving a drawn marigold arc of evenly spaced tick marks.

Calculator

The values filled in come from the fictional Orlenna example campaign; money values are illustrations, not Blendpipe prices. Replace them with your own; results update as you type. Nothing you enter leaves your browser.

23.976, 24, 25, 29.97, 30, 50, 59.94 or 60.

Results

Timecode base
24 frames per timecode second
Frames in the spot length
720
Last frame of the spot
00:00:29:23
Timecode of the frame count (non-drop)
00:00:59:22
Real time of the frame count
59.977 seconds
Difference, wall clock minus timecode
0.060 seconds

At fractional rates such as 23.976 and 29.97, non-drop timecode counts whole frames, so it drifts from the wall clock by 0.1%. Broadcast at 29.97 often uses drop-frame timecode, which skips frame numbers (not frames) to stay in step with the clock.

Edits, renders and delivery specs all count in frames, while briefs and media plans count in seconds. Timecode sits between the two, and at fractional frame rates such as 23.976 and 29.97 it does not quite match the clock. This calculator converts between seconds, frames and timecode at the common frame rates and shows how far non-drop timecode drifts from real time.

How to use it

  • Frame rate. 23.976, 24, 25, 29.97, 30, 50, 59.94 or 60 frames per second. Use the rate of the project or the deliverable, not a rounded version of it.
  • Spot length, in seconds of timecode. The length as the timeline counts it, such as 30 for a 30-second spot.
  • Frame count to convert. Any number of frames, for example from a render log or an edit decision list.

How the calculation works

  • Timecode base = the frame rate rounded to a whole number (23.976 counts as 24, 29.97 as 30, 59.94 as 60).
  • Frames in the spot length = seconds x timecode base.
  • Last frame of the spot = that frame count minus one, written as timecode. Counting starts at 00:00:00:00, so the last frame of a 30-second spot is one frame short of 00:00:30:00.
  • Timecode of a frame count (non-drop) = whole timecode seconds, written as hours, minutes and seconds, plus the remaining frames.
  • Real time = frames / the actual frame rate.
  • Difference = real time minus frames / timecode base. At whole-number rates it is zero.

The worked example

Example (fictional). Suppose the Orlenna Ridge Bottle edit runs at 23.976 instead of the planned 24 fps. The timecode base is 24 frames per timecode second, so the 30-second spot is 720 frames and its last frame is 00:00:29:23.

A count of 1,438 frames reads as 00:00:59:22 in non-drop timecode. At 23.976 those frames take 59.977 seconds of real time, so the clock is 0.060 seconds ahead of the timecode.

23.976 and 24 are different rates

23.976 is shorthand for 24 slowed by 0.1 percent (exactly 24 x 1000 / 1001 frames per second). Timecode at both rates counts 24 frames per second, so a 23.976 project and a 24 project show the same timecode for the same frame count, but the 23.976 one plays 0.1 percent longer. The gap is 0.060 seconds in the example and 3.6 seconds over an hour.

Mixing the two in one timeline can lead to drift against the sound, or a frame repeated or skipped to correct it. Choose one rate in the production plan, set every camera, render and edit to it, and check that it matches the delivery spec.

Non-drop and drop-frame timecode

Non-drop timecode gives every frame a number in sequence. At whole-number rates (24, 25, 30, 50, 60) it matches the clock exactly. At fractional rates it falls behind the clock by 0.1 percent, which is the difference this calculator shows.

Drop-frame timecode was designed for 29.97 video so that timecode stays in step with the clock. It removes no frames. It skips frame numbers: at 29.97, the numbers 00 and 01 are skipped at the start of every minute, except minutes evenly divisible by ten. Apple’s QuickTime documentation gives the example: timecode jumps from 00:00:59:29 to 00:01:00:02. That is 108 numbers skipped per hour, which at 30 numbers per second is the 3.6 seconds non-drop loses. Drop-frame timecode is usually written with a semicolon before the frames, as in 00:01:00;02. It is also used at 59.94; 23.976 projects use non-drop timecode.

This calculator shows non-drop timecode only. For a 29.97 drop-frame deliverable, the frame counts and real times are still correct, but the timecode labels after the first minute will differ from what your editing system shows in drop-frame mode.

Limits

  • Frame counts are whole frames. Fractions of a frame in the spot length are rounded.
  • The calculator does not convert between rates (for example 24 to 25 for a PAL broadcaster), which changes running time or needs frame rate conversion.
  • Whether a destination wants drop-frame or non-drop, and which rate, is set by its delivery spec. Broadcast at 29.97 often uses drop-frame. Check each spec rather than assuming.

Seconds from the script timing calculator become frames here, and frames feed the render time calculator. Frame rate and timecode are fixed in post-production and recorded for each file in the deliverables; the delivery specs checklist includes frame rate for every destination.

Name the frame rate your placements need when you send a brief, and the production plan will set it for the whole job.