Veo 3.1 Preview Can Shut Down on 22 October. Swapping the String Is Not the Brief

Veo 3.1 Preview Can Shut Down on 22 October. Swapping the String Is Not the Brief

Google’s Gemini API deprecations table now gives Veo 3.1 preview IDs an earliest shutdown date of 22 October 2026. The three strings are veo-3.1-generate-preview, veo-3.1-fast-generate-preview, and veo-3.1-lite-generate-preview. The recommended replacement on that table is gemini-omni-1.1-flash. The same date sits on gemini-omni-flash-preview. Google’s own footnote says those dates are the earliest possible retirement, and that it will communicate the exact shutdown with advance notice. This is not the Gemini app rename from last week, and it is not a signed restock. ClipCanva is not affiliated with Google, VEED, or Kapwing. 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 paste “migrate to Omni” into Slack and call Friday shipped.

Product facts (confirmed 11 October 2026)

Source	Public claim	Workflow implication
Gemini API deprecations (checked 11 Oct 2026)	Preview: veo-3.1-lite-generate-preview (released 31 Mar 2026), veo-3.1-generate-preview and veo-3.1-fast-generate-preview (released 15 Oct 2025) — shutdown date 22 October 2026, replacement gemini-omni-1.1-flash. Same date on gemini-omni-flash-preview. gemini-omni-1.1-flash itself: released 27 Aug 2026, no shutdown date announced.	Three Veo preview strings and one Omni preview string share a calendar. The GA Omni ID does not.
Same deprecations page, opening note	Shutdown dates in the table are the earliest possible dates a model might be retired. Google will communicate the exact shutdown date with advance notice. Once shutdown, the endpoint is off.	Do not brief “Veo dies at midnight on the 22nd.” Brief “the string can go dark on or after that date; screenshot the table the day you cut over.”
Video generation in the Gemini API (page last updated 2026-06-30 UTC)	Two families: Gemini Omni Flash and Veo. “Use Gemini Omni Flash as your default model for video generation.” “Use Veo 3.1 for specific capabilities like scene extension, last-frame control, or integration with legacy pipelines.”	This overview is older than Omni 1.1 GA. Do not treat June copy as the 22 October runbook.
Gemini API changelog — 27 Aug 2026	GA: gemini-omni-1.1-flash. Video extension; interpolation (first + last frame) via image_to_video with up to 2 images; resolution in video_config: 360p, 720p (default), 1080p, 4k (1080p and 4K via upscaling). The preview endpoint “will be deprecated on September 30, 2026.”	Extend / first-last-frame are Omni 1.1 claims on the changelog. Preview deprecation (30 Sep) is not the same event as shutdown (table: 22 Oct).
Gemini Omni Flash model card (latest update August 2026)	Code: gemini-omni-1.1-flash. Input: text, image, video (up to 10s for editing and extension). Output: video. Output length 3s–10s at 360p / 720p / 1080p / 4K, 24 FPS. Preview alias still listed: gemini-omni-flash-preview.	A 10-second clip with a 10-second edit window is not a two-minute explainer.
Gemini API pricing (checked 11 Oct 2026)	Omni 1.1 Flash, paid: input $1.50 / 1M tokens; output $9.00 text, $17.50 video. Google’s equivalent: ~ $0.10 per second of 720p (5,792 tokens/sec). Free tier not available. Veo 3.1 still listed on the preview IDs: Standard $0.40/sec (720p and 1080p), $0.60 (4K); Fast $0.10 / $0.12 / $0.30; Lite $0.05 / $0.08 (no 4K). Charge only if the video is successfully generated.	Price the second, not the nickname. Fast at $0.10 is not a reason to keep a preview ID past the table.
VEED AI Video Generator	Own URL. Generate from text, scripts, or images. Separate AI Script Generator.	Writer and renderer stay different URLs.
Kapwing AI Video Generator	Own URL. Text-prompt video. Separate Script Generator in AI nav.	Kapwing still splits script and video.

Google did not publish, on the pages above, a hard “Veo is deleted from every Google product on 22 October,” a ClipCanva credit map, or a statement that the June video overview has been rewritten. If a capability is not on the page you are briefing from today, it is not a brief.

