Check my GPU →

Can the Mac 16 GB run Ming-Image 0.1 Design?

Yes. Q8_0 fits on the Mac 16 GB with 3.1 GB to spare.

Image model · 6.15B16 GB unified · ~12.7 GB for the GPU · 68.25–200 GB/s · Apple SiliconData 2026-10-01
Runs well
Yes.

Take Q8_0 (7.3 GB). In use it comes to about 9.6 GB, with 3.1 GB left over on 12.7 GB.

Best fileQ8_0
File size7.3 GB
GPU memory needed~9.6 GB
Shared memory26 / 16 GB
Memory map · Mac 16 GB9.6 GB / 12.7 GB
06 GB13 GB
Weights Q8_0 · 7.3 GBWorking memory · 1.5 GBReserve · 0.8 GBFree · 3.1 GB

01What to download

PartFileFolderSize
ModelMing-Image-0.1-Design-Q8_0.gguf
Q8_0 · realrebelai/Ming-Image_GGUFs
models/unet7.3 GBDownload →
Text encoderming_image_0.1_ling_mini_2.0_w4a8.safetensors
Ling-Mini-2.0 (4-bit w4a8) · Comfy-Org/Ming-Image
models/text_encoders12.8 GBDownload →
VAEming_image_vae_bf16.safetensors
Ming-Image VAE · Comfy-Org/Ming-Image
models/vae0.3 GBDownload →
Total download · keep about the same free on disk20.4 GB

Alternatives: Ling-Mini-2.0 BF16 (36.7 GB). On a Mac, FP8 text encoders do not load, so a 16-bit one is listed. Sizes from Hugging Face, 2026-10-01.

Free ComfyUI workflow, tested on my RTX 5060 Ti: INT8 workflow (.json). Drag the file into ComfyUI. All workflows →

Shared memory: about 26.4 GB of your 16 GB. On this machine the model, the text encoder, the VAE and the operating system all use the same memory. That is about 10.4 GB more than there is. It still runs: while the model works, the system compresses or swaps the idle text encoder, so loading and changing the prompt get slower. A smaller file or text encoder avoids that. calculated

02Every Ming-Image file on 12.7 GB

FileSizeNeededOn this cardQualityDownload
16-bit
SAFETENSORS · Comfy-Org
12.3 GB14.6 GBspills 1.9 GBthe original weightsHugging Face →
Q8_0 ←
GGUF · realrebelai
7.3 GB9.6 GBfits · 3.1 GB sparepractically identical to the originalHugging Face →
Q6_K
GGUF · realrebelai
6.8 GB9.1 GBfits · 3.6 GB sparevery close to the originalHugging Face →
Q5_K_M
GGUF · realrebelai
6.2 GB8.5 GBfits · 4.2 GB spareclose; small differences in fine detailHugging Face →
Q4_K_M
GGUF · realrebelai
5.9 GB8.2 GBfits · 4.5 GB sparegood; some loss in fine detail and textHugging Face →
Q3_K_M
GGUF · realrebelai
5.1 GB7.4 GBfits · 5.3 GB sparenoticeable loss of detailHugging Face →
Q2_K
GGUF · realrebelai
4.7 GB7.0 GBfits · 5.7 GB spareheavy loss; a last resortHugging Face →

“Needed” adds 1.5 GB of working memory for Ming-Image and a 0.8 GB reserve. Sizes 2026-10-01. Made for 2048×2048 as well as 1024×1024; at 2048 the working memory is several times larger than the figure used here. A separate "layer" checkpoint of the same size splits a design into layers. Native in ComfyUI since v0.38.0 (late September 2026). FP8 and INT8 files are left out on a Mac: Apple GPUs cannot compute FP8, so ComfyUI either fails to load them or converts them back to 16-bit, which saves no memory. Use a 16-bit or GGUF file.

03The text encoder

At 12.8 GB even the smallest Ling-Mini-2.0 (a large language model) file is too big for 12.7 GB, so it runs from system RAM. That slows down reading the prompt, not the picture. Sizes: 16-bit 36.7 GB, INT8 19.5 GB, 4-bit w4a8 12.8 GB (GGUF versions from realrebelai: Q4_K_M 11.5 GB, Q2_K 7.9 GB). Why the encoder does not count against VRAM →

04Measured and reported results

Nobody has sent measured numbers for this pair yet. If you run Ming-Image on a Mac 16 GB, send your time per image and peak VRAM and it will appear here, credited.

05About the Mac 16 GB

A Mac with 16 GB shares that memory between the CPU and the GPU. On current macOS the GPU may use about 12.7 GB of it by default (older macOS versions: about 11.5 GB); that is the figure used here. ComfyUI can go past it, but macOS then starts compressing and swapping memory and everything slows down. ComfyUI runs on Apple GPUs through PyTorch's MPS backend. 16-bit and GGUF files work; FP8 and INT8 files do not save memory on a Mac, so they are skipped. Speed is the catch: even the fastest Macs are several times slower per image than a desktop RTX card. Chips sold with 16 GB: M1, M1 Pro, M2, M2 Pro, M3, M4, M5, M6 (memory bandwidth 68.25–200 GB/s - the higher, the faster). Everything about Macs and local AI →

16 GB unified · ~12.7 GB for the GPU · 68.25–200 GB/s · Apple Silicon. Everything that runs on it →

06Questions

How much VRAM does Ming-Image need?

Around 7.0 GB with the smallest file (Q2_K) and 8.5 GB with an 8-bit file (INT8). The full 16-bit file needs about 14.6 GB.

Which Ming-Image file should I download for the Mac 16 GB?

Q8_0 (7.3 GB) from realrebelai/Ming-Image_GGUFs. Load it with Unet Loader (GGUF) from the ComfyUI-GGUF node pack.

How much do I need to download for Ming-Image on the Mac 16 GB?

20.4 GB: Ming-Image-0.1-Design-Q8_0.gguf, ming_image_0.1_ling_mini_2.0_w4a8.safetensors, ming_image_vae_bf16.safetensors.