CogVideoX: what the repository publishes
CogVideoX is the one family here whose licence changes with the model size: the 2B model is Apache 2.0 and the 5B carries a separate licence of the project's own. Its smallest model is also the lowest hardware bar in this register, from 4GB. As of 2026-09-12.
| Field | What is stated | Detail |
|---|---|---|
| Licence | Split by model size | 2B is Apache 2.0; 5B carries a separate CogVideoX licence |
| Hardware | From 4GB in FP16 on the 2B | From 5GB on the 5B, from 10GB on 1.5-5B |
| Length | Up to 161 frames on 1.5-5B | Described as 5 or 10 seconds |
| Resolution | 1360x768 on 1.5-5B | 720x480 on the 5B |
Inclusion rule. The same four fields for every family here. A field the repository does not state is recorded as not stated rather than estimated from the parameter count. Order. Fixed field order, identical on every family page.
1One family, two licences, and the difference is the useful part
A reader who checks the licence on the smaller model and assumes it covers the larger one gets it wrong. That is not an unusual arrangement in this field and it is the only case in this register where it happens inside a single project.
The register therefore records the licence per model rather than per family. A family-level cell would have to pick one and would be wrong for whoever was reading about the other.
2Four gigabytes is a different category of accessible
Every other hardware figure in this register is measured in tens of gigabytes and implies a rented card. Four gigabytes in FP16 is a laptop-class graphics card, which puts this model in reach of someone experimenting rather than someone provisioning.
What that buys is the smaller model at the lower resolution. The register keeps the figures attached to the model they were stated for, because the gap between the smallest and largest entry in this family is itself a factor of several.
3Length is stated in frames and translated by the vendor
Up to 161 frames on the larger current model, which the repository describes as 5 or 10 seconds. Frames are the honest unit here because the seconds depend on frame rate, and the vendor supplies both so the register carries both.
Against the sixty seconds another family in this register states, this is short. Against what most hosted services sell as a single generation, it is comparable.
4The same field, across every family
| Family | Licence |
|---|---|
| CogVideoX | Split by model size |
| HunyuanVideo | tencent-hunyuan-community |
| Mochi 1 | Apache 2.0 |
Inclusion rule. Families whose vendor has published weights openly. A family whose repository does not state this particular field keeps its row, marked hollow. Order. Alphabetical by family name.
| Family | Hardware |
|---|---|
| CogVideoX | From 4GB in FP16 on the 2B |
| HunyuanVideo | Over 13 billion parameters |
| Mochi 1 | 10 billion parameters |
Inclusion rule. Families whose vendor has published weights openly. A family whose repository does not state this particular field keeps its row, marked hollow. Order. Alphabetical by family name.
| Family | Length |
|---|---|
| CogVideoX | Up to 161 frames on 1.5-5B |
| HunyuanVideo | 60GB peak at 720px1280px, 129 frames |
| Mochi 1 | About 60GB VRAM on a single GPU |
Inclusion rule. Families whose vendor has published weights openly. A family whose repository does not state this particular field keeps its row, marked hollow. Order. Alphabetical by family name.
- LicenceSplit: CogVideoX-2B is Apache 2.0 while CogVideoX-5B carries a separate CogVideoX licencediffers by model size inside one family
- HardwareFrom 4GB in FP16 for the 2B model, from 5GB in BF16 for the 5B, and from 10GB for CogVideoX1.5-5Bthe lowest figures the repository states
- Length and resolutionCogVideoX1.5-5B states 1360x768 and up to 161 frames, described as 5 or 10 secondsper model
5One family, two licences, and the difference is the useful part
A reader who checks the licence on the smaller model and assumes it covers the larger one gets it wrong. That is not an unusual arrangement in this field and it is the only case in this register where it happens inside a single project.
The register therefore records the licence per model rather than per family. A family-level cell would have to pick one and would be wrong for whoever was reading about the other.
6Four gigabytes is a different category of accessible
Every other hardware figure in this register is measured in tens of gigabytes and implies a rented card. Four gigabytes in FP16 is a laptop-class graphics card, which puts this model in reach of someone experimenting rather than someone provisioning.
What that buys is the smaller model at the lower resolution. The register keeps the figures attached to the model they were stated for, because the gap between the smallest and largest entry in this family is itself a factor of several.
7Length is stated in frames and translated by the vendor
Up to 161 frames on the larger current model, which the repository describes as 5 or 10 seconds. Frames are the honest unit here because the seconds depend on frame rate, and the vendor supplies both so the register carries both.
Against the sixty seconds another family in this register states, this is short. Against what most hosted services sell as a single generation, it is comparable.
- LicenceSplit: CogVideoX-2B is Apache 2.0 while CogVideoX-5B carries a separate CogVideoX licencediffers by model size inside one family
- HardwareFrom 4GB in FP16 for the 2B model, from 5GB in BF16 for the 5B, and from 10GB for CogVideoX1.5-5Bthe lowest figures the repository states
- Length and resolutionCogVideoX1.5-5B states 1360x768 and up to 161 frames, described as 5 or 10 secondsper model
8Sources
Read from github.com/THUDM on 2026-09-12. Hardware figures across every family are collected on requirements; what counts as a published weight is on how read. Next family: Mochi 1.