Veo 3 shutdown: which Gemini API models retired and what replaces them

If you still call veo-3.0-generate-001, veo-3.0-fast-generate-001 or veo-2.0-generate-001, those models have a shutdown date of June 30, 2026 on Google's deprecations page, which recommends veo-3.1-generate-preview or veo-3.1-fast-generate-preview (or the GA models on the Gemini Enterprise Agent Platform). The fix is a model-code change plus a check of the parameters that differ. Sume does not list a Veo model, so this is Google-side work.

Dates are from Google's deprecations page and the Veo page, read 2026-09-29.

Which Veo models are shut down?

The Veo 3.1 rows are Preview models with no announced shutdown, so Google can still change them.

What changes when I move to Veo 3.1?

Google's Veo page lists the 3.1 additions: portrait 9:16, video extension, first and last frame, and up to three reference images. Duration is 4, 6 or 8 seconds; 1080p and 4K need 8 seconds, and reference images need 8 seconds. Read your existing calls against that page rather than assuming they carry over.

How do I stop a retirement from breaking my pipeline?

Keep the model code in config, not in code, and re-read the vendor's deprecations page on a schedule. On Sume, ask GET /v1/videos/models for the live list, or send model: "sume/auto" and let Sume pick the family. Sume docs also say the older Video 1.0 URLs are retiring soon and map to the same Auto pipeline.

curl "https://api.sume.com/v1/videos/models" \
  -H "Authorization: Bearer $SUME_API_KEY" | jq -r '.data[].id'

Is Sora retiring too?

Yes, on a different date: OpenAI's deprecations page lists the Videos API and the Sora 2 models with a 2026-09-24 shutdown. Sora API alternatives covers that move.