What 22 October is — and what it is 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
Veo 3.1 preview IDs (veo-3.1-*-preview)	Listed with earliest shutdown 22 Oct 2026; replacement gemini-omni-1.1-flash	Prove Enterprise Agent Platform Veo GA is gone; prove the exact clock time	Leaving veo-3.1-generate-preview in prod because “pricing still shows it”
gemini-omni-flash-preview	Same earliest shutdown 22 Oct 2026; changelog already called deprecation 30 Sep 2026	Keep answering after shutdown; become the GA string	Shipping the preview alias after you meant 1.1
gemini-omni-1.1-flash (GA, 27 Aug 2026)	Default video generate + conversational edit; 3–10s; extend; first/last frame; 360p–4K	Sign Legal copy; replace a shot list; run a 60-second Magic Video	Briefing “Omni 1.1 is the campaign”
Video overview (updated 30 Jun 2026)	Omni = default; Veo 3.1 = extend / last-frame / legacy	Override the October deprecations table	Pasting June advice into the 22 Oct cutover ticket
Gemini app Omni rename	Omni replaces Veo in the Gemini app — covered in the 7 October note	Move your API key; kill preview IDs	Telling engineering “the app FAQ already migrated us”
VEED / Kapwing video URLs	Generate from text / script / image on a video URL	Disclose on YouTube or lock your SKU	Hitting generate-video from an unsigned paragraph

If you are calling veo-3.1-*-preview, you are on a dated preview desk. If you are calling gemini-omni-1.1-flash, you are on the GA generate desk. 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 “replacement: gemini-omni-1.1-flash” 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 are migrating 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 Omni as if video-in meant a new master
Motion from a locked still	Image to video, or Omni image_to_video (changelog: up to 2 images, first + last frame)	The signed still as frame one	Camera path, extra hands, a spoken line you did not approve	Animating take three because the new string looks sharper
New motion without a locked frame	AI video generator or a named video model on Compare	Locked caption, crop, seconds (Omni card: 3–10s)	Props, voices, a second location	Briefing Omni as a two-minute explainer
Model pick	Compare plus the live deprecations table	Job = preview ID vs GA Omni vs a non-Google renderer	A leaderboard screenshot from June	Picking Veo Fast because $0.10 matches Omni’s 720p equivalent

If the brief is “grep the repo for veo-3.1 and gemini-omni-flash-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 “Omni will handle the clip because Google said replacement,” you do not have a brief.

VEED still keeps AI Video Generator as its own URL and AI Script Generator as another. Kapwing still keeps Video Generator and Script Generator as different nav items. Neither page says a Google model-ID swap writes your CTA. ClipCanva’s Omni 1.1 first/last-frame note is the control surface for extend and interpolation — not a substitute for the signed line.

Creator / operator checklist

1. Read the table footnote out loud. 22 October is the earliest possible shutdown, not a confirmed kill-switch timestamp. If the next sentence in Slack is “we have until the 21st for sure,” stop.
2. Name the string. veo-3.1-generate-preview ≠ veo-3.1-fast-generate-preview ≠ veo-3.1-lite-generate-preview ≠ gemini-omni-flash-preview ≠ gemini-omni-1.1-flash. Screenshot the model code in logs, not the nickname on a slide.
3. Grep before you generate. Search production, staging, notebooks, and vendor dashboards for the four preview IDs. A hidden Fast call at $0.10/sec is still a preview ID.
4. 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. Omni will say whatever the prompt implied, including the lie.
5. Do not confuse deprecation with shutdown. Changelog: Omni preview deprecated 30 September 2026. Deprecations table: earliest shutdown 22 October 2026. A deprecated alias can still answer. A shutdown endpoint does not.
6. Do not confuse the Gemini app with the API. The app FAQ is a consumer rename. This table is developer preview IDs. Two desks. Two tickets.
7. Bill the second. Omni 1.1 ~ $0.10/sec at 720p. Veo 3.1 Fast is also $0.10/sec at 720p on the pricing page that still lists preview IDs. Matching unit price is not a stay of execution.
8. Respect 3–10 seconds. The Omni card lists output 3s–10s at 24 FPS. A 10-second edit/extension input cap is not a loophole for a three-minute cut.
9. Re-read the video overview on cutover day. The copy checked today still says use Veo 3.1 for extend / last-frame / legacy, and it is dated 30 June 2026. The 27 August changelog already put extend and first/last-frame on Omni 1.1. Screenshot whichever page is live when you ship.
10. Keep writer, still, and renderer as three objects. A script, a locked frame, an Omni (or image-to-video) pass, and a YouTube disclosure are four things. Do not hide all four under “we swapped Veo for Omni.”

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 deprecations table, saw 22 October, saw gemini-omni-1.1-flash, saw Omni’s $0.10/sec equivalent, and told the channel “Veo preview is shutting down, so we point the job at Omni 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. Omni can speak. 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 or the ads and Shorts prompt pack, 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
• 6s — end card with the signed sentence only

