Veo 3.1 4K API: 8 seconds only, and 4K options on Sume
Veo 3.1 makes 4K video only at 8 seconds, and not on the Lite model. On Sume, gemini-omni-flash-1.1 lists 4K for 3 to 10 seconds.
Yes, Veo 3.1 makes 4K video through the Gemini API, but only at 8 seconds and not on Veo 3.1 Lite; Google's page also ties higher resolution to higher latency. On Sume, Veo is not in the catalog. gemini-omni-flash-1.1 lists 4K at 3 to 10 seconds in 16:9 or 9:16, and sume/auto accepts 4K on POST /v1/videos.
Google's limits are from its Veo page and Sume's from Video generation, read 2026-09-29.
What does Google say about Veo 3.1 4K?
The page lists the resolution values 720p (default), 1080p and 4k, with 1080p and 4k supported only at an 8-second duration. Video extension works at 720p only. It also lists 4K as not available on Veo 3.1 Lite and gives a request latency of 11 seconds to 6 minutes at peak.
Which Sume models make 4K?
In the catalog, gemini-omni-flash-1.1 lists 360p, 720p, 1080p and 4K for 3 to 10 seconds. Most other catalog models list at most 1080p, apart from MiniMax H3 2K/4K upscales priced on request. The Video Router docs say that for 4K you use POST /v1/videos with sume/auto, since the older /v1/video-1.0/generate URL rejects 4k.
curl -X POST https://api.sume.com/v1/videos \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: uhd-001" \
-d '{
"model": "gemini-omni-flash-1.1",
"prompt": "Slow drone pass over a harbor at dawn.",
"resolution": "4K",
"aspect_ratio": "16:9",
"duration": 5
}'How do the 4K limits compare?
Read the row you need; the two sides use different clip lengths.
| Item | Veo 3.1 (Google) | On Sume |
|---|---|---|
| 4K duration | 8 s only | gemini-omni-flash-1.1: 3 to 10 s |
| Aspect ratios | 16:9 or 9:16 | gemini-omni-flash-1.1: 16:9 or 9:16 |
| Audio | Always on | Native synced audio, always on |
| Model that does it | Veo 3.1 and Fast, not Lite | gemini-omni-flash-1.1, or sume/auto |
Do I need 4K?
Most social placements do not: a 1080p clip is enough for vertical and feed video. Use 4K when the clip will be cropped or shown large, and test one 5-second clip first because the higher tiers cost more.
Sources
Related posts
More in Models
- Veo 3.1 API: how to call it, and what Sume lists instead
The Veo 3.1 API is Google's, called through the Gemini API with preview model codes. Sume does not list Veo; here are the catalog models with the same inputs.
- Veo 3.1 extend video, and how to chain clips on Sume
Veo 3.1 extends only videos Veo made, 7 seconds at a time. Sume has no extend call, so you chain clips from a last frame or pick a model with a longer limit.
- Veo 3.1 first and last frame: how the API works
Veo 3.1 takes a first image and a last image and generates the motion between them. Here is Google's request shape and where the same input works on Sume.
- Veo 3.1 Lite, Fast or standard: how to choose
Veo 3.1 has three preview models: standard, Fast and Lite. Lite drops 4K and extension; Fast targets speed. What each does, plus Sume's tiered Seedance.
Written by Sume