NodeValid

Published video-model weights, licences and hardware notes

Storage footprint, the cost nobody states

A storage footprint is what the weights occupy on disk and how fast that disk has to be. It follows from the parameter count and the numeric format, and no repository in this register states it. As of 2026-09-22.

From a count to the disk it occupiesBytes per parameter turn a count into a download size, and the variants a release publishes multiply it, which is where a local plan meets its first hard limit.CountThe published parameterfiguretimes bytes perparameterOne buildThe download for asingle varianttimes the buildsyou keepOn diskWhat a local deploymentactually holdsDerivable, and rarely derivedThis is the one derivation the register considers safe, because the format is arithmeticrather than behaviour.
Fig. 1 The one figure a reader can derive safely, and the multiplier that surprises them.
What multiplies a storage estimate beyond one download. Recorded 2026-09-22.
FactorEffect on disk
Variants keptOne copy each
Numeric formats keptOne copy each
Fine-tunesOne copy each
Cache and intermediatesAdded during runs

Inclusion rule. Factors that multiply a stored weights estimate. Run-time files are included because they occupy the same disk. Order. From the factor a reader controls to the one the software imposes.

1The one safe derivation

Bytes per parameter is arithmetic, not behaviour, so a count and a format give a download size within a reasonable margin. That is the only inference this register treats as sound, and it still is not published as a value.

Everything else about a run resists the same treatment, which is why memory figures are quoted rather than calculated here.

2Keeping several builds is the normal case

A release that publishes a full model, a distilled build and an fp8 build invites a reader to keep all three, and a team comparing them will. The disk cost is the sum, not the largest.

Add fine-tunes and the cache a pipeline writes during runs, and storage becomes a real constraint for a local deployment. It appears in no column here because no vendor states it.

3Why this is derived and never recorded

No repository in the register states a download size or a disk requirement. Bytes per parameter is arithmetic rather than behaviour, so a reader can estimate it safely, and the register still does not publish the estimate as a value.

The reason is consistency: every cell here can be traced to a page and a date. A derived figure would be the one number in the register with no source behind it.

A reading note, not an entry: no vendor value appears on this page. Where the register records this term for a particular release, it is on the hardware column and on that family's own page. Nearby terms: Resolution tier, Aspect ratio.