Runway Enhance Frame Rate vs Generate: Interpolation Is a Conform Desk, Not a New Clip

Runway Enhance Frame Rate vs Generate: Interpolation Is a Conform Desk, Not a New Clip

Raising the frame rate does not rewrite the claim. On 17 September 2026, Runway introduced Enhance Frame Rate: a model that converts a video you already have — generated on Runway or not — to a delivery rate such as 25, 30, 48, 60, or 120 fps, including NTSC 59.94, without leaving the platform. ClipCanva is not affiliated with Runway, Canva, VEED, Kapwing, OpenAI, or Google. If you treat interpolation as a second generate pass, you will spend credits smoothing a pack shot whose type was already unreadable, or you will ship a 120 fps file whose spoken line was never signed. Lock the line on the AI script generator, lock the still, generate on the AI video generator or image to video, then conform.

Launch facts (confirmed 19 September 2026)

Source	Public claim	Workflow implication
Runway: Introducing Enhance Frame Rate, 17 Sep 2026	Converts any video (Runway-generated or not) to 25, 30, 48, 60 or 120 fps, including NTSC 59.94. Runs on generated video up to 4K and five minutes. Holds source resolution. Costs one credit per two seconds, regardless of resolution or target frame rate.	This is a conform desk. It retimes a cut you already accept. It does not write VO, lock a SKU, or invent a new shot.
Same Runway news post	Runway says the model runs up to seven times faster and three times cheaper than other interpolation models, with higher output quality. At launch, output options run from 25 to 120 fps; support for additional frame rates is on the way.	Speed and cost vs “other interpolation models” is Runway’s own claim, not an independent bench. Confirm the live selector; do not quote 24 or 50 fps from this page.
Same Runway news post	Paired with Runway Ruby, the SDR-to-HDR model, so a clip can go from first draft to production-ready. Cites UK 25 fps broadcast as a precise spec.	Ruby is HDR. Enhance Frame Rate is fps. Do not merge them into one “make it broadcast” button.
Runway Dev: Available AI Models	Set model to enhance_frame_rate on POST /v1/video_upscale. Required targetFramerate: 24, 25, 30, 48, 50, 60, 120, 23_98 (23.98), 29_97 (29.97), or 59_94 (59.94). Inputs at most 300 seconds. Same endpoint also hosts Magnific video upscale (magnific_video_upscaler_creative, 30-second cap).	The API list is longer than the 17 Sep news list. 300 seconds is five minutes, which matches the news length cap. Do not assume the web app and the API expose the same rates on the same day.
Runway Dev: API Changelog	Changelog section “Enhance Frame Rate on Runway Dev.” Pricing line on the models guide: 1 credit per 2 seconds of input.	Bill against input seconds, not output frame count. That is the opposite of Magnific upscale, which the same docs bill per output frame.
Canva Help: Video clip	Canva AI Video clip: 8-second videos with audio, 6-second videos without. English prompts only. Optional reference image. You cannot manually change in-clip audio.	An 8-second social cut is not a 5-minute conform job. Split first. Interpolating a 6-second silent clip does not add a signed line.
VEED: Script to Video	Describe the video type → customize aspect / presenter / subtitles → type a script or generate one → export. Positions training, walkthroughs, tutorials.	VEED is assembly-from-script. Frame-rate conversion is not on that page. Sign the script before anyone retimes the file.
OpenAI Help: Sora discontinuation	Sora web/app ended 26 April 2026. Sora API ends 24 September 2026.	Do not interpolate a Sora API job you will lose next week and call that a master. Export, then decide whether the file is worth conforming.

Confirm the live Runway control before you quote 24 fps, 50 fps, or “the web app matches the API.” The 17 September news page lists 25, 30, 48, 60, 120 plus 59.94, and says more rates are coming. The Dev models page already lists 24, 50, 23.98, and 29.97 as well. Those are two contracts. Click the one you opened.

What interpolation is — and what a generate desk is not

Surface	What is actually on the public record	What operators often assume	Fail condition
Enhance Frame Rate (Runway news, 17 Sep)	Convert existing video to a target fps; up to 4K, 5 minutes; 1 credit / 2 seconds	A second generate that “fixes” motion, type, and audio	Interpolating a clip whose label you cannot read
enhance_frame_rate (Runway Dev)	Same endpoint as video upscale; 300s cap; extra rates including 23.98 / 29.97 / 24 / 50	One button named “production-ready”	Sending a 31-second Magnific upscale job to an endpoint that only takes 30s for upscale, or mixing the two models
Magnific video upscaler (same Dev endpoint)	magnific_video_upscaler_creative; 30-second inputs; billed per output frame	“Enhance” means fps and resolution	Paying for upscale frames when you only needed 25 fps
Runway Ruby (news + prior ClipCanva note)	SDR → HDR, separate model	HDR and fps are the same pass	Grading HDR before the picture is true
Canva AI Video clip	8s with audio / 6s silent	A place to dump a broadcast conform	One paragraph, one generate, then “make it 60 fps”
VEED script-to-video	Script (typed or generated) → assemble	A clip model with native audio and fps tools	Pasting a Docs outline and calling the export a 25 fps master
Generate desk	Text-to-video or image-to-video on a named model	Interpolation will invent the missing beat	Conforming a shot that never contained the CTA

