Runway Enhance Frame Rate: 300 s cap and credits vs Sume fps
Runway's Enhance Frame Rate takes inputs up to 300 seconds at 1 credit per 2 seconds. Sume's Timeline sets output.fps to 24, 25, 30 or 60. Compared.
Runway's Enhance Frame Rate accepts inputs of at most 300 seconds and bills 1 credit per 2 seconds. On Sume you set output.fps to 24, 25, 30 or 60 on a Timeline 1.0 render, or omit it to match the sources.
Runway's numbers are from its API changelog entry dated September 17th, 2026 (read 2026-09-30). Sume's are from the Timeline docs. For the 60 fps angle alone, see the 60 fps alternative.
What are the two limits side by side?
| Item | Runway Enhance Frame Rate | Sume Timeline 1.0 |
|---|---|---|
| Target rates | 24, 25, 30, 48, 50, 60, 120, 23.98, 29.97, 59.94 | 24, 25, 30, 60 |
| Input length | At most 300 seconds | audio.duration_seconds 1 to 1800 s |
| Billing unit | 1 credit per 2 seconds | Per Timeline render; see API pricing |
| Default rate | You choose a target | Matches the sources if omitted |
Does Timeline interpolate new frames?
No. The docs say a rate that differs from a source's is met by repeating or dropping a frame every few frames, which causes judder on motion. Sume reports this as the warning output_fps_resamples_sources, with the rate the sources wanted. If you need synthesized in-between frames, Timeline is not that tool.
When is Timeline the right fit?
When the frame rate is one step in a larger render: joining clips, trimming, fades, or an audio spine. Callers never send filtergraphs or codecs; the server compiles ffmpeg on the worker. For a one-call trim plus conform example, see trim and conform a clip.
How do I stay under a 300-second input cap?
Split the source into segments of 300 seconds or less before sending it to Runway, and rejoin them after. On Sume the Timeline length limit is 1800 seconds, so a long edit can be conformed in a single document.
Sources
Related posts
More in Developers
- Rough cut from a script by API: one scene per Timeline slot
Descript Quick Design splits a script into moments with changing visuals. With Sume you map each scene to a Timeline video slot over a voiceover spine yourself.
- Search footage for a spoken phrase with an API: words with timing
DaVinci Resolve 21 lists IntelliSearch. To find a spoken phrase in a clip by API, transcribe with video inspect and search words[] in your own code.
- Seedream image URL expired after 24 hours: use the Sume copy
BytePlus keeps Seedream image URLs for 24 hours, then clears them. On Sume, read data[].url or the job result URL and store that, not a provider link.
- Create vs read rate limits: Managed Agents 300/1,200, Sume plans
Anthropic's Managed Agents limit creates and reads separately. Sume splits its per-minute budget the same way by plan, so polling cannot starve submits.
Written by Sume