Veo 2.0 and Veo 3.0 API Shutdown

End of Life for Veo 2.0 and Veo 3.0

Google has announced the shutdown of its first two generations of video generation API endpoints, effective June 30, 2026. Three model IDs are affected: veo-2.0-generate-001, veo-3.0-generate-001, and veo-3.0-fast-generate-001. After that date, any API call targeting these endpoints will return an error — Google has confirmed there is no automatic fallback or routing to a newer model.

Which Models Are Being Removed

The affected models span two product generations:

• Veo 2.0 (veo-2.0-generate-001): Released April 9, 2025. Google's first widely available video generation API, capable of 720p output with cinematic control.
• Veo 3.0 (veo-3.0-generate-001): Released September 9, 2025. Brought natively synchronized audio generation alongside visual output.
• Veo 3.0 Fast (veo-3.0-fast-generate-001): Also released September 9, 2025. The lower-latency variant of Veo 3.0, designed for higher-volume pipelines.

All three share the same June 30, 2026 hard shutdown date.

Migration Path: Veo 3.1

Google's recommended replacement for all three deprecated models is the Veo 3.1 family, available through the Gemini API. The migration is a model ID swap in the API call:

• Replace veo-3.0-generate-001 or veo-2.0-generate-001 with veo-3.1-generate-preview
• Replace veo-3.0-fast-generate-001 with veo-3.1-fast-generate-preview

Veo 3.1 brings meaningful capability improvements over its predecessors, including richer native audio synthesis, better narrative control, reference-image-guided generation (up to 3 input images), scene extension for creating longer videos from connected clips, and first/last frame generation for creating smooth transitions. Pricing for Veo 3.1 is the same as Veo 3.0.

For developers running production workloads on Vertex AI or the Gemini Enterprise Agent Platform, GA-tier Veo 3.1 endpoints are also available alongside the preview endpoints, offering stronger reliability guarantees.

What Happens If You Do Not Migrate

Unlike some past Google API deprecations, there is no silent auto-routing to a newer model. Calls to the deprecated model IDs will begin returning errors on June 30, 2026. Any application, pipeline, or integration that references veo-2.0-generate-001, veo-3.0-generate-001, or veo-3.0-fast-generate-001 will stop working at that date without intervention.

Developers should audit their codebases for hardcoded model IDs and update them before the deadline. The Gemini API deprecations page at ai.google.dev/gemini-api/docs/deprecations is the canonical reference for tracking current shutdown schedules.