ClipCanva

Veo 3.1 Split on 22 October. Enterprise GA Is Not a Signed Script

Google’s Agent Platform still documents Veo 3.1 GA after 21 Oct 2026. Gemini API preview cards list a 22 Oct shutdown. Lock the script before you pick a string.

October 22, 2026ClipCanva Editorial

Veo 3.1 Split on 22 October. Enterprise GA Is Not a Signed Script

22 October 2026 is the shutdown date Google’s Gemini API model cards still print on Veo 3.1 preview IDs. Those cards name gemini-omni-1.1-flash or the GA models on Gemini Enterprise Agent Platform as the way out. Google Cloud’s own Veo 3.1 page, last updated 21 October 2026, still lists veo-3.1-generate-001 as GA, with clips of 4, 6, or 8 seconds and a retirement date of 17 November 2026 or later. Those are two desks. ClipCanva is not affiliated with Google, VEED, Kapwing, or Synthesia. Lock the spoken line on the AI script generator. Steal shot language from prompt ideas. Animate a locked frame on image to video or generate motion on the AI video generator. Do not brief “Veo died today, ship the restock.”

Product facts (confirmed 22 October 2026)

Source Public claim Workflow implication
Gemini API: Veo 3.1 (page last updated 2026-10-19 UTC) veo-3.1-generate-preview and veo-3.1-fast-generate-preview “are deprecated and will be shut down on October 22, 2026.” Migrate to Gemini Omni Flash (gemini-omni-1.1-flash) or the GA models on Gemini Enterprise Agent Platform. A preview string on the Gemini API. Not a statement that every Veo SKU is gone.
Gemini API: Veo 3.1 Lite preview (page last updated 2026-10-19 UTC) veo-3.1-lite-generate-preview “is deprecated and will be shut down on October 22, 2026.” Same migration sentence. Lite is a third preview ID. Grep it too.
Generate videos with Veo 3.1 in Gemini API Repeats the same 22 October 2026 shutdown for all three preview IDs, and the same Omni Flash / Agent Platform GA migration. One video overview. Three strings. One calendar.
Veo 3.1 on Gemini Enterprise Agent Platform (fetched 22 Oct 2026; page last updated 2026-10-21 UTC) 3.1 Generate model ID veo-3.1-generate-001. Launch stage GA. Release date 17 November 2025. Retirement date 17 November 2026 or later. Text-to-video, image-to-video, first and last frame, extend, reference images, sound, C2PA: supported. Lengths 4, 6, or 8 seconds; reference-image-to-video 8 seconds only. Output 720p / 1080p / 4K, 24 FPS, 9:16 and 16:9. Region us-central1. Prompt language English. Batch inference not supported. Pay-as-you-go not supported. A GA Cloud ID. Updated yesterday. Not the preview string.
Same Cloud page, 3.1 Fast Generate Model ID veo-3.1-fast-generate-001. GA. Same 17 Nov 2025 / 17 Nov 2026-or-later window. Output 720p and 1080p (this row does not list 4K). Lengths 4 / 6 / 8 seconds. Fast is a second GA ID, not “the cheap preview.”
Same Cloud page, 3.1 Lite Generate Model ID veo-3.1-lite-generate-001. Launch stage Preview. Release date 2 April 2026. Reference images not supported. Modalities list Image: not supported. Capabilities still list text-to-video / image-to-video / first-and-last-frame / extend. Do not brief Lite from the nickname. Screenshot the row.
Same Cloud page, footnote “The Gemini API is not a Google Cloud offering and is subject to its own terms of service.” Retirement dates “refer to retirement of support in Gemini Enterprise Agent Platform.” API shutdown and Cloud retirement are different calendars.
VEED AI Script Generator Own URL. Prompt → script. Separate AI Video Generator. FAQ still splits “generate a video script” from hitting generate-video. Writer and renderer stay different URLs.
Kapwing AI Script Generator Own URL. Separate AI Video Generator. Kapwing still splits script and video.
Synthesia Explainer Video Maker Own URL for explainers. Product nav still lists an AI Video Generator that turns docs and prompts into video. An explainer maker is not an 8-second restock desk.

Google did not publish, on the pages above, a hard “every Veo endpoint is dark at 00:00 UTC on 22 October,” a ClipCanva credit map, or a signed legal sentence for your SKU. If a capability is not on the page you are briefing from today, it is not a brief. This machine could not open ai.google.dev without an OAuth redirect loop; the Gemini API rows above are the public model-card text those URLs still served as of the 19 October 2026 update. Treat a live 404 or a new banner as a new screenshot, not as this table.

