Veo 3.0 Generate 001 retirement date: June 30, 2026
Retired on June 30, 2026; requests to veo-3.0-generate-001 now fail.
- Provider
- Google (Gemini API)
- Model IDs affected
veo-3.0-generate-001- Shutdown date
- June 30, 2026
- Replacement
- gemini-omni-1.1-flash or the GA models on the Gemini Enterprise Agent Platform
- Platforms
- Dates apply to the Gemini API and are the earliest possible shutdown dates Google publishes. If you use Gemini through another platform, check that platform's own schedule.
- Source
- Official Google (Gemini API) deprecations page (data last changed 2026-11-02, re-checked daily)
Migrating from Veo 3.0 Generate 001
Not yet reviewed. We haven't written model-specific migration notes for Veo 3.0 Generate 001 yet. Start with the provider's official guidance and the replacement's model page, and use this general checklist:
- Search your code, config and environment variables for
veo-3.0-generate-001. - Re-run your evaluation set against gemini-omni-1.1-flash or the GA models on the Gemini Enterprise Agent Platform before switching traffic.
- Recount tokens with the new model's tokenizer and re-check
max_tokens, context fit and cost. - Check tool calling, structured output and stop sequences on your real prompts.
- Dates apply to the Gemini API and are the earliest possible shutdown dates Google publishes. If you use Gemini through another platform, check that platform's own schedule.
Check your code before Jun 30
Also shutting down on June 30, 2026
- Veo 2.0 Generate 001
veo-2.0-generate-001 - Veo 3.0 Fast Generate 001
veo-3.0-fast-generate-001
All model retirements · All Google (Gemini API) deprecations
FAQ
When was Veo 3.0 Generate 001 retired?
Veo 3.0 Generate 001 (veo-3.0-generate-001) was retired on the Gemini API on June 30, 2026, according to the official Gemini API deprecations page. Requests to it now fail.
What should I use instead of veo-3.0-generate-001?
The recommended replacement is gemini-omni-1.1-flash or the GA models on the Gemini Enterprise Agent Platform.
What happens to veo-3.0-generate-001 requests after the shutdown date?
After a model is retired, API requests to it return an error. Move traffic to the replacement and test it on your own prompts before the date.
Does this date apply to Amazon Bedrock, Vertex AI or Azure?
Dates apply to the Gemini API and are the earliest possible shutdown dates Google publishes. If you use Gemini through another platform, check that platform’s own schedule.