Runway Enhance Frame Rate: 10 target rates, 300 s, vs Sume

Runway's Enhance Frame Rate (enhance_frame_rate) converts a video to a target frame rate on POST /v1/video_upscale, accepts inputs up to 300 seconds, and costs 1 credit per 2 seconds of input. Sume has no model of that name. The nearest control is the output.fps field on Video trim, which accepts 24, 25, 30 or 60 and costs $0.02 per job.

Runway facts here come from its models page and pricing page, read 2026-10-02. Sume facts come from the Video trim doc. Neither page says how the new frames are produced, so this post compares inputs, limits and price only.

Which target frame rates does Runway accept?

The models page says the required targetFramerate is one of 24, 25, 30, 48, 50, 60, 120, 23_98 (23.98 fps), 29_97 (29.97 fps) or 59_94 (59.94 fps), and that the same endpoint also hosts the Magnific video upscaler.

At 1 credit per 2 seconds and $0.01 per credit, a 60-second clip is 30 credits ($0.30) and a 300-second clip is 150 credits ($1.50). Those totals are arithmetic on the pricing page, not a Runway quote.

How do I set an output frame rate on Sume?

Send the clip to POST /v1/video-trim with precision: "exact" (the default) and an output object. The doc calls output a conform on the way out; fps takes 24, 25, 30 or 60, width and height take 256 to 2160, and output with precision: "keyframe" is refused with video_trim_output_requires_exact.

The source must be a media.sume.com clip, so import an outside file first with POST /v1/media-imports. An Idempotency-Key header is required.

curl -X POST https://api.sume.com/v1/video-trim \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: fps-30-001" \
  -d '{
    "video_url": "https://media.sume.com/artifacts/artf_demo/talk.mp4",
    "start": 0,
    "duration": 8,
    "output": { "fps": 30 }
  }'

Which rates does Sume not cover?

If you need 48, 50, 120 or the 23.98, 29.97 and 59.94 rates, Sume's trim field does not list them, so those rates stay on Runway's endpoint. If you only need to bring a clip to 24, 25, 30 or 60 before a Timeline, the trim field covers it for a flat $0.02 a job.

Check the result. The Video trim doc does not describe motion synthesis, so view a sample of your own footage before you rely on a 24 to 60 conversion for fast action.