Sora 2 vs Veo 3: the short answer
For a new API project, the Sora 2 API is discontinued. Google’s documentation lists its Veo 3.0 Agent Platform endpoints for retirement and recommends migration to Veo 3.1. That is a route-specific status—not proof that every Veo 3 route, including Gemini API or third-party hosting, is unavailable. For a current Google API option documented here, consider Veo 3.1 Generate on Gemini Enterprise Agent Platform; it is a different model version, not a like-for-like substitute in every respect.
Older comparisons also mix Sora app access, third-party API hosting, Veo 3, and Veo 3.1. Those versions and routes should not be treated as interchangeable. The status below reflects the sources available as of November 8, 2026.
Versions and API status
| Model or route | Documented status | What it means for a buyer |
|---|---|---|
| OpenAI Sora 2 API | OpenAI’s notice gives September 24, 2026 as the API discontinuation date. | Don’t plan a new integration around the discontinued API. The notice does not establish the status of third-party hosting. |
| Google Veo 3.0 on Gemini Enterprise Agent Platform | Google lists veo-3.0-generate-001 and veo-3.0-fast-generate-001 for retirement on June 30, 2026, and recommends migrating to corresponding Veo 3.1 endpoints. Google notes that Agent Platform retirement dates do not necessarily determine Gemini API availability. |
Treat these specific Agent Platform endpoints as a migration issue. The cited documentation does not establish that every Veo 3 route or third-party host is unavailable. (docs.cloud.google.com) |
| Google Veo 3.1 on Gemini Enterprise Agent Platform | Google documents GA model veo-3.1-generate-001. |
This is a current documented Google API route to evaluate—not the original Veo 3.0 model. (docs.cloud.google.com) |
| Google Veo 3.1 preview on Gemini API | Google says the preview IDs veo-3.1-generate-preview, veo-3.1-fast-generate-preview, and veo-3.1-lite-generate-preview shut down on October 22, 2026. |
Don’t confuse the ended Gemini API preview IDs with the separately documented GA models on Gemini Enterprise Agent Platform. (ai.google.dev) |
What the models offered—and what the specifications establish
OpenAI described Sora 2 as offering synchronized dialogue and sound effects, more physically accurate motion, and improved controllability. These are OpenAI’s launch descriptions, not a current availability statement or a head-to-head benchmark. Its API has since been discontinued.
For the Veo 3.0 Agent Platform model, Google documents text-to-video and image-to-video, sound generation, 4-, 6-, or 8-second clips, 720p or 1080p output, and 24 fps. The same page lists the relevant 3.0 endpoint IDs for retirement; these specifications do not show that those endpoints remain callable. They also do not establish status on every other route. (docs.cloud.google.com)
For Veo 3.1 Generate on Agent Platform, Google documents 4-, 6-, or 8-second clips, 720p, 1080p, or 4K output at 24 fps, plus text-to-video, image-to-video, first-and-last-frame generation, video extension, reference images, and sound generation. A specific restriction: reference-image-to-video generation supports 8 seconds only. The documented model ID is veo-3.1-generate-001; Google lists U.S. availability in us-central1. (docs.cloud.google.com)
These specifications don’t settle which model produces the better image or motion for a particular scene. Older third-party comparisons report different winners across prompts, but do not provide enough repeat testing or evaluation detail to support a general quality ranking.
Production API fit
Sora 2: OpenAI’s published API discontinuation date has passed. Historical Sora API prices, endpoint names, or access instructions should not be used to plan a new integration. The status of third-party hosting is not established by that notice.
Veo 3.0: Google’s retirement information is specific to the named Agent Platform endpoints. Google recommends migration to corresponding 3.1 endpoints, but its documentation cautions that Agent Platform retirement dates do not necessarily determine Gemini API availability. Don’t turn a route-specific notice into a model-wide claim. (docs.cloud.google.com)
Veo 3.1: The Agent Platform model page lists provisioned throughput and fixed quota as supported consumption options; it says pay-as-you-go and batch inference are not supported for veo-3.1-generate-001. It also lists text-to-video, image-to-video, first-and-last-frame generation, extension, reference images, and sound generation. For the reference-image-to-video mode, the documented duration is 8 seconds only. Verify access, quotas, security controls, and operating terms for your own Google Cloud project before committing a workload. (docs.cloud.google.com)
Pricing and access
A like-for-like current API price comparison isn’t available here: the Sora 2 API is discontinued, and the cited Google model page doesn’t state a dollar rate for Veo 3.1 Generate. It does specify consumption options, but that is not enough to calculate a comparable per-video cost. Don’t reuse historical third-party per-second prices as current quotes. Check applicable Google Cloud pricing and quota terms for the model and account you plan to use. (docs.cloud.google.com)
Which one should you choose?
- Starting a new API integration? Don’t plan around the discontinued Sora 2 API. For Google, evaluate the documented Veo 3.1 Agent Platform route and confirm its quota and consumption requirements.
- Maintaining a Veo 3.0 integration? Check which route and model ID you use. Google’s Agent Platform page lists the 3.0 endpoint IDs for retirement and recommends migration; it does not, by itself, establish the status of every Veo 3 route. (
docs.cloud.google.com) - Comparing historical creative strengths? OpenAI’s Sora 2 launch materials emphasized motion realism, controllability, and synchronized audio. Google documents sound generation and specific output controls for Veo 3.1. These descriptions don’t establish a head-to-head winner, and Sora 2 API access is no longer available through its former route. (
docs.cloud.google.com)
Bottom line: “Sora 2 vs Veo 3” is now partly a historical comparison and partly a route-specific migration question. The Sora 2 API is discontinued; Google’s retirement notice applies to named Veo 3.0 Agent Platform endpoints, not necessarily every Veo route. For a present-day Google API evaluation, consult the Veo 3.1 Agent Platform documentation and confirm exact model IDs, route status, and billing conditions before building.
Sources
What to know about the Sora discontinuation
Veo 3 | Gemini Enterprise Agent Platform