Timecode to Frame Number Calculator

What a timecode represents

A non-drop-frame timecode is commonly written as hours, minutes, seconds, and a frame number within the current second. The last component is not another unit of time that can be added to seconds directly; it is a position inside the selected frame-rate interval.

The conversion formula

First convert all complete hours, minutes, and seconds into whole seconds. Multiply that total by the frame rate, then add the remaining frame number. The result is a zero-based frame index when the first frame of the timeline is index 0.

Zero-based versus one-based answers

Editing software and programming interfaces often number the first frame as zero. Human-facing reports sometimes call that same image frame one. Both values are shown so a handoff does not silently shift a cut by one frame. The one-based count is always the zero-based index plus one.

Worked example

For 00:08:35:13 at 24 frames per second, the complete time is 515 seconds. Multiplying 515 by 24 gives 12,360 frames before the current second, and adding 13 gives zero-based index 12,373. Counting from one gives 12,374.

Why frame rate changes the answer

The timecode components identify the same clock position, but each second contains a different number of frames at 24, 25, or 30 frames per second. A conversion is therefore incomplete without the project frame rate. Keep the frame-rate value beside any exported or copied result.

Drop-frame and non-drop-frame limits

Drop-frame timecode is a labeling convention used with some nominal rates to keep clock labels aligned with elapsed time. This calculator deliberately uses simple constant-rate arithmetic and does not emulate a particular broadcast standard. Check the editing system’s project setting before using the value in a conform or broadcast workflow.

Variable frame rate is different

A phone recording or screen capture can vary its frame timing. In that case, multiplying elapsed seconds by one constant rate may not identify the stored frame that a media parser reports. Use the file’s metadata or an editor’s own frame-count view when variable-rate media matters.

A practical handoff checklist

Record the source clip, timecode, frame rate, whether the timecode is drop-frame, the starting offset, and the indexing convention. Then compare the calculator result with the receiving application on a short known clip. This separates arithmetic errors from project-setting differences.

Read the four components as positions

Hours, minutes, and seconds describe complete elapsed time before the current frame. The final frame component identifies a position inside that second, starting at zero. At 24 frames per second, the valid frame positions are 0 through 23; frame 24 belongs to the next second and is not a valid value for the current second.

This distinction matters when a person reads a timecode as though it were a decimal timestamp. The label 00:00:00:13 at 24 frames per second means thirteen frames after the beginning of the first second, not thirteen seconds or thirteen twenty-fourths written as an arbitrary fraction. The calculator keeps the components separate so the boundary is visible.

Derive the index from complete seconds

The conversion first forms complete seconds as hours multiplied by 3,600, plus minutes multiplied by 60, plus seconds. It then multiplies that total by the constant frame rate and adds the zero-based frame position. In symbols, index = (((hours × 60 + minutes) × 60 + seconds) × frame rate) + frame.

For 00:08:35:13 at 24 frames per second, the complete time is 515 seconds. The 515 completed seconds account for 12,360 frames, and the current position adds 13, producing index 12,373. The one-based count is 12,374 only because a human count starts the first frame at one.

Boundary examples catch off-by-one errors

At 24 frames per second, 00:00:00:00 maps to zero-based index 0 and one-based count 1. The last valid frame in the first second, 00:00:00:23, maps to index 23 and count 24. The next second begins at 00:00:01:00 and maps to index 24, not index 25.

Test a conversion with both the first and last frame of a second before trusting a long timeline result. If a handoff differs by exactly one frame, check whether one system uses an index and the other uses a human count. If it differs by many frames, check frame rate, offset, and drop-frame settings first.

Frame rate is part of the meaning

A timecode such as 00:01:00:00 is a label, not a complete frame identity without the project rate. At 24 frames per second it maps to 1,440 frames; at 25 it maps to 1,500; at 30 it maps to 1,800. The clock label is the same while the integer frame position changes.

Store the frame-rate value with a frame index in filenames, edit notes, subtitles, or code. A bare integer such as 1,800 is ambiguous because it can represent a different elapsed time under another rate. The calculator makes this dependency visible for a clean media handoff.

