The MiniMax H3 license, mapped to the files in your ComfyUI folder

What this page is — and is not

This is a source-indexing and reading note, not legal advice. We are not lawyers, and this page does not decide whether a particular person, company, product or territory is covered. Check the current upstream text yourself and ask qualified counsel for a situation-specific answer.

GenVidKit is an independent content site. We do not distribute model weights and do not operate a generation service for readers.

Start with the agreement, then inspect the file path

2026-08-02 — Agreement date shown in the MiniMax H3 Community License text.

4 — Excluded Territories named in §I.5: the EU, UK, Republic of Korea and United States.

$20M — Annual-revenue line in §IV.1 that calls for separate prior written authorization.

• The base weights are openly downloadable, but the repository is marked license: other with minimax-h3-community-license-agreement, not Apache or MIT.
• “Applicable Territory” is worldwide minus the four Excluded Territories. The agreement grants the listed actions — including use, reproduction, modification, distribution and display — only inside that territory.
• Outputs are named separately in §V.4 and Exhibit A.1. §VI.4 says MiniMax claims no rights over them, so the restriction is a contract term rather than an ownership claim.
• Turbo LoRAs can be marked Apache 2.0 at their source, while a ComfyUI repackage presents a repository-level MiniMax license field. The download route is part of the provenance record.

Official sources: MiniMaxAI/MiniMax-H3 LICENSE and its License Q&A. Both links were checked on 2026-08-19.

Which file falls under which license?

Each row separates the repository you downloaded from the upstream author's license. A repository-level label is not a substitute for recording where an individual file came from.

Why the split matters: Comfy-Org/MiniMax-H3 presents one repository-level license: other field over directories whose upstream contents include Apache 2.0 components. The repackaged repository is also the dominant entry point: in the 30 days to the 2026-08-20 snapshot it recorded 15,721,667 downloads against 3,308,673 on the official repository, a 4.75× difference. We are not claiming that the repackage relicensed those files. We are saying that the download source and the original author's notice are both worth recording when you document a ComfyUI installation.

What the territory clause actually reaches

You may not use, reproduce, modify, distribute, or display the MiniMax H3 Works or any of their Outputs or results outside the Applicable Territory. Any such use outside the Applicable Territory is not authorized by this Agreement.

MiniMax H3 Community License Agreement §V.4; Exhibit A.1 repeats “Use outside the Applicable Territory.”

The clause does not only say distribute. It names use and display too. The agreement defines “MiniMax H3 Works” in §I.7 as Materials, Model Derivatives and their derivatives; §I.11 then says Outputs are not deemed Model Derivatives. Outputs are still named separately in §V.4 and Exhibit A.1, while §VI.4 says MiniMax claims no rights over them.

That is the distinction this page can state without filling in a legal conclusion: Outputs are not treated as MiniMax-owned Works by the definition, but they are still included in the territory restriction as a contract term. The agreement also places responsibility for Outputs and subsequent use on the user.

Do not collapse these into either shortcut: “MiniMax owns your generated videos” is not what §VI.4 says. “Generated videos are automatically unrestricted” skips the separate wording in §V.4 and Exhibit A.1.

Two obligations people state too broadly

Commercial display

§IV.2 requires prominent “MiniMax H3” display on the user interface of a commercial product or service that uses H3. That is different from the three items in §III.3, which the agreement describes as encouraged rather than required.

Revenue threshold

§IV.1 says commercial products and services above 20 million US dollars in yearly revenue require separate prior written authorization. The page records the clause; it does not decide how an individual business should apply the line.

Other-model training

§V.3 addresses using the Works or their Outputs to improve another AI model, with the stated H3 and derivative exceptions. This is a licensing question, not a claim that every generated file is a free training corpus.

Source control

Exhibit A says MiniMax reserves the right to update the Acceptable Use Policy. The copy we read says “Last revised: August 2, 2026,” so the current upstream text matters more than a saved excerpt.

Open weights and hosted API are not the same rule set

Downloaded weights

This page covers the community license attached to local model files, their repository provenance, and the territory and use language in that agreement.

Hosted API

The API has its own service terms. The official License Q&A explains the split; do not reason from the open-weight license to the API, or back in the other direction.

What we could not settle from the text

• Whether an editorial page displaying generated frames counts as “display outside the Applicable Territory.” We do not answer that from a guess; this page contains no H3-generated media.
• The official Q&A's first heading says the open-weight license is limited “to” the EU, UK, South Korea and US, while the body and §I.5 describe those places as restricted. We record the conflict rather than silently correcting MiniMax's document.
• Exhibit A reserves a right to update its Acceptable Use Policy. A changed upstream file can change the reading even if this page does not.

Check the license version before relying on a section number

The LICENSE copy we read is pinned to repository revision 42ed227ee7df40d41602854ae760620d6eb651fe, 17,604 bytes, SHA-256 59b99642b95ea21630e311198ddbfffbfe05aadba0c2f5d884cbdf4efcc90f44. Retrieved August 19, 2026.

curl -sSL "https://huggingface.co/MiniMaxAI/MiniMax-H3/resolve/main/LICENSE" | shasum -a 256

If the hash differs: the upstream terms changed after our reading. Recheck every quoted section and the repository metadata before treating this page as current. The archived snapshot used for this page is 01-requirements/license-snapshot-2026-08-19/.

MiniMax H3 license questions

Is MiniMax H3 open source?

The weights are openly downloadable, but Hugging Face records the repository license as other with license_name minimax-h3-community-license-agreement. “Open weights under the MiniMax H3 Community License” is the more precise phrase.

Can I use MiniMax H3 in the United States?

The Community License names the United States, the European Union, the United Kingdom and the Republic of Korea as Excluded Territories, while its Applicable Territory is worldwide minus those regions. §II also points organizations in excluded territories to MiniMax's application route. This page records the text and does not provide a case-specific legal conclusion.

Does MiniMax own the videos I generate?

§VI.4 says MiniMax claims no rights over the Outputs you generate. §V.4 separately restricts use, reproduction, modification, distribution and display of Works or their Outputs outside the Applicable Territory; that is a contract term, not an ownership claim.

Are the Turbo LoRAs under the same license as the base model?

No. The lightx2v/Minimax-h3-Turbo and larryvrh/MiniMax-H3-Turbo-Lora source repositories are marked Apache 2.0, while the base model is marked with the MiniMax H3 Community License.

Does the API use this open-weight license?

No. This page maps the community license for downloaded open weights. The hosted API has its own service terms, and the official License Q&A explains that the two routes are governed separately.

What happens if the license text changes?

Download the upstream LICENSE file and compare its SHA-256 with the version recorded in the “Read it yourself” section. A different hash means the terms were revised and the references on this page need to be rechecked.