Google sets June 30 shutdown for Veo 2 and Veo 3 video generation model IDs, migrates users to Veo 3.1

Google has scheduled the shutdown of its Veo 2.0 and Veo 3.0 video generation model IDs for June 30, 2026 — three days away — with users directed to migrate to Veo 3.1 preview or GA models. The deprecation was announced June 15 and also covers Imagen 4.0 image generation models on a longer August 17 timeline.

What's new

According to the Gemini API changelog, Google is retiring the following video model IDs on June 30, 2026: veo-2.0-generate-001, veo-3.0-generate-001, and veo-3.0-fast-generate-001. Developers must migrate to either veo-3.1-generate-preview, veo-3.1-fast-generate-preview, or the 3.1 GA models available through the Gemini Enterprise Agent Platform.

A parallel deprecation with a longer runway covers Imagen 4.0 image generation models — imagen-4.0-generate-001, imagen-4.0-ultra-generate-001, and imagen-4.0-fast-generate-001 — scheduled for shutdown on August 17, 2026.

Also retired on June 15: the GMP Contextual View Tool, an experimental feature for Grounding with Google Maps outputs.

Context

Veo 3 was Google's flagship video generation model at launch, delivering high-quality cinematic output with audio synthesis. Veo 3.1 follows with a refined architecture and is now the production path Google actively supports. Sunsetting both Veo 2.0 and Veo 3.0 simultaneously pushes all API users to a single upgrade target rather than allowing multiple legacy versions to persist.

The Imagen 4.0 deprecation follows the same pattern: a two-month window before shutdown. Google has not specified a named Imagen replacement in this entry, but the Gemini Enterprise Agent Platform routing for Veo 3.1 GA suggests enterprise media generation is consolidating into a managed platform rather than raw API model IDs.

The rapid succession of Veo generations — 2.0, then 3.0, then 3.1 — reflects how quickly video generation capability is improving. Each iteration has been meaningfully better at temporal consistency, motion quality, and audio alignment. Google appears unwilling to let developers default to stale model IDs when better options exist.

Why it matters

The June 30 deadline is immediate. Production systems using veo-2.0-generate-001 or the Veo 3.0 model IDs have three days to validate Veo 3.1 and update their integration before requests start failing. Pipelines that generate video at scale — content marketing, social media automation, video localization, UI preview generation — face interruption if migration is not completed in time.

For developers, the lesson is practical: building against specific Google media model IDs carries integration debt. Dynamic routing logic that does not hard-code model strings will be less painful to maintain as Google continues accelerating its deprecation cadence.

For the broader video generation market, Google's willingness to force migration to Veo 3.1 within 15 days of announcement signals confidence that 3.1 is ready for production traffic and that the company views prolonged legacy support as a cost not worth paying when a better model is available.