Free tool · runs in your browser

Time to Frames Converter

Enter a duration as HH:MM:SS or HH:MM:SS:FF SMPTE timecode and pick a project framerate — the converter returns the exact total frame count, with the unrounded decimal shown whenever rounding is happening.

Time

Total frames

1,798

60.000 s × 29.970 fps = 1798.200 frames (rounded)

Fractional framerates (23.976, 29.97, 59.94) produce non-integer frame counts when the duration isn't aligned to a frame boundary — editors round to the nearest whole frame, and so does this converter. Leave the Frames field at 0 if you're entering HH:MM:SS wall-clock time; set it for SMPTE non-drop HH:MM:SS:FF input.

How to use this tool

  1. 01

    Enter the time

    Standard HH:MM:SS or SMPTE HH:MM:SS:FF.

  2. 02

    Pick the framerate

    Match your source material.

  3. 03

    Use the frame count

    For animation work, frame-accurate scripting, or scrubbing.

Why this matters

Anyone working in motion graphics, VFX, or frame-accurate editorial has to translate seconds into frames constantly — After Effects, Nuke, Houdini, and most scripting languages measure time in frames, not seconds, so keyframe offsets, expression-driven timing, and EDL hand-offs all want integer frame numbers. Getting the math wrong by a single frame in a 30 fps project lands an animation cue a frame early or late, which is visible on every cut and sync point, and silently doing the wrong multiplication (× 30 instead of × 29.97) on an NTSC project drifts your timeline by 3.6 seconds per hour.

This converter handles both wall-clock HH:MM:SS and SMPTE HH:MM:SS:FF input, supports the full NTSC family plus 120 fps and a custom rate, and shows both the rounded integer count and the exact decimal so you can see when rounding is happening. Pair it with the Frames to Time Converter for the inverse direction, and the Frame Extractor when you actually need to pull the pixels at the frame index you've computed.

Related tools

FAQ

Fractional framerates like 23.976 and 29.97 fps aren't whole numbers, so when your input time isn't aligned to a frame boundary the literal math (seconds × fps) gives a non-integer answer — one minute at 29.97 fps is exactly 1,798.2 frames. Editing software always rounds to the nearest whole frame because the codec can't store half a frame; this converter shows you the rounded count and exposes the exact decimal so you can spot when rounding is happening. If you need an integer-accurate count, switch to a project framerate that divides your time cleanly (24, 25, 30, 50, 60, 120).

Explore the full toolkit

94 free tools covering titles, tags, thumbnails, scripts, captions, embeds, schema, and in-browser video processing.

Browse all tools →