NodeValid

Published video-model weights, licences and hardware notes

HunyuanVideo states 60GB at 720p, 45GB at 544p

The repository gives peak GPU memory of 60GB at 720px1280px with 129 frames, and 45GB at 544px960px. Both were taken on a single 80G GPU, so neither is a floor for smaller hardware. As of 2026-09-12.

HunyuanVideo in the hardware column, as publishedTwo figures at two pixel sizes on the same card describe how the requirement moves, which is a different claim from stating what the model needs.The memory statement as published60GB peak at 720px1280px,129 frames45GB at 544px960px, on a single 80G GPUNo output size recordedIts pixel dimensions size the memory figures instead129 frames, as ameasurement settingFrames, sizing a memory figure rather than a ceilingBoth taken on the same large card
Fig. 1 Measured on an 80G card at two sizes, so the pair describes scaling, not a minimum.
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 pagesstateHardware, in the vendor's own wordsHardware, in the vendor's own words — What the pages state: 60GB peak at 720px1280px, 129 framesThe detail published beside itThe detail published beside it — What the pages state: 45GB at 544px960px, on a single 80G GPUResolution, from the same pagesResolution, from the same pages — What the pages state: No output size recordedLength, 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 hardware column, with the columns that qualify it. Read from github.com/Tencent-Hunyuan on 2026-09-12.
ColumnWhat the pages state
Hardware, in the vendor's own words60GB peak at 720px1280px, 129 frames
The detail published beside it45GB at 544px960px, on a single 80G GPU
Resolution, from the same pagesNo output size recorded
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.

1Peak memory is not a requirement

A peak figure is the high-water mark a particular script reached. It tells a reader that an 80G card completed the run with headroom, and it does not tell them whether a 48G card would have finished.

The distinction matters because a reader with a smaller card wants a floor and will read a peak as one. The register keeps the word peak in the value for that reason.

2The two figures are a gradient

From 544px960px to 720px1280px the pixel count roughly doubles and the memory rises from 45GB to 60GB, which is a third rather than a doubling. Weights dominate; activations move with the frame.

Anyone planning at a third resolution can interpolate along that line with some confidence, and should treat the result as an estimate rather than as something the vendor published.

3What the 129 frames are doing in the figure

They are part of the configuration, not a ceiling. The larger figure is stated for 129 frames, so frame count, pixel size and memory are quoted as one bundle.

That is the useful form for a hardware statement and the reason the register never separates a memory number from its setting. Split apart, both halves become unfalsifiable.

4Sources

Every figure above is the vendor's own, taken from github.com/Tencent-Hunyuan on 2026-09-12 with nothing measured here. The rest of the release is on its family entry, the whole column is on hardware, and all memory figures together are on requirements. Nearby: From four gigabytes, Sixty gigabytes and an H100.