LongCat-Video: what the repository publishes

LongCat-Video publishes 13.6B parameters under the MIT License and states 720p output at 30fps. It states no GPU memory figure and names no card, so the one cell that decides whether the weights can be run on hardware somebody owns is empty. As of 2026-09-22.

Inclusion rule. The same five 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.

1Licence and size answered, cost unanswered

MIT and 13.6B are both one-line facts, quickly checked and quickly cleared. Neither tells a reader whether the model will load on the card in front of them, and the repository supplies nothing that does.

This is the most common shape of gap in this register, and it is worth stating as a pattern rather than as a complaint. A licence name and a parameter count are cheap to publish and interesting to announce. A memory figure requires running the thing and committing to a configuration, so it is the value most often left out.

2Minutes-long is a capability claim with no figure behind it

The repository describes the model as able to generate minutes-long videos and attaches no maximum to the phrase. The length cell therefore records that no ceiling is stated, rather than reading a number into an adjective.

The distinction matters because a ceiling is a commitment and an adjective is not. Three families here put an actual number on sixty seconds; a description of duration without a figure is a different kind of statement, and flattening the two into one column would make this register look more decided than it is.

3A 720p claim with nothing behind it in the next cell

720p at 30fps is the stated output, and nothing in the repository ties that output to a memory figure or to a card. So the resolution cell is filled and the hardware cell beside it is empty, which is the pairing a reader should treat most carefully.

An output size is the easiest value to publish and the least constraining, because it says what the code will emit rather than what emitting it costs. Read on its own it gets taken as evidence that the model is practical at that size, and this register keeps the two cells adjacent to make that harder to do.

4The same field, across every family

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.

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.

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.

• Licence
  MIT Licensestated in the repositorymeituan-longcat, LongCat-Video repository / recorded 2026-09-22
• Model size
  13.6B parametersstated in the repositorymeituan-longcat, LongCat-Video repository / recorded 2026-09-22
• Resolution
  720p, 30fps videosstated with a frame rate and no memory figure beside itmeituan-longcat, LongCat-Video repository / recorded 2026-09-22

5Sources

Read from github.com/meituan-longcat on 2026-09-22. Hardware figures across every family are collected on requirements; the licence column is set out on licence and what counts as a published weight is on how read. Previous family: Cosmos Predict 2.5. Next family: HunyuanVideo.