Non-drop-frame and drop-frame labels

Non-drop-frame arithmetic treats every labeled frame as part of a constant count. Drop-frame timecode is a labeling convention used with some nominal rates to keep the displayed clock closer to real elapsed time; it does not mean that video frames are physically removed. The skipped labels follow a standard pattern that depends on the rate and convention.

This calculator intentionally does not emulate a broadcast drop-frame standard. If an editing project uses drop-frame, use the application’s own conversion or a standard-specific tool and document the exact rule. Do not feed a drop-frame label into simple arithmetic and assume the resulting index is a compliant broadcast timecode.

Starting offsets change the frame identity

The formula assumes the supplied timecode starts at the first frame of the timeline. A reel, sequence, camera card, or nested composition may begin at a nonzero start timecode. In that case, the same visible label can refer to a different absolute frame position depending on the source offset.

Record whether the value is relative to a clip, sequence, reel, or program. If an offset must be applied, calculate the local index first and then add the documented offset in frames under the same rate and numbering convention. The page does not infer hidden offsets because they belong to the media project, not to the four displayed fields.

Variable-frame-rate media needs metadata

A constant-rate formula assumes each frame interval is the same. Phone footage, screen recordings, and some web captures can use variable frame timing, so elapsed wall-clock time and stored frame number do not have a fixed one-to-one relationship. A timecode label generated by an application may also be a presentation choice rather than a raw-file index.

For variable-rate media, inspect the container metadata or ask the editing application for the frame at the requested timestamp. Use this calculator for a clearly stated constant-rate worksheet and label the boundary. A simple formula is valuable when its model is explicit; it is misleading when it silently stands in for a media parser.

Frame index and frame count serve different readers

Programmers commonly use a zero-based index because the first array element is position zero. Editors, reviewers, and production notes may use a one-based count when saying first frame, second frame, or frame 12,374. Neither convention is universally correct; the important step is naming it in the handoff.

If a cut, subtitle, or effect is specified by frame number, write zero-based or one-based next to the number. When converting between them, add or subtract exactly one and do not change the frame rate. This small label prevents a visually subtle off-by-one error from moving a cut or caption.

Use the result in an edit decision list

An edit decision list may identify source and record in/out points, transitions, and timecode format. A frame index from this worksheet can help verify one position, but it does not create a complete EDL. Reel names, source timecode, record timecode, rate, and drop-frame flags still belong to the project record.

For a conform, compare the calculator result with the receiving system on a short clip and note the exact frame displayed at the in point. If the applications disagree, stop and reconcile their timebase or offset rather than compensating by eye. A repeatable numeric check is safer than shifting a cut until it appears close.

Captions and animation have the same boundary

A subtitle cue, animation pose, or audio marker can be attached to a frame index. The timing will be consistent only if the frame rate, start offset, and indexing convention match the playback or editing system. A one-frame difference can be perceptible in a fast cut even though the timestamp looks nearly identical.

Keep the calculated index and the original timecode together in production notes. The original label helps a human find the point; the index helps software compare positions. If a platform converts the media to another rate, recalculate or use the platform’s timebase rather than carrying the old index unchanged.

Long timelines and numerical safety

The calculator accepts large hour values, but a project can still impose practical limits on frame counts, integer types, or application formats. A long timeline at a high rate may exceed a spreadsheet’s preferred precision even though the arithmetic is conceptually simple. Check the receiving software’s supported range before using an extremely large result.

When a result is copied into code, preserve it as an integer type that can hold the expected frame count. Do not round a frame index or use a floating-point approximation for an exact edit position. The displayed decimal timing can be useful for a human, while the index should remain an exact integer.

A reproducible conversion record

Save the source identifier, hours, minutes, seconds, frame, frame rate, drop-frame status, start offset, and zero- or one-based convention. Include both the calculated index and the original timecode. Another editor should be able to reproduce the value without asking which project setting was assumed.

For the worked example, record 00:08:35:13, 24 frames per second, non-drop-frame arithmetic, local start offset zero, index 12,373, and one-based count 12,374. The explicit record is more useful than a screenshot of a number with no timebase or labeling context.

