I spent last week rewriting the same three sentences on a landing page.
Not because the product changed. Because I kept mixing what is live, what is reported, and what I wish were true. If you ship AI tools, you’ve probably done the same. Here’s the short version of what burned me — and the Kling 4.0 notes that actually got me excited again.
Release notes pits I fell into (again)
1. Pasting the roadmap into the hero.
I drafted a headline that read like Kling 4.0 was already generating on the site. A teammate caught it. Readers don’t care that “we’re ready.” They care whether the Generate button works. If it doesn’t, say coming soon and stop decorating it.
2. Turning a leak table into a feature checklist.
Someone on the team had a long list: durations, reference caps, Flash vs long video. I almost published it as “Kling 4.0 supports…” with no hedge. That’s how you earn a support ticket on day one. Better: “early reports / what people with access are seeing,” then update when it’s on your own stack.
3. Forgetting the “what you can do today paragraph.
The first soft-launch note I wrote was 100% future tense. A friend replied: “Cool. So… do I close the tab?” Now every note ends with a usable loop for the models that already run — and a clear line that 4.0 isn’t on the site yet.
4. Burying cost honesty.
I once put “free credits in the title and left the quote-before-generate bit in a footnote. People felt baited. Credits up front beats adjectives.
If you’re writing notes for a version that isn’t live: label the buckets. Live / Reported / Not on our site yet. Paste that into the draft before the marketing pass.
What about Kling 4.0 has me most excited
I’m still waiting to wire it up. Kling 4.0 is coming soon on my side — not a pretend launch. But a few people already have clearer notes on what’s in the build, and these are the bits that made me stop doomscrolling and start sketching workflows:
Quick comparison a lot of people ask for first: 4.0 vs Flash vs 3.0. Treat it as a working chart from early notes — especially resolution and long-form rows — and re-check when 4.0 is actually live on your stack. On my site, 4.0 generation is still **coming soon.
Video generation & models
- Kling 4.0: about 3–30s across Omni-reference and keyframe workflows; 720p / 1080p; keyframe mode up to ~10 keyframes
- Extensions: roughly 3–60s extension steps (source clips often capped around 60s) — this is the dont re-roll the whole spot” piece I’m impatient for
- Long video (experimental): reports of 3–120s at 720p / 1080p only (no 2K/4K in those notes), with forward and backward extension
- Kling 4.0 Flash: about 3–20s, Omni-ref style, currently called out as 720p-locked
- Omni in these notes looks like a workflow inside 4.0, not a separate standalone model name on the box
Multimodal reference limits (the part makers will argue about)
- Standard mode: up to about 15 combined references (caps people are citing: ~10 images, ~5 videos, ~7 Elements)
- Uploaded reference clips: roughly 230s on 4.0, 2–20s on Flash (input length ≠ output length)
- Voice refs: up to ~3 on full 4.0; Flash lists 0 voice inputs in the notes I’ve seen (doesn’t always mean silent output — just no voice inputs yet)
- Long video mode: much tighter — hard cap around 5 image/Element refs total; no video or voice inputs in those reports
Image 4.0 / other flags (lighter excitement, still watching)
- Default & Series modes, batches of about 1–9 images
- Resolution toggles showing 2K / 4K / 8K (native 8K still unconfirmed in what I’ve read)
- Early chatter on plugin hooks, experimental audio tools, VIP tiers — I’m not betting the landing page on those yet
API & billing
- Full 4.0 sounds like separate API packages and dedicated video-input billing; Flash may ride existing 3.x-style packages. No final pricing in anything Id put in a public changelog without a TBD” stamp.
The five lines I’d put in a “why I’m excited” blurb
If I had to soft-announce without lying:
- Up to ~30s generation, with extension paths people are citing toward ~60s
- On the order of ~15 reference elements in standard mode
- Up to 1080p in the main 4.0 path
- Multilingual lip-sync / sound with up to ~3 voice references (where the notes list them)
- An experimental long video path people describe as up to ~120s at 1080p, extendable forward and back
That’s the wishlist energy. Not a promise that it’s on my Generate button today.
What I’m doing while I wait (and what you can do too)
Until Kling 4.0 is actually integrated, I keep shipping 3–15s clips with the Kling models that are live — 2.6, 3.0, 3.0 Omni, and the rest of the series you can run now. Same boring loop: short prompt, reference only when identity matters, read the credit quote, then generate.
I keep the waitlist + the “try other Kling models free (eligible users)” path in one place: kling-4.ai. Independent site — not official Kuaishou / Kling. When 4.0 is really there, the release note will say live, not “excited.”
If you’re drafting your own “coming soon” page this week: steal the bucket labels. Future-you will thank present-you when support opens the ticket.
Happy to compare how you’re wording duration vs extension vs long-mode in the comments that’s where most of us accidentally overclaim.
Disclosure: I work on kling-4.ai. Feature numbers above are from early/reported notes others have shared, not a claim that Kling 4.0 generation is live on the site today. No paid placement on DEV.
Top comments (1)
the live / reported / not on our site yet distinction is actually a really useful way to think about release notes.
it's surprisingly easy to blur the line when you're excited about an upcoming feature, especially with ai products where things can change between an early report and the actual release.
i also like the point about ending with something people can actually use today. even if the upcoming feature is the interesting part, readers still need to know what they can do right now.
the "coming soon" label isn't really the problem. pretending it's already live is.