NodeValid

Published video-model weights, licences and hardware notes

Resolution: the pixels a release says it produces

The resolution column holds the output size a repository states for a named release, with whatever qualifier the vendor attached. Some pixel sizes here are not output claims at all: they are the settings a memory figure was measured at, and those are filed elsewhere. As of 2026-09-12.

Why a pixel size appears, and where it is filedA repository states pixel dimensions either to describe what a run produces or to describe the conditions a memory measurement was taken under. Those are different claims. Only the first belongs in the resolution column, and confusing them invents an output ceiling no vendor claimed.Why does this release state a pixel sizeTo describe outputRecorded hereWith the model it belongsto and any qualifier thevendor attached.To size a measurementRecorded as hardwareThe dimensions a memoryfigure was taken at, not alimit.Not stated at allLeft emptyOne repository publishes alength ceiling and no size.Same digits, different claim
Fig. 1 The same numbers, written for two different purposes. Which purpose decides which column the value is recorded in.
What the repositories actually stateFilled where the repository states something, hollow where it does not. A blank is not an inference.What the repositories actually stateStated resolutionWhat kind of statement it isWhat kind ofstatement it isCogVideoXCogVideoX — Stated resolution: 1360x768 on CogVideoX1.5-5BCogVideoX — What kind of statement it is: An output size, stated per model, 720x480 on the 5BHunyuanVideoHunyuanVideo — Stated resolution: No output size recordedHunyuanVideo — What kind of statement it is: Its pixel dimensions size the memory figures insteadLTX-VideoLTX-Video — Stated resolution: No output size recordedLTX-Video — What kind of statement it is: The repository states a length ceiling rather than a sizeMochi 1Mochi 1 — Stated resolution: 480pMochi 1 — What kind of statement it is: An output size, described as the current capabilityWanWan — Stated resolution: 720P on the 5B releaseWan — What kind of statement it is: An output size, stated at 24fps with the model
Fig. 2 Filled where the repository states something, hollow where it does not. A blank is not an inference.
Where each family states a pixel size, and whether it describes output or a measurement. Recorded 2026-09-12.
FamilyStated resolutionWhat kind of statement it is
CogVideoX1360x768 on CogVideoX1.5-5BAn output size, stated per model, 720x480 on the 5B
HunyuanVideoNo output size recordedIts pixel dimensions size the memory figures instead
LTX-VideoNo output size recordedThe repository states a length ceiling rather than a size
Mochi 1480pAn output size, described as the current capability
Wan720P on the 5B releaseAn output size, stated at 24fps with the model

Inclusion rule. Pixel sizes a repository states for a released model. A size quoted only to describe how a memory measurement was taken is recorded in the hardware column, not here. Order. Alphabetical by family name.

1A pixel size shows up for two different reasons

Sometimes it is a claim about what comes out. Mochi 1 states 480p, CogVideoX1.5-5B states 1360x768 with 720x480 on the 5B, and Wan's 5B release is described at 720P and 24fps. Those belong in this column because they describe the artefact a run produces.

Sometimes a pixel size is instead the setting a memory figure was measured at. HunyuanVideo's 60GB and 45GB are quoted at 720px1280px and 544px960px, which says what the measurement assumed and not what the model is limited to. Filing those here would invent an output ceiling the repository never claimed, so they stay with the figure they qualify.

2The qualifier is part of the value

Current capability is a form of words that says more is intended. Dropping it would turn a snapshot of one release into a permanent property of the model, so the cell keeps the phrase and the date the repository was read. A row that has gone out of date should look out of date rather than look authoritative.

The same reasoning rules out a single headline size per family. A family publishes several models, the pixel size belongs to one of them, and the one it belongs to is usually the one carrying the highest memory figure. A family-level cell would be wrong for whichever reader was asking about the other model.

3This is the dial that moves the number in the next column

Cutting the pixel count is the cheapest way to move a memory figure, and one repository publishes the trade directly: sixty gigabytes at the larger dimensions and forty-five at the smaller, same model, same page. Resolution and hardware move together, and the register records both so the trade is visible rather than merely described.

It also explains why comparing memory across families means little unless both sides name a size. Two figures quoted at unstated dimensions are two numbers about different work, and setting them in one sentence is how a team ends up provisioned for the run it was not planning.

  • Resolution
    480p, described as the current capabilitystated as a present limitGenmo, Mochi repository / recorded 2026-09-12
  • Length and resolution
    CogVideoX1.5-5B states 1360x768 and up to 161 frames, described as 5 or 10 secondsper modelTHUDM, CogVideo repository / recorded 2026-09-12
  • Smallest published model
    A 5B text-to-video and image-to-video model at 720P and 24fpsTI2V-5BWan-Video, Wan2.2 repository / recorded 2026-09-12

4Sources

Values in this column are quoted from the CogVideo repository, the Mochi 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: Length, Licence.