Runway will conform your shot for a penny a second

A generated shot can look finished and still be turned away at the door. The color holds, the motion reads, the cut works, and then a delivery spec asks for 25 frames per second and the file says 24, and the whole thing goes back down the corridor. That number has nothing to do with taste or craft. It is the last piece of plumbing between a piece of AI footage and a broadcast slot, and until this week the fix meant leaving your edit for Topaz, Resolve or a plugin chain and hoping the retime did not smear the motion.

What Runway actually shipped

On 17 September Runway shipped Enhance Frame Rate, a model that takes an existing video and converts it to a target delivery rate without leaving the platform. It works on footage that was never generated on Runway, and its own developer changelog lists ten targets: 24, 25, 30, 48, 50, 60 and 120, plus the fractional broadcast rates 23.98, 29.97 and 59.94. The company's news post lists a shorter set and calls out NTSC's 59.94 by name. Input is capped at 4K resolution and five minutes, source resolution is held through the conversion, and for developers calling it in code, through Runway's API, it runs on the existing video upscale endpoint with the model id enhance_frame_rate.

The number worth writing down

The pricing is the part to write down. Runway charges one credit per two seconds of video, and it says so twice, on the news post and in the developer changelog: the rate does not move with resolution or with the target frame rate. API credits are a cent each, which puts a 60 second clip at about 30 cents and the five minute ceiling at about $1.50. Because the meter runs on the input, a 24 to 25 conform and a 24 to 120 conform cost exactly the same, which is the opposite of how per-output-frame tools price the same job, including Runway's own Magnific video upscaler sitting on that same endpoint. If you are budgeting a finishing pass, that single fact does more work than anything else in the announcement.

The claim nobody has tested

What we cannot check is the comparison Runway leads with. The company says the model runs up to seven times faster and three times cheaper than other interpolation models, with higher output quality, and it names no comparator, publishes no benchmark, no methodology and no sample beyond a 38 second demo clip. As of today there is no independent test of this model anywhere: no trade coverage, no reviewer, no side by side against Topaz Video AI, Resolve optical flow or the open interpolation models people already run locally. The only third-party write-up we could find is an API aggregator blog restating the changelog, and it concedes the same gap. Treat the speed, cost and quality line as an unaudited vendor claim until somebody runs it against Apollo on the same footage.

There is a smaller stretch in how the launch is being described, including in our own working title. Runway's production paragraph scopes the model to any generated video up to 4K and five minutes, which sits awkwardly beside a headline promise of any video at all. Five minutes is a clip ceiling, not a program. This conforms shots.

Broadcast QC has notes about buttons like this

Runway pegs the feature to the UK's 25 fps broadcast standard, and in substance that checks out, though the word to avoid is mandated in the legal sense. ITV's AS-11 delivery specification requires 1080i/25 for HD and 2160p/25 or 50 for UHD. It is a delivery requirement a broadcaster enforces, not a statute.

Read further into that same document and the story gets more interesting than the announcement. AS-11 does not only ask for a number, it asks how you arrived at it. Frame rate conversion must be agreed with the broadcaster in advance, and it is permitted only provided the conversion does not produce excessive motion judder, image softening or visible frame blending. An interpolation model is precisely the process that gets looked at under that clause. So the button now exists, and the quality control standard it is aimed at has notes about buttons like it. Nothing in Runway's materials says whether this is true motion-compensated interpolation or a blend, how it handles interlaced sources or pulldown, or whether Content Credentials survive the conversion. Those are the questions a delivery engineer will ask first, and right now the answer sheet is blank.

Runway keeps shipping post, not generation

A pattern is forming in what Runway ships. Ruby, its SDR to HDR model, landed on 20 August and reached Tool Mode with outside footage on 31 August. Premiere Pro and After Effects plugins followed on 8 September. Frame rate conform arrived on 17 September. None of those are generation features. They are finishing features, the unglamorous middle of a post workflow, and they are being built for footage that did not come out of Runway at all. Curiously, this launch is missing from the consumer changelog, whose newest entry is still the Adobe plugins, and it does not appear on the published credit table either, so what a conform costs inside a subscription plan rather than on the API is still unknown.

What this means if you are finishing a short

For anyone cutting an AI short with a festival or a broadcaster in mind, the practical read is this. Most text to video models still generate at 24 fps natively and interpolate anything faster on export, so a retime step was always coming; having it priced by the second, in the same place as the rest of your shots, removes a real errand. Do the conform once, at the end, on your locked cut rather than shot by shot, keep the 24 fps masters, and put the converted version in front of whoever is going to run QC before you commit a whole film to it. If a broadcaster is in the chain, mention the conversion early, because AS-11 says you have to. And if you can put a genuine before and after through it against Topaz, publish the frames. The one number nobody has yet is the one Runway is claiming.

Timeline

• Date: 20 Aug 2026. Event: Runway Ruby, an SDR to HDR model, ships on Pro and higher plans; Source: runway.com/changelog
• Date: 31 Aug 2026. Event: Ruby reaches Tool Mode and accepts footage from outside Runway; Source: runway.com/changelog
• Date: 8 Sep 2026. Event: Runway plugins for Premiere Pro and After Effects ship; Source: runway.com/changelog
• Date: 17 Sep 2026, 16:18 UTC. Event: Runway posts the announcement with a 38 second demo; Source: x.com/runwayml
• Date: 17 Sep 2026. Event: News post published, model live in product and on the developer API; Source: runway.com/news
• Date: 17 Sep 2026. Event: Developer changelog entry: enhance_frame_rate, 10 target rates, 300 second cap, 1 credit per 2 seconds; Source: docs.dev.runwayml.com
• Date: 18 Sep 2026. Event: Still no trade coverage and no independent benchmark; Source: searches run this date
• Date: 30 Sep 2026. Event: Runway AI Summit, San Francisco, possible follow-on news; Source: runway.com