Frames to Timecode Calculator — Both Ways

Editors count frames; clocks count seconds; timecode is the treaty between them. Enter a frame count and a frame rate to get the timecode — or enter a timecode to get the frame count. This calculator converts both directions, non-drop-frame, exactly.

Counting in Two Currencies at Once

A frame count is a pure integer — the Nth picture since the beginning — while a timecode HH:MM:SS:FF is that integer written in a mixed-radix notation: frames roll into seconds at the frame rate, seconds into minutes at 60, minutes into hours at 60. Conversion is therefore division with remainders, carried out in the right order: total seconds = frames ÷ fps (integer part), the leftover frames are the FF field, and the seconds decompose into hours, minutes and seconds. The system exists because film and video are addressed by it — every edit decision list, every subtitle, every "cut at 00:41:07:12" is a mixed-radix address — and because humans schedule in clock units while machines store in frames. This calculator is the exchange office, in both directions, at the five frame rates that cover nearly all production.

Worked Example: Ninety Thousand Frames

The defaults run a round production number: 90,000 frames at 30 fps. Seconds: 90,000 ÷ 30 = 3,000 exactly, decomposing to 50 minutes, no remainder — the timecode reads 00:50:00:00, a clean halfway through a typical programme hour. Run it backwards (choose the other direction, enter 00:50:00:00) and the accumulation ((0×3600 + 50×60 + 0) × 30) + 0 returns the same 90,000 — the round trip is exact, as a sane notation demands. The note's side-figures are the ones editors actually quote: an hour at this rate is 108,000 frames, and one frame is 33.3 milliseconds — the quantum of all cutting, short enough that a two-frame error is a blink, long enough that a twelve-frame error is a visible stumble in a music cut.

The Drop-Frame Confession

This calculator is honestly non-drop-frame, and the exception must be named: NTSC broadcast's true rate is 29.97 fps, not 30, so counting at 30 drifts about 3.6 seconds per hour against the wall clock. Broadcast's repair is drop-frame timecode, which skips frame numbers (never actual frames) — two numbers at the start of most minutes — to keep the notation honest with the clock. Drop-frame is a numbering convention with its own arithmetic, used in broadcast deliverables at 29.97 and 59.94; for film (24), PAL (25), and the web's true 30/60, the non-drop arithmetic on this page is exact. Knowing which regime a production lives in is the professional's first question, and any timecode handed over without its rate and its drop status is only three-quarters of an address — this page makes you specify the rate precisely so the answer can be exact.

Timecode's Other Life: The Studio Clock

The same HH:MM:SS:FF addresses synchronise machines that never touch pictures: in audio studios, timecode (as MTC or LTC) locks sequencers, tape machines and lighting desks to one master count, so a note, a lyric projection and a strobe can share an address — and the frame remains the quantum although no camera is present, because the notation's installed base outlived its origin. Theatre automation cues, broadcast playout and museum installations all rent the same addressing, for the same reason the EDL survives: an unambiguous, human-readable, machine-countable address for moments is a technology too useful to retire. This calculator converts the address's two currencies; the address itself is one of media's quiet universal standards, hiding inside every "at 00:41:07:12" ever spoken on a set. Learn to convert fluently and a dozen adjacent crafts — subtitling, conforming, cueing, archiving — become dialects of one language you already speak.

Animation and the Tyranny of the Frame Count

Animators meet this conversion as a budget: a 90-minute feature at 24 fps is 129,600 frames, and a studio rendering or hand-drawing "on twos" (one drawing per two frames) still owes 64,800 drawings — the arithmetic that decided, for a century, how much motion a production could afford. The frame is animation's atom of labour the way it is editing's atom of address, and shot lengths are still quoted in frames on production floors ("the shot is 214 frames") because frames, unlike seconds, are the unit work is assigned in. This calculator's 90,000-frame example is, in that dialect, a modest sequence. The mixed-radix timecode dresses the count for the clock; the count itself is where the money lives — a truth every producer who has approved a frame budget learns in their bones. Render farms bill it, animators are assigned it, and archivists multiply it by a per-frame file size (the hub's Image File Size arithmetic) to learn what a restored feature will weigh before a single frame is scanned.

