MiniMax-H3
MiniMax · video gen · reviewed by Stan K. · Source: data snapshot · data as of 2026-11-12
A 33B community model whose LICENSE (2026-08-02) excludes the USA, EU, UK and Korea — for US work it is unusable, full stop.
#14 of 14 in Video Gen
ToolScore breakdown — why 6/100
10 criteria × 10 points. Low pillars are visible on purpose — that's the point of a score you can audit. Methodology →
What it does well
- ▸33B params — the raw model is large, if you could use it
- ▸The license states its exclusions clearly — the ban is documented, not buried
- ▸The exclusion list is explicit (USA, EU, UK, Korea) — no ambiguity about where it can and cannot run
Where it costs you
- ▸The LICENSE (2026-08-02) excludes the USA — for US work it is unusable, full stop
- ▸The EU, UK and Korea are excluded too — most of the West is off the map
- ▸No amount of VRAM fixes a territory ban
Hidden traps — the stuff the pricing page doesn't say
The MiniMax-H3 LICENSE, dated 2026-08-02, excludes the USA, EU, UK and Korea. For US work it is unusable, full stop. This is not a rumor or an early-days misunderstanding — it is the license text. Read LICENSE files before betting a pipeline on any community-licensed model; this row is why the local table scores licenses so heavily.
Know the limits before you pay: read the traps above, then decide with eyes open.
Affiliate link where available — never affects the score.
- internal ToolScore Video Gen hub — snapshot 2026-11-12 (numbers from LICENSE files and model cards) verified
Data as of 2026-11-12. Prices and limits change monthly — report anything stale. How we verify: methodology.
Closest alternatives
The Apache pioneer of the open-video wave — a clean license with no verified hardware numbers.
5-second clips with audio under MIT — but the weights are gated, so "open" here means ask first.
A clean MIT license from Meituan at 13.6B dense — and no verified hardware figure published yet.
MiniMax-H3 review
In-depth analysis · last updated 2026-11-12
The red flag row
MiniMax-H3 is why this hub reads LICENSE files before it writes scores. The model is 33B and the weights cost $0 — and both numbers are irrelevant, because the LICENSE (2026-08-02) excludes the USA, EU, UK and Korea. For US work it is unusable, full stop. That is not our interpretation; it is the license text, stated plainly.
Why it still has a row
It stays on the page as the lesson. Territory bans in community licenses are the single sharpest trap in local video generation — sharper than VRAM walls, sharper than revenue caps. A US team that downloads first and reads second ends up with a pipeline built on a model it has no right to run. HunyuanVideo 1.5 carries a softer version of the same clause (EU/UK/KR out, USA explicitly in); MiniMax-H3 is the hard version.
How the pillars land
This is the one row where the neutral-5 rule does not apply, and we say so explicitly: the neutral 5 is for usable products with missing data. A US-banned license is not missing data — it is a verdict, and it floors every pillar. Price/Value 0 — no legal US run means no value at any price. Length & resolution caps 0.5. Render speed 0.5 — not neutral 5: there is no permitted run to time. Training use & license 0 — the license bans the country this site writes for. API access 0.5 — the weights exist; the right to run them in the US does not. Feature set 1.5 — 33B params is the one fact that survives. Track record 0.5. Ease of use 0.5 — ease of a door that will not open. Pricing transparency 1.5 — the one credit: the LICENSE states its exclusions clearly, so the trap is documented rather than discovered. Support & docs 0.5 — moot for a banned product.
Verdict — 6/100, US-BANNED
Do not use this model for US work. The score is not a quality judgment — it is the license, read aloud. If a future license version lifts the territory ban, this row gets re-scored from zero; until then it is the reference example of why "open weights" and "open to you" are different sentences.