Runway's API Adds Enhance Frame Rate, Converting Video Up to 120 fps for $0.05 Per 10 Seconds

Runway's developer API can now convert existing video to as much as 120 fps with a new model, Enhance Frame Rate.

Runway listed Enhance Frame Rate in its API changelog on September 17, 2026. The model, enhance_frame_rate, does not get its own endpoint. Developers call the existing POST /v1/video_upscale route and set the model name.

Enhance Frame Rate converts a video to a target of 24, 25, 30, 48, 50, 60 or 120 fps. It also accepts three fractional broadcast rates, written 23_98, 29_97 and 59_94 for 23.98, 29.97 and 59.94 fps. Inputs can run to 300 seconds per job.

Billing is 1 credit per 2 seconds, charged per second of input, according to Runway's API pricing page. Runway sells API credits at $0.01 each, as of September 19. A 10-second clip therefore costs 5 credits, or $0.05 (10 / 2 = 5 credits x $0.01), and a maximum-length 300-second job costs 150 credits, or $1.50. The pricing page lists one rate for Enhance Frame Rate whatever the target, so a 120 fps conversion is billed the same as a 25 fps one.

Runway's API reference lists three required fields: videoUri, targetFramerate and model. There is no text prompt.

The other video model on that endpoint is far pricier. Runway bills its Magnific video upscaler per output frame, at $0.007 a frame for 720p or 1K, and the pricing page's own example puts a 10-second, 30 fps clip at 210 credits, or $2.10. The two do different jobs: Magnific adds resolution, while Enhance Frame Rate changes cadence.

Enhance Frame Rate is the third post-production update in Runway's changelog in a week. Ruby, the SDR-to-HDR converter that reached the Runway API on August 20, 2026, began preserving a source video's alpha channel on September 11, for sources such as ProRes 4444 and WebM with alpha. On September 12, Ruby's ACEScg EXR sequences were rebuilt so they are referenced to the source plate. Ruby is billed at 20 credits per second, or $0.20, and double that when the source is larger than 4 megapixels.

Now, one caveat: Runway's changelog, pricing page and API reference describe what Enhance Frame Rate outputs, not how it behaves on difficult footage. AlphaSignal, which describes the model as frame interpolation that synthesizes in-between frames, notes that Runway has not documented any scene-cut detection and that no independent benchmarks exist yet. AlphaSignal suggests splitting long footage at shot boundaries before processing; the 300-second cap already forces a split for anything over five minutes. AlphaSignal's sample request also spells the rate field targetFrameRate, where Runway's reference uses targetFramerate.

If the output holds up on fast motion, Enhance Frame Rate could give creators a cheap way to conform 24 fps generations to 25, 29.97 or 59.94 fps delivery specs without a local tool.

Enhance Frame Rate is available now to Runway Dev accounts through POST /v1/video_upscale with model set to enhance_frame_rate; credits are bought in Runway's developer portal at $0.01 each.