Product Launch

Veo 4 Release Date (2026): What Google Has Confirmed So Far

Q: Is Veo 4 officially released?

No. As of April 6, 2026, Google has not published an official Veo 4 announcement, model page, or API model ID in the sources reviewed for this article.

Q: What is the newest officially documented Veo release?

The newest official Veo-family addition we found is Veo 3.1 Lite. Google announced it for developers in the Gemini API on March 31, 2026, and Vertex AI docs list the Vertex model version with an April 2, 2026 release date.

EvoLink Team

Product Team

April 6, 2026

12 min read

If you are searching for Veo 4, the honest answer as of April 6, 2026 is simple:

Google has not officially announced Veo 4.

What Google has officially documented is still the Veo 3.1 family, including a new Veo 3.1 Lite launch for developers in late March and early April 2026. That means this should be treated as a release-watch page, not a specs page.

This article separates three things:

what Google has officially published
what community pages and search results are circulating
what developers should do now if a Veo 4 launch matters to their roadmap

TL;DR

No official Veo 4 launch has been published by Google as of April 6, 2026.
Google's own model pages and docs still stop at Veo 3.1.
Veo 3.1 Lite is the newest official Veo-family addition: Google announced it for the Gemini API on March 31, 2026, and Vertex AI docs list the Vertex model version with an April 2, 2026 release date.
A Wikipedia edit or rumor page is worth watching, but it is not enough to plan against.
If you are building video features, the safest move is to ship against today's Veo 3.1 APIs and keep model choice abstracted.

Official information vs community signals

This distinction is worth making explicitly because many "Veo 4 release date" pages blur the line.

Official information

Use these for planning, implementation, and customer-facing claims:

Google blog posts
Google DeepMind's Veo model page
Gemini API documentation
Vertex AI model documentation and release notes

If a claim appears in one of those places, you can usually treat it as a real product signal with a defined scope.

Community signals

These are still useful, but only as watchlist items:

Wikipedia edits
forum threads
social posts
prediction markets
SEO pages summarizing rumors

These can tell you that interest is rising or that people think a launch is close. They do not tell you that a Veo 4 model is officially available, documented, or stable enough to plan around.

Official sources and community signals for Veo 4 release tracking

What is actually confirmed right now

Topic	Officially confirmed	Still unconfirmed	Why it matters
Veo 4 release status	No official Google blog post, DeepMind model page, Gemini API doc, or Vertex AI model doc announcing Veo 4	Release date, rollout scope, model naming	Determines whether there is anything real to integrate
Latest official Veo activity	Google announced Veo 3.1 Lite for developers on March 31, 2026, and Vertex AI docs list `veo-3.1-lite-generate-001` with an April 2, 2026 release date	Whether Veo 4 follows immediately after Lite	Shows Google is still actively shipping Veo-family updates
Current documented API family	Official docs list Veo 3, Veo 3.1, and Veo 3.1 Lite variants across Gemini API / Vertex AI	A `veo-4-*` model ID, pricing page, or model card	Impacts implementation planning
Current documented capabilities	Veo 3.1 docs cover text-to-video, image-to-video, first-and-last-frame workflows, audio on supported routes, and short clip generation	Any official Veo 4-only capability list	Tells you what is usable today versus pure rumor
Storyboarding claim	Google already describes storyboarding and previsualization use cases around Veo 3.1 partner workflows	Whether Google will package storyboarding as a public Veo 4 feature	Prevents over-reading rumor pages
Market timing pressure	OpenAI has published Sora discontinuation dates for web/app and API	Whether that accelerates a new Veo generation	Affects whether teams feel pressure to replatform video stacks

The short answer to "When is Veo 4 coming out?"

There is no official Veo 4 release date from Google right now.

If you have seen search results or community pages claiming "April 2026", treat that as a rumor signal, not as confirmation. For a release to be considered real, you should expect at least one of these:

an official Google or Google DeepMind announcement
a public Gemini API or Vertex AI model page with a Veo 4 model ID
pricing documentation
a model card or release notes entry

As of April 6, 2026, those signals are not present.

Timeline of official signals

May 14, 2024: Google introduced the original Veo at Google I/O.
December 16, 2024: Google announced Veo 2.
May 20, 2025: Google announced Veo 3, highlighting native audio and Flow integration.
October 15, 2025: Google announced Veo 3.1 updates in Flow.
November 17, 2025: Vertex AI documentation lists GA release dates for veo-3.1-generate-001 and veo-3.1-fast-generate-001.
January 13, 2026: Google published another Veo 3.1 update focused on "Ingredients to Video."
March 31, 2026: Google announced Veo 3.1 Lite for developers in the Gemini API.
April 2, 2026: Vertex AI docs list veo-3.1-lite-generate-001 with a release date of April 2, 2026.
April 6, 2026: Google still has no official Veo 4 announcement across the main public Veo pages reviewed for this article.

Why the Wikipedia-style claim is not enough

The main problem with rumor-driven Veo 4 posts is that they mix a possible next model name with features Google is already discussing elsewhere.

For example, "storyboarding" is not a clean Veo 4 signal by itself. On Google's current Veo page, DeepMind already says Promise Studios uses Veo 3.1 for generative storyboarding and previsualization. That means a community page mentioning storyboarding does not prove a new model exists.

The same logic applies to clip length rumors. Until Google publishes a model page or API spec, claims like 10 to 30 seconds, new storyboard mode, or new API surfaces should be treated as unverified.

Practical rule:

