Wan 3.0 reference limits: how many images, videos and audio clips
Wan 3.0 reference-to-video takes up to 10 images, 5 video clips and 5 audio tracks. See the per-type caps, what Sume rejects with unsupported_capability, why.

Wan 3.0 reference-to-video accepts up to 10 reference images, up to 5 reference video clips and up to 5 reference audio tracks in one request. The video clips together are limited to 15 seconds, and so are the audio tracks. Sume checks the counts when you submit and refuses a request over a cap with 400 unsupported_capability.
The vendor limits are from fal's Wan 3 page and Alibaba Cloud's guide; the Sume checks are from the Video generation docs and current API code. All read 2026-09-29.
What are the exact caps?
| Reference type | Count | Duration or size |
|---|---|---|
Image (image_url) | Up to 10 | Alibaba lists 20 MB per image |
Video (video_url) | Up to 5 | 15 s in total; fal says 16 fps or higher |
Audio (audio_url) | Up to 5 | 15 s in total |
What does Sume check on submit?
Only the counts. wan-3.0 is refused with 400 unsupported_capability if a request lists more than 10 image, 5 video or 5 audio references; the error names the input_references field. The 15-second totals and the frame rate are the provider's limits, so keep each request inside them yourself.
Is there also a cap on the whole list?
For Wan 3.0 the per-type caps are the only count check in current code, so the three add up to at most 20. Other models use different rules: for example a general cap of 12 input_references on models without their own per-type caps.
What happens if I send frames and references together?
frame_images wins. The request becomes image-to-video and the input_references are dropped, so send one or the other. Image-to-video vs reference-to-video explains the split.
{
"model": "wan-3.0",
"prompt": "The character from the images walks to the window while the song plays",
"duration": 10,
"resolution": "720p",
"input_references": [
{ "type": "image_url", "image_url": { "url": "https://example.com/character.png" } },
{ "type": "audio_url", "audio_url": { "url": "https://example.com/song.mp3" } }
]
}Sources
Related posts
More in Models
- Wan 3.0 thinking mode: why document and web page input needs it
fal says Wan 3.0 needs thinking mode to read a document or web page; Alibaba says prompt_extend must be true. What each means, and why Sume's wan-3.0 skips it.
- Wan 3.0 vertical video: 9:16 for Reels, Shorts and TikTok
Wan 3.0 supports 9:16. Send aspect_ratio 9:16 to wan-3.0 for a vertical clip of 2 to 30 seconds at 480p, 720p or 1080p. Accepted ratios and cost.
- Wan 3.0 vs MiniMax H3: clip length, ratios and reference caps
Wan 3.0 runs 2 to 30 s at up to 1080p; MiniMax H3 runs 5 to 15 s at 480p or 768p. Where they differ on Sume: ratios, reference caps and audio inputs.
- Wan 3.0 vs Seedance 2.0: which model to call when
Wan 3.0 and Seedance 2.0 are both on Sume's video API. Wan runs 2 to 30 s and bills per second; Seedance 2.0 runs 4 to 15 s with a 21:9 frame. Pick by the job.
Written by Sume