FramePack: what the repository publishes

FramePack states its memory floor together with what the floor buys: to generate a one-minute video at 30fps, 1800 frames, using the 13B model, the minimal required GPU memory is 6GB. It names the card generations that support the run and the ones nobody tested. As of 2026-09-22.

Inclusion rule. The same five fields for every family here. A field the repository does not state is recorded as not stated rather than estimated from the parameter count. Order. Fixed field order, identical on every family page.

1A floor attached to an output, which is the form every other entry here lacks

Every other hardware figure in this register answers whether the weights will load. This one answers what they produce at that memory: one minute, 30fps, 1800 frames, from a 13B model, at 6GB. The two halves of the sentence are inseparable, which is why the row quotes it whole.

It also demolishes the intuition the size column keeps inviting. Thirteen billion parameters sits beside a 60GB figure in one entry here and a 6GB figure in this one, so the parameter count is not what decided the memory. What decided it is how the work is broken up over time, and a parameter count cannot see that.

2Naming the card generations, and naming the ones nobody checked

The requirement names Nvidia GPUs in the RTX 30XX, 40XX and 50XX series that support fp16 and bf16, and adds that the GTX 10XX and 20XX are not tested. Publishing what was not tested is rarer than publishing what was, and for anybody holding older hardware it is the more useful half of the sentence.

The numeric formats are part of the requirement rather than a footnote to it. A card with enough memory and no bf16 support is not covered by this figure at all, which is precisely why this register quotes hardware statements instead of reducing them to a number of gigabytes.

3Speed given as a comparison between named laptops

The repository puts a per-frame time against an RTX 4090 and then says that on the maintainer's own 3070ti and 3060 laptops it runs about four to eight times slower. That is a range rather than a benchmark, and it is expressed in the unit that matters at the low end: how much longer the cheap card takes.

Nothing else in this register makes that comparison. Where other repositories publish timings at all, they are measured on data-centre cards, so the question of what a laptop does is normally unanswerable from published material.

4The same field, across every family

Inclusion rule. Families whose vendor has published weights openly. A family whose repository does not state this particular field keeps its row, marked hollow. Order. Alphabetical by family name.

Inclusion rule. Families whose vendor has published weights openly. A family whose repository does not state this particular field keeps its row, marked hollow. Order. Alphabetical by family name.

Inclusion rule. Families whose vendor has published weights openly. A family whose repository does not state this particular field keeps its row, marked hollow. Order. Alphabetical by family name.

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

5Sources

Read from github.com/lllyasviel on 2026-09-22. Hardware figures across every family are collected on requirements; the licence column is set out on licence and what counts as a published weight is on how read. Previous family: Stable Video Diffusion. Next family: Pyramid Flow.