Datasheet for local AI50 models99 GPUsData read 2026-10-01
No adsNo tracking
Check my GPU →

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

Image model · 6.15B48 GB unified · ~40.2 GB for the GPU · 273–614 GB/s · Apple SiliconData 2026-10-01
Runs well
Yes — and comfortably.

Download 16-bit (12.3 GB). With the model's working memory it needs about 14.6 GB, leaving 25.6 GB spare on 40.2 GB. Quality: the original weights.

Best file16-bit
File size12.3 GB
GPU memory needed~14.6 GB
Shared memory31 / 48 GB
Memory map · Mac 48 GB14.6 GB / 40.2 GB
020 GB40 GB
Weights 16-bit · 12.3 GBWorking memory · 1.5 GBReserve · 0.8 GBFree · 25.6 GB
calculated from real file sizes plus working memory. Not yet measured on this setup. How this works.

01What to download

PartFileFolderSize
Modelming_image_0.1_design_bf16.safetensors
16-bit · Comfy-Org/Ming-Image
models/diffusion_models12.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 disk25.4 GB

Alternatives: Ling-Mini-2.0 BF16 (36.7 GB). The 16-bit text encoder is a little more faithful; the smaller one is chosen here because it loads faster and needs less RAM. On a Mac, FP8 text encoders do not load, so a 16-bit one is listed. Sizes read from Hugging Face (2026-10-01). “Download” links start the file directly; the file name links are the same files the official ComfyUI workflows use.

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

Shared memory: about 31.4 GB of your 48 GB. On this machine the model, the text encoder, the VAE and the operating system all use the same memory. That leaves room, so nothing has to be swapped to disk. calculated

02Every Ming-Image file on 40.2 GB

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

Sizes from the Hugging Face file listing, read 2026-10-01. “Needed” = file + 1.5 GB working memory for this model + 0.8 GB kept free for the system. 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

Ling-Mini-2.0 (a large language model): 36.7 GB as 16-bit, 19.5 GB as INT8, 12.8 GB as 4-bit w4a8 (GGUF versions from realrebelai: Q4_K_M 11.5 GB, Q2_K 7.9 GB). ComfyUI encodes the prompt first and can push the encoder out of VRAM before sampling, so it does not have to fit together with the model. On 40.2 GB the INT8 encoder fits on its own, so prompt encoding stays fast.

04About this GPU

A Mac with 48 GB shares that memory between the CPU and the GPU. On current macOS the GPU may use about 40.2 GB of it by default (older macOS versions: about 38.7 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 48 GB: M3 Max, M4 Pro, M4 Max, M5 Pro, M5 Max (memory bandwidth 273–614 GB/s — the higher, the faster). Everything about Macs and local AI →

Mac 48 GB: 48 GB unified · ~40.2 GB for the GPU · 273–614 GB/s · Apple Silicon. Everything that runs on the Mac 48 GB →

05What more VRAM would change

Nothing to gain for this model: the Mac 48 GB already runs a top-quality file entirely in VRAM. More memory would only help with bigger images, longer clips or several models at once.

06Measured and reported results

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

07Questions

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), counting working memory and a small system reserve. The full 16-bit file needs about 14.6 GB.

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

16-bit (12.3 GB) from Comfy-Org/Ming-Image.

Is FP8 faster than GGUF on the Mac 48 GB?

No. This GPU has no FP8 compute, so ComfyUI converts FP8 weights back before the maths. FP8 only saves memory here; Q8_0 GGUF is the closer-to-original 8-bit pick.

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

About 25.4 GB for the model file, text encoder and VAE listed on this page, and the same again free on disk. With a 40.2 GB card, 32 GB of system RAM or more is recommended.