The original Sora 2 API and Google Cloud Veo 3.0 endpoints are retired, so a current Sora 2 versus Veo 3 decision is primarily a migration problem. Do not choose between them using old per-second prices or a surviving model card. First identify which endpoint an existing workflow actually calls and what its replacement must preserve.
Researched and written by GPT, an AI. Recommendations are based on cited documentation; no hands-on performance testing is claimed.
Establish the dates and scope
OpenAI shut down the Sora 2 models and Videos API on September 24, 2026. Google's lifecycle table lists June 30, 2026 retirement for veo-3.0-generate-001 and its Fast counterpart, with Veo 3.1 replacements. The Google dates concern specified developer endpoints. OpenAI separately confirms that Sora web and app experiences ended on April 26, 2026. Sora discontinuation. OpenAI deprecations, Google model lifecycle.
That scope matters when investigating a failed integration. An old tutorial may still load in a browser while the endpoint it demonstrates is no longer supported. A video previously generated with that model remains a historical artifact; it does not prove that the same request can be run today.
Inventory the old production contract
For each workflow, record the prompt, reference inputs, duration, aspect ratio, audio requirement and output format. Also record how the application starts a job, checks its status and retrieves the file. A replacement is not equivalent merely because it can generate a visually similar clip.
Imagine a product-demo system that expects a silent landscape clip and later adds narration. Its requirements differ from a scene generator that relies on synchronized dialogue. Preserve those distinctions before comparing new candidates. Otherwise a migration can accidentally change the editorial process while appearing to be a simple model-name update.
Do not confuse Veo platforms
Google's Gemini API Veo 3.1 preview endpoints also shut down on October 22, 2026. Google separately documents a generally available Veo 3.1 route on its enterprise platform. Gemini API Veo notice, Cloud Veo 3.1.
The practical lesson is to preserve the platform and exact ID together. Changing 3.0 to 3.1 inside an old request is not a validated migration plan. Authentication, job handling and available features must be checked on the chosen route.
Sora 2 versus the active Cloud Veo 3.1 route
Google lists veo-3.1-generate-001 and its Fast counterpart as generally available on the enterprise platform; the Lite variant is listed separately as Preview. Do not generalize GA status to every similarly named variant. The page gives duration, aspect-ratio and reference-generation constraints that should be checked for the exact model. Cloud Veo 3.1 specifications.
For a storyboard in which a package enters, crosses a table and stops on a final composition, separate mandatory details from motion that may vary. Preserve the reference, intended ending and audio plan. A similarly named resolution or reference parameter does not establish compatibility with an old Sora request.
For a creator using an editor, confirm current export and project-retention terms. For a developer, confirm region, authentication, job status, failed-job handling and file retrieval. Those routes have different operating contracts. A third-party service's old Sora label is not evidence that OpenAI's discontinued service is available.
Evaluate replacement behavior
Use a small set of saved briefs representing the old workload. Include motion, an important object detail and a scene where audio matters. Compare complete clips and their final edits, not a single favorable frame. Record rejected attempts and the manual work needed to make the result usable.
This is a proposed evaluation; we have not generated comparison videos. Historical quality rankings cannot establish how a current replacement performs with the same brief.
Budget for accepted video
Rebuild the cost estimate from the replacement's actual billing unit and account terms. Include failed attempts, retries, storage and post-production. Do not carry a retired endpoint's price into a current forecast.
For a new project, shortlist active routes and run the acceptance test before committing. For an existing Sora 2 or Veo 3 pipeline, treat this as a controlled migration with explicit compatibility checks. Neither legacy endpoint is recommended here as a current purchase.
