veo-3.1-generate-preview — Deprecated

Quick fix — copy & paste

Choose your language. The "before" block matches the deprecated call; the "after" block is the drop-in replacement.

# Gemini: veo-3.1-generate-preview (active)
model = "veo-3.1-generate-preview"

# No direct replacement — see Gemini docs.
# Pick a current model from the provider's available list.

// Gemini: veo-3.1-generate-preview (active)
const model = "veo-3.1-generate-preview";

// No direct replacement — see Gemini docs.
const model = "<choose a current model>";

"model": "veo-3.1-generate-preview"

"model": "<choose a current model>"

This migration was generated automatically from the model rename. If your code does more than swap a model id, double-check request/response shapes against the official Gemini migration guide.

Error messages

Seeing one of these? You're in the right place.

• model_not_found: veo-3.1-generate-preview
• The model `veo-3.1-generate-preview` has been deprecated
• The model `veo-3.1-generate-preview` does not exist or you do not have access to it

Other Gemini deprecations

• gemini-3.1-flash-lite-preview 2026-05-25 · 17d
• gemini-2.0-flash 2026-06-01 · 24d
• gemini-2.0-flash-001 2026-06-01 · 24d
• gemini-2.0-flash-lite 2026-06-01 · 24d
• gemini-2.0-flash-lite-001 2026-06-01 · 24d

What this means for your code

veo-3.1-generate-preview is a specialized model with provider-specific behavior. Verify the replacement supports the same modalities, parameters, and rate limits as the deprecated model. Read the provider's migration notes carefully — these models often have non-obvious behavioral changes.

veo-3.1-generate-preview has been marked deprecated by Gemini. A specific shutdown date has not been published, but deprecated models typically receive 6-12 months of notice before retirement.

Find every call in your codebase

Before you change anything, locate every place the deprecated model id is referenced. Search source files, environment files, feature flags, and config repos. Use these commands from your project root:

grep -rn '"veo-3.1-generate-preview"' --include="*.py" .

grep -rn '"veo-3.1-generate-preview"' --include="*.{js,ts,tsx,jsx}" .

grep -rn "veo-3.1-generate-preview" .

Migration checklist

Steps in order. Skip any that don't apply, but read the whole list — for other models, the non-obvious steps are usually the ones that break in production.

1. 1. Read the provider's official migration guide for this model
2. 2. Update the model id and any model-specific parameters
3. 3. Audit rate limits and request size caps for the replacement
4. 4. Re-run your full integration test suite against the new model
5. 5. Plan a rollback path in case the new model behaves differently in production