This is not the 11 October preview note. That piece flagged the earliest date. Today the Cloud GA page is a day old, and the API cards still print 22 October.

What 22 October split — and what it did not

Operators will collapse four objects into “Veo is dead, Omni will write the restock.” The public pages refuse that.

Surface What the public page says it does What it does not do Fail condition
Gemini API veo-3.1-*-preview Listed with shutdown 22 Oct 2026; replacement Omni Flash or Agent Platform GA Prove veo-3.1-generate-001 is gone; prove the exact clock time Leaving a -preview ID in prod because “Cloud still has Veo”
gemini-omni-1.1-flash Named as the Gemini API migration target on the 19 Oct cards Sign Legal copy; become a two-minute explainer; inherit Cloud’s 4K row Briefing “Omni is the campaign”
Agent Platform veo-3.1-generate-001 (GA) 4 / 6 / 8s, first+last frame, extend, refs, sound, C2PA, up to 4K Run on the Gemini API preview key; write the VO; ship a 60s cut Calling it “the same Veo as yesterday’s notebook”
Agent Platform veo-3.1-fast-generate-001 (GA) Same lengths; output 720p / 1080p 4K; a stay of execution for -preview Picking Fast because the nickname matches the old preview
Agent Platform veo-3.1-lite-generate-001 (Preview) Preview since 2 Apr 2026; no reference images on that row Cancel the API Lite shutdown; fix a contradictory Image row Shipping Lite because “Cloud still lists it”
VEED / Kapwing script URLs Generate a script Disclose on YouTube; pick 6s vs 60s; lock a SKU still Hitting generate-video from an unsigned paragraph

If you are calling veo-3.1-generate-preview, you are on a dated Gemini API preview desk. If you are calling veo-3.1-generate-001, you are on a Cloud GA desk whose own retirement line is November, not today. If the bottle still needs a legal sentence, you are on a writer. If you cannot tell which, do not cut over.

Pick the desk before you rewrite the model string

The fail is treating “shutdown: 22 October” as “the eight-second restock is covered.” Map the job.

Job Where it actually runs What you must supply What the system may invent Fail condition
One claim the clip must carry AI script generator — or VEED / Kapwing if that is already your writer Audience, seconds, the signed sentence A second CTA, a health claim, a competitor name Skipping the card because “we migrated Veo”
Recap of a long cut AI video summarizer Source cut, claims to keep, claims to strike Compression that changes meaning Feeding the webinar into Veo as if video-in meant a new master
Motion from a locked still Image to video, or Cloud Veo image-to-video / first+last frame The signed still as frame one. Cloud: reference-image-to-video is 8 seconds only Camera path, extra hands, a spoken line you did not approve Animating take three because the GA ID looks sharper
New motion without a locked frame AI video generator or a named model on Compare Locked caption, crop, seconds (4 / 6 / 8 on the Cloud card) Props, voices, a second location Briefing Veo GA as a two-minute explainer
Model pick Compare plus the live API card and the Cloud GA page Job = API preview vs Omni Flash vs …-001 vs a non-Google renderer A leaderboard screenshot from June Picking “Veo” as if it were one string

VEED still keeps AI Script Generator as its own URL and AI Video Generator as another. Kapwing still keeps Script Generator and Video Generator as different nav items. Synthesia still keeps an explainer URL next to a docs-to-video generator. None of those pages say a Google model-ID swap writes your CTA.

If the brief is “grep the repo for -preview,” that is engineering. If the brief is “the two-pack restocks Friday on YouTube,” that is script, still, then image-to-video. If the brief is “Enterprise GA will handle the clip because Cloud updated yesterday,” you do not have a brief.

