MiniMax H3 Commercial Use License: The 4 Countries, the $20M Line, and the Clause That Actually Kills Deals

A cold-brew can, a printed production contract with one clause ringed in red, and a paper contact sheet of the spot's frames on a walnut desk

The three objects this article is about: the product, the paperwork, and the frames you want to invoice for. Generated with openai/gpt-image-2/text-to-image.

You send the cut on a Thursday afternoon. Nice spot, five seconds, native voiceover, type that does not wobble. The client's legal reviewer replies in three lines: this model's license excludes the United States, we are a US entity, we cannot use this.

So you go read the license. They are right. Section I.5 names the United States by name.

Then you read the second document, the one governing the endpoint you actually called, and they are wrong. Not partly wrong. Wrong about which document applies to you at all.

Two files, same company, both current. Nothing in them contradicts. They give opposite answers, because they govern two different things. Almost every "can we use H3 commercially" thread online is people arguing across that gap without noticing it exists.

Here is the gap, closed.

Key takeaways

• The hosted API path is globally available, has no revenue ceiling, and does not require UI attribution. MiniMax says so itself: "API: Globally available with built-in safeguards."
• The self-hosted weights path excludes the EU, UK, South Korea and the US under §I.5, and §V.4 pushes that exclusion onto the outputs too, not just the download.
• Cross $20M in yearly revenue and you need prior written authorization (§IV.1). That line only binds the weights path.
• The two paths split on indemnity, in the direction nobody expects. The weights license gives you none: §VI.4 hands you the outputs and the liability, §VI.3 makes you indemnify MiniMax. MiniMax's own API terms do the opposite and promise to defend you, but only against patent and copyright claims, only if you meet five conditions, and not for trademark or likeness.
• Excluded-territory teams can apply, and MiniMax's own developer relations lead says the form is effectively self-serve: "apply will auto get access."

This article is a plain-language reading of public documents, not legal advice. Every section number below points at text you can open yourself in the MiniMax H3 Community License Agreement (August 2026). Snapshot date: August 5, 2026. If the license text changes, we will update this page and say what changed.

What a Cleared MiniMax H3 Commercial Use License Looks Like When You Deliver It

One fictional brand, HALDVIK COLD BREW. One base frame, one five-second spot with a native English voiceover, delivered through the hosted API. Nothing in this clip triggers a single obligation in the Community License, because the Community License never entered the room.

The delivered HALDVIK COLD BREW spot: five seconds, 2K, native English voiceover generated in the same pass as the picture

The delivered spot, shown here as a silent GIF. The file we shipped carries 32kHz stereo audio generated in the same pass as the picture. Generated with minimax/h3/image-to-video.

Now the same frame under the other path. Left is what we delivered through the API. Right is the same frame carrying the lockup that self-hosted deployment pulls in: the "MiniMax H3" name plus an AI-generation identifier.

Side by side: the clean API-delivered frame on the left, the same frame with the MiniMax H3 name and an AI-GENERATED badge on the right

Same model, same frame, two different sets of duties. The difference is not quality. It is which document you accepted.

Why the MiniMax H3 Commercial Use License Kills Deals That Price Never Would

H3 is not a toy you are talking your client into. On the Artificial Analysis video-editing-with-audio Elo board it sits first at 1,130, ninety-three points clear of second place, and it is the only open-weight model in that board's top seven (snapshot: August 4, 2026, vote-driven and rolling).

That is the level of work at stake. Fifteen seconds of cinematic kinetic type, letters holding razor-sharp through the whole move, which is exactly where most video models fall apart:

Fifteen seconds of cinematic title-card work: kinetic type stays sharp and stable through the entire camera move

H3 title-card work, shown as a silent GIF. Watch the letterforms during the push: no crawl, no wobble, no re-rendered edges. Official MiniMax H3 demo clip, reference-to-video.

Price advantage is easy. Clearance is the wall. Four ways teams walk into it:

1. Measuring API usage with the wrong document. The Community License governs "the video generation model, together with its software and algorithms, including trained model weights" as released on Hugging Face (§I.6). If you have never downloaded a checkpoint, you never accepted it. Your reviewer read the famous file. It is not your file.

2. Reading "open weights" as "deploy anywhere." §I.5 excludes the EU, UK, Republic of Korea and the US. Most coverage stops there. §V.4 does not: you may not "use, reproduce, modify, distribute, or display the MiniMax H3 Works or any of their Outputs or results outside the Applicable Territory." Spin up H3 on a Frankfurt GPU and the render is unauthorized. Render it legally in Singapore and run the ad in Berlin, and the ad is unauthorized too. Exhibit A repeats it as prohibited use number one.

