Google to shut down Veo 2.0 and Veo 3.0 video generation models on June 30, with Imagen 4 to follow in August

Google announced on June 15, 2026 that Veo 2.0 and Veo 3.0 — its current video generation models available via the Gemini API — will shut down on June 30, 2026. The same changelog entry confirmed that Imagen 4 image generation models will follow, with an August 17, 2026 shutdown date. The shutdown window for Veo is unusually tight: developers had just 15 days from the announcement to migrate.

What's changing

Three sets of model IDs are being retired:

Video generation — shutting down June 30, 2026:

• veo-2.0-generate-001
• veo-3.0-generate-001
• veo-3.0-fast-generate-001

Image generation — shutting down August 17, 2026:

• imagen-4.0-generate-001
• imagen-4.0-ultra-generate-001
• imagen-4.0-fast-generate-001

For Veo, Google's changelog directs developers to migrate to Veo 3.1 — either the preview or generally available model IDs — before June 30 to avoid service interruptions. For Imagen 4, the changelog points to Google's Gemini deprecations page for migration guidance.

Context

Veo 2.0 launched in late 2024 and Veo 3.0 followed in early 2026, with Veo 3.0 adding audio synthesis to video generation — one of the first publicly available models to produce synchronized video with sound. Both have been accessible to developers through the Gemini API.

The retirements are part of a broader fleet consolidation Google has been running since early 2026. Gemini 2.0 Flash and Flash Lite were discontinued on June 1, 2026. The GMP Contextual View tool was also discontinued effective June 15. Google has shipped newer image generation capabilities — gemini-3.1-flash-image (Nano Banana 2) and gemini-3-pro-image (Nano Banana Pro) — as generally available models since May 28, 2026.

Why it matters

The 15-day shutdown window for Veo 2.0 and Veo 3.0 is the most immediate concern. Developers with production video generation pipelines need to update their integration to Veo 3.1 model IDs by June 30, 2026 — five days from today — or face broken API calls. Google's changelog links to the deprecations page for specifics, but the tight timeline leaves limited room for testing and migration.

For Imagen 4 users, the August 17 deadline provides more time, but the pattern here — multiple model generations being retired in rapid succession — reflects how quickly Google is consolidating around the Gemini 3.5 and 3.1 generation of models. Developers building on Gemini API media generation capabilities should treat any preview model IDs as temporary and plan for regular migration cycles going forward.