Luma uni-1: 9 references for images, 8 for edits, and Sume limits
Luma uni-1 takes up to 9 image_ref images, or 8 for image_edit because the source uses a slot. Sume ceilings come from each model's catalog entry.

Luma uni-1 accepts up to 9 image_ref images for text-to-image and up to 8 for image_edit, because the source image takes one of the 9 slots. On Sume there is no fixed number: each model carries its own reference ceiling in the catalog, and some models take none.
Luma facts are from its Models and Pricing page; Sume facts are from Image models, read 2026-10-01.
Where does the 9-versus-8 rule come from?
The Luma Models page says reference-guided generation accepts up to 9 reference images via image_ref for text-to-image, or up to 8 for image editing, "where the source image occupies its own slot". The pricing page repeats it: image_edit supports up to 8 references and image up to 9.
| Type | Source image | Reference limit |
|---|---|---|
image | None | 9 |
image_edit | source (uses one slot) | 8 |
What are the reference limits on Sume?
They are per model. In the catalog code, edit-capable models default to a max_images of 4 and the Grok image entry sets 1. The docs say ChatGPT Image 2.5 supports up to 16 references, and a model whose input_references descriptor is {"min": 0, "max": 0} is text-to-image only and rejects references.
Reference URLs must be public HTTPS; localhost, private-network and non-HTTPS URLs are rejected before submission.
Does a Sume edit use up a reference slot?
The docs describe an edit as input_references on an image request and do not describe a separate source slot. Treat the descriptor's max as the total number of images you can send, and test one edit at that number before you rely on it.
How do I plan around the difference?
Keep your reference list sorted by importance and trim to the target model's max at call time. The Grok image reference post shows the same pattern for a lower ceiling.
Sources
Related posts
More in Developers
- Luma uni-1 output_format png or jpeg vs Sume's per-model enum
Luma uni-1 output_format is png or jpeg, and the model picks one from the prompt if you omit it. Sume lists formats per model; set it explicitly.
- Luma uni-1 web_search grounding vs Sume's unsupported_parameter
Luma uni-1 accepts web_search: true to look up visual references before it generates. Sume has no such field and returns 400 unsupported_parameter.
- Regenerate one rejected variant on Sume: use a new key
Luma Variants lets you regenerate any preview that is not right. On Sume a repeated Idempotency-Key replays the old job, so a redo needs a fresh key.
- Lyria 3.5 has no Batch API: queue many tracks on Sume instead
Google's Lyria 3.5 page says batch, Flex and Priority inference are not supported. Sume accepts many music jobs and queues them past your concurrency.
Written by Sume