Google releases Gemini Omni 1.1 Flash video generation model

The headline technical change in 1.1 Flash is almost boring to describe but hard to overstate in effect: scene extension now reads up to 10 seconds of prior footage before generating the next segment, instead of relying on a single final frame the way the original Omni Flash did ^[1]. That sounds like a minor parameter tweak, but it directly targets the failure mode that made multi-clip AI video so fragile - a character's jacket changing color, a room's lighting flattening out, or a background prop vanishing between cuts because the model had almost no memory of what came before. With a 10-second window, the model can extend clips in 10-second increments up to a 40-second cumulative maximum, giving creators enough runway to build a short scene rather than a single disconnected shot.

Paired with the context-window upgrade is first-and-last-frame keyframe control, which lets a creator specify exactly how a shot should begin and end - useful for camera orbits, zooms, and looping clips that need to land on a precise final composition rather than wherever the model happens to drift ^[2]. Google also added support for up to three seconds of reference video, drawn from as many as three separate clips, specifically to help the model hold onto a character's appearance or a camera's motion style across generations ^[2]. None of this makes Omni cinematic, but it is a meaningful admission that the previous version's memory was the bottleneck, not raw image quality.

That memory upgrade shows up plainly in how creators are actually using the model. Developer walkthroughs posted online have leaned into conversational, iterative editing - asking the model to change a cat's color mid-conversation, for instance, while it keeps the same scene, shot, and camera framing intact. Hands-on demos have also highlighted native audio output generated alongside the video and what creators describe as a kind of world knowledge - motion that respects physics like weight, momentum, and contact rather than sliding or floating unnaturally. A recurring practical use case in these demos is restyling: taking an existing clip and changing its visual style while preserving the underlying character movement, camera path, and composition, which is exactly the kind of workflow the extended context window and reference-video support are built to support.

The more consequential change for anyone actually paying for this model is economic, not creative. A new 360p draft mode generates up to 60% faster and at roughly one-third the cost of standard 720p generation ^[3], which turns AI video from a one-shot gamble into an iterative workflow: generate cheap, rough drafts at 360p, lock in the composition and motion you want, then pay only once to upscale the winning take to 1080p or 4K. Google's published pricing makes the tiering explicit - $0.03 per second at 360p, $0.10 at 720p, $0.15 at 1080p, and $0.30 at 4K, a 10x spread between the cheapest draft and the most expensive final export ^[4].

That pricing structure, alongside a separate token-based rate for API calls that mix text, video, and output tokens, is clearly built around a production mentality rather than a one-off novelty generation ^[1]. For a marketing team or solo creator, it means the cost of exploring five or ten variations on a shot no longer scales linearly with final-render cost - you only pay full price for the version you keep. That draft-first economics is arguably a bigger unlock for adoption than any single creative feature, because it removes the main reason generative video felt too expensive to iterate on.

Omni Flash's release timing and feature set only make full sense against the competitive backdrop. Commentary framing the model notes a direct contrast with OpenAI's Sora 2: where Sora leans into longer, higher-fidelity premium clips, Omni Flash is being positioned around workflow integration and high-volume, conversational multimodal output rather than chasing raw visual fidelity ^[6]. That's a different bet - instead of winning on any single generation's polish, Google is trying to win on how many tools a team can retire by using one model for relighting, reframing, wardrobe changes, and text overlays in a single conversational thread ^[5].

The model's multilingual support (Chinese, Japanese, Korean) is also read as a deliberate move to compete head-on with ByteDance's Seedance, Alibaba's Wan, and Kuaishou's Kling, rather than ceding the fast-growing Asian video-generation market to them ^[6]. Production integrations reinforce the workflow-first strategy: Adobe has already wired Omni Flash into Firefly for plain-English video edits with provenance metadata carried through ^[8], and Figma's Weave canvas product cites it as one of the strongest video models it has access to ^[2]. Both partnerships suggest Google is optimizing for where the model gets embedded, not just how good any single clip looks in isolation.

There's a real tension between how Omni 1.1 Flash is performing on leaderboards and how it's landing with people actually using it day to day. Third-party benchmarking has been favorable, with the model reported to top text-to-video rankings and place near the top of image-to-video comparisons. But community reaction on forums where creators post side-by-side tests has been decidedly more mixed: the extended context window for scene extension is welcomed as a genuine technical leap that addresses the character- and lighting-consistency problems of the earlier model, yet plenty of hands-on testers still rate the output as noticeably behind Seedance, Minimax, and Kling on physical realism - motion like backflips or fast action still shows artifacts and unnatural slow-motion glitches.

VentureBeat's enterprise-focused analysis lands somewhere in the middle of that divide: it credits the conversational, multi-turn editing as a real productivity win for marketing teams who need quick relighting or wardrobe swaps, while flagging that native clip lengths remain short (three to ten seconds before extension), the base resolution tops out at 720p before upscaling, and there's still no native audio-input support or deepfake/lip-sync capability - meaning premium, longer-form production work is still likely to stay on Veo 3.1 or Sora 2 ^[5]. The gap between "state of the art on a benchmark" and "as good as the leading Asian video models in practice" is the most honest read on where Omni 1.1 Flash currently sits.

Every video Omni produces carries Google's imperceptible SynthID digital watermark, with no option in the API to disable it, layered alongside C2PA Content Credentials for provenance tracking ^[7]. That's a deliberate design choice going back to Omni's original unveiling at Google I/O 2026 by Sundar Pichai and Demis Hassabis, where the model was introduced as Google's first any-to-any multimodal system - and the provenance stack has stayed intact as the model has moved from a consumer-only Gemini app feature into a full developer API and enterprise platform ^[7]. Notably, the first public hint of the model's existence came weeks earlier, when leak tracker TestingCatalog spotted an unreleased "Powered by Omni" string inside Gemini's video tab ^[10].

With SynthID and C2PA now baked into every clip with no opt-out, Google is effectively trying to make watermarking a default expectation for AI-generated video rather than an optional add-on - relevant given that OpenAI has also adopted C2PA for its own outputs ^[7]. As enterprises adopt tools like Omni Flash for real production work, that provenance layer intersects with governance concerns such as the EU AI Act, and analysts have flagged workforce and compliance questions as a medium-term consideration for any company building creative workflows on top of the model ^[6].