3. Assuming the two paths carry the same liability. They do not, and most people have it backwards. Under the weights license there is no backstop at all. §VI.4: "MiniMax claims no rights over the Outputs you generate. You and your users are entirely responsible." §VI.3 runs the other direction, obliging you to defend and indemnify MiniMax against third-party claims arising from your use. §VII.2 disclaims warranties of title and noninfringement outright.

MiniMax's own API terms are the reverse. Their IP section commits MiniMax to defend you against third-party claims that your use of the platform "infringes or misappropriates third-party patents or copyrights", and to pay the resulting judgment or settlement, capped by the agreement's liability limits. Read the fine print before you relax. It applies only if you notify promptly, hand MiniMax sole control of the defense, assist, stay current on fees, and stay inside the agreed scope. It excludes claims arising from your own data, from combining the service with things MiniMax did not supply, and from continued use after a cease notice. And it names patents and copyrights, which means trademark and likeness claims are not in it. That section is also declared to be MiniMax's entire liability and your sole remedy.

Why that matters concretely. Here is H3 animating a product landing page. The brief named a well-known sportswear site as a style reference and supplied a shoe photo. It never asked for a logo:

A model-generated landing page in which a real third-party sportswear trademark and product-line wordmark render clearly and legibly

Do not ship this. Asked for a brand's layout energy, the model drew the brand: the swoosh and the product-line wordmark come back sharp enough to read. Shown as evidence of model behavior, not as something to copy. Official MiniMax H3 demo clip, reference-to-video.

A swoosh is a trademark, so this is precisely the frame the API indemnity does not cover. Exhibit A clause 2 prohibits use that infringes third-party IP, and on the weights path §VI.4 puts the whole consequence on you. And the backdrop is not hypothetical: Disney, Universal and Warner Bros. Discovery sued MiniMax over Hailuo on September 16, 2025 in the Central District of California (Variety, September 2025). Judge Stanley Blumenfeld denied MiniMax's motion to dismiss on May 26, 2026, sending the case into discovery. MiniMax's own developer relations lead ties the regional carve-out straight to it: "This regional carve-out stems from our ongoing generative video copyright litigation with major Hollywood studios." That case is MiniMax's problem. The frame above is yours.

4. Never opening the terms you did accept. The hosted API runs on MiniMax's Open Platform Terms, and its intellectual property section says you keep ownership, then keeps going: "We may use the input and generated content to provide, maintain, develop, and improve our Services" (MiniMax Open Platform Terms of Service, effective March 30, 2026). If you are an agency pushing an unannounced client product into that endpoint, that sentence is a confidentiality question, and it is in the document nobody quotes.

Three Delivery Paths, Three Different MiniMax H3 Commercial Use License Answers

Same model, three ways to reach it, three different rulebooks. Pick the row that describes how you actually generate.

Path 1, hosted API. The Community License does not reach here. What reaches here is whichever provider's terms you signed. Read that document literally, including its data-use language, because it is the one binding you. MiniMax's own API is a selectable US service region, which is the quiet proof the API is open to US customers: the terms carve out ITAR content and HIPAA data specifically "if you select the United States as the service region."

Running the whole chain on one provider keeps that surface small. On Atlas Cloud, the three models this tutorial uses sit behind one key and one balance, billed per second and per image, with no vendor swap in the middle:

Path 2, self-hosted weights. Now the Community License is yours, all of it. The hardware and download side is covered in our MiniMax H3 open source weights guide; this is the paperwork side, clause by clause:

Two footnotes worth knowing: the encoder is Qwen3-VL-32B under Apache 2.0, and §V.3 bars you from using H3 or its outputs to improve any other AI model. Content filtering is a separate topic, covered in our H3 content restrictions guide.

Path 3, the consumer app. Hailuo's subscription terms are their own document. Do not reason from consumer terms to API rights, in either direction.

Step 1: Shoot the Base Frame

The deliverable starts as a still. GPT Image 2 handles product photography with legible packaging type, which matters because the label text has to survive being animated later.

Open the GPT Image 2 playground, set quality to high and size to 2048x1152 (16:9), and paste this:

textCopy
1Photorealistic commercial product still, 16:9. A matte-black 250 ml cold-brew coffee can
2labeled "HALDVIK COLD BREW" in a thin white condensed sans, standing on wet dark slate.
3Heavy condensation beads across the can, one bead running down the front of the label.
4Behind it, out-of-focus crushed ice and a single warm amber rim light from the right;
5deep teal fill from the left; seamless black background. 85mm macro look, f/2.8, shallow
6depth of field, crisp specular highlight along the can's left edge. No people, no other
7logos, no text other than the label.
8

