NodeValid

Published video-model weights, licences and hardware notes

HunyuanVideo states pixels, not an output size

720px1280px and 544px960px appear on these pages as the settings two memory figures were measured at. Neither is presented as what the model produces, so no output size is recorded in this column. As of 2026-09-12.

HunyuanVideo in the resolution column, as publishedA pixel size can enter a repository as an output specification or as a row label on a memory table, and the two are not the same claim.Output sizeNo output size recordedsizes the memoryfigureMemory it sizes60GB peak at720px1280px, 129 framesheld over thismany framesClip length129 frames, as ameasurement settingSizes borrowed from the memory tableIts pixel dimensions size the memory figures instead
Fig. 1 The numbers exist; what they describe is a measurement rather than a product.
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 stateWhat the pages stateWhat the pagesstateResolution, in the vendor's own wor…Resolution, in the vendor's own wordsResolution, in the vendor's own words — What the pages state: No output size recordedThe detail published beside itThe detail published beside it — What the pages state: Its pixel dimensions size the memory figures insteadHardware, from the same pagesHardware, from the same pages — What the pages state: 60GB peak at 720px1280px, 129 framesLength, from the same pagesLength, from the same pages — What the pages state: 129 frames, as a measurement setting
Fig. 2 Filled where the repository states something, hollow where it does not. A blank is not an inference.
HunyuanVideo in the resolution column, with the columns that qualify it. Read from github.com/Tencent-Hunyuan on 2026-09-12.
ColumnWhat the pages state
Resolution, in the vendor's own wordsNo output size recorded
The detail published beside itIts pixel dimensions size the memory figures instead
Hardware, from the same pages60GB peak at 720px1280px, 129 frames
Length, from the same pages129 frames, as a measurement setting

Inclusion rule. The value this page is about, the detail the vendor attached to it, and the two columns that change how it should be read. A column the vendor left empty keeps its row and says so. Order. This column first, then its detail, then the two columns that qualify it.

1Where a pixel figure sits changes what it means

A resolution stated as output is a claim about the artefact: this is what comes out. The same number used to label a memory measurement is a claim about a run, and says nothing about whether other sizes work.

Reading the second as the first would put a ceiling in the register that the repository never asserted, and would suggest 720px1280px is a limit rather than a test point.

2What the memory table does establish

That both sizes were run to completion on a single 80G card, with 129 frames at the larger one. That is more than many rows here offer, and it is not an output specification.

It also fixes the aspect ratios that were actually exercised, which is useful for anyone planning vertical output and does not tell them what the widest supported frame is.

3Why the column stays empty

Because filling it would require choosing one of two test settings and calling it the answer. The register records the absence and keeps the two pixel figures in the hardware column where they were published.

The same repository is precise about its parameter bound and its card, so the omission here is a documentation choice rather than a gap in what the vendor knows.

4Sources

Output sizes above appear on github.com/Tencent-Hunyuan, checked 2026-09-12. The full entry is at this family's page; what counts as a stated size is on resolution. Nearby: Two sizes, two releases, 480p, for now.