Files read on Hugging Face: 2026-10-31

SDXL Base 1.0 GGUF files and Mac RAM

SDXL Base 1.0 text-to-image model with a UNet denoiser and two CLIP text encoders. The refiner is an optional second stage; the base model works standalone.

Answer

No published Mac run with a GGUF build yet. The smallest complete GGUF download is 2.80 GB; a download that fits in memory does not prove the model runs.

Smallest Mac with a published run
none yetunknown below
Smallest complete download
2.80 GBQ4_K GGUF
Files read
2026-10-31Hugging Face

CreativeML Open RAIL++-M License. Commercial use: allowed. Excluded territories: none listed. Broad use grant with the use-based restrictions in Attachment A.

This is SDXL Base 1.0. The SDXL Refiner 1.0 is an optional second-stage model and is not included in these sizes.

Table 1

Which exact GGUF files make a complete build?

Only builds with every required component and an exact probed file size are shown.

Q4_K GGUF

gguf · Q4_K · 2.80 GB complete

Mac routes: stable-diffusion.cpp

Exact component files for Q4_K GGUF
FileComponentRequiredDownloadSource
sd_xl_base_1.0_0_Q4_K.ggufkostakoff/stable-diffusion-xl-base-1.0-GGUFSDXL UNetditYes2.80 GBHugging FaceRead 2026-10-31

Build sources: SDXL GGUF card.

Q8_0 GGUF

gguf · Q8_0 · 4.18 GB complete

Mac routes: stable-diffusion.cpp

Exact component files for Q8_0 GGUF
FileComponentRequiredDownloadSource
sd_xl_base_1.0_0_Q8_0.ggufkostakoff/stable-diffusion-xl-base-1.0-GGUFSDXL UNetditYes4.18 GBHugging FaceRead 2026-10-31

Build sources: SDXL GGUF card.

Table 2

Does it fit your Mac's RAM?

Published names the exact measured machine. est. is a memory calculation. unknown means the run verdict is not established, not that the model fails.

Run verdicts by Mac memory tier
Mac RAMComplete buildDownloadRun verdictBasis
8 GBQ4_K GGUFQ4_K · stable-diffusion.cpp2.80 GBunknownunknown
16 GBQ4_K GGUFQ4_K · stable-diffusion.cpp2.80 GBunknownunknown
24 GBQ4_K GGUFQ4_K · stable-diffusion.cpp2.80 GBunknownunknown
32 GBQ4_K GGUFQ4_K · stable-diffusion.cpp2.80 GBunknownunknown
48 GBQ4_K GGUFQ4_K · stable-diffusion.cpp2.80 GBunknownunknown
64 GBQ4_K GGUFQ4_K · stable-diffusion.cpp2.80 GBunknownunknown
96 GBQ4_K GGUFQ4_K · stable-diffusion.cpp2.80 GBunknownunknown
128 GBQ4_K GGUFQ4_K · stable-diffusion.cpp2.80 GBunknownunknown

Every image model, ranked by memory: 8 GB Mac · 16 GB Mac · 24 GB Mac · 32 GB Mac · 64 GB Mac

Table 3

Does it fit your NVIDIA GPU's VRAM?

Runs · Stated means the linked model card, app maker or NVIDIA says a GPU with that much VRAM runs the model; Runs · Published names the card of a dated run. Fits with offload means the main model weights fit in VRAM with a 15% margin but the full set does not: the text encoder and VAE run from system RAM, which is slower. Exceeds VRAM means even the main weights are too large for the card. Mac runs never count here.

Run verdicts by NVIDIA VRAM tier
NVIDIA VRAMComplete buildDownloadRun verdictBasis
8 GBQ4_K GGUFQ4_K · stable-diffusion.cpp2.80 GBunknownunknown
12 GBQ4_K GGUFQ4_K · stable-diffusion.cpp2.80 GBunknownunknown
16 GBQ4_K GGUFQ4_K · stable-diffusion.cpp2.80 GBunknownunknown
24 GBQ4_K GGUFQ4_K · stable-diffusion.cpp2.80 GBunknownunknown
32 GBQ4_K GGUFQ4_K · stable-diffusion.cpp2.80 GBunknownunknown

Every image model, ranked by memory: 8 GB of VRAM · 12 GB of VRAM · 16 GB of VRAM · 24 GB of VRAM

How does it rank in blind votes?

No independent score yet.

Which Mac software routes are listed?

  • stable-diffusion.cpp

    Official

    Formats: gguf, safetensors. Memory policy: component stages stay resident.

    C/C++ runner with Metal on Mac and CUDA on NVIDIA. It reads GGUF and safetensors, and its docs keep a page per model family. Resident size is the sum of the weights, an upper bound.

    Sources: stable-diffusion.cpp README, backends

What does the official configuration say?

"No numeric RAM or VRAM minimum is given. The card suggests CPU offloading when limited by GPU VRAM."

Source: SDXL Base model card · Read 2026-10-24.

What known issues should you check?

  • Known issue 1

    ComfyUI documents that running the VAE in fp16 might cause black images. Individual SDXL black-image reports on Macs exist but are not general rules.

    Source: ComfyUI CLI arguments · Read 2026-10-24

Sources