FLUX.1 Fill [dev] on NVIDIA Jetson Orin Nano Super (8 GB)

Can the NVIDIA Jetson Orin Nano Super (8 GB) run FLUX.1 Fill [dev]?

No, it doesn’t fit

No. FLUX.1 Fill [dev] needs about 6.8 GB even at FP8; the NVIDIA Jetson Orin Nano Super (8 GB) has 6.0 GB usable.

Download FLUX.1 Fill [dev]

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.1-Fill-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/flux (opens in a new tab)

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

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

How it’s rated

Quality 74Great quality (A) · 74 of 100: how capable the model is at FP8, whatever it runs on. Match score 10/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 Won't run: How well it runs on the NVIDIA Jetson Orin Nano Super (8 GB): 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.	10.1 / 45
Memory fitFull marks when the model fits in the share of unified memory the GPU can use; fewer when it goes past that limit.	0.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.	0.0 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.	0.0 / 15
Match score	10.1 / 100

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

It doesn’t fit, so only a reduced share of the quality points counts and fit, speed and memory use score zero.

Every precision on the NVIDIA Jetson Orin Nano Super (8 GB)

Quant	Memory needed	Available	Speed	Memory mode	Runs	Quality	Download
`FP16`	11.0 GB	6.0 GB	—	—	Won't run	76Great quality (A) · 76 of 100: how capable the model is at FP16, whatever it runs on. Match score 10/100 (quality, fit, speed and memory use) sets the ranking.	Original weights (opens in a new tab)
`FP8`	6.8 GB	6.0 GB	—	—	Won't run	74Great quality (A) · 74 of 100: how capable the model is at FP8, whatever it runs on. Match score 10/100 (quality, fit, speed and memory use) sets the ranking.	Original weights (opens in a new tab)

Hardware that can run it

74Great quality (A) · 74 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 GeForce RTX 4090 FP8 · 11 s · Runs great
74Great quality (A) · 74 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 GeForce RTX 5090 FP8 · 9.4 s · Runs great
74Great quality (A) · 74 of 100: how capable the model is at FP8, whatever it runs on. Match score 86/100 (quality, fit, speed and memory use) sets the ranking. AMD Radeon RX 7900 XTX FP8 · 13 s · Runs great
74Great quality (A) · 74 of 100: how capable the model is at FP8, whatever it runs on. Match score 83/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 3090 FP8 · 21 s · Runs well
76Great quality (A) · 76 of 100: how capable the model is at FP16, whatever it runs on. Match score 82/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA RTX PRO 6000 Blackwell FP16 · 9.2 s · Runs great
74Great quality (A) · 74 of 100: how capable the model is at FP8, whatever it runs on. Match score 78/100 (quality, fit, speed and memory use) sets the ranking. AMD Radeon RX 9070 XT FP8 · 16 s · Runs well (tight fit · encoder in RAM)

Models that do run on the NVIDIA Jetson Orin Nano Super (8 GB)

72Great quality (A) · 72 of 100: how capable the model is at Q4 GGUF, whatever it runs on. Match score 78/100 (quality, fit, speed and memory use) sets the ranking. FLUX.2 [klein] 4B Q4 GGUF · 20 s
52Fair quality (C) · 52 of 100: how capable the model is at FP8, whatever it runs on. Match score 76/100 (quality, fit, speed and memory use) sets the ranking. SDXL-Lightning (4-step) FP8 · 9.9 s
84Great quality (A) · 84 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. FLUX 3 Image Klein Q4 GGUF · 1.9 min
56Good quality (B) · 56 of 100: how capable the model is at FP8, whatever it runs on. Match score 74/100 (quality, fit, speed and memory use) sets the ranking. DreamShaper XL v2 Turbo FP8 · 18 s
39Basic quality (D) · 39 of 100: how capable the model is at FP8, whatever it runs on. Match score 72/100 (quality, fit, speed and memory use) sets the ranking. SDXL Turbo FP8 · 2.1 s

Quick answers

How much memory does FLUX.1 Fill [dev] need on the NVIDIA Jetson Orin Nano Super 8GB?

Even at FP8 it needs about 6.8 GB; the NVIDIA Jetson Orin Nano Super 8GB has 6.0 GB usable.

What can the NVIDIA Jetson Orin Nano Super 8GB run instead?

FLUX.2 [klein] 4B, SDXL-Lightning (4-step) and FLUX 3 Image Klein run best on it; the page lists more, each with its speed.

What hardware can run FLUX.1 Fill [dev]?

RTX 4090 24GB, RTX 5090 32GB and RX 7900 XTX 24GB run it; the page lists more, each with its 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.