Stable Diffusion 3.5 Large Turbo on Apple M5 Pro (48 GB)

Can the Apple M5 Pro (48 GB) run Stable Diffusion 3.5 Large Turbo?

Yes, it runs well

Runs well. At FP8 it needs about 16.3 GB of 36.0 GB usable and takes about 14 s per image.

Best precision: FP8
Memory mode: Everything on GPU
Time per image: 14 s
Output: 1024×1024, 4 steps

Best app to run it on the Apple M5 Pro (48 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 Stable Diffusion 3.5 Large Turbo 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 Stable Diffusion 3.5 Large Turbo

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/stable-diffusion-3.5-large-turbo-gguf (opens in a new tab)

Original weights · Hugging Face

Full-precision files from Stability AI, for fine-tuning, vLLM, Transformers, Diffusers or ComfyUI.

huggingface.co/stabilityai/stable-diffusion-3.5-large-turbo (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 Stability AI. The weights themselves download from Hugging Face.

github.com/Stability-AI/sd3.5 (opens in a new tab)

git clone https://github.com/Stability-AI/sd3.5

Links checked 3 days ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 60Good quality (B) · 60 of 100: how capable the model is at FP8, whatever it runs on. Match score 75/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 Runs well: How well it runs on the Apple M5 Pro (48 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.	27.3 / 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.	25.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.	12.7 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.	10.4 / 15
Match score	75.5 / 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 (48 GB)

Quant	Memory needed	Available	Speed	Memory mode	Runs	Quality	Download
`FP16`	30.0 GB	36.0 GB	16 s	Everything on GPU	Runs well	62Good quality (B) · 62 of 100: how capable the model is at FP16, whatever it runs on. Match score 79/100 (quality, fit, speed and memory use) sets the ranking.	Original weights (opens in a new tab)
`FP8`	16.3 GB	36.0 GB	14 s	Everything on GPU	Runs well	60Good quality (B) · 60 of 100: how capable the model is at FP8, whatever it runs on. Match score 75/100 (quality, fit, speed and memory use) sets the ranking.	Original weights (opens in a new tab)
`Q8 GGUF`	16.8 GB	36.0 GB	18 s	Everything on GPU	Runs well	61Good quality (B) · 61 of 100: how capable the model is at Q8 GGUF, whatever it runs on. Match score 74/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q4 GGUF`	13.0 GB	36.0 GB	19 s	Everything on GPU	Runs well	57Good quality (B) · 57 of 100: how capable the model is at Q4 GGUF, whatever it runs on. Match score 70/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)

Other hardware that runs it

61Good quality (B) · 61 of 100: how capable the model is at Q8 GGUF, whatever it runs on. Match score 82/100 (quality, fit, speed and memory use) sets the ranking. AMD Radeon RX 7900 XTX Q8 GGUF · 2.0 s · Runs great
61Good quality (B) · 61 of 100: how capable the model is at Q8 GGUF, whatever it runs on. Match score 82/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 3090 Q8 GGUF · 3.5 s · Runs great
61Good quality (B) · 61 of 100: how capable the model is at Q8 GGUF, whatever it runs on. Match score 82/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4090 Q8 GGUF · 1.8 s · Runs great
62Good quality (B) · 62 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. Apple M4 Max (64 GB) FP16 · 9.4 s · Runs great
57Good quality (B) · 57 of 100: how capable the model is at Q4 GGUF, whatever it runs on. Match score 80/100 (quality, fit, speed and memory use) sets the ranking. AMD Radeon RX 9070 XT Q4 GGUF · 2.5 s · Runs great
57Good quality (B) · 57 of 100: how capable the model is at Q4 GGUF, whatever it runs on. Match score 80/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4060 Ti 16GB Q4 GGUF · 5.2 s · Runs great

Quick answers

How much memory does Stable Diffusion 3.5 Large Turbo need on the M5 Pro 48GB?

At FP8 it needs about 16.3 GB. The M5 Pro 48GB has 36.0 GB usable.

How long does Stable Diffusion 3.5 Large Turbo take on the M5 Pro 48GB?

About 14 s 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.