MiniMax H3 (33B, video + audio) on AMD Ryzen AI Max+ 395 (128 GB)
Can the AMD Ryzen AI Max+ 395 (128 GB) run MiniMax H3 (33B, video + audio)?
Yes, but slowly
Slow. At FP8 it needs about 66.8 GB of 96.0 GB usable, with an estimated speed of 30.0 min.
- Best precision
FP8- Memory mode
- Everything on GPU
- Time per clip
- 30.0 min
- Output
- 1344×768, 124 frames, 50 steps
Best app to run it on the AMD Ryzen AI Max+ 395 (128 GB)
On Windows
- Runs this model with built-in or popular custom nodes; GGUF files load with ComfyUI-GGUF.
On Linux
- Runs this model with built-in or popular custom nodes; GGUF files load with ComfyUI-GGUF.
Download MiniMax H3 (33B, video + audio)
Quantized files · GGUF for ComfyUI
Smaller GGUF versions for ComfyUI (with the ComfyUI-GGUF node). No sign-in needed; the model’s license still applies.
Original weights · Hugging Face
Full-precision files from MiniMax, for fine-tuning, vLLM, Transformers, Diffusers or ComfyUI.
Official repo · GitHub
Reference code, inference scripts and docs from MiniMax. The weights themselves download from Hugging Face.
github.com/MiniMax-AI/MiniMax-H3 (opens in a new tab)
git clone https://github.com/MiniMax-AI/MiniMax-H3How it’s rated
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 quality | 39.7 / 45 | |
|---|---|---|
| Memory fit | 25.0 / 25 | |
| Speed | 4.7 / 15 | |
| Memory use | 15.0 / 15 | |
| Match score | 84.4 / 100 |
Every precision on the AMD Ryzen AI Max+ 395 (128 GB)
| Quant | Memory needed | Available | Speed | Memory mode | Runs | Quality | Download |
|---|---|---|---|---|---|---|---|
FP16 | 61.1 GB | 96.0 GB | 35.0 min | Text encoder offloaded | Slowencoder unloaded after use | 90Excellent quality (A+) · 90 of 100: how capable the model is at FP16, whatever it runs on. Match score 79/100 (quality, fit, speed and memory use) sets the ranking. | Original weights (opens in a new tab) |
FP8 | 66.8 GB | 96.0 GB | 30.0 min | Everything on GPU | Slow | 88Excellent quality (A+) · 88 of 100: how capable the model is at FP8, whatever it runs on. Match score 84/100 (quality, fit, speed and memory use) sets the ranking. | Original weights (opens in a new tab) |
Q8 GGUF | 68.2 GB | 96.0 GB | 38.3 min | Everything on GPU | Slow | 89Excellent quality (A+) · 89 of 100: how capable the model is at Q8 GGUF, whatever it runs on. Match score 84/100 (quality, fit, speed and memory use) sets the ranking. | GGUF (opens in a new tab) |
Q4 GGUF | 58.7 GB | 96.0 GB | 40.0 min | Everything on GPU | Slow | 83Great quality (A) · 83 of 100: how capable the model is at Q4 GGUF, whatever it runs on. Match score 80/100 (quality, fit, speed and memory use) sets the ranking. | GGUF (opens in a new tab) |
Other hardware that runs it
-
88Excellent quality (A+) · 88 of 100: how capable the model is at FP8, whatever it runs on. Match score 87/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA RTX PRO 6000 Blackwell
-
90Excellent quality (A+) · 90 of 100: how capable the model is at FP16, whatever it runs on. Match score 87/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA B200
-
88Excellent quality (A+) · 88 of 100: how capable the model is at FP8, whatever it runs on. Match score 87/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA GH200 Grace Hopper (96 GB GPU)
-
88Excellent quality (A+) · 88 of 100: how capable the model is at FP8, whatever it runs on. Match score 87/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA H100 80GB SXM
-
88Excellent quality (A+) · 88 of 100: how capable the model is at FP8, whatever it runs on. Match score 87/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA H800 80GB SXM
-
88Excellent quality (A+) · 88 of 100: how capable the model is at FP8, whatever it runs on. Match score 87/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA H100 NVL
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.