Kling API Pricing (2026): Six Models on the Price Page, No 2.1 Row — Which Version You Are Actually Billed For

Type "kling api pricing" into Google and the suggestions offer you five different version numbers: 3.0, 2.6, 2.5, 2.1 and the bare word "cost". That is the problem in one screen. People do not know which Kling they are buying, and the version number changes the price by a factor of ten.

So we went to the one page that settles it. Everything below is as listed on Kling's own API pricing page (kling.ai/dev/pricing, and the matching pricing table in Kling's API documentation), checked 2026-09-23. No reseller prices, no subscription-app prices, and no conversions we did not show.

The unit, then the six models on today's page

Kling's page states 1 Unit = $0.14 (list price) and sells video through prepaid packages. Every video model is billed per second, with separate columns for 720p, 1080p and 4K. Here is the full video table as it read on 2026-09-23, dollar amounts exactly as Kling prints them.

The same documentation table also prices the extras you tend to need around a clip: Avatar at 0.4 units ($0.056) per second at 720p, lip sync at 0.5 units ($0.07) per 5 seconds, and text-to-audio or video-to-audio at 0.25 units ($0.035) per call.

The version number you searched for may not be on the page

Look at what is missing. There is no Kling 2.1 row, and nothing older, on the 2026-09-23 price page. The autocomplete still suggests "kling 2.1 api pricing", and there are plenty of third-party pages quoting a figure for it, but the vendor's own list does not show it. We are not going to guess whether 2.1 still answers API calls on older accounts; the point is narrower. If a price you are relying on is not on the vendor's page, you are relying on someone's memory of it.

This is the same pattern playing out across the whole category. Google's Gemini API retired Veo 3.0 on June 30, 2026, and OpenAI's Sora 2 API shuts down on September 24 with an empty replacement column. The cheapest row on any video price page tends to be the oldest model, and the oldest model is the one most likely to leave next. A Hacker News commenter summed up the mood back in June: "All of them are increasing prices and deprecating cheap models." (mistic92, 2026-06-26.) That is one developer's view, not a measurement, but it is a good reason not to hard-code a version.

The cheapest row on a video price page is usually the oldest model, and the oldest model is the one that disappears first.

If your workflow is currently built on a version that is not on the page, treat that as a to-do rather than an emergency. Pull a handful of your best recent prompts, run them on the nearest listed model at the same resolution, and compare the outputs side by side with what you have been publishing. Note the per-second rate of the listed model next to the result. If quality holds, move now, on your own schedule, instead of on the day an old endpoint stops answering. If quality drops, you have learned which feature you depend on, and you can look for it specifically across vendors rather than hunting for a like-for-like replacement under pressure. Either way, the decision is based on the vendor's current page and your own outputs, not on a price someone quoted for a model you can no longer find.

What a 5 and 10-second Kling clip costs, by the choices you make

Multiplying Kling's per-second rates by clip length gives the numbers below. These are single successful generations; if you need three attempts per usable clip, multiply by three.

Three readings that matter for a budget:

• Audio is a real line item. On Kling 3.0 at 1080p, native audio takes you from $0.112 to $0.168 per second, a fifty percent jump. If you lay your own voiceover and music on top, pay for silent video.
• 4K is priced flat across 3.0 and Omni at $0.42 per second, which is almost four times 1080p. For vertical short-form, that is money spent on pixels a phone screen throws away.
• Turbo is not always cheaper. 3.0 Turbo is only listed with native audio, so for silent clips plain 3.0 at 1080p ($0.112) costs less than 3.0 Turbo ($0.14).

For the cross-vendor picture, including Veo 3.1, Seedance, MiniMax and Runway at the same checked date, see AI video generator API pricing (2026) and the Google-specific breakdown in Veo 3 API cost per video. If you arrived here from the Sora shutdown, the cost side of that move is in Sora 2 leaves the API and the replacement column is empty.

Budgeting a month of Kling clips without guessing

A per-second rate becomes a budget only after you decide three things in advance. Here is a way to do it that does not rely on any number we cannot see from Kling's page.

1. Fix the spec. Pick one model, one resolution and one audio setting for routine work, and write it down. For example: Kling 2.6 at 1080p, silent, which Kling lists at 0.5 units ($0.07) per second.
2. Fix the length. Decide the seconds of generated footage per finished video. A 30-second short that uses three generated 5-second shots needs 15 generated seconds, not 30, because the rest can be stock, screen recording or text.
3. Measure your take ratio. Run your real prompts for a week and count how many generations each usable shot needed. That ratio is the multiplier nobody publishes.

With those three, the math is simple: seconds per video, times videos per month, times take ratio, times the per-second rate. At $0.07 per second, 15 generated seconds per video and a take ratio of two, each finished video costs $2.10 in generation. Change only the audio switch to native audio at 1080p and the same plan runs at $0.14 per second, doubling the bill for sound you may be replacing anyway.

Two habits keep that budget honest over time. Re-read the price page before each monthly top-up rather than trusting last month's numbers, and keep the model name in a configuration file so that moving from 3.0 to 2.6, or away from Kling entirely, is a one-line change instead of a rewrite. The Sora shutdown showed what happens when that line is buried in code.

Kling API pricing FAQ

How much is 1 Kling API unit in dollars?

Kling's pricing page states 1 Unit = $0.14 at list price (checked 2026-09-23). Units are bought in prepaid packages; package sizes and any volume discount are shown in the purchase flow rather than on the public table, so treat $0.14 as the list rate and check what your package actually works out to.

Is there a Kling API free trial?

The public pricing page we checked lists prepaid packages and per-second rates; it does not advertise a free API allowance. Free generations on Kling's consumer app are a different product with different terms, and they do not carry over to API keys. For the broader question of what "free" usually costs in AI video, see why "free" and "without watermark" rarely come together.

Which Kling version should I use for short-form social video?

Start with the cheapest model that passes a blind test on your own prompts, at 720p or 1080p, with native audio off if you add your own voice. On today's page that means trying 2.5 Turbo or 2.6 first and moving up to 3.0 only for shots where viewers would notice the difference. Keep the model name in configuration so moving up or down is a one-line change.