Google shuts down Veo 2.0 and Veo 3.0 video generation API models today — migrate to Veo 3.1 or GA

Google's Veo 2.0 and Veo 3.0 video generation models reached end-of-life on June 30, 2026, with access to the deprecated model IDs now cut off. Developers who have not yet migrated away from these endpoints will find their API calls returning errors starting today.

What's new

Three model IDs were shut down effective June 30, 2026:

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

The deprecation was announced on June 15, 2026, giving developers a 15-day migration window. Google's recommended paths are the Veo 3.1 preview model IDs or the generally available Veo models accessible through the Gemini Enterprise Agent Platform.

No equivalent action is required for Veo 3.1 or the GA model family — only the specific model IDs listed above have been retired.

Context

The Veo 2.0 and Veo 3.0 model IDs were the original generation of Google's video synthesis capability on the Gemini API. Since their introduction, Google has developed Veo 3.1, which offers improved video quality and faster generation, as well as a stable GA version designed for production use. The June 15 deprecation notice came alongside the announcement that Imagen 4.0 image generation models would also be deprecated, with a longer runway: Imagen 4.0 shuts down August 17, 2026.

This is part of a broader lifecycle housekeeping cycle at Google, which has been accelerating model generations across its Gemini family throughout 2026.

Why it matters

For teams that built video generation pipelines on the Veo 2.0 or Veo 3.0 API endpoints, today is a hard cutoff. Applications still pointing at the retired model IDs will start failing immediately. The migration itself is straightforward — update the model ID string and test output quality against Veo 3.1 — but teams that missed the June 15 deprecation notice are now in incident response mode rather than planned migration mode.

Developers should audit their integrations today and update any hardcoded references to veo-2.0-generate-001, veo-3.0-generate-001, or veo-3.0-fast-generate-001 before production traffic is impacted.