Can the Apple M6 (16 GB) run Z-Image Turbo?

Yes, it runs well (encoder unloaded after use)

Runs well (encoder unloaded after use). At FP8 it needs about 8.5 GB of 10.7 GB usable and takes about 33 s per image.

Best precision: FP8
Memory mode: Text encoder offloaded
Time per image: 33 s
Output: 1024×1024, 8 steps

Best app to run it on the Apple M6 (16 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 Z-Image Turbo in Draw Things

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

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 Z-Image 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/unsloth/Z-Image-Turbo-GGUF (opens in a new tab)

Original weights · Hugging Face

Full-precision files from Alibaba (Tongyi), for fine-tuning, vLLM, Transformers, Diffusers or ComfyUI.

huggingface.co/Tongyi-MAI/Z-Image-Turbo (opens in a new tab)

No sign-in needed.

Official repo · GitHub

Reference code, inference scripts and docs from Alibaba (Tongyi). The weights themselves download from Hugging Face.

github.com/Tongyi-MAI/Z-Image (opens in a new tab)

git clone https://github.com/Tongyi-MAI/Z-Image

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

How it’s rated

Quality 82Great quality (A) · 82 of 100: how capable the model is at FP8, whatever it runs on. Match score 80/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 wellencoder unloaded after use: How well it runs on the Apple M6 (16 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.	37.0 / 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.	20.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.	8.2 / 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	80.3 / 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 M6 (16 GB)

Quant	Memory needed	Available	Speed	Memory mode	Runs	Quality	Download
`FP16`	6.5 GB	10.7 GB	46 s	Sequential CPU offload	SlowCPU offload	84Great quality (A) · 84 of 100: how capable the model is at FP16, whatever it runs on. Match score 70/100 (quality, fit, speed and memory use) sets the ranking.	Original weights (opens in a new tab)
`FP8`	8.5 GB	10.7 GB	33 s	Text encoder offloaded	Runs wellencoder unloaded after use	82Great quality (A) · 82 of 100: how capable the model is at FP8, whatever it runs on. Match score 80/100 (quality, fit, speed and memory use) sets the ranking.	Original weights (opens in a new tab)
`Q8 GGUF`	9.0 GB	10.7 GB	43 s	Text encoder offloaded	Slowencoder unloaded after use	83Great quality (A) · 83 of 100: how capable the model is at Q8 GGUF, whatever it runs on. Match score 79/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q4 GGUF`	10.1 GB	10.7 GB	42 s	Everything on GPU	Slowtight fit	78Great quality (A) · 78 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.	GGUF (opens in a new tab)

Other hardware that runs it

84Great quality (A) · 84 of 100: how capable the model is at FP16, whatever it runs on. Match score 92/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 5090 FP16 · 2.1 s · Runs great
83Great quality (A) · 83 of 100: how capable the model is at Q8 GGUF, whatever it runs on. Match score 92/100 (quality, fit, speed and memory use) sets the ranking. AMD Radeon RX 9070 XT Q8 GGUF · 3.8 s · Runs great
83Great quality (A) · 83 of 100: how capable the model is at Q8 GGUF, whatever it runs on. Match score 92/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4060 Ti 16GB Q8 GGUF · 7.7 s · Runs great
83Great quality (A) · 83 of 100: how capable the model is at Q8 GGUF, whatever it runs on. Match score 92/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4070 Ti SUPER Q8 GGUF · 4.6 s · Runs great
83Great quality (A) · 83 of 100: how capable the model is at Q8 GGUF, whatever it runs on. Match score 92/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4080 SUPER Q8 GGUF · 4.1 s · Runs great
83Great quality (A) · 83 of 100: how capable the model is at Q8 GGUF, whatever it runs on. Match score 92/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 5060 Ti 16GB Q8 GGUF · 7.3 s · Runs great

Quick answers

How much memory does Z-Image Turbo need on the M6 16GB?

At FP8 it needs about 8.5 GB. The M6 16GB has 10.7 GB usable.

How long does Z-Image Turbo take on the M6 16GB?

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