GPT Image 2.5 Flare & Sunburst are live on EvoLinkTry GPT Image 2.5
Gemini Omni Flash Preview to Gemini Omni 1.1 Flash migration workflow
Product Launch

Gemini Omni Flash GA Migration: Move Preview Calls to 1.1

EvoLink Team
EvoLink Team
Product Team
May 12, 2026
Updated on August 28, 2026
6 min read
As of August 28, 2026, Gemini Omni Flash is no longer only a public preview. Google released Gemini Omni 1.1 Flash as generally available on August 27, with the stable Gemini API model ID gemini-omni-1.1-flash. The older Gemini API ID gemini-omni-flash-preview is scheduled for deprecation on September 30, 2026.
The practical job of this page is migration: identify which channel-specific ID your application uses, update the route before the deadline, and retest the new resolution and extension behavior. For live EvoLink pricing and the five callable route IDs, use the Gemini Omni 1.1 Flash model page.

Current Gemini Omni status

ItemVerified status on August 28, 2026
Public model nameGemini Omni 1.1 Flash
Gemini API lifecycleGenerally available (GA)
Stable Gemini API IDgemini-omni-1.1-flash
Legacy Gemini API preview IDgemini-omni-flash-preview
Preview deprecation dateSeptember 30, 2026
Output per generation or extension3–10 seconds, 24 FPS
Resolution choices360p, 720p, 1080p upscale, 4K upscale
New 1.1 controlsVideo extension, first-and-last-frame interpolation, resolution control

Google's current pricing page had not yet published a separately verified 1.1 price that we could safely copy when this article was updated. Do not carry the old preview price into a production budget by assumption. EvoLink settles its routes from live token usage; check the model page or console for the current route price.

Do not confuse the three model-ID layers

The similar names describe different access surfaces:

SurfaceIDWhat it means
Gemini API stablegemini-omni-1.1-flashGoogle's GA public model ID
Gemini API legacy previewgemini-omni-flash-previewOld ID to migrate before September 30
Vertex AI / Agent Platform preview channelgemini-omni-1.1-flash-previewSeparate channel-specific ID used in EvoLink's upstream verification
EvoLink unified video APIFive gemini-omni-1.1-flash-* route IDsTask-specific EvoLink IDs for generation, editing, and extension

EvoLink exposes text-to-video, image-to-video, reference-to-video, video edit, and video extend as separate route IDs on one asynchronous video endpoint. They are not alternate Google model IDs. This separation lets an application validate task-specific parameters and compare another video route without rebuilding authentication, status polling, or cost logging.

Gemini Omni 1.1 Flash multi-turn video extension workflow with overlapping context windows

What "up to 40 seconds" actually means

It does not mean one request returns a 40-second video. Google documents 3–10 seconds per generation or extension. In a multi-turn workflow, you can append up to 10 seconds at a time until the combined clip reaches 40 seconds. For continuity, the model uses the last up to 10 seconds as context; it does not reread an arbitrary 40-second previous video on every turn.
EvoLink has verified the semantics of one explicit extension request: duration is the number of seconds appended, not the final total. Repeated extension all the way to 40 seconds has not yet been verified end to end on the current EvoLink route, so the product page does not advertise a one-shot or guaranteed 40-second EvoLink output.

Migration checklist

  1. Search application code, environment variables, and stored job templates for gemini-omni-flash-preview.
  2. If you call the Gemini API directly, move to gemini-omni-1.1-flash; do not substitute the Agent Platform preview ID.
  3. Recheck response parsing and task history because the Interactions API is stateful for conversational editing.
  4. Retest resolution handling. The default remains 720p; 1080p and 4K are upscaled outputs and have higher token cost.
  5. Treat extension duration as appended seconds. Validate 3–10 on your side instead of relying on upstream clamping.
  6. Load-test quotas and keep retry/backoff logic. EvoLink testing observed a 429 with four concurrent upstream requests.
  7. Keep a fallback route for production workloads whose quality, latency, or regional constraints differ by task.

Limits that still matter

Audio is generated with the video, but uploaded audio references and voice editing are not supported. Extension appends only to the end of a clip; it cannot prepend content or insert footage in the middle. System instructions, temperature, top_p, stop sequences, and a separate negative-prompt parameter remain unsupported. Write exclusions into the normal prompt.

Google also documents restrictions for extending uploaded videos with spoken dialogue and regional limits for uploaded-video extension in the EEA, Switzerland, and the United Kingdom. Multi-turn extension of model-generated video is a different workflow from uploading a long finished clip.

If your decision is specifically whether to move from the original Preview release, read Gemini Omni Flash vs Gemini Omni 1.1 Flash for a capability-by-capability upgrade guide.
Compare Gemini Omni 1.1 Flash routes and token costs

FAQ

Is Gemini Omni 1.1 Flash generally available?

Yes. Google marked gemini-omni-1.1-flash GA on August 27, 2026.

When is gemini-omni-flash-preview deprecated?

Google's release notes list September 30, 2026. Migrate and regression-test before that date.

Is gemini-omni-1.1-flash-preview the stable model ID?

No. It is a separate Vertex AI / Agent Platform preview-channel ID. The stable Gemini API ID is gemini-omni-1.1-flash.

Can one API call generate 40 seconds?

No. One generation or extension returns 3–10 seconds. Forty seconds is the cumulative ceiling after repeated multi-turn extensions.

Are 1080p and 4K native outputs?

No. Google explicitly describes both as upscaled outputs. The default remains 720p.

What does duration mean for video extension?

It is the number of seconds appended to the input, not the final output length.

Can I reuse the old preview price for 1.1?

Do not assume that. Use a currently verified provider price or EvoLink's live route price and keep the two scopes separate.

Choose the task-specific ID on the Gemini Omni 1.1 Flash page: text-to-video, image-to-video, reference-to-video, video edit, or video extend.

Sources

Ready to Reduce Your AI Costs by 89%?

Start using EvoLink today and experience the power of intelligent API routing.