Wan 3.0 'Image 1' and 'Audio 1' prompt labels on Sume
Alibaba says to name references 'Image 1', 'Video 1', 'Audio 1' in the prompt. How Sume's input_references order maps to those labels, and a cheap test.

Alibaba's Wan 3.0 reference page tells you to point at media in the prompt as "Image 1", "Image 2", "Video 1" and "Audio 1", by position in the media array. Sume's docs do not define a label syntax for wan-3.0 or say how labels are read, so try the same labels and check the result at 480p before a long run.
What does Alibaba say about referring to media?
The Wan3.0 API reference (read 2026-10-09) lists these media types and the labels used in prompts.
| Media type | Prompt label | Sume input_references type | Limit on wan-3.0 |
|---|---|---|---|
| reference_image | Image 1, Image 2 | image_url | 10 |
| reference_video | Video 1 | video_url | 5, 15 seconds in total |
| reference_audio | Audio 1 | audio_url | 5, 15 seconds in total |
| first_frame, last_frame | not referred to by label | frame_images | 2 |
How does Sume order the references?
On POST /v1/videos you send one input_references array that mixes types, up to 12 items. Sume's docs do not say how entries are numbered for labels, so keep each type in list order and number your labels the same way, then check the result.
If you send frame_images as well, the request is treated as image-to-video and input_references are ignored. Keep the two modes apart.
What does a labeled request look like?
This body uses two images and one audio clip. The prompt names each one.
{
"model": "wan-3.0",
"prompt": "Image 1 is the barista, Image 2 is the shop. Audio 1 is her voice: she greets a customer at the counter.",
"duration": 5,
"resolution": "480p",
"aspect_ratio": "16:9",
"input_references": [
{"type": "image_url", "image_url": {"url": "https://example.com/barista.png"}},
{"type": "image_url", "image_url": {"url": "https://example.com/shop.png"}},
{"type": "audio_url", "audio_url": {"url": "https://example.com/voice.mp3"}}
]
}What does the test cost?
fal lists Wan 3.0 at $0.05 a second at 480p (fal, read 2026-10-09) and Sume bills list times 1.25, so a 5-second test is 5 x $0.0625 = $0.3125. Run it first, look at whether the right face ended up on the right person, and only then move to 720p. If the labels were ignored, describe each reference by what it shows instead of its number.
Sources
Related posts
More in Developers
- Wan 3.0 reference file limits: pixels, ratio, MB and fps preflight
Alibaba lists per-file limits for Wan 3.0 reference images, videos and audio. A runnable Python check to run before you submit them to Sume.
- Wan 3.0 reference video needs 16 fps: probe clips before Sume
Alibaba lists 16 fps or more, 1 to 15 s and 100 MB for each Wan 3.0 reference clip. An ffprobe script that checks your real files before you send URLs to Sume.
- Wan 3.0 reference clips: four 4-second videos break the 15 s cap
Wan 3.0 accepts up to 5 reference videos totalling 15 seconds at 16 fps or more. Four 4-second clips total 16 seconds and fail; three 5-second clips pass.
- wave_size_hint on an empty workspace: Free 4, Pro 18, Startup 36
What generation_limits.wave_size_hint returns before any job is queued, by Sume plan, with the arithmetic and a Python check you can run.
Written by Sume