The useful split is the same one VEED already prints: script first, generate second. Runway’s news page adds a third split: generate (or film), then retime. None of those desks write the legal line for you. In-between frames are predicted pixels. They are not a new take.

Pick the desk before you pick 60 fps

The fail is treating “production-ready” as “generate again, smoother.” A 120 fps file of the wrong product is still the wrong product. A 25 fps UK delivery of a line legal did not approve is still a compliance miss.

Job	Where it actually runs	What you must supply	What the system may invent	Fail condition
Spoken claim, legal line, CTA	AI script generator	Audience, one claim, duration, forbidden words	Extra steps, unearned superlatives	Interpolating first, writing VO later
Pack shot / readable type	Locked still, then image to video	First frame at a resolution you can read	Camera path, warped glyphs	120 fps on a compressed thumbnail
Short campaign or social cut	AI video generator or Canva-class clip desk	Locked caption and/or locked still, crop, seconds	Extra props, a second spoken line	“We’ll smooth it in Enhance” as the brief
Reusable camera language	Prompt ideas	Shot type, lighting, camera, duration	A chat you will lose when the app row changes	Changing five variables, then blaming fps
Model choice when the first desk warps the label	ClipCanva Compare	The same still and the same caption	A new story	Starting over because 60 fps “felt more premium”
Delivery fps (25 / 29.97 / 59.94 / 60 / 120)	Runway Enhance Frame Rate (news + Dev)	A cut you already accept; the spec on the delivery ticket	In-between frames	Conforming a clip you would not ship at 24 fps
Resolution / “make it 4K”	Magnific upscale on the same Dev endpoint, 30s cap — or generate at the resolution you need	A file under that cap	Sharpened artifacts	Upscaling and interpolating in one unreviewed pass
HDR	Runway Ruby, not Enhance Frame Rate	SDR source you already signed	Highlight reconstruction	HDR10 of a claim you never approved
Long source you already filmed	AI video summarizer	The file, the claim you still want	Highlights that skip the disclaimer	Summarizing, generating a new plot, then retiming it

If the brief is “the cut is true; BBC / UK broadcast wants 25,” that is Enhance Frame Rate. If the brief is “the bottle looks cheap, add motion,” that is image-to-video from a locked still. If the brief is “we do not know the line yet,” that is script, not interpolation.

News page vs Dev API vs clip desk vs assembly desk

Dimension	Enhance Frame Rate (Runway news, 17 Sep)	enhance_frame_rate (Runway Dev)	Canva AI Video clip	VEED script-to-video
Official surface	Introducing Enhance Frame Rate	Available AI Models	Canva Help: Video clip	VEED Script to Video
Input	Any video, Runway or not	Video on POST /v1/video_upscale	English prompt; optional still	Video type + script you type or generate
What it changes	Frame rate	Frame rate (targetFramerate)	Generates a new 6s/8s clip	Assembles a video from a script
Documented length	Five minutes / 4K	300 seconds	8s with audio / 6s silent	Whatever runtime you accept after generate
Documented rates	25, 30, 48, 60, 120 + 59.94; more “on the way”	24, 25, 30, 48, 50, 60, 120, 23.98, 29.97, 59.94	Not an fps tool	Not an fps tool
Billing (as published)	1 credit / 2 seconds, any resolution or target	1 credit / 2 seconds of input	Canva AI allowance (see Canva Help)	VEED plan (see VEED checkout)
Do not use it for	Signing the claim	Inventing 24 fps if your UI only lists 25	Writing the shot list	Writing the plot you will defend

Runway’s 18 September unified pricing post says purchased credits become one pool across the web app and Runway Dev for enterprise customers. That is a billing change, not a new generate model. Confirm whether your workspace is on that pool before you assume a web-app interpolate and a Dev interpolate draw from the same invoice.

Workflow: sign the shot, generate once, then retime to the ticket

Write the packet once. Generate on a desk that matches the seconds you will actually publish. Conform last.

