Frame counts for 5 minutes at 25, 30, 48, 60 and 120 fps

How many frames is a 5-minute clip at each Runway Enhance Frame Rate target? The math, plus why Sume's video_frames cap of 24 stills makes it a sampling tool.

4 min readSume
All posts

A 5-minute clip is 300 seconds, so the frame count is 300 times the rate: 7,500 frames at 25 fps, 9,000 at 30, 14,400 at 48, 18,000 at 60, 36,000 at 120 and about 17,982 at 59.94. Those are the Enhance Frame Rate targets listed by Runway's changelog, up to 5 minutes. Sume's Video frames tool pulls at most 24 stills per call, so it samples a clip and does not export every frame.

What are the counts?

This is arithmetic, not a measurement of any tool. Doubling the rate doubles the frames the model or filter must produce.

Frames in a 300-second clip. Rates from the Runway changelog, read 2026-10-02; counts are arithmetic.
Target fpsFrames in 300 sRatio to 30 fps
257,5000.83x
309,0001.00x
4814,4001.60x
59.9417,9821.998x
6018,0002.00x
12036,0004.00x

Can Sume export all those frames?

No. Video frames takes one media.sume.com clip of up to 300 seconds and either an at list of 1 to 24 times or an fps value of at most 2, which is also capped at 24 frames. It returns durable image files, jpeg by default or png, with a max_edge of 16 to 2160. It is unbilled. It is meant for stills such as covers, checks and contact sheets.

How many frames can I sample for a check?

With fps 2 on a 12-second window you get 24 stills. Use trim first to pick the window, then sample. Spreading 24 values over a full 300 seconds gives one still about every 12.5 seconds.

Why does the frame count matter?

It sets the size of the job. A 120 fps conversion of 5 minutes means 36,000 frames in the output. Plan storage and delivery accordingly, and check that your downstream player handles the rate. Sume's own output.fps stops at 60.

How do I check the rate of a finished file?

Run the Video inspect probe with frames set to false and read fps and duration_seconds. Multiply them to get the expected frame count. If the number is far from what you planned, the file was resampled or trimmed somewhere. The probe is unbilled and takes one call for a source of up to 1800 seconds. Sume's docs list the exact limits and error codes for each call, so read the page for the endpoint you use before you build on it, and keep a short note of which limits applied to your run, so a later change is easy to spot. If a call is refused, the error code names the cause, and fixing that one input is usually enough to retry safely with the same Idempotency-Key.

Sources

Related posts

More in Developers

All Developers posts

Written by Sume