Frames to Timecode Calculator
Break a frame count into hours, minutes, seconds and remaining frames at an integer frame rate.
How the result changes
Only total frames changes; all other inputs stay at your current values. Each dot represents one whole-number input. This is not a forecast of real-world outcomes.
About this calculation
Frames to Timecode Calculator: Break a frame count into hours, minutes, seconds and remaining frames at an integer frame rate. Enter total frames, frames per second; the reported quantities are hours (hours), minutes (minutes), seconds (seconds), remaining frames (frames). The equations and examples below show how those inputs lead to the result and where the model's assumptions matter.
Formula
total whole seconds = floor(frames / fps); remainder frames = frames mod fps
Worked example
With Total frames: 90000 frames, Frames per second: 25 fps, hours is 1 hours.
Method and inputs
Divide the total frame count by integer frames per second to obtain elapsed whole seconds. Split those seconds into hours, minutes and seconds. The remainder from dividing the original frame count by fps is the final frame component.
Worked example
At 25 fps, 90,000 frames equal 3,600 seconds, so the components are 1 hour, 0 minutes, 0 seconds and 0 remaining frames. At 90,012 frames, the final component would be 12 frames.
At 25 fps, adding 13 frames to the 90,012-frame example would carry its 12-frame remainder to a full second, yielding 01:00:01:00. This carry behavior is why the last component ranges from zero through 24 rather than zero through 25.
How to read the result
Read the four numeric outputs together as HH:MM:SS:FF, adding leading zeroes manually when writing a timecode. A one-frame increment advances the final component until it reaches fps, then carries into the seconds component.
A 29.97-fps recording cannot be represented accurately by entering 30 as though it were the physical playback rate for long durations. Drop-frame timecode skips selected frame labels to keep clock labels aligned with elapsed time; it never discards actual video frames.
Assumptions and checks
This is non-drop-frame counting at an integer frame rate. Broadcast rates such as 29.97 fps and drop-frame timecode require different numbering rules and are intentionally outside this form. The starting frame is treated as zero.
Do not enter a fractional frame rate into this integer-fps model. A media player’s displayed timecode can differ if it uses one-based frame numbering or drop-frame labels. Distinguish elapsed real time from a labeling convention.
Common questions
What does the frames to timecode calculator calculate?
It decomposes a whole number of frames into four numeric timecode components under non-drop-frame assumptions.
When should I recalculate or check another method?
Recalculate if the footage is conformed to another frame rate. For SMPTE drop-frame workflows, use a dedicated timecode conversion that handles skipped labels at the specified nominal rate.
Inputs
- Total frames (frames)
- Frames per second (fps)