on

Can the NVIDIA GeForce RTX 5060 run CogVideoX 5B I2V?

53Fair quality (C) · 53 of 100: how capable the model is at FP8, whatever it runs on. Match score 59/100 (quality, fit, speed and memory use) sets the ranking.

Yes, it runs well (CPU offload)

Runs well (CPU offload). At FP8 it needs about 6.1 GB of 8.0 GB usable and takes about 10.5 min per clip.

Best precision
FP8
Memory mode
Sequential CPU offload
Time per clip
10.5 min
Output
720×480, 49 frames, 50 steps

Best app to run it on the NVIDIA GeForce RTX 5060

On Windows

ComfyUI

Desktop app · runs on PyTorch (ComfyUI), GGUF via ComfyUI-GGUF

  • Runs this model with built-in or popular custom nodes; GGUF files load with ComfyUI-GGUF.

Get ComfyUI

On Linux

ComfyUI

Desktop app · runs on PyTorch (ComfyUI), GGUF via ComfyUI-GGUF

  • Runs this model with built-in or popular custom nodes; GGUF files load with ComfyUI-GGUF.

Get ComfyUI

How we choose: the files published for this model, your operating system and GPU, whether it fits fully in memory, and published speed tests (MLX vs llama.cpp on Apple silicon, vLLM vs llama.cpp vs Ollama on NVIDIA). Details.

Download CogVideoX 5B I2V

Original weights · Hugging Face

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

huggingface.co/zai-org/CogVideoX-5b-I2V (opens in a new tab)

No sign-in needed.

Official repo · GitHub

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

github.com/zai-org/CogVideo (opens in a new tab)

git clone https://github.com/zai-org/CogVideo

How it’s rated

Quality 53Fair quality (C) · 53 of 100: how capable the model is at FP8, whatever it runs on. Match score 59/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 Runs wellCPU offload
How well it runs on the NVIDIA GeForce RTX 5060: 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.24.3 / 45
Memory fitFull marks when everything sits in GPU memory; fewer when part spills to system RAM.12.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.8.0 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.15.0 / 15
Match score59.3 / 100

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

Every precision on the NVIDIA GeForce RTX 5060

Quant Memory needed Available Speed Memory mode Runs Quality Download
FP16 8.1 GB 8.0 GB — — Won't run 55Good quality (B) · 55 of 100: how capable the model is at FP16, whatever it runs on. Match score 7/100 (quality, fit, speed and memory use) sets the ranking. Original weights (opens in a new tab)
FP8 6.1 GB 8.0 GB 10.5 min Sequential CPU offload Runs wellCPU offload 53Fair quality (C) · 53 of 100: how capable the model is at FP8, whatever it runs on. Match score 59/100 (quality, fit, speed and memory use) sets the ranking. Original weights (opens in a new tab)

Other hardware that runs it

Quick answers

How much memory does CogVideoX 5B I2V need on the RTX 5060 8GB?

At FP8 it needs about 6.1 GB. The RTX 5060 8GB has 8.0 GB usable.

How long does CogVideoX 5B I2V take on the RTX 5060 8GB?

About 10.5 min per clip at FP8 and default settings, an estimate scaled from a reference timing by this hardware’s compute 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.

Was this page helpful?