Runway Enhance Frame Rate API: what Sume offers instead

Sume has no frame-interpolation feature, so it is not a like-for-like replacement for Runway's Enhance Frame Rate. What Sume can do is conform a clip to 24, 25, 30 or 60 fps with output.fps, and the Timeline docs say a rate that differs from a source's is met by repeating or dropping frames. That changes the file's rate; it does not invent new in-between motion.

Runway's changelog describes Enhance Frame Rate, dated Sep 17 2026, as converting any video "to 25, 30, 48, 60, 120 or 59.94 fps, up to 4K and 5 minutes long", on the Max+ plan. This page reads only that entry and does not describe how Runway does it.

What frame rates does each side list?

Sume's numbers are from the Timeline and video trim docs; Runway's are from its changelog entry.

What does Sume do when the rate changes?

Per the Timeline docs, an omitted output.fps renders at the rate the sources already run at. A rate that differs from a source's is met "by repeating or dropping a frame every few frames", and the job reports output_fps_resamples_sources. The docs call that judder on motion. Both tools are worker ffmpeg only, with no provider model involved.

The video filter docs describe the allowlisted filters as tone, blur, geometry, fade and internal compositing, so a motion-interpolation pass is not documented there either.

What does it cost on Sume?

Timeline is $0.10 per output minute, rounded up. Video trim is $0.02 per job. Both docs tell you to confirm the rate live in GET /v1/catalog.

How do I get a 60 fps file from Sume today?

For one clip, send POST /v1/video-trim with output: { "fps": 60 }; the conform works only with precision: "exact", the default. For several clips, set output.fps on the Timeline render. Both read only your workspace's media.sume.com files, so import first. Neither route takes a rate outside 24, 25, 30 and 60, so 48, 120 and 59.94 from Runway's list are not available.

Before you convert, run a free frames: false inspect probe to see what the clip is now. There is no point converting a clip that already runs at your target rate.

When is Sume's conform enough?

When you need a delivery spec, such as a platform that wants 30 or 60 fps, and smoother motion is not the goal. If you want the extra frames to look like real motion, that is the job Runway describes, and Sume does not document an equivalent. Setup for the Sume route is in convert a video to 60 fps with an API, and the wider set of size and rate tools is in [change a video's frame rate or resolution.