NodeValid

Published video-model weights, licences and hardware notes

SkyReels-V2 maps 1457 frames to sixty seconds

The repository gives num_frames of 257 for a ten second video, 377 for fifteen, 737 for thirty and 1457 for sixty. A conversion table rather than a single figure, which settles the frame rate implicitly at every point. As of 2026-09-22.

SkyReels-V2 in the length column, as publishedA frames-to-seconds table is the most usable form a length statement can take, because it answers the question in whichever unit the reader brought.Length as published1457 frames for a 60s videoframes, seconds or bothFrames against seconds, inthe vendor's own tableOutput size544 x 960 at 540P, 720 x 1280 at720Ppixels per frameStated with the frame countsthey run atMemoryAbout 14.7GB peak on the 1.3B at540Pwhat holding them costAround 51.2GB for the same540P on the 14BOne clip, as this release describes itBoth units, four times over
Fig. 1 Four durations with their frame counts, published as a table rather than as a maximum.
SkyReels-V2 in the length column, with the columns that qualify it. Read from huggingface.co/Skywork on 2026-09-22.
ColumnWhat the pages state
Length, in the vendor's own words1457 frames for a 60s video
The detail published beside itFrames against seconds, in the vendor's own table
Resolution, from the same pages544 x 960 at 540P, 720 x 1280 at 720P
Hardware, from the same pagesAbout 14.7GB peak on the 1.3B at 540P

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.

1A table beats a ceiling

Most releases publish a maximum. This one publishes four points, which tells a reader not only how long a clip can be but what each intermediate target costs in frames.

The rate falls out of the table: roughly 24 frames per second at every row. Publishing the pairs rather than the rate is more robust, because it survives any rounding the code does.

2Sixty seconds, on which variant

The table is stated for the family, and the memory figures are stated for the 1.3B and the 14B at 540P. Whether 1457 frames is reachable on the smaller variant is not addressed.

That is the gap in an otherwise complete row. Length and memory are both documented and they are documented against different things.

3Long output is where the numbers matter most

A minute of video at 540P is a serious workload, and the memory figures published for this family, about 14.7GB and around 51.2GB, are for unstated clip lengths.

So the longest entry in the table is the one a reader can least afford to plan blind. The register keeps the table and the memory figures in separate columns because the vendor did.

4Sources

Lengths above are in the unit the vendor chose, from huggingface.co/Skywork on 2026-09-22, with no conversion applied. The full entry is at this family's page; frames against seconds is on length. Nearby: No ceiling on frames, Five seconds, stated.