Can the Intel Arc B570 run Z-Image?

Yes, but slowly (tight fit · encoder in RAM)

Slow (tight fit · encoder in RAM). At FP8 it needs about 8.5 GB of 10.0 GB usable and takes about 75 s per image.

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

Best app to run it on the Intel Arc B570

On Windows

ComfyUI

Desktop app · runs on PyTorch (ComfyUI), GGUF via ComfyUI-GGUF

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

Get ComfyUI

On Linux

ComfyUI

Desktop app · runs on PyTorch (ComfyUI), GGUF via ComfyUI-GGUF

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

Get ComfyUI

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

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-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 (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 2 days ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 80Great quality (A) · 80 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 Slowtight fit · encoder in RAM: How well it runs on the Intel Arc B570: 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.	36.2 / 45
Memory fitFull marks when everything sits in GPU memory; fewer when part spills to system RAM.	18.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.	5.5 / 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.6 / 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 Arc B570

Quant	Memory needed	Available	Speed	Memory mode	Runs	Quality	Download
`FP16`	6.5 GB	10.0 GB	1.7 min	Sequential CPU offload	SlowCPU offload	82Great quality (A) · 82 of 100: how capable the model is at FP16, whatever it runs on. Match score 68/100 (quality, fit, speed and memory use) sets the ranking.	Original weights (opens in a new tab)
`FP8`	8.5 GB	10.0 GB	75 s	Text encoder offloaded	Slowtight fit · encoder in RAM	80Great quality (A) · 80 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`	9.0 GB	10.0 GB	1.6 min	Text encoder offloaded	Slowtight fit · encoder in RAM	81Great quality (A) · 81 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`	6.1 GB	10.0 GB	1.7 min	Text encoder offloaded	Slowencoder in RAM	76Great quality (A) · 76 of 100: how capable the model is at Q4 GGUF, whatever it runs on. Match score 73/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)

Other hardware that runs it

82Great quality (A) · 82 of 100: how capable the model is at FP16, whatever it runs on. Match score 89/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 5090 FP16 · 14 s · Runs well
80Great quality (A) · 80 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 9070 XT FP8 · 20 s · Runs well
80Great quality (A) · 80 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. NVIDIA GeForce RTX 5080 FP8 · 20 s · Runs well
80Great quality (A) · 80 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. NVIDIA GeForce RTX 4080 SUPER FP8 · 22 s · Runs well
80Great quality (A) · 80 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 4070 Ti SUPER FP8 · 24 s · Runs well
80Great quality (A) · 80 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 5070 Ti FP8 · 25 s · Runs well

Quick answers

How much memory does Z-Image need on the Arc B570 10GB?

At FP8 it needs about 8.5 GB. The Arc B570 10GB has 10.0 GB usable.

How long does Z-Image take on the Arc B570 10GB?

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