
The Kling Image 4.0 API (kling-4.0-image) is the successor to the Kling O3 Image API (kling-o3-image and kling-o3-image-edit) on PoYo. The short version: Kling Image 4.0 adds 8K, image sets, a 50,000-character prompt and a separate long-page model, and costs roughly three to four times more per image. This post compares the two request by request so you can decide which calls to move. Both live on PoYo: Kling Image 4.0 and Kling O3 Image.
The decision in one table
| If your request needs… | Call |
|---|---|
| 1K output, or the lowest price per image | kling-o3-image / kling-o3-image-edit |
| JPEG or WebP straight from the API | Kling O3 Image (output_format) |
| More than 4K, or exactly 8K | kling-4.0-image |
| A set of 2–10 images with the same subject and style | kling-4.0-image with enable_sequential |
| Prompts longer than 2,000 characters | kling-4.0-image (up to 50,000) |
| A full webpage or ecommerce detail page as one image | kling-4.0-long-image |
| Text-to-image and editing on one model ID | kling-4.0-image |
Field-by-field request differences
Both use POST https://api.poyo.ai/api/generate/submit, the same status endpoint and the same callback_url. The differences are in model and input, taken from each model's PoYo docs.
| Field | Kling O3 Image | Kling Image 4.0 API |
|---|---|---|
model | kling-o3-image (text-to-image), kling-o3-image-edit (edit) | kling-4.0-image for both; image_urls selects edit mode |
prompt | up to 2,000 characters | 1–50,000 characters |
image_urls | 1–10, required for kling-o3-image-edit | 1–10 (optional); 30 MB, ≥300 px, ratio 0.4–2.5 each |
| Elements | elements: [{frontal_image_url, reference_image_urls}] | kling_elements: [{element_input_urls: [front, …]}], 2–4 views, up to 7, images + elements ≤ 10 |
resolution | 1K (default), 2K, 4K | 2K (default), 4K, 8K |
size | 8 ratios, default 16:9; auto only on the edit model | same 8 ratios plus auto, default auto |
output_format | jpeg, png (default), webp | not accepted; PNG only |
n | 1–9 | 1–9 independent, or 2–10 with enable_sequential: true |
enable_sequential | not available | true returns an ordered, consistent set |
| Long pages | not available | separate model kling-4.0-long-image |
Kling describes Kling Image 4.0 in its launch post as its first model with native 8K generation, able to plan up to 10 images from one prompt and render up to 2,000 characters of text in seven languages. Those are Kling's claims; the API differences above are what changes in your code.
Price per same request
PoYo prices, 1 credit = $0.005. Kling O3 Image has no reference surcharge on PoYo; the Kling Image 4.0 API adds 1 credit per reference image or element, once per request. Kling's own pricing page notes the same change: Kling Image 4.0 bills reference inputs, earlier models did not.
| Same request | Kling O3 Image | Kling Image 4.0 API |
|---|---|---|
| 1 image, 1K | 3.5 credits ($0.0175) | not offered (2K minimum: 13 credits) |
| 1 image, 2K | 3.5 credits ($0.0175) | 13 credits ($0.065) |
| 1 image, 4K | 7 credits ($0.035) | 19 credits ($0.095) |
| 1 image, 8K | not offered | 32 credits ($0.16) |
| 2K edit, 2 reference images + 1 element | 3.5 credits ($0.0175) | 16 credits ($0.08) |
| 4 images at 2K | 14 credits ($0.07), independent | 52 credits ($0.26), as a set or independent |
| Webpage design, 1K | not offered | 110 credits ($0.55) |
At 2K the Kling Image 4.0 API costs about 3.7× Kling O3 Image per image, and about 2.7× at 4K. Full Kling Image 4.0 tables are in Kling Image 4.0 API pricing.
Limits that change
- Resolution floor rises. 1K is gone; the smallest Kling Image 4.0 output is 2K. If you serve thumbnails, keep them on O3 or resize on your side.
- Ceiling rises to 8K. PoYo's docs list 8192×8192 at 1:1. In our launch-day test (PoYo production API, November 19, 2026), a 16:9 8K request returned a 10880×6144 PNG of about 128 MB and took about 3.8 minutes, at 32 credits.
- File handling. No
output_format: you get PNG. Our downloads were RGBA PNGs even for opaque images. Plan conversion and storage if you usedjpegorwebpon O3. - Reference rules are explicit. Kling Image 4.0 validates each reference: up to 30 MB, at least 300 px per side, width/height between 0.4 and 2.5. The O3 docs list no such limits, so validate very wide or small images before you migrate.
- Sets take longer. Our four-image 2K set took about 4.9 minutes. Move long or large jobs to
callback_url.
When to switch
Switch a call to kling-4.0-image when it needs something O3 cannot do: 8K, a consistent set, a long prompt or a page design. For example:
- Storyboards and product angles. On O3 you would send
n: 4and hope the subject matches. Withenable_sequential: truethe model plans the set; our test kept the same rider, bike and outfit across dawn, noon, sunset and night. - Print and crop-heavy assets. Anything above 4K.
- Long, structured prompts. Brand guides, shot lists and copy blocks over 2,000 characters.
- Ecommerce pages.
kling-4.0-long-imagebuilds the whole detail page; O3 has no equivalent.
Keep O3 for high-volume 1K–2K drafts, thumbnails and pipelines that need JPEG or WebP from the API. Running both is fine: O3 to explore, Kling Image 4.0 for the final set, on the same key.
Migration diff
A text-to-image call:
{
- "model": "kling-o3-image",
+ "model": "kling-4.0-image",
"input": {
"prompt": "A cinematic futuristic alley with rain and neon reflections",
"resolution": "4K",
"size": "16:9",
- "output_format": "png",
"n": 2
}
}
An edit with an element. Two field renames, one model ID merge:
{
- "model": "kling-o3-image-edit",
+ "model": "kling-4.0-image",
"input": {
"prompt": "Place @Element1 sitting on the sofa in @Image1. Keep the room layout of @Image1 unchanged.",
"image_urls": ["https://example.com/living-room.png"],
- "elements": [
- {
- "frontal_image_url": "https://example.com/character-front.png",
- "reference_image_urls": ["https://example.com/character-side.png"]
- }
- ],
+ "kling_elements": [
+ {
+ "element_input_urls": [
+ "https://example.com/character-front.png",
+ "https://example.com/character-side.png"
+ ]
+ }
+ ],
- "resolution": "1K",
- "size": "auto",
- "output_format": "png"
+ "resolution": "2K",
+ "size": "auto"
}
}
Checklist:
- Replace both O3 model IDs with
kling-4.0-image; edit mode now follows fromimage_urls. - Rename
elementstokling_elementsand mergefrontal_image_urlplusreference_image_urlsinto oneelement_input_urlsarray, front view first, 2–4 URLs in total. A single-view O3 element needs at least one more view. - Drop
output_format. The schema rejects unknown fields. - Map
1Kto2K; setsizeexplicitly if you relied on O3's16:9default, since the new default isauto. - Add the reference surcharge to your cost estimates.
- Raise client timeouts or switch to webhooks for 8K and sets.
Status polling, files[].file_url parsing and webhook verification stay the same. The full request reference is in the Kling Image 4.0 API guide.
What about Kling O1 Image?
Kling O1 Image is edit-only (kling-o1-image-edit) at 1K or 2K for 3.5 credits per image. Treat it like kling-o3-image-edit in the table above: a cheap reference edit, no 4K or 8K, no sets.
Frequently asked questions
Is the Kling Image 4.0 API a drop-in replacement for the Kling O3 Image API?
Almost. The endpoint, auth, polling and webhooks are the same. You change the model ID, rename elements to kling_elements, drop output_format and move 1K requests to 2K.
Which is cheaper, the Kling Image 4.0 API or Kling O3 Image? Kling O3 Image: 3.5 credits per image at 1K or 2K and 7 at 4K, versus 13, 19 and 32 credits at 2K, 4K and 8K for Kling Image 4.0, which also adds 1 credit per reference.
Does Kling O3 Image support 8K or image sets?
No. Kling O3 Image on PoYo tops out at 4K and returns 1–9 independent images. 8K and enable_sequential sets are Kling Image 4.0 API features.
Can I still get JPEG from the Kling Image 4.0 API? Not from the API: output is PNG. Convert after download, or keep JPEG and WebP jobs on Kling O3 Image.
Do I need a new API key for the Kling Image 4.0 API?
No. The same PoYo key works for kling-4.0-image, kling-4.0-long-image, kling-o3-image and every other model.