Kling 4.0 Omni Reference takes 15 references; Sume limits compared
fal says Kling 4.0 Omni Reference accepts up to 15 references. On Sume, kling-3 takes none; Wan 3.0 and Gemini Omni Flash 1.1 publish their own limits.

fal's Kling 4.0 explainer says Omni Reference accepts up to 15 references and the model takes up to 10 keyframes. Sume's kling-3 takes no reference images or videos. For reference-to-video on Sume use wan-3.0 (up to 10 images, 5 videos and 5 audio files) or gemini-omni-flash-1.1 (up to 10 images and 3 videos).
Reference limits (read 2026-10-04)
Kling 4.0 is not in the Sume catalog and its API is not yet published in the sources I read, so the first row is context only.
| Model | Reference images | Reference videos | Reference audio |
|---|---|---|---|
| Kling 4.0 Omni Reference (fal, citing Kling) | Up to 15 references in total | Counted within the 15 | Not stated |
| kling-3 (Sume) | None | None | None |
| wan-3.0 (Sume) | Up to 10 | Up to 5, 15 s total, at least 16 fps | Up to 5, 15 s total |
| gemini-omni-flash-1.1 (Sume) | Up to 10 | Up to 3, each up to 3 s | Not accepted |
Send references on Sume
References go in input_references. Each entry is an image object. If you also send frame_images, Sume treats the request as image-to-video and the references are not used as guidance.
curl -X POST "https://api.sume.com/v1/videos" \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "wan-3.0",
"prompt": "The two products rotate on a marble table",
"duration": 10,
"resolution": "720p",
"input_references": [
{"type": "image_url", "image_url": {"url": "https://example.com/a.png"}},
{"type": "image_url", "image_url": {"url": "https://example.com/b.png"}}
]
}'Check the live limits
Sume's per-model limits are in the catalog, and supported_input_references lists which types a model accepts. Read it before you build a reference workflow.
If you need more than 10 images
Neither Wan 3.0 nor Gemini Omni Flash 1.1 takes more than 10 reference images on Sume. Pick the most informative ten, or split the scene into shots and render them separately, then join them on the Timeline endpoint.
Sources
Related posts
More in Models
- Kling 4.0 saved elements: 7 slots vs Sume reference URLs
Kling 4.0 reuses up to 7 saved elements per generation. Sume has no saved-element object: you send image, video and audio URLs per request. What that changes.
- Kling AI official domain: avoid lookalike sites with Kling 4.0
Kling 4.0 hype brings fake sites. TechTimes names kling.ai as official and two lookalike domains tied to malware. A checklist, plus Kling 3 via Sume.
- Lip sync with a hand over the mouth: sync-3 vs Fabric on Sume
Sync Labs says sync-3 handles obstructions on faces. Sume's lip-sync routes start from a still plus audio. What each takes as input and what is promised.
- LTX-2.3 extend and retake at $0.10/s: the nearest Sume route
fal sells LTX-2.3 extend-video and retake-video at $0.10 a second. Sume has neither endpoint; Omni's video_url edit mode and Timeline joins come closest.
Written by Sume