Google deprecates Imagen 4 and Veo 2/3 models from the Gemini API, Veo shutdown in 15 days

Google announced on June 15 that it is deprecating all three Imagen 4 image generation models and three Veo video generation models from the Gemini API. The Imagen 4 family shuts down August 17, 2026; Veo 2.0 and Veo 3.0 models shut down June 30, 2026 — fifteen days from now.

What's new

Image generation models — shutdown August 17, 2026:

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

Video generation models — shutdown June 30, 2026:

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

Google's Gemini API changelog states that "the following image generation models are being deprecated and will be shut down on August 17, 2026" for the Imagen 4 family. For video, the announcement specifies "the following video generation models are being deprecated and will be shut down on June 30, 2026." Developers are directed to migrate to Veo 3.1 preview model IDs, or to the Veo 3.1 GA models available through the Gemini Enterprise Agent Platform.

The Gemini API deprecations page carries full migration guidance for affected integrations.

Context

This deprecation cycle reflects Google's accelerating model replacement pace in 2026. Imagen 4 and the Veo 2.0/3.0 family were the primary image and video generation options in the Gemini API. Veo 3.1 — both preview and GA — is now the designated successor for video.

Google has been consolidating its Gemini API surface aggressively this year. The Gemini 2.0 Flash family was shut down June 1. Today's announcement adds six more model IDs to the sunset list, all in the generation category. The pattern suggests a quarterly deprecation rhythm for older model generations once successors reach general availability.

The Veo 3.1 GA path is notable: access is tied to the Gemini Enterprise Agent Platform rather than the standard Gemini API endpoint. Developers using the direct API may need to evaluate whether their access tier or contract covers the new platform.

Why it matters

The June 30 Veo deadline is the urgent concern. Any production application calling veo-2.0-generate-001, veo-3.0-generate-001, or veo-3.0-fast-generate-001 will fail in fifteen days without migration. Veo 3.1 is the direct replacement, but the move to the Gemini Enterprise Agent Platform for GA access may require a different quota, contract tier, or authentication path.

For the Imagen 4 family, the August 17 deadline provides more runway, but teams should begin migration planning now. The gap between today and August 17 looks long until it doesn't — production migrations for image generation pipelines that have been running on stable model IDs often surface integration issues that take longer than expected to resolve.

Google has not announced a direct Imagen 5 replacement in the public Gemini API changelog, though newer preview models exist in some access tiers. Developers should consult the Gemini deprecations page for the current recommended migration target before assuming a direct swap is available.