NodeValid

Published video-model weights, licences and hardware notes

FramePack ties a minute to its memory floor

A 1-minute video at 30fps, 1800 frames, on the 13B model, from a minimum of 6GB. The length is not stated on its own: it is stated as the output that memory floor delivers. As of 2026-09-22.

FramePack in the length column, as publishedPublishing a length together with the memory it needs turns two separate claims into one checkable statement about a run.Length as published1 minute, 1800 frames at 30fpsframes, seconds or bothSeconds and frames, tied tothe memory floorOutput sizeNo output size recordedpixels per frameThe repository states lengthand memory insteadMemory6GB minimum for 1800 frames at30fpswhat holding them costRTX 30XX, 40XX, 50XX withfp16 and bf16One clip, as this release describes itLength and memory in one claim
Fig. 1 A duration with a cost attached, which no other row in the register manages.
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 pagesstateLength, in the vendor's own wor…Length, in the vendor's own wordsLength, in the vendor's own words — What the pages state: 1 minute, 1800 frames at 30fpsThe detail published beside itThe detail published beside it — What the pages state: Seconds and frames, tied to the memory floorResolution, from the same pagesResolution, from the same pages — What the pages state: No output size recordedHardware, from the same pagesHardware, from the same pages — What the pages state: 6GB minimum for 1800 frames at 30fps
Fig. 2 Filled where the repository states something, hollow where it does not. A blank is not an inference.
FramePack in the length column, with the columns that qualify it. Read from github.com/lllyasviel on 2026-09-22.
ColumnWhat the pages state
Length, in the vendor's own words1 minute, 1800 frames at 30fps
The detail published beside itSeconds and frames, tied to the memory floor
Resolution, from the same pagesNo output size recorded
Hardware, from the same pages6GB minimum for 1800 frames at 30fps

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.

1The pairing is what makes both halves credible

Six gigabytes on its own would be an eyebrow-raising claim for a 13B model. Six gigabytes for 1800 frames at 30fps is a specific assertion somebody can try and report on.

It also runs the other way. A minute of output on its own would be a marketing figure; tied to a floor it becomes a description of a configuration.

2Thirty frames a second, stated

The rate is published, so 1800 frames and one minute agree with each other. Three other releases in the register give a frame count with no rate at all.

At 30fps this is also the highest published rate here, which matters for output intended to sit beside conventionally shot material without interpolation.

3What is missing from the claim

The frame size. No resolution is recorded for this family, so a minute of 1800 frames has no pixel dimensions, and memory scales with pixels.

That leaves the most complete length statement in the register attached to the least complete frame description. Both are recorded as they stand.

  • Hardware
    To generate a 1-minute video at 30fps, 1800 frames, using the 13B model, the minimal required GPU memory is 6GBa floor stated together with the output it buyslllyasviel, FramePack repository / recorded 2026-09-22
  • Hardware
    Nvidia GPU in RTX 30XX, 40XX, 50XX series that supports fp16 and bf16; the GTX 10XX/20XX are not testedcard generations and numeric formatslllyasviel, FramePack repository / recorded 2026-09-22

4Sources

Lengths above are in the unit the vendor chose, from github.com/lllyasviel on 2026-09-22, with no conversion applied. The full entry is at this family's page; frames against seconds is on length. Nearby: Ten seconds, or five, A frames-to-seconds table.