Status checked: September 28, 2026. This article will need an update when Kling publishes a 4.0 announcement or API documentation.
The first question about Kling 4.0 is surprisingly practical: can you make a video with it today? I cannot point to an official public Kling 4.0 release or a documented 4.0 API model ID yet. What people are calling “Kling 4.0” is a possible next generation of Kuaishou's Kling video models, discussed after screenshots and a feature list circulated online. Kling's public site still presents the 3.0 series as its current lineup.
That distinction matters if you are planning a product video or wiring an API into a production workflow. A setting seen in a preview screen is a clue about development. It is not a promise about the model you can buy, call, or compare today.
Is Kling 4.0 Released? What Happened in September 2026
On September 24, an X post describing a Dev Mode leak named VIDEO 4.0 Preview, VIDEO 4.0 Flash Preview, and a separate Image 4.0. The accompanying image appears to show model names in a creator interface. Neither the post nor the image establishes a general release, an official API endpoint, or final specifications.
On September 27, Kling's official account said it had news. The post did not say that the news was Kling 4.0. Reading the two posts together makes a 4.0 announcement seem plausible; it does not supply a release date. That is my inference, not a confirmed rollout schedule.
For now, the useful answer to “What is Kling 4.0?” is: a prospective Kling video generation, with Preview and Flash names reported in a leak, whose public features, price, and availability have not been confirmed by Kuaishou.
What Do the Kling 4.0 Preview Leaks Actually Claim?
Most of the eye-catching numbers trace back to the same September 24 post. Repetition across model directories does not turn one unverified report into several independent confirmations.
| Reported detail |
What we can establish now |
| Up to 30 seconds per video generation |
Claimed in the post. No public 4.0 documentation or repeatable output test confirms the limit. |
| Up to 1080p video |
Reported alongside the video claims. This is not evidence for 30-second 4K video. |
| 15 Omni Reference elements and up to 3 voice references |
Numbers from the post. It does not establish that all 15 can be images, or which combinations will work in each mode. |
| Video extension to 60 seconds |
A reported extension workflow, distinct from generating a 60-second clip in one pass. |
| Experimental long-video mode up to 120 seconds |
An early claim about a separate mode, not a demonstrated two-minute production result. |
| Flash Preview |
A name in the circulated material. There are no confirmed speed, quality, or price figures for a Flash-versus-standard comparison. |
These are reported settings, not Kling 4.0 features I have tested. The limitations may change, and access could differ by plan or task. There is also a naming trap: the same post discusses Image 4.0 generating multiple images, with possible 4K or 8K image settings. Those image rumors say nothing about the resolution of a 4.0 video clip.
The reference count is worth watching for creators who reuse a character or product across shots. But a larger upload allowance alone would not prove better consistency. The result has to preserve the subject after a camera change, a new background, and an action involving other objects.
Kling 4.0 vs Kling 3.0: What Can We Compare Today?
Kuaishou announced the Kling 3.0 family on February 5, 2026. Its announcement describes clips up to 15 seconds, native audio, reference-guided creation, and multi-shot storytelling. On April 23, Kling added native 4K video output to its 3.0 series. Different 3.0 models and tasks can expose different settings, so check the exact route before treating a family-level feature as universal.
| Question |
Kling 3.0 |
Kling 4.0 |
| Public model family |
Officially announced |
Preview names reported; official launch not established |
| Video duration |
Up to 15 seconds in Kuaishou's 3.0 announcement |
Up to 30 seconds claimed, unverified |
| Native 4K video |
Officially added to the 3.0 series |
Not established by the leak |
| Audio and multi-shot controls |
Described in the official 3.0 announcement |
Final 4.0 modes and limits unknown |
| Published API specification and price |
Check the current model and provider pages |
No verified public 4.0 specification or price in the sources reviewed |
Here is the correction that matters most: Kling 4K is a resolution feature of the existing 3.0 generation; “Kling 4.0” would be a version name. Combining the leaked “30 seconds” with 3.0's confirmed “4K” creates a specification nobody has established. A 1080p setting in a leaked interface also cannot prove that a later 4.0 release will never offer 4K. Both claims go further than the evidence.
Need native 4K now? See the currently listed Kling 3 Omni 4K model on GPT Proto. Check that model's task and pricing panel before starting a batch; it is a 3.0 route.
Kling 4.0 vs Seedance 2.5: What Would Settle the Comparison?
There is no honest head-to-head verdict before Kling 4.0 can be run under the same conditions. A longer maximum duration would help a creator fit more of a scene into one job, but it might also make a failed take more expensive to redo. More references could improve direction, or simply add conflicting instructions. Both are hypotheses.
I would test the models with the same short briefs, aspect ratio, reference assets, and output target:
| Test scene |
Check the delivered clip for |
| A person walks into a café, sits, picks up a cup, then speaks across two angles |
Face, clothing, hand-to-cup contact, continuity, and lip sync |
| A product rotates under a changing light, then appears in a second setting |
Label legibility, shape, color, and logo consistency |
| A shot requiring one small correction |
Whether changing the requested detail also changes the rest of the scene |
Record render time, failed attempts, and cost per accepted clip, not just the price of the first generation. One creator discussing a 30–60-second animation series describes how a character and visual style can drift between individually convincing shots. That is a real production question to test. It is not evidence that Kling 4.0 has solved it.
Want a live comparison baseline? Seedance 2.5 is listed on GPT Proto. Use the capabilities shown for its specific API task rather than assuming every feature of the wider model family is enabled on that route.
Can You Use Kling 4.0 Through an API? What to Try Now
An interface screenshot does not define an API. Before integrating Kling 4.0, a developer needs a published model ID, input schema, supported tasks, output constraints, error behavior, and billing unit. We have not established those for a public 4.0 endpoint, nor a date when GPT Proto will list one. A third-party page labeled “Kling 4.0 API” is not proof that it calls a released Kuaishou 4.0 model.
You can work with a currently listed Kling model instead. For example, the GPT Proto Kling 3 Omni 4K model page shows this text-to-video request. It is a Kling 3.0 example, not a preview 4.0 call:
export GPTPROTO_API_KEY="YOUR_API_KEY"
curl --request POST \
'https://gptproto.com/api/v3/kling/kling-v3-omni-4k/text-to-video' \
--header "Authorization: Bearer $GPTPROTO_API_KEY" \
--header 'Content-Type: application/json' \
--data '{
"prompt": "One unbranded ceramic coffee cup on a wooden table. The camera slowly moves closer as morning light crosses the surface.",
"sound": false,
"aspect_ratio": "16:9",
"duration": 5
}'
Set your own key before running it; a successful submission may use your balance. Follow the Check Status instructions on the same model page to retrieve the completed video. The request structure is taken from that live model page, but I have not executed a paid generation with a GPT Proto key for this article. Verify the response and billing in your own account before building on it.
Ready to try a model that is listed today? Browse GPT Proto's Kling models, choose the task you need, and use the quick start attached to that model page. A future 4.0 route should be added here only after its model ID and behavior are verified.