Can the NVIDIA GeForce RTX 5090 run FLUX.2 [dev]?

Yes, it runs well (encoder in RAM)

Runs well (encoder in RAM). At Q4 GGUF it needs about 22.8 GB of 32.0 GB usable, with an estimated speed of 38 s.

Best precision: Q4 GGUF
Memory mode: Text encoder offloaded
Time per image: 38 s
Output: 1024×1024, 28 steps

Best app to run it on the NVIDIA GeForce RTX 5090

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 FLUX.2 [dev]

Recommended for the NVIDIA GeForce RTX 5090: q4_gguf. Every other precision has its own download link in the table below.

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.

Download the q4_gguf (Q4_K_S) file (opens in a new tab)

huggingface.co/unsloth/FLUX.2-dev-GGUF (opens in a new tab)

Original weights · Hugging Face

Full-precision files from Black Forest Labs, for fine-tuning, vLLM, Transformers, Diffusers or ComfyUI.

huggingface.co/black-forest-labs/FLUX.2-dev (opens in a new tab)

Free Hugging Face account needed: accept the license on the model page and the download starts right away.

Official repo · GitHub

Reference code, inference scripts and docs from Black Forest Labs. The weights themselves download from Hugging Face.

github.com/black-forest-labs/flux2 (opens in a new tab)

git clone https://github.com/black-forest-labs/flux2

Links checked 1 day ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 85Excellent quality (A+) · 85 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.: How capable the model itself is at Q4 GGUF, 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 wellencoder in RAM: How well it runs on the NVIDIA GeForce RTX 5090: 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.	38.5 / 45
Memory fitFull marks when everything sits in GPU memory; fewer when part spills to system RAM.	20.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.	7.7 / 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 score	81.2 / 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 5090

Quant	Memory needed	Available	Speed	Memory mode	Runs	Quality	Download
`FP16`	25.8 GB	32.0 GB	39 s	Sequential CPU offload	Runs wellCPU offload	92Excellent quality (A+) · 92 of 100: how capable the model is at FP16, whatever it runs on. Match score 75/100 (quality, fit, speed and memory use) sets the ranking.	Original weights (opens in a new tab)
`FP8`	14.6 GB	32.0 GB	35 s	Sequential CPU offload	Runs wellCPU offload	90Excellent quality (A+) · 90 of 100: how capable the model is at FP8, whatever it runs on. Match score 71/100 (quality, fit, speed and memory use) sets the ranking.	Original weights (opens in a new tab)
`Q8 GGUF`	15.4 GB	32.0 GB	45 s	Sequential CPU offload	SlowCPU offload	91Excellent quality (A+) · 91 of 100: how capable the model is at Q8 GGUF, whatever it runs on. Match score 71/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q4 GGUF`	22.8 GB	32.0 GB	38 s	Text encoder offloaded	Runs wellencoder in RAM	85Excellent quality (A+) · 85 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.	GGUF (opens in a new tab)

Other hardware that runs it

90Excellent quality (A+) · 90 of 100: how capable the model is at FP8, whatever it runs on. Match score 89/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA RTX PRO 6000 Blackwell FP8 · 24 s · Runs well
92Excellent quality (A+) · 92 of 100: how capable the model is at FP16, whatever it runs on. Match score 91/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA B200 FP16 · 22 s · Runs well
92Excellent quality (A+) · 92 of 100: how capable the model is at FP16, whatever it runs on. Match score 90/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA H200 141GB SXM FP16 · 25 s · Runs well
90Excellent quality (A+) · 90 of 100: how capable the model is at FP8, whatever it runs on. Match score 90/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA H100 80GB SXM FP8 · 23 s · Runs well
90Excellent quality (A+) · 90 of 100: how capable the model is at FP8, whatever it runs on. Match score 90/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA H800 80GB SXM FP8 · 23 s · Runs well
92Excellent quality (A+) · 92 of 100: how capable the model is at FP16, whatever it runs on. Match score 90/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA H200 NVL FP16 · 27 s · Runs well

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.