Frame Rate Calculator
Convert between frames and time at any frame rate: frames to duration, duration to frames, or the same footage between two frame rates.
Frames to time answers “how long is 150 frames at 30 fps”. Time to frames answers the reverse. The third option remaps a frame count from one rate to another.
The frame rate of the footage. Used as the source rate in all three modes.
Used by “Frames to time” and “Convert between frame rates”.
Used by “Time to frames”. Decimals are fine, for example 2.5 for two and a half seconds.
Only used by “Convert between frame rates”. The frame count is scaled so the duration stays the same.
Frame rate is one of those quiet numbers that controls how motion looks, how long footage lasts and how big files get. It simply counts how many still images, or frames, appear every second. A film at 24 frames per second shows 24 pictures each second. A phone video at 60 shows 60. The number itself is small, but everything in video math flows from it: durations, timecodes, conversions between standards, and storage estimates all start with frames per second.
The arithmetic is straightforward once you see the pattern. Frames divided by frame rate gives seconds. Seconds times frame rate gives frames. And converting footage from one frame rate to another scales the frame count while the duration stays fixed. These are the three conversions people actually need, whether they are editing a video, syncing audio, programming an animation or answering a homework question about film. A Frame Rate Calculator does the division for you and presents the answer the way video people expect: seconds, minutes, hours and timecode.
This guide covers what frame rate means, the standard rates you will meet in the wild, the three core conversions with the formulas behind them, how timecode works, and the rounding issues that trip people up. You will find worked examples with concrete numbers and answers to the fifteen questions that come up most often. No production jargon is required; if you can divide, you can follow everything here.
What Frame Rate Actually Measures
Frame rate, written fps, is the number of individual frames displayed or captured per second. Each frame is a single still image. Show them fast enough in sequence and the human eye perceives smooth motion, an illusion called persistence of vision that kicks in somewhere around 12 to 16 frames per second. Below that, motion looks like a flickering slideshow. Above it, motion looks continuous, and higher rates look progressively smoother.
The key insight for calculations is that fps is a rate, exactly like miles per hour. Just as distance divided by speed gives time, frames divided by fps gives seconds. That single relationship, seconds equals frames divided by fps, is the foundation of every conversion in this guide. Flip it around and frames equals seconds times fps. Everything else is presentation.
The Standard Frame Rates You Will Meet
A handful of rates dominate real footage. 24 fps is the cinema standard, the look of movies for nearly a century. 25 fps is the television standard in much of Europe and Asia, tied to 50 Hz power systems. 30 fps is the television standard in North America and the default for much online video. 50 and 60 fps are used for smoother broadcast and sports. 120 fps and above are high frame rate territory, used for slow motion: shoot at 120, play back at 30, and motion stretches to quarter speed.
Older formats add quirks. NTSC color television actually runs at 29.97 fps rather than exactly 30, a historical oddity from adding color to broadcasts in the 1950s, and that is why video professionals deal with drop-frame timecode. For everyday conversions, though, the whole numbers above cover nearly everything you will meet, and this calculator works with all of them.
Conversion One: Frames to Time
Given a frame count and a frame rate, the duration in seconds is frames divided by fps. So 150 frames at 30 fps is 150 divided by 30, which is 5 seconds. 72 frames at 24 fps is 72 divided by 24, which is 3 seconds. From seconds you can go anywhere: divide by 60 for minutes, format as hours and minutes for long durations, or express as timecode.
Timecode deserves a moment because it is how editors talk about positions in footage. Written HH:MM:SS:FF, it gives hours, minutes, seconds and the frame number within the current second. At 30 fps, 150 frames is 5 seconds exactly, written 00:00:05:00. At 24 fps, 100 frames is 4 seconds and 4 frames, written 00:00:04:04. The frame counter after the last colon always runs from 0 to fps minus 1, then rolls over into the next second.
Conversion Two: Time to Frames
The reverse direction multiplies instead of dividing: frames equals seconds times fps. A 10 second clip at 24 fps contains 240 frames. A 2.5 second animation at 60 fps needs 150 frames. This is the calculation animators and motion designers do constantly, because animation software thinks in frames while directors think in seconds.
Watch the rounding. Real durations are rarely whole numbers of frames. 1 second at 24 fps is exactly 24 frames, but 0.1 seconds at 24 fps is 2.4 frames, and there is no such thing as 0.4 of a frame in a finished file. You must round to a whole frame, which nudges the actual duration slightly. At 2.4 frames you would use 2 frames, giving an actual duration of 2 divided by 24, or about 0.0833 seconds. For single clips the difference is invisible, but across a long timeline of many small roundings it can accumulate, which is why editors sometimes work at higher precision internally.
Conversion Three: Between Frame Rates
Converting a frame count from one rate to another keeps the duration fixed and rescales the frames. The formula is new frames equals old frames times new fps divided by old fps. So 150 frames at 30 fps becomes 150 times 24 divided by 30, which is 120 frames at 24 fps. Check: 150 divided by 30 is 5 seconds, and 120 divided by 24 is also 5 seconds. Duration preserved, as required.
This is a pure numbers conversion. Real frame rate conversion of actual video is a separate and harder problem involving dropping or blending frames, but the frame count math is what you need for planning: how many frames a clip will contain after conforming, how long a render will take at a new rate, or how animation keyframes map across standards. When the result is not a whole number, round it, exactly as with time to frames.
Why Small Rounding Errors Matter
Frame math lives at the boundary between continuous time and discrete frames, and that boundary is where errors creep in. A one-frame rounding error at 24 fps is about 42 milliseconds, inaudible and invisible once. But a subtitle file built from rounded timings can drift against the video over an hour. An animation loop whose length was rounded down will visibly jump each cycle. A game running logic at 60 updates per second against a 59.94 Hz display will slowly desync.
The professional habit is to keep full precision through every intermediate step and round only the final frame count. Never round, then feed the rounded number into the next calculation. And when exact sync matters, work in the smallest unit available: frames for video, samples for audio at 48,000 per second, where rounding errors shrink to irrelevance. Precision is cheap in planning and expensive to retrofit.
Worked Example: Frames to Duration
An editor has a clip of 450 frames at 30 fps and wants the duration. Divide: 450 divided by 30 is 15 seconds. In minutes that is 15 divided by 60, or 0.25 minutes. As timecode: 15 seconds is 00:00:15:00, since 450 is an exact multiple of 30. The answer is 15 seconds flat.
Worked Example: Duration to Frames With Rounding
An animator needs frames for a 3.2 second shot at 24 fps. Multiply: 3.2 times 24 is 76.8 frames. Round to 77 frames. The actual duration becomes 77 divided by 24, which is about 3.208 seconds, eight milliseconds longer than asked. For the shot, the difference is imperceptible, and the animator notes the true duration in case it matters for audio sync.
Worked Example: Converting Between Rates
A 240-frame sequence at 24 fps needs conforming to 30 fps. Scale: 240 times 30 divided by 24 is 300 frames. Verify the duration is unchanged: 240 divided by 24 is 10 seconds, and 300 divided by 30 is 10 seconds. The conformed sequence has 300 frames and still runs exactly 10 seconds.
Worked Example: Timecode From a Frame Count
A colorist receives 5,432 frames at 25 fps and wants the timecode. Divide: 5,432 divided by 25 is 217.28 seconds. That is 3 minutes (180 seconds) plus 37.28 seconds, so 3 minutes and 37 seconds with 0.28 of a second left over. Multiply the leftover: 0.28 times 25 is 7 frames. The timecode is 00:03:37:07. Quick check: 3 times 60 plus 37 is 217 seconds, times 25 is 5,425 frames, plus 7 is 5,432. It reconciles.
Frequently Asked Questions
1. What is frame rate in simple terms?
It is how many still images appear every second in a video, animation or game. Higher numbers mean smoother motion. Cinema uses 24, most online video uses 30, and slow motion is shot at 120 or more.
2. How do I convert frames to seconds?
Divide the frame count by the frame rate. 300 frames at 30 fps is 300 divided by 30, which is 10 seconds. That one division is the entire formula.
3. How do I convert seconds to frames?
Multiply the seconds by the frame rate and round to a whole number. 5 seconds at 24 fps is 120 frames. 2.5 seconds at 60 fps is 150 frames.
4. How do I convert frames between two frame rates?
Multiply by the new rate and divide by the old rate: new frames equals old frames times new fps divided by old fps. 150 frames at 30 fps becomes 120 frames at 24 fps, and the duration stays 5 seconds in both.
5. What does 24 fps mean exactly?
Twenty-four individual frames are shown every second. It is the traditional cinema rate, and its slight motion blur is part of what people call the film look. One second of film is always exactly 24 frames.
6. How do I read a timecode like 00:01:30:12?
It reads hours, minutes, seconds, then frames: 0 hours, 1 minute, 30 seconds and 12 frames into the current second. At 30 fps that position is 1 times 60 plus 30 seconds, times 30, plus 12, which is 2,712 frames from the start.
7. Why is NTSC 29.97 fps instead of 30?
When color was added to American television in the 1950s, the rate was shifted slightly to 29.97 to avoid interference between the color signal and the audio. The oddity survives in broadcast standards and in drop-frame timecode, which compensates for it.
8. How many frames are in one minute of video?
Multiply the frame rate by 60. At 24 fps a minute holds 1,440 frames. At 30 fps it holds 1,800. At 60 fps it holds 3,600. Long durations multiply fast, which is why storage math starts here.
9. What should I do with fractional frames?
Round to the nearest whole frame, since frames are indivisible in a finished file. Keep full precision through your working and round only at the end, and note the tiny duration change if exact sync matters.
10. Does a higher frame rate always look better?
Not always. Higher rates look smoother and more lifelike, which suits sports and games, but many viewers find 24 fps more cinematic for drama. Extremely high rates can produce the soap opera effect that makes films look like cheap video.
11. How long is 1,000 frames at 25 fps?
Divide 1,000 by 25 to get 40 seconds. As timecode that is 00:00:40:00, since 1,000 is an exact multiple of 25. In minutes it is 40 divided by 60, about 0.667 minutes.
12. Can frame rate affect file size?
Yes, proportionally. Twice the frames per second means roughly twice the picture data at the same quality settings. That is why high frame rate footage needs faster storage and bigger cards, and why delivery platforms often cap frame rates.
13. What is the difference between fps and refresh rate?
Frame rate is how many frames the content contains per second; refresh rate is how many times the display redraws per second, measured in hertz. A 60 fps video on a 120 Hz screen shows each frame twice. Mismatches can cause judder, which is why matching rates matters.
14. How do animators use frames instead of seconds?
Animation software timelines are marked in frames, so animators plan timing as frame counts: a 12-frame hold at 24 fps is half a second. Converting the director’s seconds into frames is the daily arithmetic of the job, and this calculator does exactly that step.
15. Why do my conversions sometimes drift out of sync?
Usually accumulated rounding. Each rounded frame count is off by a fraction of a frame, and hundreds of small roundings add up. Keep unrounded values through the chain, round once at the end, and for critical sync work in audio samples rather than video frames.