Step-Video T2V (30B) on Rockchip RK3588 / RK3588S (16 GB)

Can the Rockchip RK3588 / RK3588S (16 GB) run Step-Video T2V (30B)?

No, it doesn’t fit

No. Step-Video T2V (30B) needs about 25.0 GB even at FP8; the Rockchip RK3588 / RK3588S (16 GB) has 13.6 GB usable.

Download Step-Video T2V (30B)

Original weights · Hugging Face

Full-precision files from StepFun, for fine-tuning, vLLM, Transformers, Diffusers or ComfyUI.

huggingface.co/stepfun-ai/stepvideo-t2v (opens in a new tab)

No sign-in needed.

Official repo · GitHub

Reference code, inference scripts and docs from StepFun. The weights themselves download from Hugging Face.

github.com/stepfun-ai/Step-Video-T2V (opens in a new tab)

git clone https://github.com/stepfun-ai/Step-Video-T2V

Links checked 2 days ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 74Great quality (A) · 74 of 100: how capable the model is at FP8, whatever it runs on. Match score 10/100 (quality, fit, speed and memory use) sets the ranking.: How capable the model itself is at FP8, from its editorial quality tier scaled by the quantization or precision. It’s the same on any hardware that runs this variant. Scale: A+ 85+ · A 70+ · B 55+ · C 40+ · D under 40.
Runs Won't run: How well it runs on the Rockchip RK3588 / RK3588S (16 GB): speed, capped by how well it fits in memory. Runs great: 30+ tokens/s (or near the image, video or decision speed target) · Runs well: 10+ tokens/s · Slow: 3+ tokens/s · Very slow: under 3 · Won’t run: doesn’t fit even with offload. A tight fit or RAM offload caps it at Runs well; heavy offload caps it at Slow.

Match score

To order lists, each result also gets a match score out of 100 from four parts. It favors the most capable model that still runs well.

Model qualityEditorial quality tier of the model, scaled by the quantization or precision used.	10.1 / 45
Memory fitFull marks when the model fits in the share of unified memory the GPU can use; fewer when it goes past that limit.	0.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.	0.0 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.	0.0 / 15
Match score	10.1 / 100

The match score orders results; it is not shown as a grade. Quality and Runs are the two ratings in the tables.

It doesn’t fit, so only a reduced share of the quality points counts and fit, speed and memory use score zero.

Every precision on the Rockchip RK3588 / RK3588S (16 GB)

Quant	Memory needed	Available	Speed	Memory mode	Runs	Quality	Download
`FP16`	35.5 GB	13.6 GB	—	—	Won't run	76Great quality (A) · 76 of 100: how capable the model is at FP16, whatever it runs on. Match score 10/100 (quality, fit, speed and memory use) sets the ranking.	Original weights (opens in a new tab)
`FP8`	25.0 GB	13.6 GB	—	—	Won't run	74Great quality (A) · 74 of 100: how capable the model is at FP8, whatever it runs on. Match score 10/100 (quality, fit, speed and memory use) sets the ranking.	Original weights (opens in a new tab)

Hardware that can run it

76Great quality (A) · 76 of 100: how capable the model is at FP16, whatever it runs on. Match score 78/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA RTX PRO 6000 Blackwell FP16 · 37.9 min · Slow
76Great quality (A) · 76 of 100: how capable the model is at FP16, whatever it runs on. Match score 78/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GH200 Grace Hopper (96 GB GPU) FP16 · 36.0 min · Slow
76Great quality (A) · 76 of 100: how capable the model is at FP16, whatever it runs on. Match score 78/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA H100 NVL FP16 · 39.0 min · Slow
76Great quality (A) · 76 of 100: how capable the model is at FP16, whatever it runs on. Match score 78/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA RTX PRO 6000 Blackwell Server Edition FP16 · 39.0 min · Slow
74Great quality (A) · 74 of 100: how capable the model is at FP8, whatever it runs on. Match score 76/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA H100 80GB SXM FP8 · 32.4 min · Slow
74Great quality (A) · 74 of 100: how capable the model is at FP8, whatever it runs on. Match score 76/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA H800 80GB SXM FP8 · 32.4 min · Slow

Models that do run on the Rockchip RK3588 / RK3588S (16 GB)

49Fair quality (C) · 49 of 100: how capable the model is at FP8, whatever it runs on. Match score 65/100 (quality, fit, speed and memory use) sets the ranking. LTX-Video 2B FP8 · 55.0 min
83Great quality (A) · 83 of 100: how capable the model is at FP8, whatever it runs on. Match score 65/100 (quality, fit, speed and memory use) sets the ranking. Bernini-R A14B (video generation + editing) FP8 · 34.3 h
53Fair quality (C) · 53 of 100: how capable the model is at FP8, whatever it runs on. Match score 63/100 (quality, fit, speed and memory use) sets the ranking. Wan 2.1 T2V 1.3B FP8 · 8.8 h
44Fair quality (C) · 44 of 100: how capable the model is at FP8, whatever it runs on. Match score 62/100 (quality, fit, speed and memory use) sets the ranking. CogVideoX 2B FP8 · 2.2 h
76Great quality (A) · 76 of 100: how capable the model is at FP16, whatever it runs on. Match score 61/100 (quality, fit, speed and memory use) sets the ranking. HY-OmniWeaving (8.3B, unified video) FP16 · 28.1 h

Quick answers

How much memory does Step-Video T2V (30B) need on the Rockchip RK3588 / RK3588S 16GB?

Even at FP8 it needs about 25.0 GB; the Rockchip RK3588 / RK3588S 16GB has 13.6 GB usable.

What can the Rockchip RK3588 / RK3588S 16GB run instead?

LTX-Video 2B, Bernini-R A14B (video generation + editing) and Wan 2.1 T2V 1.3B run best on it; the page lists more, each with its speed.

What hardware can run Step-Video T2V (30B)?

NVIDIA RTX PRO 6000 Blackwell 96GB, NVIDIA GH200 Grace Hopper (96GB GPU) and NVIDIA H100 NVL 94GB run it; the page lists more, each with its speed.

Estimates come from published hardware specs and our open formulas, not from running the model on your machine. Real speed varies with runtime, drivers and settings. Numbers marked “Measured” come from a linked benchmark.