Frames, seconds, and why frame rate runs your video
Video is a sequence of still images shown fast enough that the eye perceives motion, and frame rate — frames per second, or fps — is the speed of that sequence. It controls how smooth motion looks, how large files become, and how much time any given number of frames occupies. A clip of 300 frames at 30 fps lasts 10 seconds; the same 300 frames at 24 fps last 12.5 seconds; at 60 fps they last just 5. Every editing decision, from trimming a clip to syncing audio to exporting for a platform, depends on converting between frames and seconds at the project's frame rate. This calculator performs that conversion both ways in spirit — frames to seconds for planning edits, and seconds to frames when you plan in time — so you can think in whichever unit the task at hand demands.
Frame rate also shapes the feel of footage in ways beginners underestimate. Twenty-four fps carries the familiar motion blur of cinema and feels filmic; 30 fps looks clean and televisual; 60 fps looks hyper-real and is preferred for sports and gaming, where fast motion must stay sharp; 120 fps and beyond enable smooth slow motion when played back at lower rates. Choosing a rate is therefore an aesthetic decision as well as a technical one, and mixing rates carelessly — 24 fps footage on a 30 fps timeline, for example — creates judder that audiences notice even when they cannot name it. Convert first, choose deliberately, and keep the project timeline at one rate throughout.
How the calculation works
Divide frames by frames per second to get seconds: seconds equals frames divided by fps. Minutes are seconds divided by 60. That is the entire formula, and its simplicity is deceptive, because the errors come not from the maths but from the inputs. The frame rate must be the timeline's rate, not the camera's recording rate — slow-motion footage shot at 120 fps but played on a 30 fps timeline advances at 30 fps, so a 300-frame slow-motion clip occupies 10 timeline seconds, not 2.5. Similarly, variable-frame-rate phone footage can report a nominal rate that differs from its true average, which is why professional workflows convert phone footage to a constant rate before editing. Get the fps right and the conversion is exact; get it wrong and every edit point drifts.
Timecode adds a wrinkle worth understanding. Professional timelines display time as hours, minutes, seconds, and frames — 00:01:12:15 means 1 minute, 12 seconds, and 15 frames — and converting between timecode and total frames requires multiplying out each unit at the project rate. Drop-frame timecode, used for 29.97 fps broadcast, further complicates the display by skipping numbers to keep timecode aligned with real time, though no actual frames are dropped. For most creators, the frames-to-seconds conversion in this calculator covers daily needs; timecode matters when you deliver broadcast files or collaborate with editors who reference specific frame numbers.
Reading your results
| Frames | At 24 fps | At 30 fps | At 60 fps |
|---|---|---|---|
| 300 frames | 12.5 seconds | 10 seconds | 5 seconds |
| 1,440 frames | 60 seconds | 48 seconds | 24 seconds |
| 90 frames | 3.75 seconds | 3 seconds | 1.5 seconds |
Worked example: 300 frames at 30 fps is exactly 10 seconds, or 0.17 minutes. A longer 1,440-frame clip at 24 fps is exactly 60 seconds, or 1 minute — the length of a full cinematic minute. A short 90-frame cut at 30 fps is 3 seconds, or 0.05 minutes, which is about the length of a quick reaction shot. And a zero-frame clip at any rate is zero seconds — the edge case that confirms the formula behaves at its limits. Notice how the same frame count means very different durations at different rates: frame counts are meaningless without the fps attached, which is why editors always state both together.
Choosing the right frame rate
Match the rate to the destination and the content. Social platforms accept 30 and 60 fps widely; cinema distribution expects 24; sports and gaming content benefits from 60. Shooting higher than delivery — 60 fps footage delivered at 30 — gives you the option of smooth half-speed slow motion, because every second of delivery can draw on two seconds of captured frames. Shooting lower than delivery forces frame duplication and judder, which is why you should never shoot 24 fps for a 60 fps deliverable. File size also scales with frame rate: all else equal, 60 fps footage contains twice the frames of 30 fps and needs roughly twice the storage and encoding effort. Higher is not better by default; it is a trade of smoothness against size, and the right choice is the lowest rate that serves the content.
Practical editing tips
- Set the timeline rate before importing anything, and convert mismatched footage to it first.
- For slow motion, shoot at a multiple of the delivery rate — 60 for a 30 timeline, 120 for a 60 timeline.
- Count cuts in frames when precision matters: a 6-frame difference at 30 fps is a fifth of a second, enough to change a joke's timing.
- When syncing audio, align by frames, not by seconds rounded to whole numbers, to avoid drift over long clips.
- Export at the timeline rate; re-encoding to a different rate after editing degrades motion quality.
From calculation to craft
Frame-rate fluency pays off in the edit room in small, constant ways. Knowing that 12 frames at 24 fps is half a second lets you trim with confidence; knowing that a 3-second gap needs 90 frames at 30 fps lets you plan B-roll precisely; knowing that your 10-second intro at 60 fps is 600 frames lets you budget rendering time honestly. The calculator handles the arithmetic, but the craft is in choosing rates deliberately, keeping timelines consistent, and remembering that behind every second of video is a countable number of still images, each one earning its place in the motion you see. Convert carefully, shoot intentionally, and the maths will disappear into footage that simply looks right.
Audio sync and the shutter connection
Frame rate does not only govern pictures; it governs sound sync and motion feel through its relationship with shutter speed. Audio is recorded continuously, while video is sampled in frames, so sync depends on both sharing the same timeline rate — a clip edited at the wrong rate drifts out of sync gradually, by a frame here and there, until lip movement visibly mismatches speech. The fix is the same discipline as before: one timeline rate, all footage converted to it before editing, and audio aligned by frame numbers rather than by rounded seconds. For long recordings such as interviews, even a small rate mismatch accumulates: a 0.1 percent drift over an hour is nearly four seconds, which is unwatchable. Professionals therefore treat rate consistency as a sync requirement, not a cosmetic preference.
Shutter speed interacts with frame rate through the 180-degree rule: the shutter should typically stay open for about half the frame duration, giving 1/48 second at 24 fps and 1/60 second at 30 fps. This produces the natural motion blur audiences expect; a much faster shutter gives crisp but stuttery motion, while a much slower shutter smears movement. When you raise the frame rate for slow motion, keep the shutter proportional — 1/120 second at 60 fps preserves the same blur character that 1/60 gives at 30 fps. Understanding this relationship helps you choose rates on set, not just in the edit: the rate sets the duration maths this calculator performs, and the shutter sets how each of those frames looks. Together they decide whether your footage feels cinematic, televisual, or hyper-real, and getting both right is what separates footage that looks professional from footage that merely plays.