Google's Omni-first video rule has an expiry: Veo 3.1 ends Oct 22
Google's Gemini API docs name Omni Flash the default for video and keep Veo 3.1 for extension, last-frame control and legacy pipelines until October 22.
Google tells developers to start with Gemini Omni Flash, and to use Veo 3.1 only "when scene extension, last-frame control, or integration with legacy pipelines are required." That exception has an end date. The deprecations page lists every Veo 3.1 preview id as shut down on October 22, 2026, with gemini-omni-1.1-flash as the replacement. Sume carries only the Omni side.
Google's rule, line by line
From the Gemini API video overview and the deprecations page.
| Need | Google recommends | Lasts until |
|---|---|---|
| Default video generation | Gemini Omni Flash (fast, multimodal, conversational video editing) | No shutdown date announced |
| Scene extension | Veo 3.1 | October 22, 2026 |
| Last-frame control | Veo 3.1 | October 22, 2026 |
| Legacy Veo pipelines | Veo 3.1 | October 22, 2026 |
What Sume offers for each need
Sume's docs describe gemini-omni-flash-1.1 as text, first-and-end-frame image, and reference to video. A first frame and an optional last frame go in frame_images with frame_type set to first_frame or last_frame, and a request that sends both frame_images and input_references runs as image-to-video. Google's page names last-frame control as a reason to keep Veo, so test your own clip on Omni before you assume equal results.
Extension is the real gap. The Sume docs say Sume does not expose previous_interaction_id or an extend parameter for Omni.
| Need | On Sume | Where it is documented |
|---|---|---|
| Default generation | gemini-omni-flash-1.1, also the sume/auto default | Video Router docs, Video docs |
| Scene extension | Not exposed | Video Router docs |
| First and last frame | frame_images with first_frame and last_frame | Video docs |
| Video editing | video_url on the Video Router, Omni only | Video Router docs |
What to do now
Decide before October 22 what replaces Veo.
- If you use extension, plan a replacement: chain clips by sending the last frame of one as the first frame of the next.
- If you only need plain text-to-video or first-frame video, move to Omni now and compare outputs.
- If you are on a legacy Veo pipeline, the clock is the shutdown date, not a Google preference.
Sources
Related posts
More in Comparisons
- Omni 1.1 Flash 1080p vs Wan 3.0 1080p: price for 30 seconds
A 30 second 1080p film costs $7.50 on Sume's Wan 3.0 in one request, or $5.625 as three 10 s Gemini Omni 1.1 Flash clips. What the cheaper route costs you.
- Omni 1.1 Flash extends to 40 s; Seedance 2.5 makes 30 s in one pass
Google extends Omni 1.1 Flash clips in 10 s steps to 40 s. Seedance 2.5 generates 30 s in one pass. How to get 40 s on Sume with Seedance and Timeline.
- Omni Flash 1.1 extends to 40 s: what Sume offers instead
Google says Omni Flash 1.1 extends in 10 s steps to 40 s. Sume lists Omni at 3-10 s, no extend. Four clips cost $5.00 at 720p; H3 Max needs three.
- Omni Flash 40-second extension vs four 10-second Sume jobs: $5.00
Google describes Omni 1.1 Flash scene extension up to 40 seconds in 10-second steps. Sume lists 3 to 10 seconds per job, so 40 seconds is four jobs.
Written by Sume