other

Timecode to Frame Calculator

Video editors and post-production professionals regularly need to pinpoint exact frames using timecode references. This tool translates the standard timecode notation—hours, minutes, seconds, and frames—into absolute frame numbers based on your project's frame rate. Whether you're working at 24 fps for cinema, 30 fps for broadcast, or 60 fps for high-speed work, the conversion accounts for all time components in a single calculation.

Last updated: April 26, 2026

Creators Mateusz Mucha, BEng

Reviewers Krishna Nelaturu and Jasmine J. Mah

7,614 people find this calculator helpful

Understanding Timecode Format

Timecode appears in nearly every professional video project as a four-part identifier: HH:MM:SS:FR. The segments represent hours, minutes, seconds, and frames beyond the integer second mark. For example, 00:15:42:07 means 15 minutes, 42 seconds, and 7 additional frames from the video start.

Unlike clock time, the frames component doesn't reset at 60—it resets at your project's frame rate. In a 24 fps timeline, frames count from 0 to 23; at 30 fps, from 0 to 29. This structure makes it straightforward to reference any single frame unambiguously, which is essential when collaborating across editing suites or marking precise edit points.

Frame Rates and Visual Perception

Frame rate determines how many still images display per second, directly affecting perceived motion smoothness. Common rates include:

24 fps — Cinema standard; natural, film-like motion
25 fps — PAL video standard in Europe and Asia
29.97 fps — NTSC video standard in North America (often rounded to 30)
60 fps — Broadcast sports and high-motion content

Higher frame rates capture more motion detail, which matters for slow-motion playback and fast-action sequences. The choice affects not only how your footage looks but also how many frames you'll accumulate across a given duration. A one-hour video at 24 fps contains 86,400 frames; the same duration at 60 fps holds 216,000 frames.

Timecode to Frame Number Conversion

The conversion multiplies the total elapsed time in seconds by the frame rate, then adds the remaining frames specified in the timecode:

Frame Number = (Hours × 3,600 + Minutes × 60 + Seconds) × Frame Rate + Frames

Hours — Number of hours in the timecode (0–23 typical)
Minutes — Number of minutes within the current hour (0–59)
Seconds — Number of seconds within the current minute (0–59)
Frame Rate — Frames per second (fps) of your video project
Frames — Individual frames beyond the current second (0 to frame rate minus 1)

Common Conversion Pitfalls

Watch out for these frequent mistakes when translating timecode to frame numbers.

Frame offset boundaries — Remember that frames reset at the frame rate boundary. At 30 fps, valid frame values are 0–29. Entering 30 or higher will produce an incorrect result. Some timecode displays round to the next second automatically, so verify your source.
Non-integer frame rates — NTSC video runs at 29.97 fps rather than exactly 30. Using 30 instead of 29.97 accumulates significant errors over long durations—a full 86 frames of drift per hour. Use the precise rate your editing software reports.
Counting from zero versus one — Frame numbering starts at frame zero, not frame one. A timecode of 00:00:00:00 points to the very first frame (frame 0), not frame 1. This distinction matters when matching frame numbers across different systems or spreadsheets.

Practical Example

Suppose you're working on a 24 fps project and need to locate the frame corresponding to timecode 00:12:35:18.

First, convert time to seconds: (0 × 3,600) + (12 × 60) + 35 = 755 seconds.

Multiply by frame rate: 755 × 24 = 18,120 frames.

Add the extra frames: 18,120 + 18 = 18,138.

At 24 fps, the timecode 00:12:35:18 lands on frame 18,138. This frame appears roughly 12.5 minutes into your sequence, and you can now jump directly to it in your editing software or reference it in notes.

Frequently Asked Questions

What does the FR component of a timecode represent?

The frames portion (FR in HH:MM:SS:FR) counts individual video frames within the current second. Its range depends on your frame rate. At 24 fps, it spans 0–23; at 30 fps, 0–29. These frames represent the fractional part of a second. For instance, in <code>00:05:12:15</code> at 24 fps, the :15 means 15 individual frames past the 5-minute, 12-second mark—equivalent to 0.625 seconds beyond that point.

Why do projects use 29.97 fps instead of exactly 30 fps?

The 29.97 rate originated in the 1950s when American television shifted from black-and-white to color. Engineers reduced the frame rate by 0.1% to maintain synchronization with color subcarrier frequencies. This awkward standard persists in NTSC regions today. Modern capture and playback equipment handles it transparently, but timecode calculations must use the precise 29.97 value, not 30, to avoid drift that accumulates to significant frame errors across longer content.

Can I convert frame numbers back to timecode?

Yes, the reverse process divides the total frame number by the frame rate to get elapsed seconds, then breaks that into hours, minutes, and seconds. The remainder when dividing by the frame rate gives you the excess frames. For example, frame 18,138 at 24 fps yields 755.75 seconds, which equals 0 hours, 12 minutes, 35 seconds, and 18 frames—the same as our previous example in reverse.

How many frames fit into a standard eight-hour workday at 24 fps?

Eight hours contains 28,800 seconds (8 × 3,600). Multiplying by 24 fps gives 691,200 frames. At 30 fps, that same workday captures 864,000 frames. These numbers demonstrate why frame-based projects can accumulate enormous file sizes; video data bandwidth compounds quickly over extended durations.

What if my editing software reports a different frame count than my calculator?

Double-check three things: the frame rate (ensure it matches exactly, including .97 decimals if applicable), whether timecode starts from 00:00:00:00 or 01:00:00:00 (some systems offset by one hour), and whether the software rounds or displays drop-frame timecode. Drop-frame timecode skips certain frame numbers to keep timecode aligned with wall-clock time in NTSC, which complicates calculations compared to standard non-drop-frame notation.

Why does cinema use 24 fps when broadcast uses 30 or 59.94 fps?

Cinema adopted 24 fps as a minimum frame rate for smooth motion perception while minimizing film stock consumption and projection costs. Broadcast video adopted higher rates to align with electrical line frequency standards (60 Hz in North America, 50 Hz in Europe) and to provide better motion resolution for fast-action content. Both standards remain in use today because converting between them introduces quality loss and complicates post-production pipelines.

More other calculators (see all)

Pi Attenuator Calculator ASCII Converter Calculator Op-Amp Gain Calculator CBM for Shipping Calculator Crosstalk Calculator GPA Calculator TV Mounting Height Calculator Numbers to Letters Converter Calculator