The invented brand name is deliberate. A made-up label cannot collide with anyone's trademark, which removes the entire Exhibit A clause 2 problem before it starts.

GPT Image 2 playground on Atlas Cloud: quality high, 2048x1152, the finished HALDVIK can in the output panel

Step 1 complete: quality high, 2048x1152, base frame rendered. Billed $0.1745, not the $0.009 floor on the model card.

Step 2: Build the Attribution the MiniMax H3 Commercial Use License Asks For

You only need this frame if you take Path 2, but building it takes one edit call and it makes the obligation concrete instead of theoretical. Nano Banana 2's edit endpoint adds overlays without relighting or restaging the photograph underneath, which is the whole requirement here.

Open the Nano Banana 2 edit playground, load your Step 1 result as the reference image, set resolution to 2k and aspect ratio to 16:9, then paste:

textCopy
1Keep the photograph exactly as it is: same can, same condensation, same lighting, same
2shadows, same background. Add two small overlays only. (1) Bottom-right corner: one line
3of small light-gray text reading "Powered by MiniMax H3". (2) Bottom-left corner: a thin
4rounded-rectangle outline badge containing the words "AI-GENERATED". Both overlays in the
5same light gray, about 60% opacity, matching the existing film grain of the frame.
6Do not relight, retouch, recolor, crop or restage anything else.
7

Keep both overlays small, keep them light gray, and keep them out of the product. Where each one is actually required, and where it is not, is answered in the FAQ below.

Nano Banana 2 Edit on Atlas Cloud: the base frame loaded as reference, the attributed version in the output panel

Step 2 complete: 2k, 16:9, two overlays added, the photograph underneath untouched. Billed $0.12.

Step 3: Turn the Frame Into the Delivered Spot

The clean Step 1 frame goes in, not the attributed one. Picture and 32kHz stereo audio come out of the same pass, so the voiceover is not a second job.

Open the H3 image-to-video playground, load the clean frame, set resolution 2K, drag duration to the length you are delivering, and paste:

textCopy
1Slow four-second push-in on the can as a fresh bead of condensation runs down the label.
2The crushed ice behind it shifts once. At second three, clean white kinetic type wipes in
3from the left across the lower third: "18 HOURS. NO HEAT." The type stays razor-sharp and
4perfectly still once it lands. Audio: a calm female voiceover in English, warm and
5unhurried, saying "Eighteen hours, cold. Never heated." over soft low room tone, with one
6crisp ice clink on the final beat. No music bed.
7

Three details worth knowing before you click. The duration slider starts at 8, so read the Run button before you commit: at $0.14 per second an 8-second 2K take prices itself at $1.12 live on the button, and our 5-second delivery came to $0.70. Over the API, resolution and duration are both required fields, so nothing is safe to omit. And the aspect-ratio field is adaptive only on this endpoint, which means the frame you upload decides the shape. Feed it a 16:9 still and you get a 16:9 clip.

H3 image-to-video on Atlas Cloud: the base frame loaded, resolution 2K, aspect ratio adaptive, the finished spot playing in the output panel

Step 3 complete: resolution 2K, aspect ratio adaptive, spot rendered with audio. The Run button is pricing the default 8-second take at $1.12; the version we shipped was 5 seconds at $0.70.

What a Compliant Spot Costs Under the MiniMax H3 Commercial Use License, Receipt Included

Three calls, one deliverable, real charges from this build:

Two of those three numbers are not the listed base price, and that is the point. GPT Image 2 lists from $0.009 but bills $0.1745 at high quality and 2048x1152. Nano Banana 2 Edit lists at $0.08 but bills $0.12 at 2k. H3 is the honest one: $0.14 per second, flat, no resolution surcharge. Read the Run button, not the model card.

For reference, Seedance 2.0 image-to-video is $0.112 per second on Atlas Cloud if you are cost-shopping, and MiniMax's own direct rate card sits slightly under Atlas Cloud's per-second price. All of the billing mechanics, including the tier arithmetic, live in our H3 API pricing breakdown.

Then save the part your reviewer actually needs. Poll the prediction a second time, because the price field fills in after the video URL does, and write one line per delivery:

csvCopy
1timestamp,model,duration_s,resolution,billed_usd,terms_path
22026-08-05T11:42:18Z,minimax/h3/image-to-video,5,2K,0.70,hosted-api-provider-terms
3