a rumor can tell you where to look next
an official doc tells you what you can actually build

What developers should do now

You do not need to wait for Veo 4 to prepare well.

1. Build against today's documented Veo APIs

Google's currently documented Veo family is already usable through official routes:

Gemini API documentation covers Veo 3.1 for programmatic video generation
Vertex AI documentation covers Veo 3.1 and Veo 3.1 Lite model variants

If Veo 4 appears later with a similar surface, the best migration is a model swap plus an evaluation pass, not a rewrite.

2. Keep video generation behind one internal interface

Do not scatter model IDs through product code. Put generation behind one internal contract such as:

submit generation job
poll or receive callback
fetch asset
record latency, cost, and failure reason

That keeps any future Veo-family migration much cheaper.

3. Decide what would justify a switch

Before a new model launches, write down your real upgrade criteria:

longer clips than your current workflow supports
lower cost per second or per finished deliverable
better prompt adherence
better audio quality
better reference consistency or edit controls

If you define this now, you can evaluate Veo 4 quickly when it becomes real.

4. Watch official channels, not rumor loops

The right places to monitor are:

Google DeepMind's Veo page
Gemini API video docs
Vertex AI Veo model docs
Google blog posts for Veo / Flow updates

That is where model IDs, launch stages, pricing, and supported resolutions actually show up.

What Veo 4 would need to change to matter

A new model name alone would not be enough. For most product teams, Veo 4 would become materially important only if Google ships one or more of these:

longer officially supported clip durations
broader audio support with better quality or lower cost
stronger storyboard or multi-shot workflow support in public APIs
better editing controls exposed outside Flow
simpler pricing for high-volume usage

Until then, the real operational choice is not "Veo 3.1 versus Veo 4." It is:

Do you want to keep shipping on today's documented video stack, or pause for an unconfirmed launch?

For most teams, pausing is the worse bet.

Where this sits in the 2026 video API landscape

The wider market still matters because teams comparing Veo 4 rumors are usually really making a build decision.

Question	Safer answer today
Need a real Google video API right now?	Build on Veo 3.1 and documented variants
Need to react to Sora changes?	Plan against the official discontinuation dates, not rumor summaries
Need a future-proof integration path?	Use a gateway or model abstraction so a new video model becomes an evaluation event, not a rewrite

OpenAI's current help-center guidance says:

Sora web and app are scheduled to be discontinued on April 26, 2026
Sora API is scheduled to be discontinued on September 24, 2026

That does make the video market more fluid, but it still does not count as evidence that Google has already launched Veo 4.

Should you wait?

If your team needs to ship video features in the next few weeks, no.

Use the currently documented Veo 3.1 family, keep your integration model-agnostic, and prepare to evaluate any official Veo 4 release when it actually appears.

If you are already routing video generation through a unified layer, the migration risk is lower because you can compare model behavior without rebuilding your app surface. For teams that want a practical starting point now, the current Veo 3.1 route is the right baseline to evaluate.

How EvoLink is tracking Veo 4

At EvoLink, our goal is to help customers access new model capabilities through one stable integration surface instead of rebuilding every time a provider updates its lineup.

That matters in moments like this. Rumors move fast, but production teams still need a dependable way to work with the best models that are officially available today while staying ready for what comes next.

For Veo 4 specifically, EvoLink is doing three things:

tracking official Google announcements, docs, model pages, and API updates
evaluating new video-model releases against practical criteria such as API stability, latency, pricing shape, and workflow fit
updating this post when Veo 4 becomes officially documented or materially changes the planning picture

Until then, the most useful path for customers is straightforward: use the strongest documented video routes available now, keep your architecture flexible, and be ready to test Veo 4 as soon as it becomes real rather than rumored.

Explore Veo 3.1 on EvoLink

FAQ

Is Veo 4 officially released?

No. As of April 6, 2026, Google has not published an official Veo 4 announcement, model page, or API model ID in the sources reviewed for this article.

Why do some pages say Veo 4 was released in April 2026?

Those claims appear to come from community-edited or rumor-driven sources. They may point to real market interest, but they are not the same thing as an official launch.

What is the newest officially documented Veo release?

The newest official Veo-family addition we found is Veo 3.1 Lite. Google announced it for developers in the Gemini API on March 31, 2026, and Vertex AI docs list the Vertex model version with an April 2, 2026 release date.

Does Google document any Veo 4 API today?

No public Veo 4 API documentation was found in the official Gemini API and Vertex AI materials reviewed for this article.

Are storyboarding rumors enough to assume Veo 4 is real?

No. Google already talks about storyboarding and previsualization around current Veo 3.1 partner workflows, so storyboarding references alone do not prove a new public model exists.

Should I wait for Veo 4 before integrating Google's video stack?

Usually no. The safer move is to build on the current Veo 3.1 family and keep model choice abstracted so you can evaluate Veo 4 later without reworking your app.

Could Veo 4 still launch soon?

Yes, it could. But that is still an inference, not a confirmed fact. A likely next signal would be an official Google announcement, model page, pricing entry, or new model ID.

What should I monitor for real confirmation?

Watch for:

a Google blog or DeepMind post naming Veo 4
a Gemini API or Vertex AI doc with a Veo 4 model ID
pricing documentation
a model card or release notes entry

Sources

Last updated: April 6, 2026

All Posts

#Veo 4 #Google Veo #AI video API #video generation #release watch

Veo 4 Release Date (2026): What Google Has Confirmed So Far

TL;DR