Veo 3.1 vs Luma Ray3.2
Veo 3.1 suits a short spoken or sound-led scene. Ray3.2 suits a silent product insert with several pinned keyframes and a separate audio track.
Side by side
| Spec | Veo 3.1 | Ray3.2 |
|---|---|---|
| Maker | Luma AI | |
| Version and host for these specs | Google Cloud, veo-3.1-generate-001 | Luma Agents API, ray-3.2 |
| Clip duration | 4, 6 or 8 seconds. Asset-reference mode uses 8 seconds. | 5 or 10 seconds for text or image generation. Video edits can run up to 20 seconds. |
| Output resolution | 720p, 1080p, 4K | 360p, 540p, 720p, 1080p |
| Native audio | Yes | No |
| Image-to-video | Yes | Yes |
| Published price | US$0.40/sec on Google Cloud, 720p or 1080p with audio | 100 credits/clip on Luma Agents API, 5-second 720p SDR generation |
Which to use for a product ad
For a four-to-eight-second creator line, try Veo and review the product name and timing. For an insert that must arrive at several supplied product frames, use Ray3.2 multi-keyframe mode and finish with your own narration.
Clip cost example
For a 720p insert, an eight-second Veo clip with audio costs US$3.20 on Google Cloud. A five-second Ray3.2 SDR generation costs 100 Luma API credits. Amounts are scoped to different hosts, durations and billing units.
Ray3.2’s five-second HDR mode and Google’s eight-second asset-reference mode limit some shot choices. Check the generation mode before budgeting a cut.