That single row is the whole clearance argument: which model produced the asset, on which date, through which terms. Localization does not change it. The same frame in Spanish or Japanese, using H3's native multilingual voiceover, is another $0.70 and the same terms path. Under §V.4 the self-hosted equivalent of those localized files could not legally run in the EU or the US at all, and that one asymmetry is the most practical sentence in this article.

What this guide is not. It is a reading of public documents as of August 5, 2026, not legal advice, and it does not create a lawyer-client relationship. The license text is authoritative; where we interpreted rather than quoted, we said so, and the §IV.2 question about delivered films versus product interfaces is exactly such a place. Both documents can change, and the license itself says the territory scope is under continuous review. When it moves, this page moves.

MiniMax H3 Commercial Use License: Frequently Asked Questions

Does the MiniMax H3 commercial use license let me sell work in the US or the EU?

Through a hosted API, yes. MiniMax's own license Q&A splits it cleanly: "API: Globally available with built-in safeguards and responsible-use controls. Open weights: Temporarily limited in certain regions." With local weights, no: §I.5 excludes the EU, UK, South Korea and the US, and §V.4 extends that to the outputs, so a lawfully rendered file still cannot be displayed in those markets under this license. Excluded-territory teams can apply for a formal license instead.

Does the MiniMax H3 commercial use license require me to credit MiniMax in my client's video?

Not in the video, on our reading. §IV.2 requires "MiniMax H3" prominently on "the user interface of commercial product or service that uses MiniMax H3", which we read as your app or site rather than a single delivered film. The "Powered by MiniMax H3" line and the AI-generation identifier are §III.3 encouraged items, not requirements, and §VI.2 grants the trademark license solely so you can do those. That is our interpretation of §IV.2's scope, not a quote from it.

Where is the $20 million line in the MiniMax H3 commercial use license?

Only the weights path cares. §IV.1 requires "a separate, prior written authorization from MiniMax" once your commercial products and services generate more than $20 million in yearly revenue, obtained by emailing [email protected] with the subject line "MiniMax H3 licensing - authorization request". If you generate through a hosted API, the Community License is not your document and this threshold does not apply to you.

Who is liable for infringement under the MiniMax H3 commercial use license?

Under the Community License, entirely you. §VI.4: "MiniMax claims no rights over the Outputs you generate. You and your users are entirely responsible for the Outputs and any subsequent use thereof." §VI.3 additionally requires you to defend and indemnify MiniMax against third-party claims, and §VII.2 provides everything AS IS with no warranty of title or noninfringement. Through MiniMax's own API the answer differs: their platform terms commit them to defend patent and copyright claims about your use of the service, subject to five conditions and several carve-outs, and trademark and likeness are not in that promise. Either way the ongoing studio litigation is not a defense you can borrow, and either way filtering your own outputs before delivery is the cheap move.

Can I fine-tune H3 and sell it as a service under the MiniMax H3 commercial use license?

Yes, and §VI.1 gives you ownership of your Model Derivatives, with §I.11 confirming outputs are not themselves Model Derivatives. The obligations come with it, though: §V.2 forces you to bind every downstream user to §V and Exhibit A protections, §V.5 requires real anti-abuse safeguards with a reporting channel and repeat-violator suspensions, §IV.2 puts "MiniMax H3" in your product UI, and the territory limits still apply to you and your users. That safety and terms work, not the GPU bill, is the actual cost of a self-hosted H3 service.

Do I own the videos if the MiniMax H3 commercial use license never applied to me?

Under MiniMax's Open Platform Terms, yes on ownership: you "retain your ownership rights in Client input and generated content". The same clause adds that MiniMax may use that input and generated content to "provide, maintain, develop, and improve our Services", which is worth reading twice if you push unreleased client material through it. If you generate through any other provider, the binding document is that provider's terms, so read theirs literally rather than assuming they mirror MiniMax's.

How do excluded-territory teams get a MiniMax H3 commercial use license?

By submitting the application form MiniMax links from its license Q&A. MiniMax's developer relations lead has answered the two practical questions publicly on the model's Hugging Face discussion board (MiniMax H3 license discussion, August 2026): access is effectively automatic, in their words "apply will auto get access", and independent developers with no company can put "Personal/None" in the mandatory company field. The form is currently hosted on a third-party domain, which they say will move to a MiniMax domain soon. §II frames approval around "robust controls and guardrails", and the Q&A calls today's limits "not yet", not "not ever".