Video Models

Kling 4.0 Turns On Native 4K and 10-Bit HDR: Sharper Footage, Bigger Bill, and Docs That Still Disagree With Themselves

November 21, 20260 views阅读中文原文
Kling 4.0 Turns On Native 4K and 10-Bit HDR: Sharper Footage, Bigger Bill, and Docs That Still Disagree With Themselves

TL;DR

Kling AI said on November 19 that Kling 4.0 now supports native 4K resolution and 10-bit HDR output, with HDR working at both 4K and 1080p. This is not a "coming soon" teaser — the switches are live, two explicit API settings were added, and the price table grew two new rows.

Three things to know before you spend anything:

  • It costs more. A second of 4K costs more than twice a second of 1080p, and HDR is billed as a per-second add-on. A five-second 4K HDR shot runs at more than double the price of the same shot in 1080p SDR.
  • Kling did not specify the format. The announcement names no HDR standard (HLG or PQ), no codec, no container. For anyone trying to slot this into an existing post pipeline, that is the first thing they need.
  • Kling's own documentation has not caught up. The Kling 4.0 spec table already lists "10-bit HDR (1080p and 4K)" while the body text still says "(coming soon)."

Core facts here come from Kling AI's post on X and Kling's own docs and API notice. Pricing and hands-on details are drawn from several outlets. This article is compiled from multiple media reports.

What actually changed

Native 4K, not an upscale pass

The usual route to 4K has been to generate at 1080p and push the result through an upscaler. The problem is that upscalers redraw detail: faces, wardrobe and material textures tend to drift between shots.

Native 4K means the model renders at delivery resolution from the start. Kling says facial expression, material texture and scene depth all survive. For teams shipping a master file, that removes a whole round of cleanup work.

10-bit HDR at both 4K and 1080p

10-bit HDR is not tied to 4K. According to Kling, HDR output also works at 1080p, so projects that do not need 4K still get the extra bit depth.

Kling's stated benefit: more highlight and shadow detail, less colour banding, with backlit scenes, night scenes and neon-lit environments called out by name. Those are exactly the situations where generated footage used to blow out the highlights and crush the shadows.

In plain terms, 10-bit gives each colour channel 1,024 levels instead of the 256 levels of 8-bit — four times the headroom. That is room to push a grade without the image falling apart into blocks.

A wider frame comes with it: 21:9

Kling's 4.0 spec sheet lists 21:9 ultrawide alongside 4K, pitched as more horizontal composition space for cinematic shots and large-scale scenes.

What Kling 4.0 already was

A quick refresher from the official user guide:

  • Up to 30 seconds per generation, extendable forward or backward across passes to reach 2 minutes total
  • Up to 10 keyframes to pin character poses, scene changes and shot transitions
  • Up to 15 reference assets per task: 10 images, 5 videos (30 seconds combined), 7 elements and 3 video elements
  • Two-channel stereo audio with lip sync
  • Targeted editing: change expression, camera position, background or style while the rest of the scene stays stable
  • Native audio in Chinese, English, Japanese, Korean, Spanish, Portuguese, German, French and Hindi, plus regional accents such as Beijing Mandarin, Taiwanese Mandarin, Northeastern Mandarin, Sichuan dialect and Cantonese

How to use it: two settings and one trap

There are three endpoints: /text-to-video/kling-4.0, /image-to-video/kling-4.0 and /omni-video/kling-4.0.

Turning on 4K and HDR depends on two fields inside settings:

  • settings.resolution: 720p, 1080p or 4k
  • settings.dynamic_range: sdr or hdr (defaults to sdr), and HDR only applies at 1080p or 4k

Here is the trap. Writing "4K", "HDR" or "high dynamic range" into the prompt does nothing. Only the settings values change the output. Kling's documentation is explicit about this.

If you clone a colleague's prompt to reproduce a shot, check the settings separately — otherwise you will get 1080p SDR and wonder why.

Cost: unit rates and what they convert to

Kling bills the API per second of output, in units:

  • 720p: 1.0 unit per second, no HDR option
  • 1080p: 1.5 units per second, plus 0.3 units per second for HDR
  • 4K: 3.5 units per second, plus 0.5 units per second for HDR

Converting to dollars depends on the package. Kling's Standard Package 2 sells 13,135 units for $2,000, which works out to roughly $0.152 per unit. On that basis:

  • 4K SDR: about $0.53 per second
  • 4K HDR: about $0.61 per second
  • 1080p SDR: about $0.23 per second

