ModelBrief · Kling 4.0 Flash · Topic Page
Last updated Nov 20, 2026

Kling 4.0 Flash Specs: 720p Cap, No Keyframes

ModelBrief · Published 2026-11-18 · Fact-check 2026-11-16 · Reference: Kuaishou Kling official launch page, feature page and API docs

Kling 4.0 Flash has a short spec sheet, and the shortness is the point: a 720p ceiling, a 20s cap, no keyframes, 8-bit SDR — four caps that define the tier. The table below compares it item by item with the full Kling 4.0, all from the official docs (launch page, feature page, API docs), cross-checked against OrcaRouter, Atlas Cloud, Genfire and others in Nov 2026. Kling publishes no parameter count, architecture detail or model card — what is not in the table is what the vendor never gave.

Full vs Flash: the official comparison table

CapabilityKling 4.0 (full)Kling 4.0 Flash
Clip length3–30 s (extension to 2 min coming soon)3–20 s
Resolution720p, 1080p, 4K (4K and 10-bit HDR marked "coming soon" on the release page; API currently 720p/1080p)720p ceiling (the API settings.resolution enum has no second value)
Dynamic range10-bit HDR (1080p/4K, coming soon)8-bit SDR
KeyframesUp to 10None — no keyframes, no last frame
References (Omni)Up to 15 inputs (≤10 images, ≤5 videos, ≤7 subjects, audio/voice refs)Up to 15 inputs (≤10 images, ≤5 videos); single-image image-to-video uses the first frame
Prompt budgetText up to 8,000 tokensEnglish prompt up to 26,000 characters (per OrcaRouter, from official docs)
Aspect ratiosIncl. 21:9 ultra-wideNot separately published
Languages / dialogue9 languages incl. dialectsNot separately published
AudioStereo sound on every clip (per Genfire, citing official wording)Unverified — conflicting sources, see below
Generation speedNot publishedNo number published — "faster" is positioning only
Parameters / architectureNot disclosedNot disclosed
Weights / licenseClosed, no public weightsClosed, no public weights

How to read the four caps

720p is a hard ceiling, not a default. The Flash API's resolution enum has a single value, and the website offers no 1080p option — 720p is not a "recommendation", it is the only option. For 1080p, use the full model; for 4K, even the full model does not have it yet (marked coming soon on the launch page; the API currently offers 720p/1080p).

20s is the per-request cap. Flash does 3–20s per clip, the full model 3–30s. A 30s clip needs the full model or Seedance 2.5 Flash (30s). The full model's "extension to 2 min" is likewise marked coming soon, not shipping.

No keyframes is a workflow cap. Flash has no keyframes and no last frame; first-frame control comes only from the input image. Multi-keyframe storytelling needs the full model (up to 10 keyframes). This is the single biggest workflow difference between the two tiers.

8-bit SDR is a quality cap. Flash is 8-bit SDR only; the full model's 10-bit HDR is limited to 1080p/4K and marked coming soon. Do not read the full model's HDR roadmap as Flash's current capability.

Audio: two claims side by side, neither endorsed

Flash's native-audio status is the one spec item on this topic where the sources conflict and the conflict is unresolved. UnificAlly's Flash API page says "two-channel stereo audio"; OrcaRouter (Chinese edition) says the official pricing table has no native-audio row for Flash and the API doc settings show none. The two claims directly conflict, and this topic endorses neither. Until Kuaishou clarifies: do not plan dialogue- or music-led workflows on "Flash has audio", and do not conclude from "Flash has no audio" that it is necessarily silent — neither assertion currently has verifiable official support. The full model's audio is clear: stereo on every clip (per Genfire, citing official wording).

Omni references: 15 inputs, but no separate subject count

Flash's Omni allows up to 15 inputs (≤10 images + ≤5 videos), the same input cap as the full model; with a single image, image-to-video treats it as the first frame. The gap is in subjects and audio references: the full model supports up to 7 subjects and audio/voice references, while the Flash tier's subject count is not separately published. Flash did not lose reference count — it lost length, resolution, keyframes and dynamic range.

What does not exist: parameters, architecture, model card, speed figures

Kling has published no parameter count, architecture detail, model card or tech report for Flash or 4.0, and generation speed has no number either — "faster" is positioning only, with no seconds-per-clip figure from Kling. Any circulating parameter figure has no official source, and this topic does not use it. Likewise, whether Flash supports the 21:9 aspect ratio or the 9-language dialogue coverage has not been separately published; when citing the full-model figures, they must be labelled "full-model figures".

ModelBrief's take: Flash's spec sheet reads like a subtraction list: everything the full model has, it removes one by one — resolution, length, keyframes, dynamic range — keeping only the Omni reference count. The list has one virtue: honesty. The caps are written down plainly, so choosing Flash or the full model needs no guessing. The single exception is audio: two sources conflict, with no answer yet, pending a clarification from Kuaishou.

Reference: Kling official API docs: 4.0 Flash text-to-video · Kling official usage guide: Kling 4.0 (§5.1) · OrcaRouter Flash GA analysis (Nov 4, 2026, updated Nov 7) · Atlas Cloud "Kling 4.0 vs Flash: Every Official Spec Before October" · Genfire release-date/specs/price guide (Nov 5, 2026) · UnificAlly Flash API page (Nov 5, 2026) (rewritten and organized by ModelBrief; the audio conflict is marked)