FLUX.1 Fill [dev] on Apple M5 Pro (24 GB)

Can the Apple M5 Pro (24 GB) run FLUX.1 Fill [dev]?

Yes, but slowly (tight fit · encoder unloaded after use)

Slow (tight fit · encoder unloaded after use). At FP8 it needs about 14.7 GB of 16.1 GB usable and takes about 1.9 min per image.

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

Best app to run it on the Apple M5 Pro (24 GB)

On macOS

Draw Things

Desktop app · runs on Draw Things (Metal FlashAttention)

Native Mac app with its own fast Metal engine and quantized downloads.

Open FLUX.1 Fill [dev] in Draw Things

ComfyUI Runs this model with built-in or popular custom nodes; GGUF files load with ComfyUI-GGUF.
Invoke

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.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 7 days 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 70/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 Slowtight fit · encoder unloaded after use: How well it runs on the Apple M5 Pro (24 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.	33.5 / 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.	18.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	70.9 / 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 Apple M5 Pro (24 GB)

Quant	Memory needed	Available	Speed	Memory mode	Runs	Quality	Download
`FP16`	11.0 GB	16.1 GB	2.6 min	Sequential CPU offload	Very slowCPU offload	76Great quality (A) · 76 of 100: how capable the model is at FP16, whatever it runs on. Match score 64/100 (quality, fit, speed and memory use) sets the ranking.	Original weights (opens in a new tab)
`FP8`	14.7 GB	16.1 GB	1.9 min	Text encoder offloaded	Slowtight fit · encoder unloaded after use	74Great quality (A) · 74 of 100: how capable the model is at FP8, whatever it runs on. Match score 70/100 (quality, fit, speed and memory use) sets the ranking.	Original weights (opens in a new tab)

Other hardware that runs 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)

Quick answers

How much memory does FLUX.1 Fill [dev] need on the M5 Pro 24GB?

At FP8 it needs about 14.7 GB. The M5 Pro 24GB has 16.1 GB usable.

How long does FLUX.1 Fill [dev] take on the M5 Pro 24GB?

About 1.9 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.