Validate against a known frame

Choose a short clip with a clearly identifiable first frame and compare the calculator with the editing application at the beginning, at a second boundary, and at the requested timecode. This validates the arithmetic and exposes a hidden offset or rate mismatch. Do not validate only one middle point, because an offset can make one accidental match look convincing.

If the application uses drop-frame, variable rate, or a nested sequence, record that fact and use the application’s standard-specific result. The calculator remains a useful constant-rate reference, but the project’s metadata controls the production truth.

What this calculator cannot convert

The worksheet does not decode a media file, identify a codec, interpret an edit decision list, infer a start offset, implement a broadcast drop-frame standard, or locate a frame in variable-rate footage. It also does not convert between timecode systems whose labels have different standard rules.

Those limits are intentional. The tool answers one clear question: under constant non-drop-frame arithmetic, which integer frame position corresponds to these components and this rate? When a production system has additional metadata, carry that metadata into the next step instead of treating the simple answer as the complete media identity.

Final timecode checklist

Before handing off the result, confirm the frame rate, valid frame range, minute and second boundaries, drop-frame status, start offset, source or sequence context, and indexing convention. Check the first frame and a second boundary against the receiving application. Preserve the original timecode beside the integer index.

If the result differs by one, inspect zero-based versus one-based counting. If it differs by many, inspect rate and offset. If the media is variable-rate or broadcast-specific, use a standard-aware application or tool. A precise frame number is useful only when its timebase and scope are named.

Treat timecode as a labeled coordinate

A timecode is a coordinate in a media timeline, not a universal timestamp. The same displayed label can refer to a different frame under another rate, start offset, reel, sequence, or drop-frame rule. When a timecode leaves the editing application, carry the project context with it. A bare value such as 00:08:35:13 is readable but incomplete as a technical identifier.

This is why the calculator shows the rate and the zero-based result together. It gives a precise answer for a declared model while making the missing context visible. That habit helps editors, developers, students, and reviewers ask the right follow-up question before a frame is used in a cut, caption, or automated process.

Test hour and minute rollovers

Most errors appear at boundaries rather than in the middle of a timeline. At 24 frames per second, the last frame before one minute is 00:00:59:23 and the first frame of the next minute is 00:01:00:00. The same principle applies at the hour boundary. Test the rollover values when building a spreadsheet, parser, or post-production handoff.

Use the calculator as a reference case for unit tests: first frame, last frame of a second, first frame of a minute, last frame of an hour, and a normal interior point. A result that passes only the worked example may still contain a minute-to-second or frame-range mistake.

Frame rate can be integer or project-specific

This worksheet accepts an integer frames-per-second value, which suits straightforward constant-rate calculations such as 24, 25, or 30. Real production systems may use nominal rates, fractional rates, or display conventions that require a standard-specific formula. Do not silently round a fractional project rate to an integer and call the result exact.

If the project rate is 23.976, 29.97, or another fractional value, confirm how the application stores timebase and frame duration. The displayed timecode may still use a familiar whole-number label while the underlying clock and frame count follow a different rule. Record the exact project setting before choosing a conversion method.

Drop-frame is a naming rule, not deleted media

Drop-frame timecode skips selected labels to keep a nominal clock aligned more closely with elapsed time. It does not remove pictures from the video. The skipped-label pattern is tied to a particular timebase and standard, so a generic correction is unsafe. A non-drop-frame result from this page should be labeled as such.

If a broadcast, caption, or delivery specification requires drop-frame, use a tool that implements that specification and verify it against the receiving system. Keep the original label, frame rate, drop-frame flag, and resulting index in the handoff. The calculator’s simple arithmetic remains useful as a comparison, not as a replacement for the standard.

Starting timecode and absolute frame are separate

A sequence can begin at 01:00:00:00, a camera reel can have a source offset, and a nested composition can inherit a parent timeline. In each case, a local frame index may be correct while an absolute program frame is different. Decide whether the requested answer is local to the clip or absolute to the program before converting.

Apply offsets only when they are documented in the same rate and numbering convention. Do not add a timecode offset as though it were a decimal number. Convert the offset to frames or use the editing application’s source and record fields, then preserve both local and absolute identifiers in the record.

