FireRed-Image-Edit 1.1 on NVIDIA H100 NVL
Can the NVIDIA H100 NVL run FireRed-Image-Edit 1.1?
Yes, but slowly
Slow. At FP16 it needs about 61.2 GB of 94.0 GB usable, with an estimated speed of 60 s.
- Best precision
FP16- Memory mode
- Everything on GPU
- Time per image
- 60 s
- Output
- 1024×1024, 40 steps
Best app to run it on the NVIDIA H100 NVL
On Linux
- Runs this model with built-in or popular custom nodes; GGUF files load with ComfyUI-GGUF.
On Windows
- Runs this model with built-in or popular custom nodes; GGUF files load with ComfyUI-GGUF.
Download FireRed-Image-Edit 1.1
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.
huggingface.co/FireRedTeam/FireRed-Image-Edit-1.1-ComfyUI (opens in a new tab)
Original weights · Hugging Face
Full-precision files from rednote (FireRed Team), for fine-tuning, vLLM, Transformers, Diffusers or ComfyUI.
huggingface.co/FireRedTeam/FireRed-Image-Edit-1.1 (opens in a new tab)
Official repo · GitHub
Reference code, inference scripts and docs from rednote (FireRed Team). The weights themselves download from Hugging Face.
github.com/FireRedTeam/FireRed-Image-Edit (opens in a new tab)
git clone https://github.com/FireRedTeam/FireRed-Image-EditHow 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.2 / 45 | |
|---|---|---|
| Memory fit | 25.0 / 25 | |
| Speed | 6.1 / 15 | |
| Memory use | 15.0 / 15 | |
| Match score | 85.3 / 100 |
Every precision on the NVIDIA H100 NVL
| Quant | Memory needed | Available | Speed | Memory mode | Runs | Quality | Download |
|---|---|---|---|---|---|---|---|
FP16 | 61.2 GB | 94.0 GB | 60 s | Everything on GPU | Slow | 87Excellent quality (A+) · 87 of 100: how capable the model is at FP16, whatever it runs on. Match score 85/100 (quality, fit, speed and memory use) sets the ranking. | Original weights (opens in a new tab) |
FP8 | 32.5 GB | 94.0 GB | 54 s | Everything on GPU | Slow | 85Excellent quality (A+) · 85 of 100: how capable the model is at FP8, whatever it runs on. Match score 77/100 (quality, fit, speed and memory use) sets the ranking. | Original weights (opens in a new tab) |
Q8 GGUF | 33.9 GB | 94.0 GB | 70 s | Everything on GPU | Slow | 86Excellent quality (A+) · 86 of 100: how capable the model is at Q8 GGUF, whatever it runs on. Match score 77/100 (quality, fit, speed and memory use) sets the ranking. | GGUF (opens in a new tab) |
Q4 GGUF | 24.3 GB | 94.0 GB | 73 s | Everything on GPU | Slow | 80Great quality (A) · 80 of 100: how capable the model is at Q4 GGUF, whatever it runs on. Match score 72/100 (quality, fit, speed and memory use) sets the ranking. | GGUF (opens in a new tab) |
Other hardware that runs it
-
87Excellent quality (A+) · 87 of 100: how capable the model is at FP16, whatever it runs on. Match score 85/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA RTX PRO 6000 Blackwell
-
80Great quality (A) · 80 of 100: how capable the model is at Q4 GGUF, whatever it runs on. Match score 81/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA GeForce RTX 5090
-
80Great quality (A) · 80 of 100: how capable the model is at Q4 GGUF, whatever it runs on. Match score 76/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA GeForce RTX 4090
-
80Great quality (A) · 80 of 100: how capable the model is at Q4 GGUF, whatever it runs on. Match score 75/100 (quality, fit, speed and memory use) sets the ranking.
AMD Radeon RX 7900 XTX
-
85Excellent quality (A+) · 85 of 100: how capable the model is at FP8, whatever it runs on. Match score 69/100 (quality, fit, speed and memory use) sets the ranking.
AMD Radeon RX 9070 XT
-
85Excellent quality (A+) · 85 of 100: how capable the model is at FP8, whatever it runs on. Match score 69/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA GeForce RTX 5080
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.