Creator / operator checklist

  1. Name the string out loud. veo-3.1-generate-preview ≠ veo-3.1-generate-001 ≠ veo-3.1-fast-generate-001 ≠ veo-3.1-lite-generate-001 ≠ gemini-omni-1.1-flash. Screenshot the model code in logs, not the nickname on a slide.
  2. Grep before you generate. Search production, staging, notebooks, and vendor dashboards for -preview. A hidden Fast preview call is still a preview ID.
  3. Do not treat 22 October as a Cloud kill switch. The Agent Platform page last updated 21 October 2026 still marks Generate and Fast as GA, with retirement 17 November 2026 or later. That is a different calendar, and Google says so in the footnote.
  4. Do not treat GA as unlimited length. Cloud Veo 3.1: 4, 6, or 8 seconds. Reference-image-to-video: 8 seconds only. A 10-second Omni habit does not stretch this card.
  5. Do not mix 4K rows. Generate-001 lists 720p / 1080p / 4K. Fast-001 lists 720p / 1080p. Lite-001 lists 720p / 1080p. Brief the row you will actually call.
  6. Cap the spoken line before you cut over. Use the AI script generator. One sentence. Strike “#1,” ingredient claims, and competitor names you cannot defend. Veo will say whatever the prompt implied, including the lie.
  7. Lock frame one if the SKU must survive. Cloud supports first-and-last-frame and reference images on Generate/Fast. Lite’s Modalities row says Image is not supported. If the pack shot is the brief, do not roll Lite to save a nickname.
  8. Respect English-only prompts on the Cloud card. The Agent Platform page lists prompt language English. Do not brief a JP/KR VO as if the model card promised it.
  9. Keep writer, still, and renderer as three objects. A script, a locked frame, a Veo or Omni pass, and a YouTube disclosure are four things. Do not hide all four under “we swapped preview for 001.”
  10. Re-screenshot both pages on cutover day. API cards last updated 19 Oct. Cloud page last updated 21 Oct. If either banner changed after you read this, the ticket follows the new screenshot.

Worked example: a Friday restock that does not start in veo-3.1-fast-generate-preview

Say the job is a YouTube restock cutdown. The two-pack ships Friday. Legal line approved: Same bottle. Same seal. Restock Friday. Someone opened the Gemini API card, saw 22 October, saw Omni Flash, then opened Cloud, saw veo-3.1-generate-001 still GA as of 21 October, and told the channel “Veo preview is shutting down, so we point the job at Enterprise GA and the video is covered.”

That sentence mixes five desks.

The spoken line is a writer object. Put the approved sentence on the AI script generator. Veo can add sound — Cloud lists Sound generation: supported. It will not know which sentence Legal signed unless you paste that sentence. If you already live in VEED or Kapwing, their script tools are still script tools. Copy the signed line. Do not hit generate-video from the unsigned still.

The beat list is a card object. Steal shot language from prompt ideas, then write four lines, not a chat novel:

  • 0s — kitchen, bottle already on the board (do not invent a second SKU)
  • 2s — hand in, label readable
  • 4s — pour or use, same bottle
  • 6–8s — end card with the signed sentence only

Cloud Veo tops out at 8 seconds. If the restock needs more, that is a second shot or an extend pass — still not a reason to skip the card. If the pack shot is non-negotiable, generate or photograph the still first, then image to video or Cloud first-and-last-frame. Reference-image-to-video on that page is 8 seconds only.

The renderer is a named ID. If the old notebook still says veo-3.1-fast-generate-preview, that is the string the API card dates to today. If the new notebook says veo-3.1-generate-001, that is Cloud GA, us-central1, English prompts, 4/6/8 seconds. If the new notebook says gemini-omni-1.1-flash, that is the API migration target — not proof it inherited Cloud’s 4K row. Pick one ID. Write it on the ticket.

Then generate. Then watch the label. Then disclose. None of those steps are “Veo.”

FAQ

Did Veo 3.1 die on 22 October 2026? Not as a single product. Google’s Gemini API model cards (updated 19 October 2026) still say the preview IDs shut down on 22 October. Google Cloud’s Agent Platform page (updated 21 October 2026) still lists veo-3.1-generate-001 and veo-3.1-fast-generate-001 as GA, with retirement 17 November 2026 or later. Screenshot the ID you actually call.

Is veo-3.1-generate-001 the same as veo-3.1-generate-preview? No. One is a Cloud GA ID on the 21 October page. The other is a Gemini API preview ID on the 19 October cards. Google’s Cloud footnote says the Gemini API is not a Google Cloud offering.

Can I keep using Veo Lite? Name the ID. veo-3.1-lite-generate-preview is on the API shutdown list. veo-3.1-lite-generate-001 is still a Preview row on Agent Platform, released 2 April 2026, with reference images not supported. That is not a stay of execution for the API string.

Does Enterprise GA write the script? No. VEED and Kapwing still keep script generators on separate URLs from their video generators. Lock the line on a script desk before you spend a Cloud or Omni call.

How long can a Veo 3.1 GA clip be? The Agent Platform card says 4, 6, or 8 seconds. Reference-image-to-video is 8 seconds only. It does not claim a 60-second explainer. If you need a recap of a long recording, that is the AI video summarizer, then a new short.

Sources