Related Tools

More from the Other Calculators hub: the Time Lapse Calculator — frames by the thousand, priced in storage — and the Image File Size Calculator, since every frame in this count is one of those ledgers.

Frequently Asked Questions

Why does the frame field never reach the frame rate itself?

Because the FF field is a remainder: at 30 fps, frames 0–29 live inside one second and frame 30 is the next second's frame 0 — exactly as seconds 0–59 live inside a minute. A timecode reading :30 in the FF field at 30 fps is malformed for the same reason 00:00:75:00 is malformed in the seconds field, and editing software will reject or silently normalise it. The calculator's conversion can never produce such a reading, and its reverse direction is where malformed inputs are caught: if your FF meets or exceeds the rate, add the carry yourself — the true frame count is unchanged, only its notation was untidy.

What frame rate should I use for online video today?

The rate the material was shot and edited at — conversion between rates is a rendering decision (with interpolation artefacts), not a notation decision. Most web-native production is true 30 or 60 (or 24 for the film look), where this page's non-drop arithmetic is exact; material originating in NTSC broadcast at 29.97 wants the drop-frame discussion in the section above before its timecodes are trusted against a clock. The calculator's five rates cover the honest cases; when a client says "thirty" about legacy broadcast footage, the follow-up question is this page's whole reason for existing.

How are subtitles and captions timed, exactly?

In timecode (or in milliseconds, its decimal cousin) — each caption carries an in-point and an out-point addressed exactly as this page computes, and reading-speed rules (characters per second) then decide how long a caption must stay. A two-second caption at 30 fps spans 60 frames, and the conversion between the subtitler's HH:MM:SS:FF and the player's frame counter is this arithmetic, run millions of times a day by streaming infrastructure. When subtitles drift against dialogue after a frame-rate conversion, the cause is almost always a rate assumption — 29.97 counted as 30, say — compounding quietly at 0.1% per hour of programme.

What is an EDL and why does it care so much?

An edit decision list is the edit as text: a sequence of timecode in-points and out-points from named reels, sufficient to rebuild the cut in any suite. It is the industry's oldest interchange format, and it is nothing but this page's two currencies in columns — source timecodes, record timecodes, durations in frames. Conform artists (who rebuild offline edits at full resolution) live inside these conversions, and a one-frame systematic error — a rate misread at ingest — is the classic conform disaster, discovered at the worst possible hour. Exact conversion is not pedantry in that world; it is the job.

Can timecode run past 24 hours at all?

The notation can (hours are unbounded in this calculator's arithmetic), but broadcast timecode traditionally wraps at 24:00:00:00, and programmes are usually addressed from a 01:00:00:00 start (the "hour one" convention that keeps leaders and bars in hour zero). Feature work often starts at 01:00:00:00 per reel. The calculator follows the mathematics rather than the convention — enter frames for a 26-hour count and it will print 26:00:00:00 without complaint — and the conventions are noted here so that a 01:00:00:00 programme start is recognised as an offset to subtract, not an error to fix. Studios state their house convention on the slate for exactly this reason: the address is useless if its zero is a rumour.

How accurate is a frame as a unit of speech timing, really?

At 25–30 fps a frame is 33–40 ms, and phonemes run 30–100 ms — so lip-sync tolerances (broadcast allows roughly ±1 frame before viewers sense error, and standards specify tighter) are denominated in exactly this page's quantum. Dubbing and ADR are frame crafts: the actor watches the timecode, the engineer nudges by frames, and the calculator's reverse conversion (a line's timecode address into a frame offset) is the nudge's arithmetic. It is a pleasing thought that an integer and a mixed-radix notation, properly converted, are what stand between a film and its audience believing a voice belongs to a face. Every craft that rents time by the frame — dubbing, subtitling, conforming, playout — is downstream of this one conversion being done exactly, at the stated rate, with the drop-frame question asked and answered before the arithmetic begins.