whatmodel.sh / video / HunyuanVideo

HunyuanVideo is an open-weights video model from Tencent, released December 2024. Its published size is 13B parameters. Licence: tencent-hunyuan-community.

39.0±2.5#71 of 93 video modelsfrom 6 benchmark results across 4 sources

$ how it compares

The video models ranked either side of HunyuanVideo, out of 139 with a score, then more from Tencent.

#modelscorewhereRAMreleased
103UniVideo Kuaishou (Kling AI)39±3comparison only2026-01
104T2V-Turbo (MS) UC Santa Barbara39±6comparison only2024-05
105HunyuanVideo Tencent39±3api price unknown +local~28GB2024-12
106Pandora (world model) Maitrix.org (MBZUAI / UC San Diego)39±7comparison only2024-05
107T2V-Turbo-v2 UC Santa Barbara38±5api price unknown +local~9.4GB2024-10
more from Tencent
55HunyuanVideo 1.5 (I2V) Tencent53±2api $0.075/sec +local~66GB2025-11
58HY-OmniWeaving Tencent52±4comparison only2026-03
59HunyuanVideo 1.5 Tencent52±2api $0.075/sec +local~20GB2025-11

see all video models · find the ones that fit your machine

$ what it's good at

text to video▆▄▃▄▆▅█▃▂▂▂▄ #49 of 68 · 97% of its score · 6 tests

Trails LTX-2.3, T2V-Turbo-v2 here, though they rank lower overall.

testresultvs the others in its rundifficultycountswhy
VideoPhy-2 (human, joint SA & PC)17.2% ✎▄···▄·▄·█··▄ beats 1/5hard · avg 33%▇▇▇▇▇▇▇▇▇▇ 26%typical
SkyReels-Bench T2V (human rating)56.4% ✎▄····▄···█·▄ beats 1/4medium · avg 66%▇▇▇▇▇▇▇ 18%at its level
VideoPhy (auto-evaluator average)35.0% ✎▅·▃▅··▃█···▃ beats 4/9medium · avg 56%▇▇▇▇▇▇ 15%at its level
VideoVerse overall (Gemini 2.5 Pro judge)898.07 / 1608 ✎█·▄··▄·····█ beats 1/5easy · avg 1103.17 / 1608▇▇▇▇▇▇ 15%at its level
VBench (T2V total)82.7% ✎█···▄▄▄····▄ beats 2/5very easy · avg 90%▇▇▇▇▇ 13%small run
VBench T2V total (long-prompt version, SkyReels-V2 runs)82.7% ✎█···█···█··█ beats 2/3very easy · avg 88%▇▇▇▇ 11%typical

$ where to run it

Through an API

api · fal · price unknown · fal.ai ↗

Other ways to run it

version

  1. Run it as published · needs ~31.7 GB, NVIDIA only · from github.com/Tencent-Hunyuan
    python3 sample_video.py --video-size 544 960 --video-length 129 --infer-steps 50 --prompt "A cat walks on the grass, realistic style." --flow-reverse --use-cpu-offload --save-path ./results

Official weights and documentation: huggingface.co/tencent ↗

$ how the score was worked out · VideoPhy / VideoPhy-2 officia… 41%, SkyReels-V2: Infinite-length… 29%, VideoVerse: Does Your T2V Gen… 15% and 1 more

Each result implies a score on its own, after adjusting for how hard its test is and who ran it. The score is their weighted average, with a small pull toward the middle for thinly tested models. Each test's weight is its counts column above; here it's added up by who ran the tests. How it works

sourceresultsshare of the scorelicence
VideoPhy / VideoPhy-2 official repository leaderboards2▇▇▇▇▇▇▇▇▇▇▇▇ 41%MIT
SkyReels-V2: Infinite-length Film Generative Model2▇▇▇▇▇▇▇▇▇ 29%CC-BY-4.0
VideoVerse: Does Your T2V Generator Have World Model Capability to Synthesize Videos?1▇▇▇▇ 15%CC-BY-4.0
Training-Free Efficient Video Generation via Dynamic Token Carving1▇▇▇▇ 13%CC-BY-SA-4.0
prior · pull toward the middle▇ 3%
weighted average= 39.0
$ published speed measurements · 1

Reference results for the hardware, engine and settings below. They aren't verified speeds of the downloads above or predictions for your machine.

NVIDIA L20 (48GB; single GPU)bf16 transformer, fp16 pipeline (per the guide's code); VAE tiling enabled3675.71 s/videodiffusers HunyuanVideoPipeline (ParaAttention guide baseline; versions not stated) · tencent/HunyuanVideo (revision refs/pr/18, diffusers format); 1280x720; 129 frames; 30 inference steps; 1 GPU; baseline without FBCache/context parallelism except the memory optimisation needed to avoid OOM (line 16: VAE tiling in the code)

Baseline row; the prose (line 18) states 129 frames at 720p in 30 steps in 3675.71 s. Contributed to the diffusers docs by the ParaAttention author (PR #10544, Jan 2025); datacenter GPU, not a consumer card.

source ↗

$ improve this page

Use a short GitHub form or edit the data through a pull request. Every number needs a source; here's which ones we can use.

data updated · sources and licences · json