1. Put the delivery spec in the packet, not in a hope. Audience, one claim, crop, duration per card, and the fps the ticket actually names (25, 29.97, 59.94, 60, 120). “Make it smoother” is not a spec.
2. Sign the spoken line on a script desk. On the AI script generator, lock audience, one claim, close, duration, and forbidden words. Interpolation does not add a disclaimer you forgot.
3. Split to the next desk’s cap. Canva’s clip desk is 8 seconds with audio or 6 without. Runway Enhance Frame Rate is five minutes. Those are different desks. Park reusable camera language in prompt ideas.
4. Lock a still before motion when type or SKU matters. Send that still to image to video. If there is no still, generate on the AI video generator only after the caption is a shot.
5. Accept the picture at the native rate. If you would not ship the 24 fps (or 8-second) file, do not buy in-between frames. Use ClipCanva Compare when the first desk warps the label.
6. Conform on Enhance Frame Rate after the cut is true. Pick the rate on the live selector. If you are on the API, send enhance_frame_rate with a targetFramerate from the Dev list. Do not send Magnific upscale (magnific_video_upscaler_creative) when you only needed 25 fps — different cap, different bill.
7. HDR is a later desk. Ruby is the SDR-to-HDR model Runway names next to this launch. Grade after fps only if the delivery asks for both. Do not HDR a social cut that will be crushed to 8-bit Rec.709 on the phone.
8. If you already have a long cut, respect it. Run it through the AI video summarizer so the new cards match what was on screen. Do not interpolate leftover Sora API jobs toward 24 September 2026 and call that a master.

Operator card you can paste:

Job: signed line → locked still → generate → then retime
Script desk: one claim, duration, forbidden words
Clip desk: 8s with audio / 6s silent (Canva-class) or named model on ClipCanva
Still desk: lock first frame before image-to-video
Conform desk: Runway Enhance Frame Rate AFTER the picture is true
News rates: 25 / 30 / 48 / 60 / 120 + 59.94 (17 Sep 2026)
Dev rates: also 24 / 50 / 23.98 / 29.97 — confirm live
Bill: 1 credit / 2 seconds of INPUT; 5 min / 4K (news); 300s (API)
Do not: interpolate a clip you would not ship; do not merge fps with Ruby HDR

Creator / operator checklist

• [ ] You can point to the Runway news date (17 September 2026) and you did not invent extra fps values from the news page.
• [ ] You checked whether your job is on the web app list (25–120 + 59.94) or the Dev list (includes 24, 50, 23.98, 29.97).
• [ ] Delivery ticket names a real rate (UK 25, NTSC 29.97 / 59.94, social 60, slow-mo 120) — not “smoother.”
• [ ] Spoken words were signed on a script desk before anyone hit interpolate.
• [ ] Hero pack shot used a locked still. Type is readable before fps conversion.
• [ ] You would ship the file at its native rate. Interpolation is optional polish, not rescue.
• [ ] Length is under five minutes (news) / 300 seconds (API). Magnific upscale, if used, is a separate 30-second job.
• [ ] Billing assumption is 1 credit per 2 seconds of input, not per output frame.
• [ ] Ruby / HDR is a separate pass, only if the ticket asks for HDR.
• [ ] Canva 8s/6s clips were split, not dumped into a 5-minute conform.
• [ ] No leftover Sora API dependency past 24 September 2026.
• [ ] No claim that ClipCanva, Runway, VEED, or Canva are the same product.

FAQ

Does Enhance Frame Rate generate a new video from a prompt? No. Runway’s 17 September post is explicit: it converts a video you already have to a target frame rate, including footage not generated on Runway. Prompt-to-clip still belongs on a generate desk such as the AI video generator. Interpolation predicts in-between frames. It does not write the shot.

Which frame rates can I actually request? It depends which contract you opened. The news page lists 25, 30, 48, 60, and 120 fps, plus NTSC 59.94, and says more rates are coming. The Dev models page already documents 24, 50, 23.98, and 29.97 as well. Confirm the live selector or the targetFramerate enum. Do not mix the two lists in a brief.

Is 120 fps a reason to skip the script? No. A video script generator is where you accept the words. VEED still asks for a script before it assembles. Canva’s clip desk still caps you at 8 seconds with audio. Extra frames will not add a CTA you never signed.

Can I interpolate a Canva 8-second clip into a broadcast master? You can retime a file. You cannot turn an 8-second English-prompt clip (optional still, no manual in-clip audio, per Canva Help) into a five-minute 25 fps programme. Split, generate the cards you need, then conform only the cut you would already ship.

Should I still generate on ClipCanva if Runway now conforms fps? If the job is a signed short with a locked still, yes: script on the AI script generator, still on image to video, or text-to-clip on the AI video generator. Use Compare when the first desk warps the label. Runway’s conform desk is Runway’s. It does not sign your claim.

Interpolation is a gift only if the picture was already true. Enhance Frame Rate is a conform desk. Runway did not give you a generate button. Do not pretend it did.