Veo 3.1 offers 4, 6 or 8 seconds; Sume Omni takes any 3 to 10
Veo 3.1 only accepts 4, 6 or 8 second clips. On Sume, gemini-omni-flash-1.1 takes any whole second from 3 to 10, and an 8 second 720p clip bills $1.00.

Veo 3.1 gives you three clip lengths: 4, 6 or 8 seconds. Gemini Omni Flash 1.1 on Sume takes any whole second from 3 to 10, which is eight choices. If a 5 or 7 second clip fits your edit, Veo cannot make it, and Omni can.
Duration limits side by side
The Veo guide lists durations of 4, 6 and 8 seconds. The Sume Video Router table lists 3 to 10 seconds for gemini-omni-flash-1.1, and supported_durations on GET /v1/videos/models reports whole seconds.
| Model | Allowed durations | Where it is documented |
|---|---|---|
| Veo 3.1, 3.1 Fast, 3.1 Lite | 4, 6, 8 s | Gemini API Veo guide |
| gemini-omni-flash-1.1 on Sume | 3 to 10 s, whole seconds | Sume Video Router docs |
| sume/auto on Sume | 3 to 10 s, default 8 s | Sume Video docs |
What each length costs
Sume lists a 720p rate of $0.125 per second for Omni (a $0.10 fal list rate times 1.25). The clip price is the number of seconds times that rate, so each extra second adds the same amount. Google's own Veo rows are per second too, but you can only pick 4, 6 or 8 seconds.
| Seconds | Veo 3.1 Fast 720p ($0.10/s) | Veo 3.1 Standard 720p ($0.40/s) | Omni on Sume 720p ($0.125/s) |
|---|---|---|---|
| 3 | not offered | not offered | $0.375 |
| 4 | $0.40 | $1.60 | $0.50 |
| 5 | not offered | not offered | $0.625 |
| 6 | $0.60 | $2.40 | $0.75 |
| 7 | not offered | not offered | $0.875 |
| 8 | $0.80 | $3.20 | $1.00 |
| 10 | not offered | not offered | $1.25 |
How to use the extra choices
The Veo rows are Google's direct prices for models that Sume does not carry, so this is a length comparison, not a like-for-like price comparison. The Omni column is the Sume price for a different model. The Sume docs describe the billable amount as list x 1.25 rounded up to cents, so the rows with a fraction of a cent (3, 5 and 7 seconds) are shown before rounding.
Under sume/auto, which resolves to Omni 1.1, the default is 8 seconds and the default resolution is 720p, so a request with no duration gives the 8 second row above.
Checklist
Pick the length your edit needs, then send it as duration. Sume validates it against the catalog and returns 400 for a value the model does not advertise, rather than rounding it for you. Read supported_durations before you submit.
- Veo: choose 4, 6 or 8 s; 1080p, 4K and reference images need 8 s (see the 8 second rule post).
- Sume Omni: any whole second from 3 to 10.
- Both: durations are fixed per request, so plan cuts around the length you pick.
Sources
Related posts
More in Comparisons
- Veo 3.1 Lite, Fast or Standard: matching Sume models by job
Google lists Veo 3.1 at $0.05, $0.10 and $0.40 a second at 720p, and Sume does not list it. Match each tier to a listed model: Wan, Omni, Kling by job.
- Veo, Luma, Runway, HappyHorse not on Sume: the listed model per job
Sume lists no Veo 3.1, Luma Ray3.2, Runway or HappyHorse id. For ads, product shots and talking heads, these catalog rows are the nearest to call.
- Video file-size caps: Shopify 1 GB, Pinterest 2 GB, TikTok 500 MB
Video size and length caps for Shopify, Pinterest, TikTok ads, TikTok Shop listings and Amazon in one table, with bitrate math for staying under each.
- Reference limits in 2026 video models: Seedance, Wan, Omni, H3
Seedance 2.5 takes 30 images, 10 clips, 10 audio files per pass; Wan 3.0 up to 20 assets; Omni video refs of 3 s. H3 numbers and Sume's rows.
Written by Sume