Captions and markers need a timebase

Subtitle cues, chapter markers, visual effects, audio events, and review comments often use timecode. A marker copied between projects can move if the frame rate or start offset changes. Keep the marker’s original timecode and add the project timebase beside it. If the delivery platform re-encodes the video, inspect how it maps the cue to its new timeline.

For frame-accurate captions, validate the first and last frame of a cue in the target player or authoring tool. A one-frame shift can change whether a subtitle appears during a shot or on the transition. The calculator helps explain the integer position, while the caption standard and playback system control the final behavior.

Editing decisions need in and out semantics

An in point may be inclusive while an out point may be exclusive, depending on the application and interchange format. Two frame indices can therefore describe a duration differently even when the visible labels look adjacent. State whether the range includes both endpoints, includes the in point only, or follows the receiving tool’s convention.

For example, a clip from index 100 through index 123 contains 24 frames when both endpoints are included. If the out point is exclusive, the range may be written as [100,124). Use the project’s documented convention rather than assuming a generic subtraction answers every edit-duration question.

Long projects need integer-safe records

At high frame rates and long durations, the frame count grows quickly. Keep the index as an exact integer in spreadsheets, databases, and code, and avoid formatting it with thousands separators if a system expects a machine-readable value. The human-facing report can show both a grouped number and a plain numeric field.

If a workflow crosses software boundaries, test a large but representative value and check for rounding, signed-integer limits, or floating-point conversion. A timecode may look valid after import even when the underlying frame number was truncated. Preserve the source value and the receiving-system validation result.

A reproducible media handoff

A good handoff includes project or clip name, source identifier, original timecode, frame rate, drop-frame status, start timecode, local or absolute scope, zero- or one-based convention, calculated index, and the receiving application. If the media uses variable frame timing, attach the relevant metadata or a frame-accurate export instead of relying on this constant-rate worksheet.

This record answers why two people might see different results and gives them a short path to resolve it. It also makes a future review possible when the edit has moved to another workstation or when the same marker must be recreated in a new sequence.

A small validation matrix

For a production check, create rows for 00:00:00:00, the final frame before a second, the first frame after the boundary, the worked example, and one long-timeline value. Columns can include expected zero-based index, expected one-based count, application result, and notes. This simple matrix exposes off-by-one errors and hidden offsets faster than comparing one screenshot.

Repeat the matrix if the rate or timecode convention changes. Keep it with the project documentation and update it when the editing application changes. The goal is not to create bureaucracy; it is to make a frame-accurate decision explainable to the next person who touches the media.

Related questions after conversion

Visitors who calculate a frame index often need duration in frames, frame-to-timecode conversion, video storage size, bitrate, caption timing, or edit-range duration next. Descriptive internal links to those related tools help the visitor continue the task with the same vocabulary. The links should explain the next decision rather than simply display a long list of unrelated calculators.

A learning path can also move from time units to frame rate, then to storage and delivery planning. This turns a single conversion into a useful media lesson for students and a practical checklist for editors. Keep the current rate and source context in the visitor’s notes when opening the next page.

Know when not to use the simple formula

Do not use the result as a file decoder, a variable-frame-rate index, a drop-frame broadcast answer, an EDL generator, a caption compliance check, or proof that two applications share the same start offset. Those tasks require metadata or a standard-aware implementation. A concise limitation is part of a reliable technical answer.

When a project is high stakes, verify the result inside the target application and retain the project settings. If the application disagrees, investigate the timebase and range semantics before applying a manual adjustment. A guessed correction may make one marker look right while moving every other marker.

Final timecode handoff

The most useful output is an exact frame index with a named rate and convention, not an isolated number. Add the original label, source scope, offset, drop-frame status, and validation note. If the question is educational, show the unit conversion; if it is production work, show the receiving-system check.

Once the record is complete, link the visitor to the next relevant calculation—frame duration, video size, or edit range—and invite them to preserve the assumptions. A timecode answer becomes durable when another person can reproduce it and knows exactly when the simple model should be replaced.