Google Gemini API · model
veo-3.0-generate-001 deprecation: shutdown date & replacement
Shut down June 30, 2026
All providers: veo-3.0-generate deprecation status →
- Provider
- Google Gemini API
- Type
- model
- Announced
- —
- Shutdown
- Replacement
veo-3.1-generate-preview- Source
- Official Google Gemini API notice
Page lists announced earliest shutdown date. Page also suggests the GA Veo models on the Gemini Enterprise Agent Platform.
How to migrate off veo-3.0-generate-001
- Find every place that references it:
grep -rn --exclude-dir={node_modules,.git,dist} "veo-3.0-generate-001" . - Replace the model ID:
- model: "veo-3.0-generate-001" + model: "veo-3.1-generate-preview" - Re-run your evals or a sample of real prompts — output style, token usage and pricing can change between models.
- Check config outside code too: environment variables, feature flags, prompt-management tools, and fine-tuned model references.
- Deploy before June 30, 2026, and add the CI scanner so it cannot come back.
Same model on other platforms
- Google Cloud Vertex AI (Gemini Enterprise Agent Platform) — June 30, 2026
Also shutting down on June 30, 2026 (Google Gemini API)
Questions
Is veo-3.0-generate-001 deprecated?
Yes. Google Gemini API has deprecated veo-3.0-generate-001. It was shut down on June 30, 2026.
When does veo-3.0-generate-001 shut down?
June 30, 2026, according to Google Gemini API's official deprecation notice.
What should I use instead of veo-3.0-generate-001?
Google Gemini API recommends veo-3.1-generate-preview. Switch the model ID and re-test your prompts, since outputs, pricing and limits can differ.
What happens to requests to veo-3.0-generate-001 after the shutdown?
Requests using the retired model ID fail with an error, so any code still calling it breaks. Update and deploy before the shutdown date.