Kling 3.0 and Kling 4.0, side by side: reported versus confirmed
Updated 2026-10-02
Kling 4.0 was announced on 2026-09-28. Between an announcement and a usable API sits a stretch where a lot of confident-sounding specs circulate. This page does not try to fill that gap with guesses. Every item below is labelled as confirmed (we can verify it ourselves), reported (it comes from announcement coverage or a third party and we have not tested it), or unconfirmed. Where a point has no reliable source, we say so.
Status as of this page
Kling 4.0 is not available through any host in the VideoRouter catalog. We check this against host model lists directly. Reporting indicates limited testing, with a wider release expected in October 2026. That timeline is also reported, not confirmed by us. Nothing on this page should be read as a statement that you can call Kling 4.0 today.
Side-by-side
| Attribute | Kling 3.0 | Kling 4.0 |
|---|---|---|
| Callable through VideoRouter | Confirmed. Tiers are the model ids kling-v3.0-std, kling-v3.0-pro, kling-v3.0-4k. | Confirmed not available: no host in the catalog serves it yet. |
| Maximum clip length | 15 seconds, per VideoRouter's own research notes. Check a model page for the host-specific cap. | 30 seconds. Reported, unconfirmed. |
| Keyframes | Start-image input is supported. Last-frame control (end_image_url) is currently documented as rejected with a 400 on every model in our API; check the model page. | 10 or more keyframes. Reported, unconfirmed. |
| Reference input | Reference image, video and audio inputs are listed on the model pages for the Kling v3 and O3 families. Host support varies. | Multimodal reference input. Reported, unconfirmed; the exact accepted types and limits are not known. |
| Per-second price | See the live table. | Unknown. No host has published a confirmed rate we can bill against. |
| Output quality versus 3.0 | Not rated here. | Unconfirmed. We have no output to evaluate. |
| Audio generation | Check the model page; this platform's video API has no request field for audio output on the Kling v3 rows. | Unknown for our API. |
The three headline claims, one at a time
30-second clips
The reported maximum doubles the 3.0 limit. If accurate, this matters for anything that currently needs stitching multiple generations. But a maximum is a ceiling, not a guarantee: a host can cap duration lower than the model's own limit, and a longer clip may carry different pricing rules and queue behaviour. Until a host publishes its accepted duration range, treat 30 seconds as a design target, not a spec.
10+ keyframes
More keyframes would give you finer control over where a clip goes, closer to a storyboard than a single start image. It is also the claim with the most open questions for an API: how keyframes are passed (an array, named fields, timestamps), whether each needs a position in time, and how they interact with a text prompt. None of that is known. Our current API reference documents no multi-keyframe field, so a new request field would be needed.
Multimodal reference input
Kling 3.0 and O3 already list reference images, video and audio on their model pages, so "multimodal reference" is not new as a concept. What is unknown is what 4.0 adds: higher caps, mixing types in one call, or new roles for a reference. Do not assume it is a superset of what 3.0 accepts today.
What pre-release signals exist
Our provider notes record that, as of 2026-10-01, one host had published pre-release endpoint shells for a Kling v4 family, including schemas that suggest wider duration and reference ranges. We treat that as a hint about the shape of the eventual API, not as a confirmed spec: the same listing showed placeholder pricing, so there was no real rate to bill against, and we do not onboard a model without a confirmed price. Schemas on pre-release shells can change before launch. The same sweep found no Kling 4 model on the other hosts we check.
Why we label so strictly
A tracker is only useful if its status can be trusted. Two failure modes are common around a launch. The first is spec inflation: a number appears in one article, gets repeated, and within a week it reads as fact. The second is premature availability: a host adds a placeholder page, and blogs report the model as "available". We would rather say "not callable yet" a day too long than point you at an id that returns an error. When the status here changes, it will change because a priced model id appeared in the catalog and a job ran against it, not because of a headline.
The practical effect for you is that anything in the Kling 4.0 column above should be used for planning and nothing else. Do not write it into a customer contract, a price quote or a launch date.
How to read future coverage
- Distinguish an app feature from an API feature. A model can be live in a consumer app long before any developer API exposes it.
- Distinguish limited testing from general availability. Early access is gated; "released" can mean either.
- A third-party host listing a model name is not the same as it being callable at a stable price.
- If a number has no source, discount it.
What to do now
Build on Kling 3.0 with the model id and duration limits in configuration so that adopting 4.0 is a config change. The sibling articles cover what you can use in the meantime and how to monitor for the launch. For a first request on the current generation, see the quickstart or create a key.
Frequently asked questions
Is the Kling 4.0 API available?
Not through any host in the VideoRouter catalog as of this page. Reporting indicates limited testing with a wider release expected in October 2026, which is also unconfirmed.
What is Kling 4.0 reported to add over 3.0?
Reported changes are clips up to 30 seconds (3.0: 15), 10 or more keyframes, and multimodal reference input. All three are unconfirmed by us.
Is the reported 30-second limit guaranteed on every host?
No. A model's own maximum is a ceiling, and a host can cap duration lower. Wait for a host to publish its accepted range.
What is Kling 4.0 going to cost?
Unknown. No host has published a confirmed per-second rate we can bill against, so this page makes no price claim.
Keep reading
- How to Prepare Your Integration for the Kling 4.0 API
- Kling 4 Alternatives You Can Call Today (Long Clips, Refs)
- How to Monitor the Kling 4.0 API Launch (Script + Test Plan)
VideoRouter puts it next to dozens of other video and image models behind one API key, so you can compare providers, prices and fail over automatically. Compare providers on VideoRouter →