Alternatives

MiniMax H3 vs Veo 3.1: the settings on one of them are locked to each other

The difference that decides most briefs is not quality. Above 720p, Veo 3.1 has exactly one duration — and that constraint is in Google's own parameter table.

Aug 9, 20268 min readEditorial deskEditorial desk
MiniMax H3 vs Veo 3.1: the settings on one of them are locked to each other

We run a MiniMax H3 tool, so we have an obvious interest here. Three things keep this useful: every Veo number comes from Google's own documentation, Veo's wins get their own section, and we name the case where Veo 3.1 Lite costs less than anything we sell.

Both output video with audio generated alongside the picture. You will read elsewhere that one of them does not; that was never true of H3 and is no longer true of Veo. The comparison turns on three other things. H3 gives you 4 to 15 seconds at any integer, six aspect ratios and up to twelve reference files, at $0.08 to $0.13 per output second. Veo 3.1 reaches 4K, which H3 cannot, and can extend a clip to 148 seconds, which H3 cannot. And above 720p, Veo has exactly one duration.

Veo 3.1's settings are coupled

Read Google's parameter table rather than its feature list and one line changes the comparison. Against durationSeconds it says: "4", "6", "8". Must be "8" when using extension, reference images or with 1080p and 4k resolutions.

So the 4, 6 or 8 seconds everyone quotes is only true at 720p with no references. Ask for 1080p and the 4 and 6 disappear. Ask for 4K, same. Attach a reference image, same. Turn on extension and you also drop to 720p, because the resolution line adds 720p only for extension.

H3 has no equivalent coupling. Any integer from 4 to 15, at 768P or 2K, in any of six aspect ratios, with up to nine images plus three videos plus three audio clips. The settings do not constrain each other.

Three different models wear the Veo 3.1 badge

Standard, Fast and Lite are not tiers of one model in the way tiers usually implies. Lite has no 4K and takes no reference images at all. Standard and Fast take both. The price spread is eight to one: $0.40 per second against $0.05 at 720p.

This matters because almost every comparison quotes Standard's $0.40 and calls it Veo. If your delivery is 720p and eight seconds, that framing costs you money: Lite is cheaper than anything on our own price list, audio included.

Price per second lies. What a finished spot costs

Per-second rates only compare cleanly when both models can produce the same segment. Above 720p they cannot, so the honest unit is a delivered spot.

Thirty seconds at 1080p-class output, keeping one take in three:

RouteSegmentsCostSeams
Veo 3.1 Standard4 × 8 s, three times over$28.803, needing matching grade
MiniMax H3 at 2K2 × 15 s, three times over$11.701
Veo 3.1 Lite, if 720p is acceptable4 × 8 s, three times over$3.603

The cheapest row on this page is not ours. Both columns use each vendor's own published list price, not a reseller's markup, which is where most comparisons quietly go wrong.

Where Veo 3.1 beats MiniMax H3

4K. Veo 3.1 Standard delivers it; H3 stops at 2K. If the contract says 4K master, this comparison is over. H3's 2K is a regeneration rather than an upscale, which recovers small text an upscaler would invent, but it is still 2K.

Length, in one specific sense. Veo extends a generated clip by seven seconds at a time, up to twenty times, to 148 seconds. H3 stops at 15. Veo's version is welded from seven-second pieces and locked to 720p, but 148 is 148.

Reproducibility, partly. Veo exposes seed, with Google's own note that it does not guarantee determinism but slightly improves it. H3 exposes nothing equivalent. Partial beats none.

Procurement. Vertex AI brings identity management, audit trails and contracts. Nothing about H3 is close on that axis.

Two geography clauses, not one

Every comparison mentions one of these and none mention both.

H3's weights ship under a community licence whose Applicable Territory excludes the US, the EU, the UK and South Korea, and the exclusion follows the outputs, not just the deployment. The hosted API is unaffected and available worldwide. The licence, clause by clause has the detail.

Veo has a geography clause too, on its own limitations page: in the EU, the UK, Switzerland and MENA, personGeneration accepts only allow_adult. Google also states that English is fully supported and other languages have not been evaluated, which is worth weighing against H3's eleven stable dialogue languages.

Two clauses, two different kinds. Not one model with restrictions and one without. A summary, not legal advice.

On the blind-preference boards

Artificial Analysis blind-preference arenas, snapshot 14 August 2026:

BoardMiniMax H3Veo 3.1
Text to video with audio1,238 Elo (7,170 votes)1,091 Elo (8,626 votes)
Image to video1,1931,085
Video editing1stnot listed

Two qualifiers before you quote that. H3 is not first on the text-to-video board; Gemini Omni Flash leads it at 1,241, inside the same confidence interval, and Google's own docs now name Omni Flash the default video model and Veo 3.1 the choice for scene extension and legacy pipelines. Second, Veo 3.1 is absent from the video editing board rather than beaten on it. That is an absence, not a loss.

Which one for your brief

Four briefs send you to Google, and we would rather say so than have you find out after the invoice. A 4K master: Standard, and only Standard. A 720p eight-second spot on a tight budget: Lite, cheaper than us. One deliverable longer than fifteen seconds where 720p is fine: Veo's extension chain. Procurement inside Google Cloud: Vertex.

Four send you here. Anything not 16:9 or 9:16. Anything needing more than three reference files, where reference to video takes twelve. Dialogue outside English. And any single continuous take between nine and fifteen seconds, which Veo cannot produce at any setting.

FAQ

Is MiniMax H3 better than Veo 3.1? Not overall. H3 leads on the blind-preference boards, on duration, aspect ratios, reference capacity and price. Veo 3.1 leads on 4K, on extension length and on seed. Pick by delivery spec, not by winner.

Does Veo 3.1 generate audio? Yes, always. Google's model features table lists audio as always on for Veo 3.1, Fast and Lite, and there is no generate_audio parameter in the current Gemini API table. Comparisons built on a silent Veo are out of date.

Does MiniMax H3 generate audio? Yes, 32 kHz stereo, produced in the same forward pass as the picture, with no switch.

Can MiniMax H3 do 4K? No. The resolution enum is 768P and 2K. Sites quoting an H3 4K rate are quoting something MiniMax does not publish.

How long can each one go? H3: any integer from 4 to 15 seconds in one continuous take. Veo 3.1: 4, 6 or 8, and only 8 above 720p, then extensions of seven seconds to a 148-second maximum at 720p.

Does Veo 3.1 support negative prompts? Not through the Gemini API; the parameter is not in its table. seed is there, with Google's own caveat.

Which is cheaper? It depends on the tier. Against Standard, H3 is roughly a third of the price. Against Lite at 720p, H3 is more expensive.

Why is Veo 3.1 still labelled preview? Google's model versions table marks Veo 3.1, Fast and Lite as preview, and Veo 3, Veo 3 Fast and Veo 2 as deprecated. Every Veo you can buy today is a preview model.

How long do results stay available? Veo stores generated videos for two days. H3 lets you query a task for seven days, and its output URLs are time-limited too. Download and re-host on both.

Are the videos watermarked? Veo watermarks with SynthID and provides a verification tool. Whether third-party resellers pass SynthID through, we have not verified.

Should I be comparing against Gemini Omni Flash instead? Possibly. Google's own docs name it the default video model.


This is easier to settle with one clip than one table. Generate one and judge the picture yourself.

Editorial desk

Written by

Editorial desk

minimax-h3ai.video

All articles