NodeValid

Published video-model weights, licences and hardware notes

FramePack states a minute and no frame size

A 1-minute video at 30fps, 1800 frames, on the 13B model, from 6GB of memory. Every part of that is stated except the size of a frame, so this column is empty on the most specific hardware row in the register. As of 2026-09-22.

FramePack in the resolution column, as publishedFrames, a rate and a memory floor without a pixel size leaves the one figure a reader needs to compare this release with any other.Output sizeNo output size recordedsizes the memoryfigureMemory it sizes6GB minimum for 1800frames at 30fpsheld over thismany framesClip length1 minute, 1800 framesat 30fpsFrames counted, frames unsizedThe repository states length and memory instead
Fig. 1 The most complete hardware statement here, missing the value that would make it comparable.
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: The repository states length and memory insteadHardware, from the same pagesHardware, from the same pages — What the pages state: 6GB minimum for 1800 frames at 30fpsLength, from the same pagesLength, from the same pages — What the pages state: 1 minute, 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 resolution column, with the columns that qualify it. Read from github.com/lllyasviel on 2026-09-22.
ColumnWhat the pages state
Resolution, in the vendor's own wordsNo output size recorded
The detail published beside itThe repository states length and memory instead
Hardware, from the same pages6GB minimum for 1800 frames at 30fps
Length, from the same pages1 minute, 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 omission is load-bearing

Memory scales with pixels. A 6GB floor for 1800 frames means one thing at 256 by 256 and something very different at 1280 by 720, and the repository does not say which it is.

That makes the register's lowest memory figure the hardest one to place. Every other 6GB claim would be comparable if the frame size were stated.

2What is stated is stated carefully

The card generations are named, the numeric formats are named, the untested generations are called untested, and the output length is given with its frame rate. This is not a careless page.

Which suggests the omission is a choice. A release built around packing long sequences may treat frame size as a runtime argument rather than a property.

3Why nothing is filled in

A resolution could be read off demo clips or off a configuration default, and either would put a number in the register that the repository never claimed.

The absence is recorded as an absence, and the entry names the values that do exist. A reader planning around the 6GB figure has to establish the frame size themselves.

  • 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
  • Model size
    13B modelsthe size the memory floor is stated forlllyasviel, FramePack repository / recorded 2026-09-22

4Sources

Output sizes above appear on github.com/lllyasviel, checked 2026-09-22. The full entry is at this family's page; what counts as a stated size is on resolution. Nearby: One size per checkpoint, 540P and 720P in pixels.