NodeValid

Published video-model weights, licences and hardware notes

Thirteen billion at 6GB, two billion at 32GB

FramePack states 13B models with a 6GB minimum. Cosmos Predict 2.5 states 2,059,174,912 parameters and requires 32.54 GB of VRAM. The bigger model asks for a fifth of the memory. As of 2026-09-22.

FramePack and Cosmos Predict 2.5 on the same columnWhen the larger count comes with the smaller requirement, any rule connecting the two columns is disproved by a single pair of rows.FramePackCosmos Predict 2.5Size, as each vendor states it13B models2,059,174,912 parametersThe detail published beside itThe size the memory floor is stated forPublished as an exact count, not arounded figureLicence, from the same pagesApache 2.0NVIDIA Open Model LicenseThe arithmetic fails in both directions
Fig. 1 Six times the parameters, a fifth of the memory, both vendors' own figures.
FramePack and Cosmos Predict 2.5 on the size column, read from github.com/lllyasviel and huggingface.co/nvidia. Recorded 2026-09-22.
PointFramePackCosmos Predict 2.5
Size, as each vendor states it13B models2,059,174,912 parameters
The detail published beside itThe size the memory floor is stated forPublished as an exact count, not a rounded figure
Licence, from the same pagesApache 2.0NVIDIA Open Model License
Hardware, from the same pages6GB minimum for 1800 frames at 30fps32.54 GB of GPU VRAM

Inclusion rule. Two families whose published values in this column lead to opposite decisions. A pair that happens to agree is not listed, because agreement is already visible on the column summary. Order. The column itself first, then its detail, then the columns that qualify it.

1The inversion is the whole point

Six times the parameters and a fifth of the memory is not a rounding error or a measurement artefact. It is what happens when one release is engineered around packing long sequences and another is documented as a deployment specification.

Anyone estimating a requirement from a count would be wrong on both rows, in opposite directions, by large factors.

2The two figures are also different kinds of claim

FramePack's 6GB is a minimum, stated for 1800 frames at 30fps. Cosmos states a requirement with three GPU architectures named, for 720P at 16FPS in five seconds.

Both are fully qualified, which is why the comparison is legitimate. Neither figure is a peak from an unrelated table.

3What the outputs do to the comparison

Cosmos produces five seconds; FramePack's figure buys a full minute. The release with less memory and more parameters also claims twelve times the duration.

No frame size is stated for FramePack, so the comparison stops there. The register records both rows and joins nothing beyond what each vendor published.

4Sources

Read from github.com/lllyasviel and huggingface.co/nvidia on 2026-09-22. Full entries: FramePack and Cosmos Predict 2.5. What this column is quoting is on size. Nearby pairs: Four seconds or sixty, Frames, or frames and rate.