Creator & media

Video frame-rate and duration calculator

Compare frame conforming with duration-preserving frame-rate conversion.

Your numbers

Calculated on your device. Your inputs aren’t sent to us.

Your result

Ready when you are

Enter your inputs and select Calculate.

Report an issue

Try it, understand it

Explore the result

Compare playback conforming in both directions. The first result keeps the modeled source frame count; the separate duration-preserving result answers a different question.

Worked example comparison
ExampleOutputWhat to notice
24 fps played at 30 fpsConformed duration at target frame rate8 secondsThe 240 modeled frames play in 8 seconds. The same frames are played faster.
30 fps played at 24 fpsConformed duration at target frame rate12.5 secondsThe 300 modeled frames play in 12.5 seconds. The same frames are played more slowly.
No frame-rate changeConformed duration at target frame rate10 secondsAt 30 fps to 30 fps, the modeled duration remains 10 seconds.

Check your understanding

Before checking: can a conversion keep both every frame and the same duration when the rate changes?

Not in this simple constant-rate model. Keeping all frames and changing playback rate changes duration. Keeping duration requires a different output frame count.

Does this modify my video file?

No. It compares arithmetic scenarios. Actual transcoding, frame interpolation, audio treatment and variable frame timing require an appropriate video tool.

Behind the numbers

How this calculation works

Playing the same modeled frame count at another rate changes duration. Preserving duration instead requires a different output frame count. These are different operations, so both scenarios are shown.

THE FORMULAFrames = source fps × source seconds; conformed seconds = frames ÷ target fps

A worked example

A 60-second source at 24 fps models 1,440 frames. Playing those at 30 fps takes 48 seconds; preserving 60 seconds at 30 fps requires 1,800 frames.

Good to know

Arithmetic only, without video upload or transcoding. Fractional-rate, variable-rate and drop-frame timecode conventions require their own interpretation.

A little curiosity

Changing the playback rate and preserving duration are different operations

A modeled 1,440-frame sequence lasts 60 seconds at 24 fps. Play the same frames at 30 fps and they take 48 seconds. Keep the duration at 60 seconds instead and a 30 fps output needs 1,800 frames.

Those scenarios answer different editing questions. The first changes the time assigned to a fixed frame count; the second needs a conversion strategy such as repeating, dropping or generating frames. This calculator does not perform that strategy.

Video file size depends on total bitrate and duration, not frame count alone. A frame-rate change does not specify an encoding bitrate.

A displayed decimal frame rate can be a rounded shorthand

Some production rates are ratios such as 30,000/1,001 rather than the decimal 29.97 exactly. For a more precise arithmetic scenario, enter enough decimal digits to represent the intended rate appropriately.

This tool works in seconds and numeric frame rates. It does not parse drop-frame timecode, variable-frame-rate timestamps or upload media. Fractional modeled frame counts signal that an actual edit needs a frame-boundary convention.

A few questions, answered

Will it return a converted video file?

No. It is a planning calculator for durations and frame counts, not a transcoder.

Why can the two scenarios show different durations?

They preserve different things: one keeps the source frames, while the other keeps elapsed time.

Find your calculator

Start typing to explore the library.