CoolFace
Modelpublic

FINAL-Bench/POCKET-Zimage-CPU

sourceHugging Faceapache-2.0updated 1d agoView on Hugging Face
35likes54downloads
Model Card
### πŸ†• [POCKET-Qwen3.8-Flash-Next](https://huggingface.co/FINAL-Bench/POCKET-Qwen3.8-Flash-Next-GGUF) β€” a 180B model running on a laptop with 8 GB VRAM + 32 GB RAM Β· 4.17 tok/s measured. ![New](https://huggingface.co/FINAL-Bench/POCKET-Qwen3.8-Flash-Next-GGUF) ![VRAM]() ![RAM]() ![Speed]() <!-- POCKET-FLASHNEXT-BADGE -->
### πŸ“š Collections β–Ά [POCKET Models](https://huggingface.co/collections/FINAL-Bench/pocket-models-6a618ee5d23eafb7e185a5c6) β€” this family (on-device, no GPU) Darwin Family Β· Aether Foundation Β· VKAE Accelerated

POCKET-Zimage-CPU

Pick your build β†’ ![35B](https://huggingface.co/FINAL-Bench/POCKET-35B-GGUF) ![26B](https://huggingface.co/FINAL-Bench/POCKET-26B-GGUF) ![KR GGUF](https://huggingface.co/FINAL-Bench/POCKET-KR-GGUF) ![KR MLX-0f6e56)](https://huggingface.co/FINAL-Bench/POCKET-KR-MLX) ![EN GGUF](https://huggingface.co/FINAL-Bench/POCKET-EN-GGUF) ![180B laptop](https://huggingface.co/FINAL-Bench/POCKET-Qwen3.8-Flash-Next-GGUF) ![Image NF4](https://huggingface.co/FINAL-Bench/POCKET-Image-Zimage) ![Image CPU](https://huggingface.co/FINAL-Bench/POCKET-Zimage-CPU)

Photoreal images in 46 seconds on a CPU only. No GPU. No CUDA. No Python.

πŸš€ Try it live, no install β†’ ![Space](https://huggingface.co/spaces/FINAL-Bench/POCKET-Zimage-CPU) β€” generating on a CPU-only box.

![License](https://www.apache.org/licenses/LICENSE-2.0) ![Runtime](https://github.com/leejet/stable-diffusion.cpp) ![No GPU]() ![Base](https://huggingface.co/Tongyi-MAI/Z-Image-Turbo) ![RAM]()

The POCKET lineup β†’ ![Zimage CPU-ff6b35)](https://huggingface.co/FINAL-Bench/POCKET-Zimage-CPU) ![35B](https://huggingface.co/FINAL-Bench/POCKET-35B-GGUF) ![KR GGUF](https://huggingface.co/FINAL-Bench/POCKET-KR-GGUF) ![KR MLX-0f6e56)](https://huggingface.co/FINAL-Bench/POCKET-KR-MLX) ![EN GGUF](https://huggingface.co/FINAL-Bench/POCKET-EN-GGUF) ![26B](https://huggingface.co/FINAL-Bench/POCKET-26B-GGUF)


Why this exists

Every image model assumes you have a GPU. Most machines don't.

POCKET-Zimage-CPU is Z-Image-Turbo packaged so that a plain office PC β€” no graphics card, no CUDA, no Python environment β€” produces a photoreal 512Γ—512 image in under a minute. One binary, three files, done.

Samples

<table> <tr> <td width="33%"><img src="./samples/apple3steps.png" width="100%"><br><sub><b>3 steps</b> Β· 48.6 s Β· the default we ship</sub></td> <td width="33%"><img src="./samples/apple4steps.png" width="100%"><br><sub>4 steps Β· 60.7 s Β· no visible gain</sub></td> <td width="33%"><img src="./samples/applekoreanprompt.png" width="100%"><br><sub>Korean prompt Β· note it lost the count</sub></td> </tr> </table>

<sub>Prompt: <code>a red apple on a wooden table, photorealistic</code> β€” Korean: <code>λ‚˜λ¬΄ νƒμž μœ„μ— 놓인 λΉ¨κ°„ 사과, 사싀적인 사진</code>. Same seed, CPU only.</sub>

Measured, not claimed

All numbers below are from our own runs. GPU count used: zero.

ResolutionTimeSamplingVAEPeak RAM
512 Γ— 51246.4 s32.7 s12.5 s6.42 GB
512 Γ— 512 (Korean prompt)45.3 s32.1 s12.0 s6.42 GB
1024 Γ— 1024192.7 s135.1 s55.8 s6.76 GB

<sub>Intel Xeon Gold 6526Y Γ—2 (32 cores / 64 threads), 48 threads, Q4_0, 3 steps, --fa --vae-tiling. Single run per row.</sub>

Korean prompts cost nothing extra β€” 45.3 s vs 46.4 s. Language is not a speed penalty here.

How it got 5.3Γ— faster

We started at 244 seconds and ended at 46. Every step is measured:

ChangeTimePeak RAM
Default settings (20 steps)244 s8.16 GB
β†’ 4 steps62.1 s8.16 GB
β†’ --fa (flash attention)59.5 s8.18 GB
β†’ 3 steps48.6 s8.00 GB
β†’ --vae-tiling46.4 s6.42 GB

The big one is step count. Z-Image Turbo is distilled for few-step sampling, but the tool's default is 20. Using the default throws away 5Γ— for nothing.

3 steps is the floor. At 4 and 3 we cannot tell the images apart. At 2 the surface collapses β€” water droplets and wood grain vanish and the texture turns cloth-like.

`--vae-tiling` is free. It cuts VAE time 16% and peak RAM by 1.27 GB. At 1024Γ—1024 it is the difference between 13.3 GB and 6.76 GB.

Do not use every thread you have. On a 32-core / 64-thread box, 48 threads took 59.5 s and 64 threads took 108.8 s β€” 1.8Γ— slower. Hyper-threads fight each other for the same physical cores.

Files

FileSizeWhat
z_image_turbo-Q4_0-pocket.gguf3.51 GBDiffusion model, 4-bit (VIDRAFT CPU build)
(bring your own) Qwen3-4B-Instruct-2507-Q4KM2.58 GBText encoder β€” download
(bring your own) ae.safetensors0.16 GBVAE β€” download
Totalβ‰ˆ 6.25 GB

The diffusion model here is VIDRAFT's own CPU build of Z-Image-Turbo: 3.51 GB, with no visible quality change.

Run it

Get a stable-diffusion.cpp binary (releases), then:

bash
sd-cli \
  --diffusion-model z_image_turbo-Q4_0-pocket.gguf \
  --vae ae.safetensors \
  --llm Qwen3-4B-Instruct-2507-Q4_K_M.gguf \
  -p "a red apple on a wooden table, photorealistic" \
  --cfg-scale 1.0 --steps 3 --fa --vae-tiling \
  -t 8 -H 512 -W 512 -o out.png

Set -t to your physical core count β€” not your thread count.

Honest limits

  • β€”It cannot render text. Any words inside the image come out garbled, in every language. If you need accurate text in an image, this is the wrong tool.
  • β€”Korean prompts lose count. "A red apple" gives one apple in English and five or six in Korean. Korean has no articles, so the singular signal is weak for the encoder. Reproduced at both 20 and 3 steps, so it is the encoder, not the step count.
  • β€”1024 Γ— 1024 takes 3 minutes on the machine above. Slower CPUs scale accordingly.
  • β€”Measured on a server CPU. Laptop and mini-PC numbers are not in yet.

Credits and licensing

ComponentLicenseAuthor
Z-Image-Turbo (diffusion)Apache-2.0Tongyi-MAI / Hangzhou Tongyi Laboratory
Qwen3-4B-Instruct (text encoder)Apache-2.0Qwen, Alibaba
GGUF conversion (upstream)Apache-2.0leejet
stable-diffusion.cpp (runtime)MITleejet

This repository redistributes a re-quantized copy of Z-Image-Turbo and keeps the original copyright notices. We did not train this model. What is ours is the CPU packaging, the 3-step setting, the re-quantization, and the measurements on this page.

Related

Runs onStrength
POCKET-Image-ZimageGPU (Python)Faster, renders Korean text via glyph-init
POCKET-Zimage-CPU (this)CPU onlyNo GPU, single binary

Different jobs. Use the first if you have a graphics card, this one if you don't.

<!-- POCKET-FAMILY -->


🧩 The POCKET Family β€” On-device AI by VIDRAFT

Big models, small hardware. No GPU, no cloud.

Models

Demos & tools (Spaces)

πŸ“š Full POCKET collection

<!-- /POCKET-FAMILY -->