Reporting based on the international site's dollar list price gives a slightly different set: $0.549 per second for 4K text-to-video, with HDR adding $0.078 per second. On that basis a five-second 4K SDR clip lands around $2.75, and about $3.14 with HDR. The two sets of numbers are close but not identical; trust the price sheet your own account shows.

One more billing detail that trips people up: with video input, billed seconds are not output seconds.

  • No video input: unit price × output seconds
  • Total input duration ≤ output duration: unit price × output seconds × 2
  • Total input duration > output duration: unit price × (input seconds + output seconds)

So a 6-second reference clip plus a 5-second output is billed on 11 seconds. When a task carries several clips, add up every video, the base footage being edited, and any video elements before you estimate.

Who it is for

Good fit right now:

  • Advertising, short film and product teams that deliver 4K masters or need headroom for a grade
  • Projects shot in difficult lighting where highlight and shadow information has to be recovered at the generation stage
  • Teams telling stories in a 21:9 widescreen frame

Who should wait

Not a good fit yet:

  • Creators publishing vertical short video only. One hands-on comparison found the gap between 1080p and 4K HDR is hard to see at full-screen vertical size
  • Teams whose post pipeline cannot ingest HDR. Kling has not published the HDR standard, codec or container, so whether the file opens and grades in your tools is something you have to test yourself
  • Anyone on a tight budget doing concept validation. 4K HDR is the most expensive tier Kling 4.0 offers

Pitfalls

  1. Editing the prompt will not enable 4K. Change settings instead.
  2. HDR is not available at 720p. If you want HDR you need at least 1080p.
  3. Kling's documentation is inconsistent. The spec table lists 10-bit HDR while the body still says "coming soon," and third-party host pages for Kling 4.0 have not been updated with 4K or HDR either. Do not treat a reseller's description as authoritative.
  4. The duration ceiling is unconfirmed. Kling's announcement does not say whether 4K or HDR still allows the full 30 seconds. Test a short clip before committing a long-take project.
  5. Billed seconds can double. This is easiest to get wrong with reference video. Run one task and check the invoice before batching.
  6. Do not treat HDR as a universal "looks better" switch. Extra bit depth is headroom for grading. If the final distribution target is still 8-bit SDR, the money buys you nothing.

How much difference it makes

One user generated 11 clips at 1080p and 11 at native 4K HDR from the same ten 8K stills, using identical first and last frames, all in a single pass with no manual fixes. Their findings:

  • The 1080p first frame matched the input still almost exactly
  • The 4K HDR version rendered the same image brighter and denser: average HLG signal rose from 0.58 to 0.76, with colour saturation about 1.27 times higher
  • Zoomed in, frost footprints and fur detail were noticeably sharper at 4K
  • At full-screen vertical size, the difference may be small

That is one user's comparison, not a standardised test. The real answer comes from running your own footage through both settings.

Next step

First, today: pick one five-second shot and generate it twice from the same first and last frames — 1080p SDR and 4K HDR. Drop both files into your editor and grade suite. Check that they open and that the colour is read correctly.

Second: verify the bill. Run a single five-second 4K HDR task and compare the estimate against what is actually charged, so you know how the HDR surcharge and billed seconds are counted.

Third: if you are only publishing to social platforms, hold off on 4K. 1080p with HDR is the better value tier; upgrade once the distribution chain handles HDR properly.

Fourth: before batching, turn your prompt and settings into a template so nobody assumes 4K is on when it is not.

Sources

  • Kling AI post on X (November 19, 2026): Kling 4.0 supports native 4K and 10-bit HDR at both 4K and 1080p
  • Kling 4.0 User Guide (official manual, including the spec table, 21:9 and 10-bit HDR notes)
  • Kling API update notice (November 19, 2026): adds settings.resolution: 4k and settings.dynamic_range
  • https://www.vp-land.com/stories/kling-4-0-adds-native-4k-and-10-bit-hdr-output
  • https://sloptvnews.com/kling-4-0-api-native-4k-10-bit-hdr/
  • https://thereelstack.com/lab/kling-4-native-4k-10-bit-hdr-api-openmotion-deepseek-hyperframes-0-9-70
  • https://cn.ai123.com/news/18783
  • https://www.biegao.ai/kling-api-4k-video-hdr-pricing/

Pricing and hands-on details are compiled from multiple media reports. Anything Kling has not disclosed is flagged as such above.

Sources

Comments

0 published
Log inorsign up to leave a comment.

Loading comments...