Runway Enhance Frame Rate 59.94 fps vs Sume's 60 fps output

Runway's changelog lists 59.94 fps as one of the Enhance Frame Rate targets. Sume does not offer 59.94: Timeline 1.0 output.fps accepts 24, 25, 30 or 60, and Video trim accepts the same four values for its output fps. Sume also has no 120 fps output and no frame interpolation step.

The difference matters if you deliver to a broadcast chain that expects NTSC-style rates. Nothing in Sume's docs describes a 59.94 setting, so treat 60 as the nearest value and not as a substitute for a 59.94 master.

What does Runway list, and what does Sume list?

Runway's changelog entry for Enhance Frame Rate, dated 2026-09-17, says it is available on Max+ plans, works on any video, whether Runway-made or not, and targets 25, 30, 48, 60, 120 or 59.94 fps, up to 4K and 5 minutes. The table puts that next to the values Sume's docs list for output frame rate.

What happens if I ask Sume for a rate it does not list?

Timeline render accepts 24, 25, 30 or 60 and refuses other values. If you omit output.fps, the render matches the sources instead. When the output rate differs from a source's rate, Sume meets it by repeating or dropping frames and reports output_fps_resamples_sources. That is a plain resample, so motion can judder; it does not synthesize in-between frames.

Is 60 fps close enough to 59.94?

The two rates differ by about 0.1 percent. For web and social delivery that is usually invisible. For a deliverable that a broadcaster checks against a spec, it can be a rejection reason, and that decision is yours to make against their spec, not something Sume can settle. If you need a true 59.94 file, you would need a tool that lists it, such as Runway's Enhance Frame Rate.

What should I do with a Sume clip that needs a higher rate?

Check the probe first: Video inspect with frames set to false returns fps, width, height and duration without billing. If the clip already has the rate you want, you are done. If you want a smoother result than a resample, run the rate change in a tool that interpolates, then bring the file back into your edit. Sume's part is the probe, trims and timeline assembly around it.

What does the Sume side cost?

Video trim is $0.02 per job and Timeline render is $0.10 per output minute, rounded up, per the pricing in Sume's catalog. The probe is unbilled.

How do I decide which rate to deliver?

Start from where the video will play. Web players and social apps handle 24, 25, 30 and 60 fps without trouble, and those are the four rates Sume writes. Broadcast and some festival specs name 59.94 or 23.976, and those need a tool that lists them. Ask the recipient for the spec in writing before you convert, since a re-export costs time even when the tool is cheap.