FLUX.1 [dev] on Intel Core Ultra 5 225H NAS (32 GB)

Can the Intel Core Ultra 5 225H NAS (32 GB) run FLUX.1 [dev]?

Yes, but slowly (encoder unloaded after use)

Slow (encoder unloaded after use). At FP8 it needs about 14.7 GB of 18.2 GB usable and takes about 2.0 min per image.

Best precision: FP8
Memory mode: Text encoder offloaded
Time per image: 2.0 min
Output: 1024×1024, 28 steps

Download FLUX.1 [dev]

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/city96/FLUX.1-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.1-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 3 days ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 78Great quality (A) · 78 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.: 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 Slowencoder unloaded after use: How well it runs on the Intel Core Ultra 5 225H NAS (32 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.	35.3 / 45
Memory fitFull marks when the model fits in the share of the NAS’s memory that models can use (the rest stays with the NAS system and its storage services); fewer when it goes past that limit.	20.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.	4.4 / 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	74.7 / 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 Intel Core Ultra 5 225H NAS (32 GB)

Quant	Memory needed	Available	Speed	Memory mode	Runs	Quality	Download
`FP16`	11.0 GB	18.2 GB	2.7 min	Sequential CPU offload	Very slowCPU offload	80Great quality (A) · 80 of 100: how capable the model is at FP16, whatever it runs on. Match score 65/100 (quality, fit, speed and memory use) sets the ranking.	Original weights (opens in a new tab)
`FP8`	14.7 GB	18.2 GB	2.0 min	Text encoder offloaded	Slowencoder unloaded after use	78Great quality (A) · 78 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.	Original weights (opens in a new tab)
`Q8 GGUF`	15.5 GB	18.2 GB	2.5 min	Text encoder offloaded	Very slowtight fit · encoder unloaded after use	79Great quality (A) · 79 of 100: how capable the model is at Q8 GGUF, whatever it runs on. Match score 72/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q4 GGUF`	14.8 GB	18.2 GB	2.5 min	Everything on GPU	Very slow	74Great quality (A) · 74 of 100: how capable the model is at Q4 GGUF, whatever it runs on. Match score 77/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`NF4`	14.4 GB	18.2 GB	2.3 min	Everything on GPU	Very slow	74Great quality (A) · 74 of 100: how capable the model is at NF4, whatever it runs on. Match score 77/100 (quality, fit, speed and memory use) sets the ranking.	Original weights (opens in a new tab)

Other hardware that runs it

78Great quality (A) · 78 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 GeForce RTX 4090 FP8 · 11 s · Runs great
78Great quality (A) · 78 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 GeForce RTX 5090 FP8 · 9.0 s · Runs great
78Great quality (A) · 78 of 100: how capable the model is at FP8, whatever it runs on. Match score 88/100 (quality, fit, speed and memory use) sets the ranking. AMD Radeon RX 7900 XTX FP8 · 12 s · Runs great
78Great quality (A) · 78 of 100: how capable the model is at FP8, whatever it runs on. Match score 85/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 3090 FP8 · 20 s · Runs well
80Great quality (A) · 80 of 100: how capable the model is at FP16, whatever it runs on. Match score 84/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA RTX PRO 6000 Blackwell FP16 · 8.8 s · Runs great
74Great quality (A) · 74 of 100: how capable the model is at NF4, whatever it runs on. Match score 82/100 (quality, fit, speed and memory use) sets the ranking. AMD Radeon RX 9070 XT NF4 · 18 s · Runs well (tight fit)

Quick answers

How much memory does FLUX.1 [dev] need on the Intel Core Ultra 5 225H NAS 32GB?

At FP8 it needs about 14.7 GB. The Intel Core Ultra 5 225H NAS 32GB has 18.2 GB usable.

How long does FLUX.1 [dev] take on the Intel Core Ultra 5 225H NAS 32GB?

About 2.0 min per image 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.