71 Prompts both models were run on. Each slide shows the two clips for one Prompt, with the Prompt and the human preference split underneath.

Summary and how to choose

Duration: 16s or 20s for OpenAI Sora, versus not confirmed for Google Veo 3. Resolution: 720p (1280x720 / 720x1280); 1024p (1792x1024 / 1024x1792, pro only); 1080p (1920x1080 / 1080x1920, pro only) for OpenAI Sora, versus not confirmed for Google Veo 3. Controls: T2V · I2V · Video editing · Video extension · Character consistency for OpenAI Sora, versus not confirmed for Google Veo 3. Audio: Native audio (generated clips include audio) for OpenAI Sora, versus Native audio (sound effects, ambient noise and dialogue) for Google Veo 3.

OpenAI Sora

Strengths: a documented output envelope (16s or 20s · 720p (1280x720 / 720x1280); 1024p (1792x1024 / 1024x1792, pro only); 1080p (1920x1080 / 1080x1920, pro only)), documented generation controls (T2V · I2V · Video editing · Video extension · Character consistency), documented audio support (Native audio (generated clips include audio)), and published exact per-second API rates.

Google Veo 3

Strengths: documented audio support (Native audio (sound effects, ambient noise and dialogue)) and a checked plan, credit or no-rate path.

Trade-offs: the full output envelope is not confirmed, generation modes are not confirmed, and pricing is not normalized to a per-second rate.

Choose OpenAI Sora when transparent exact API pricing, documented generation controls, documented audio output, and its documented duration and resolution envelope matter most. Choose Google Veo 3 when documented audio output and a checked plan, credit or no-rate path matter most.

For output quality, use the paired vote split below; it is specific to the shared Prompts shown here. This summary compares confirmed documentation and pricing only; it does not infer visual quality or rank models.

Overall · 71 shared Prompts

no ties

OpenAI Sora
44%
preferred on 27/71
Google Veo 3
56%
preferred on 44/71

Average share of weighted human votes across every shared Prompt, published by Rapidata. This is the dataset’s vote split, not a rating by this site.

Prompt 1 of 71

OpenAI Soradata/videos/sora/0002_sora_0.mp452%
Google Veo 3videos/0002_veo3_0.mp448%

Human preference on this pairing

Share of weighted human votes for these two clips, collected by Rapidata. It compares this exact pair of clips — it is not an absolute score and not our rating.

Prompt

A 'day in the life' of a cutting-edge urban dance crew rehearsing for a global competition. Showcase their intense training, creative choreography sessions, high-tech stage setups, team dynamics, and the adrenaline-filled moments of their electrifying performance under the city lights.

All 71 Prompts in this matchup

List-price signal

Checked 2026-09-19

Exact and estimate rows are USD per output second. Rows marked Exact are published provider rates; rows marked Estimate are official examples calculated from token consumption, not fixed per-second plan prices. Plan, credit and token paths are grouped separately. A dash means no comparable checked price.

Price comparison for OpenAI Sora and Google Veo 3
BasisOpenAI SoraGoogle Veo 3
USD / output second
sora-2 · 720pexact

$0.10

No comparable checked price
sora-2-pro · 720pexact

$0.30

No comparable checked price
sora-2-pro · 1024pexact

$0.50

No comparable checked price
sora-2-pro · 1080pexact

$0.70

No comparable checked price
OpenAI Sora: Final published prices, verified 2026-09-19; batch at half rate. The Videos API shut down September 24, 2026 and sora.com closed April 26, 2026 (see sora-sunset, checked 2026-09-28)
Other checked billing paths
Veo 3No comparable checked price

Not separately listed

Current listed familyNo comparable checked price

Veo 3.1 Lite / Fast / Standard

Google Veo 3: Veo 3.1 prices are not substitutes for a Veo 3 rate.

This is a price signal, not a quality ranking. Resolution, capabilities, input materials, failed generations, taxes, and regional account terms are not normalized.

API comparison

7/7 and 1/7 fields confirmed from official sources

Version-level API facts, taken from the provider documentation cited below. Unconfirmed means we have not verified it from an official source — it does not mean the feature is unsupported.

API facts for OpenAI Sora and Google Veo 3
FieldOpenAI SoraGoogle Veo 3
Official model IDsora-2 · sora-2-proUnconfirmed
Duration16s or 20sUnconfirmed
Resolution720p (1280x720 / 720x1280); 1024p (1792x1024 / 1024x1792, pro only); 1080p (1920x1080 / 1080x1920, pro only)Unconfirmed
ModesT2V · I2V · Video editing · Video extension · Character consistencyUnconfirmed
Aspect ratios16:9 · 9:16Unconfirmed
Native audioNative audio (generated clips include audio)Native audio (sound effects, ambient noise and dialogue)
Weights licenseClosed (proprietary)Unconfirmed

Sources · checked 2026-09-19

Where these clips come from

Both clips and the preference split are published by Rapidata under APACHE-2.0, retrieved 2026-09-11. Media is served directly from their Hugging Face repositories; this site re-hosts nothing and adds no rating of its own.

Where to run these models

This site does not generate video and does not sell generation credits, so it has no reason to prefer either model. To run them, use the provider’s own API or app.

Frequently asked questions

Did these two models run the same Prompts?

Yes. OpenAI Sora and Google Veo 3 were both run on the same 71 Prompts, with identical Prompt text sent to each model. Each slide on this page shows the two clips generated for one Prompt.

Which model did people prefer overall?

Across 71 Prompts, OpenAI Sora averaged 44% of the weighted human preference for each pair, and Google Veo 3 averaged 56%. These are vote shares published by Rapidata; they are not a rating by this site.

How many Prompts was each model preferred on?

OpenAI Sora was preferred on 27 of 71 Prompts and Google Veo 3 on 44, with no ties.

Can I generate these videos on this site?

No. This site does not generate video and does not sell generation credits; it compares models and links out to each provider. Running these models means using the provider's own API or app.