Licence: the name on the file, quoted not summarised
The licence column holds the name on the file that ships beside the weights, quoted rather than summarised. Three families here carry a standard permissive licence, one carries a licence its own vendor wrote, and one changes licence with the model size. As of 2026-09-12.
| Family | Recorded licence | What the cell carries with it |
|---|---|---|
| CogVideoX | Split by model size | 2B is Apache 2.0; the 5B carries a separate CogVideoX licence |
| HunyuanVideo | tencent-hunyuan-community | A licence the vendor wrote rather than adopted |
| LTX-Video | Apache 2.0 | One licence across the variants the repository publishes |
| Mochi 1 | Apache 2.0 | Beside a video autoencoder published under the same terms |
| Wan | Apache 2.0 | On the 2.1 and 2.2 releases; 3.0 publishes no weights to license |
Inclusion rule. Families whose vendor publishes weights from an organisation it controls. The value is the licence name attached to those files, never a reading of what the terms permit. Order. Alphabetical by family name.
1The cell holds a name because a paraphrase cannot be rechecked
What gets recorded is the string attached to the files: Apache 2.0, tencent-hunyuan-community, or a note that the terms change with the model size. None of them is expanded into a sentence about what you may do. A paraphrase is a new document written by somebody with no standing to write it, and it is the version a reader would end up acting on.
Quoting the name keeps the row one click from the file. That is the whole arrangement: the cell says which document governs the download, and the link says where to read it. Anything more would be this register answering a question it has no way to answer for a particular plan, in a jurisdiction it knows nothing about.
2One word, three shapes, and the third is the one that gets missed
Three of the five families here ship under a standard permissive licence whose text is fixed and widely read, which is why the column looks uniform from a distance. HunyuanVideo breaks that: its weights carry tencent-hunyuan-community, named after the company that wrote it, so the terms have to be read rather than recognised.
CogVideoX is the third shape. Its 2B model is Apache 2.0 while its 5B carries a separate licence of the project's own, which makes the licence a property of the model rather than of the family. Someone who checks the smaller file and downloads the larger one has checked a document that does not govern what they now have.
3The two things this column stays silent about
It is silent about output. A licence on weights addresses copying, modifying and passing the files on; whether the video that comes out can be sold is a separate clause, present in some releases and missing from others. Silence there is neither permission nor refusal, and the cell does not convert it into either.
It is also silent about the version on sale. Wan 2.1 and 2.2 carry Apache 2.0 and 3.0 publishes nothing, so the version billed by the second on the hosted page has no public licence at all. An empty cell is the accurate entry there: nothing was released, so nothing was licensed.
- LicenceApache 2.0stated in the repository
- LicenceApache 2.0stated in the repository
- Licencetencent-hunyuan-community, a vendor-written licence rather than a standard permissive oneshown on the model card
- LicenceSplit: CogVideoX-2B is Apache 2.0 while CogVideoX-5B carries a separate CogVideoX licencediffers by model size inside one family
- LicenceApache 2.0stated in the repository
4Sources
Values in this column are quoted from the HunyuanVideo model card, the CogVideo repository, read 2026-09-12, and from the repositories linked on each model page. The other columns are listed on fields; what counts as a published statement is on how read. Next column: Size, Hardware.