Google Veo (& Flow)

What it is

Google DeepMind’s Veo line — currently Veo 3.1 — is Google’s standalone cinematic video generation model, reachable through Flow, the Gemini app, the API, and a growing list of third-party platforms that host it. Flow is the companion studio that layers prompt-based shot control and scene assembly on top.

Worth getting the relationship right, because the “Omni replaced Veo” framing going around is wrong: the two coexist inside Flow. Gemini Omni is the conversational, iterative editing model; Veo 3.1 is the one you reach for when the job is generating a cinematic shot outright, with audio generated natively in the same pass. And despite the chatter, there’s still no Veo 4 — no model card, no release, no API ID.

What it introduced

The thing that set Veo 3 apart from most competing models: native audio output alongside the video. Not added in post, not a separate model pass — dialogue with lip-sync, sound effects, and ambient audio generated as part of the clip. That’s a real architectural difference, and it changed what you reach for the tool to do. Veo 3.1 carries it forward, with 1080p and 4K output, scene extension, first- and last-frame transitions, and object insert/remove for shot cleanup.

Flow’s shot control and scene-assembly layer is worth understanding separately from the base model — how Google structured the editing tooling around Veo is its own thing.

What the coverage covers

Veo coverage on the channel spans Veo 3, the Veo 3 upgrade, the Veo 4 rumors alongside Krea, and Google I/O workflow content. The related videos are the anchor points for what’s been tested versus what’s been reported.

Where it sits

Here’s the honest state of it: Google’s naming conventions are all over the place. Veo 3.1 and Gemini Omni split the video story between them — generation versus editing, one studio — but try as I might, I haven’t gotten anyone at Google to say straight whether Omni is now Veo, or vice versa. I put exactly that question to Logan Kilpatrick and Josh Woodward in this interview, and still came away without a clean answer.

Bottom line: Veo 3.x is getting pretty long in the tooth, and we’re all waiting for a big Omni or Veo 4 update at this point.