Omni’s card tops out at 10 seconds. If the restock needs more, that is a second shot or an extend pass — still not a reason to skip the card.

The still is a frame object. Lock the pack shot before you interpolate. Changelog: Omni 1.1 image_to_video takes up to two images (first and last). That is not fourteen Nano Banana references. If the label has to hold, generate or retouch the still first, then animate that file on image to video.

The motion pass is a clip object. After 22 October (earliest), a log line that still says veo-3.1-fast-generate-preview is a ticket, not a style choice. Point new jobs at gemini-omni-1.1-flash or at the labeled generator on the AI video generator. Confirm the live picker. Native audio, extend, and first/last-frame are claims you verify on the current model card, not on a June overview.

The cutover is an engineering object. Grep. Staging first. One signed 8-second restock. Compare crop, label, and spoken line against the Veo Fast take you already approved. If Omni invents a second bottle, you did not finish — you started.

FAQ

Does Veo 3.1 definitely turn off at midnight on 22 October 2026? No. The deprecations page says table dates are the earliest possible retirement, and that Google will communicate the exact shutdown with advance notice. Treat 22 October as the date you must already be off the preview IDs, not as a promise the endpoint survives until then.

Is Gemini Omni 1.1 Flash the same model as Veo 3.1? Google does not say that. The deprecations table names Omni 1.1 as the recommended replacement for the Veo 3.1 preview IDs. The video overview still lists two families. Pricing still lists Veo 3.1 preview IDs with a different per-second ladder than Omni’s token math. Screenshot both pages; do not merge the names.

Can I keep Veo 3.1 Fast because it is $0.10 per second, same as Omni 720p? Unit price matching is not a lifecycle matching. Fast is still a preview ID on the deprecations table. Omni 1.1 is GA with no shutdown date announced. If the job is “still cheap on the 23rd,” Fast is the wrong object.

We already moved the Gemini app to Omni. Are we done? No. The Gemini app note is a consumer-app rename. This table is Gemini API preview strings. An editor on gemini.google.com does not rewrite your veo-3.1-generate-preview calls.

Will swapping the model ID write the restock line? No. VEED and Kapwing still keep script generators on separate URLs from video generators. ClipCanva does the same: script then image to video or AI video generator. A replacement string does not sign a claim.

Do not mix these objects

Object	Tool	Done when
Signed line	AI script generator	One sentence Legal will defend
Shot card	Prompt ideas	Beats with times, no extra SKU
Preview-ID cutover	Deprecations table + repo grep	No veo-3.1-*-preview or gemini-omni-flash-preview in prod
GA generate	gemini-omni-1.1-flash or the labeled AI video generator	3–10s clip, approved audio, crop matches the upload
Locked still → motion	Image to video	Frame one is the signed pack shot
Model pick	Compare	Preview vs GA vs non-Google renderer named

Google put a calendar on the preview strings. It did not put a calendar on your CTA. Write the line, lock the frame in the crop you will ship, point new jobs at the GA Omni ID (or another live renderer), and grep the old IDs out — do not wait for the 22nd to find out which notebook still says Veo Fast.