Veo 3.1 Lite: no 4K, no extension. Checklist before Oct 22
Veo 3.1 Lite has no 4K and cannot extend clips, and all three Veo 3.1 preview ids shut down October 22, 2026. Google points to gemini-omni-1.1-flash.
Veo 3.1 Lite stops at 1080p and cannot extend a clip. 4K is only on Veo 3.1 and 3.1 Fast, and extension is only on those two as well. All three preview ids, including Lite, shut down on October 22, 2026, which is 17 days after October 5. Google's recommended replacement is gemini-omni-1.1-flash.
Lite compared with the other Veo 3.1 tiers
Facts are from the Veo guide and the deprecations page.
| Feature | Veo 3.1 | Veo 3.1 Fast | Veo 3.1 Lite |
|---|---|---|---|
| Resolutions | 720p, 1080p, 4K | 720p, 1080p, 4K | 720p, 1080p |
| Extension (7 s, up to 20 times, 720p) | Yes | Yes | No |
| Per second at 720p / 1080p | $0.40 / $0.40 | $0.10 / $0.12 | $0.05 / $0.08 |
| Shutdown | October 22, 2026 | October 22, 2026 | October 22, 2026 |
Checklist before October 22
Run these checks on every pipeline that calls a Veo 3.1 preview id.
- List every call site that uses
veo-3.1-generate-preview,veo-3.1-fast-generate-previeworveo-3.1-lite-generate-preview. - Mark each one that uses extension. Google's video overview says Veo 3.1 still fits when you need scene extension or last-frame control, but the previews end on the same date.
- Mark each one that asks for 4K. Lite never had it.
- Plan the id change to
gemini-omni-1.1-flash, which Google released August 27, 2026 and lists with no shutdown date announced. - Re-time your clips: Omni clip lengths differ from Veo's 4, 6 and 8 seconds.
Where each Veo feature goes
Each Veo habit has a counterpart on the replacement path, with one gap. The Sume column describes gemini-omni-flash-1.1 on Sume, based on the Video Router docs.
| Veo 3.1 feature | Omni on Sume | Note |
|---|---|---|
| 720p and 1080p | 360p, 720p, 1080p, 4K | Resolution is chosen per request |
| 4K (not on Lite) | 4K at $0.375/s | Sume accepts 4K and lowercase 4k for this model |
| Up to three reference images | Up to 10 images and 3 clips of 3 s or less | Addressed as <IMAGE_REF_0> and <VIDEO_REF_0> in the prompt |
| Extension by 7 s | No extend parameter | Chain with frame_images instead |
| Clip length 4, 6, 8 s | Any whole second from 3 to 10 | Default 8 s under sume/auto |
What Sume covers
Veo 3.1 is not in the Sume catalog, so nothing on Sume breaks on October 22. The Sume Video Router carries gemini-omni-flash-1.1, which reaches 4K for 3 to 10 seconds at $0.375 per second (fal list $0.30 times 1.25). A 4K clip of 8 seconds is 8 x $0.375 = $3.00.
Sume does not expose a clip-extend parameter for Omni. The Sume docs say Sume does not expose previous_interaction_id or extend, because it is not in the published fal input schema. First and last frames are available through frame_images, so you can chain clips by sending the last frame of one clip as the first frame of the next.
Sources
Related posts
More in Developers
- Veo 3.1 deletes clips after 2 days: archive them, and the Sume path
Google keeps Veo 3.1 videos on its server for 2 days, and extending a clip resets the timer. Download on completion. Veo 3.1 is not in the Sume catalog.
- Verify a Sume Avatar Video Webhook in Ruby (HMAC-SHA256)
A Ruby verifier for Sume job webhooks: sign timestamp.raw_body with HMAC-SHA256, accept a rotation header, refuse an empty secret, and dedupe on job_id.
- Vertical 9:16 text-to-video API: a 12-second Wan 3.0 clip, priced
A 12-second 9:16 text-to-video request on Sume with Wan 3.0 costs $0.75 at 480p, $1.50 at 720p and $3.00 at 1080p. Full body and the other models that fit.
- OpenRouter video lists 4-8 second clips; Sume model ranges run 2-30s
OpenRouter's video guide shows typical 4-8 second durations. Sume validates duration per model, from 2-30s on Wan 3.0 to 3-10s on Omni 1.1. See the table.
Written by Sume