Kling 3.0 native 4K at 60 fps: what Sume's kling-3 lets you order

On Sume, kling-3 takes 720p or 1080p and 4 to 15 seconds, so there is no 4K option for Kling 3.0 through the API. The fal page I read lists 3 to 15 seconds natively at up to 1080p, so the 4K figure you see in launch coverage is not something either route lets you order today.

If a 4K master is a hard requirement, use a model whose catalog row lists 4K. On Sume that is Gemini Omni Flash 1.1.

What each page lists

fal's Kling 3.0 page lists native audio in Chinese, English, Japanese, Korean and Spanish, multi-shot storyboards where each shot has its own prompt, and a 3 to 15 second range at up to 1080p.

Sume's Video Router lists kling-3 at 720p and 1080p for 4 to 15 seconds, with no reference_*_urls. Audio is a generate_audio flag that defaults to true.

How to plan around it

There are two honest options. Make the shot at 1080p with Kling and finish it in your own mastering tool, or make it with Omni at 4K. Omni is 3 to 10 seconds, 16:9 or 9:16, with audio always on.

Do not send a 4k value to Kling and expect it to be clamped. The catalog drives validation, and an unlisted resolution returns 400 unsupported_capability instead of a silent downgrade.

Check the row yourself

The catalog is the authority for what the API accepts. This one-liner prints each id with its resolutions and the first and last supported duration.

curl -s https://api.sume.com/v1/videos/models \
  -H "Authorization: Bearer $SUME_API_KEY" \
  | python3 -c "import json,sys; [print(m['id'], m['supported_resolutions'], m['supported_durations'][0], m['supported_durations'][-1]) for m in json.load(sys.stdin)['data'] if m['id'] in ('kling-3','gemini-omni-flash-1.1')]"

Longer than 15 seconds

Kling 3 on Sume ends at 15 seconds. For longer pieces, cut several clips and join them on a timeline; the post on Kling 3.0 multi-shot on Sume shows how, and the Kling 4.0 comparison covers the newer model.

What to do with the gap

A spec gap between a launch and an API is normal, and it is easy to plan around when you know it is there.

• If 1080p is enough, kling-3 gives you 15 seconds with native audio and no reference inputs.
• If you need 4K, use Omni at up to 10 seconds, or plan an upscale in your own finishing step.
• If you need frame rate beyond what the file gives you, check the output file before you promise it to a client.
• Re-read the catalog when a new model lands. The row, not the announcement, is the contract.