Google Gemini API deprecates all Imagen 4 and Veo 2.0/3.0 models, Veo shutdown set for June 30

Google announced on June 15 the deprecation of six media generation models across its Gemini API — all three Imagen 4 image generation variants and all three Veo video generation models in the 2.0 and 3.0 families. The Veo models have a hard shutdown date of June 30, 2026, giving API users roughly two weeks to migrate.

What's new

Veo video generation models — shutdown June 30, 2026:

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

The migration path is to Veo 3.1: "Update your integration to either use the Veo 3.1 preview model IDs (veo-3.1-generate-preview, veo-3.1-fast-generate-preview) or the 3.1 GA models available through the Gemini Enterprise Agent Platform to avoid service interruptions."

Imagen 4 image generation models — shutdown August 17, 2026:

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

"The following image generation models are being deprecated and will be shut down on August 17, 2026," the changelog states. Developers are directed to the Gemini deprecations page for migration guidance to newer endpoints.

Also on June 15, Google discontinued the experimental GMP Contextual View tool, which provided a fixed interface for Grounding with Google Maps outputs.

Context

Google has been consolidating its Gemini API media generation lineup throughout 2026. The Gemini 2.0 Flash model family was shut down on June 1. The June 15 deprecations continue that compression: Google is compressing its supported model surface rather than maintaining long-lived legacy endpoints.

For Veo specifically, the timeline is aggressive — 15 days from the June 15 announcement to the June 30 shutdown — suggesting Google is actively driving migration rather than allowing a long coexistence period. Veo 3.1 is being positioned as the replacement for both 2.0 and 3.0, with preview and GA versions already available.

For Imagen 4, the August 17 deadline is more generous at about two months from the announcement. But the deprecation covers all three Imagen 4 tiers (standard, ultra, and fast), making it a full generational sweep rather than selective pruning.

Why it matters

Developers using these models in production have two distinct deadlines to track. Anyone running veo-3.0-generate-001 — until recently Google's most capable video generation API model — faces a hard service interruption if they do not migrate by June 30. The compressed timeline for Veo is unusual relative to Google's typical deprecation windows and warrants immediate attention for any application built on the Veo 3.0 family.

The Imagen 4 deprecation carries a different signal: it is a full-generation removal rather than a selective cut, suggesting Google considers the Imagen 4.x line superseded by newer models. For teams with image generation pipelines, the August deadline is manageable but should enter sprint planning now rather than closer to the date.