Runway vs Kling pricing
runway vs kling pricing and kling vs runway both land on this page. Each figure is that provider’s own list price for a stated 5-second clip. This page does not score which clip looks better.
Prices checked on 2026-09-21 against Kling’s developer pricing page and Runway’s API pricing page.
Request an invitationSeats and pricing
The short answer
| Runway | Kling | |
|---|---|---|
| Prices checked on | 2026-09-21 | 2026-09-21 |
| Billing unit | Developer-portal credits at $0.01 each. Gen-4.5 is 12 credits per second. App subscriptions are a different unit. | Video API units. 1 Unit = $0.14 list price, billed per second. |
| Worked list-price example | Gen-4.5, 5 seconds, base rate (no HDR or ProRes surcharge). 60 credits x $0.01 = $0.60. The API page does not split this rate by resolution. | Kling 3.0, 720p, pricing row “With Native Audio x No Voice Control”, 5 seconds. 0.9 Units/s x $0.14 = $0.126/s. 5 seconds = $0.63. |
| Native audio | No audio parameter on the Gen-4.5 text-to-video or image-to-video request. | Yes, optional. This row is the with-native-audio price. The 720p row with no native audio is 0.6 Units/s ($0.084/s). |
| Official max length | 10 seconds. Allowed duration is 2 to 10 seconds. | 15 seconds on text-to-video for kling-3.0. Allowed duration is 3 to 15 seconds. |
| 9:16 | Yes. Text-to-video and image-to-video both include 720:1280. | Yes. aspect_ratio includes 9:16. |
| 1:1 | Image-to-video includes 960:960. Text-to-video does not. Its ratios are 1280:720 and 720:1280 only. | Yes. aspect_ratio includes 1:1. |
There is no winner column. Both figures are list price for a stated 5-second clip. They are not a lotgen quote, and they are not a measured keep rate.
What the two keywords are asking
runway vs kling pricing asks what each provider charges. This page answers with the provider’s own list price, a billing unit, and the limits that provider documents.
kling vs runway on this same URL is those same facts. It is not a beauty contest, not a quality score, and not a ranking of which model looks better. A same-prompt comparison is a different job, and it is not this page.
Someone reading either query is usually deciding which key to fund before they run a lot. The dollars below are what the provider publishes. They are not the quote lotgen would show for a specific run.
Kling list price
Prices checked on 2026-09-21 on Kling’s developer pricing page. The video grid says 1 Unit = $0.14 (list price).
One worked row, Kling 3.0 at 720p, labeled on that page “With Native Audio x No Voice Control”:
| Model | Kling 3.0 |
| Pricing-page row | 720p, With Native Audio x No Voice Control |
| Rate | 0.9 Units per second, which the same cell prints as $0.126 per second |
| Stated duration | 5 seconds (the API reference’s default, inside the allowed 3 to 15 seconds) |
| Units | 0.9 x 5 = 4.5 Units |
| List price | 4.5 x $0.14 = $0.63 |
That is list price times a stated duration. It is not a lotgen quote.
The same Kling 3.0 block has a cheaper 720p row, “No Native Audio”, at 0.6 Units per second ($0.084). Kling 3.0 Turbo and Kling 3.0 Omni are separate rows on the same grid, and they are not this $0.63. The unit crosswalk (credits versus units) lives on Kling pricing explained.
The text-to-video API reference for POST /text-to-video/kling-3.0 sets audio to native or off. It does not have a separate voice-control field. The $0.63 figure uses the pricing page’s own row label, including “No Voice Control”. Reseller and roundup pages are not a source here. If another site prints a different dollar figure, check it against Kling’s own page before you believe either.
Runway list price
Runway sells two different units. The worked row uses the developer portal, because that is the key you fund. App plans do not publish one clean dollar-per-second.
Developer portal (the worked row)
Prices checked on 2026-09-21 on Runway’s API pricing page.
| Billing unit | Credits bought in the developer portal are $0.01 per credit. Sales tax may apply. |
| Model | Gen-4.5 (gen4.5) |
| Rate | 12 credits per second. The page does not split this rate by resolution. |
| Stated duration | 5 seconds |
| Credits | 12 x 5 = 60 credits |
| List price | 60 x $0.01 = $0.60 |
| Left out of the $0.60 | ProRes, PNG sequences, 10-bit, and HDR. Those add a per-second credit surcharge on Gen-4.5. |
There is no separate 720p or 1080p dollar rate to quote. The $0.60 is the base rate.
Gen-4 Turbo is a different model on the same page: 5 credits per second, which is $0.25 for 5 seconds at $0.01 per credit. It is not the worked row.
App plans (labeled crosswalk, not the worked row)
Runway’s plan page, also checked on 2026-09-21, sells monthly credits inside a subscription. The page’s own example is that Gen-4.5 uses 12 credits per second, and the compare table lists Gen-4.5 at 60 credits per 5 seconds. It does not state a dollar value per credit. Any per-clip dollar figure below divides the plan price by the included credits. That is an assumption, not an invoice for one clip.
Checked plan prices on that page:
- Standard, billed monthly: $15 for 625 credits. Implied credit value if every credit is used: $15 / 625 = $0.024. A 5-second Gen-4.5 clip is 60 credits, or $1.44 of that allotment.
- Standard, billed yearly: $12 per month for the same 625 credits per month. Implied value: $12 / 625 = $0.0192. The same 60 credits are $1.152 of that allotment.
- On Standard and Pro, monthly credits do not roll over. The implied per-clip figure assumes the allotment is used up. A clip does not cost $1.44 if you are paying $15 anyway and leave credits unused.
- Pro and Max include more credits, so the implied dollar per credit is lower if you use them. They are not worked out here.
- The API rate of $0.01 per credit is what the developer portal page states. It is not a sentence on the app plan page.
The app page says 625 monthly credits equal 52 seconds of Gen-4.5, 104 seconds of Gen-4 Turbo, or 78 Gen-4 images at 1080p. 52 seconds of Gen-4.5 is 625 divided by 12, rounded, which matches the 12 credits per second rate. 104 seconds of Gen-4 Turbo does not match 5 credits per second (625 / 5 = 125 seconds). That line is Runway’s to reconcile, and no Gen-4 Turbo app rate is inferred from it.
What the official docs actually limit
No quality scores. Only limits with a provider doc behind them. Checked on 2026-09-21.
Kling 3.0 text-to-video
Source: Kling 3.0 text-to-video, the API reference for POST /text-to-video/kling-3.0. The page is filed under a 3-0-omni folder. The request path is still /text-to-video/kling-3.0. Omni video itself stays POST /omni-video/kling-3.0-omni.
- Duration: an integer from 3 to 15. The reference lists every integer in that range. Default 5. Max length on this call is 15 seconds.
- Resolution:
720p(default),1080p, or4k. - Audio:
nativeoroff. Defaultoff.nativemeans the video includes native audio matched to the picture.offmeans no audio. - Aspect:
16:9(default),9:16, and1:1.
Kling 3.0 Turbo text-to-video (POST /text-to-video/kling-3.0-turbo) documents 720p and 1080p only, duration 3 to 15 seconds as the same integer list, and the same three aspect ratios. It has no audio field. Its pricing row is not the $0.63 row above.
Runway Gen-4.5
Sources: API pricing, image-to-video, and text-to-video.
- Duration: 2 to 10 seconds on both text-to-video and image-to-video. Max length is 10 seconds.
- Ratio, text-to-video:
1280:720or720:1280. That second value is 9:16. 1:1 is not in this list. - Ratio, image-to-video:
1280:720,720:1280,1104:832,960:960,832:1104,1584:672.960:960is 1:1.720:1280is 9:16. - Audio: the Gen-4.5 request bodies do not include an audio parameter. A missing field is not the same as native audio.
- The 12 credits per second rate is the base model rate. HDR and professional output formats add credits on top. They are documented on the pricing page, not in the $0.60 example.
What this page will not decide
A same-prompt pair, a keep rate, and “which looks better” need a run you can watch. There is no footage on this page. There is no stills gallery. There is no quote for a take that has been run.
Kling versus Veo dollars are a different pair, already on Kling vs Veo cost. Veo’s own rows live on Veo 3 cost per second. A same-prompt footage comparison of Kling and Veo does not exist yet.
The wider per-second list is how much AI video generation costs. The cost calculator is a separate tool. It is not the source of the list prices above.
It does not pick a best model for ads either, and it does not replace a same-prompt Runway versus Kling test. That test is a different job. Sora vs Veo and Veo vs Runway are their own pages. Sora is a model on fal or evolink, not its own key.
Request access
lotgen is where a Runway key and a Kling key can be quoted before you commit. The numbers on this page stay list price. A quote is a later step, on a real request.
The invitation form lists thirteen platforms. Twelve of them are media keys, and both Runway and Kling are in that twelve. Anthropic is the thirteenth, and it is copy, text only. Luma and Sora are models on fal or evolink, not keys. ElevenLabs is voice. The OpenAI key is not a Sora key.
Request an invitationSeats and pricing
Team aside
If a team is choosing which keys to fund together, request an invitation for a brand seat or book a 20-minute walkthrough.
FAQ
Is Runway cheaper than Kling?
On the two worked rows checked on 2026-09-21, Runway Gen-4.5 is $0.60 for 5 seconds at the developer-portal base rate, and Kling 3.0 at 720p with native audio and no voice control is $0.63 for 5 seconds. Those rows are not the same product. Kling's row includes native audio. Gen-4.5 has no audio parameter. Kling's max on this call is 15 seconds and Gen-4.5's is 10. The three-cent gap is not a quality ranking and not a lotgen quote.
Why is there no winner on this page?
A winner would need the same prompt, a clip you can watch, and a keep rate. This page is list price only. It has no footage and no stills. A same-prompt quality comparison is a different job.
Does the Kling $0.63 row include audio?
Yes. It is the pricing page's row "With Native Audio x No Voice Control", at 0.9 Units per second. The 720p row with no native audio is 0.6 Units per second, or $0.084 per second. The text-to-video API reference sets audio to native or off. It does not have a separate voice-control field. The words "No Voice Control" are the pricing page's label.
Is a Runway subscription the same price as the API?
No. The worked row is the developer portal: $0.01 per credit, and Gen-4.5 is 12 credits per second, so 5 seconds is $0.60. App plans sell a monthly credit allotment and do not state a dollar value per credit. Dividing Standard's $15 by 625 credits implies $1.44 of that allotment for the same 60 credits, and only if the allotment is used up. That division is an assumption, not an invoice for one clip.
Does Gen-4.5 text-to-video do 1:1 and 9:16?
9:16 yes. Text-to-video ratios are 1280:720 and 720:1280 only, and 720:1280 is 9:16. 1:1 is not in that list. Image-to-video adds 960:960, which is 1:1, and still includes 720:1280. Kling 3.0 text-to-video includes 16:9, 9:16, and 1:1.
How do I re-check these prices?
Open Kling's developer pricing page and confirm 1 Unit = $0.14, then the Kling 3.0 720p cell labeled "With Native Audio x No Voice Control". Open Runway's API pricing page and confirm $0.01 per credit and 12 credits per second for gen4.5. Multiply by the stated seconds. If either cell moved, the dollar figure on this page moved with it.