NodeValid

Published video-model weights, licences and hardware notes

SkyReels-V2 gives pixels behind 540P and 720P

This family states 544 x 960 at 540P and 720 x 1280 at 720P, with the frame counts they run at. Naming the tier and the pixels together is what makes the values usable. As of 2026-09-22.

SkyReels-V2 in the resolution column, as publishedTier names like 540P mean different pixel counts to different vendors, so writing the dimensions out is what turns a label into a value.Output size544 x 960 at 540P, 720x 1280 at 720Psizes the memoryfigureMemory it sizesAbout 14.7GB peak onthe 1.3B at 540Pheld over thismany framesClip length1457 frames for a 60svideoThe label and the pixels togetherStated with the frame counts they run at
Fig. 1 Two tier names with their actual dimensions, so neither has to be looked up.
SkyReels-V2 in the resolution column, with the columns that qualify it. Read from huggingface.co/Skywork on 2026-09-22.
ColumnWhat the pages state
Resolution, in the vendor's own words544 x 960 at 540P, 720 x 1280 at 720P
The detail published beside itStated with the frame counts they run at
Hardware, from the same pagesAbout 14.7GB peak on the 1.3B at 540P
Length, from the same pages1457 frames for a 60s video

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.

1Tier names are not dimensions

540P and 720P are conventions, and the pixel counts behind them vary by vendor and by aspect ratio. A register that recorded only the label would be recording something different for every row that used it.

Writing 544 x 960 beside 540P closes that. It also shows the frame is portrait, which the tier name alone never says.

2The memory figures use the tier, not the pixels

About 14.7GB on the 1.3B at 540P and around 51.2GB on the 14B at the same 540P. Because the dimensions behind 540P are written out elsewhere on the page, both figures are fully specified.

That is the payoff of publishing the mapping once: every later reference to the tier inherits the precision.

3Frame counts travel with the sizes

The repository attaches frame counts to the resolutions, and a separate table maps frames to seconds from 257 for ten seconds up to 1457 for sixty.

So this row can be read in either direction. A reader starting from a target length arrives at frames, and a reader starting from a frame size arrives at a tier with a memory figure.

  • Length
    num_frames 257 for a 10s video, 377 for 15s, 737 for 30s and 1457 for 60sframes against seconds in the vendor's own tableSkyworkAI, SkyReels-V2 repository / recorded 2026-09-22
  • Hardware
    About 14.7GB peak VRAM for a 540P video on the 1.3B model, and around 51.2GB on the 14Bthe same output size on two model sizesSkyworkAI, SkyReels-V2 repository / recorded 2026-09-22

4Sources

Output sizes above appear on huggingface.co/Skywork, checked 2026-09-22. The full entry is at this family's page; what counts as a stated size is on resolution. Nearby: A default set for speed, 720P at 16FPS.