Can the RTX 3060 Ti 8 GB run Ming-Image 0.1 Design?
Download Q3_K_M (5.1 GB). With the model's working memory it needs about 7.4 GB, leaving 0.6 GB spare on 8 GB. Quality: noticeable loss of detail. For better quality, Q4_K_M (5.9 GB) also runs, with about 0.2 GB spilling into system RAM — a little slower, still practical.
Worth trying on this GPU: with an up-to-date ComfyUI, Dynamic VRAM (on by default for NVIDIA since March 2026) streams whatever does not fit from system RAM, and ComfyUI's own start-up message recommends native FP8/INT8 files over GGUF, saying they “will be faster even if they are larger than your memory”. So before settling for a heavily compressed GGUF, try the native INT8 file (6.2 GB). The file recommended above is the best one that fits entirely — the safe choice on older ComfyUI versions, AMD and Intel. Comfy blog: Dynamic VRAM →
01What to download
| Part | File | Folder | Size | |
|---|---|---|---|---|
| Model | Ming-Image-0.1-Design-Q3_K_M.gguf Q3_K_M · realrebelai/Ming-Image_GGUFs | models/unet | 5.1 GB | Download → |
| Text encoder | ming_image_0.1_ling_mini_2.0_int8_convrot.safetensors Ling-Mini-2.0 INT8 · Comfy-Org/Ming-Image | models/text_encoders | 19.5 GB | Download → |
| VAE | ming_image_vae_bf16.safetensors Ming-Image VAE · Comfy-Org/Ming-Image | models/vae | 0.3 GB | Download → |
| Total download · keep about the same free on disk | 24.9 GB | |||
Alternatives: Ling-Mini-2.0 BF16 (36.7 GB); Ling-Mini-2.0 (4-bit w4a8) (12.8 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. 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 →
System RAM: 32 GB or more. ComfyUI keeps the model file, the text encoder and the VAE in system RAM and moves them to the GPU as needed. With this set of files that is about 24.9 GB, plus roughly 6 GB for Windows, ComfyUI and a browser: 30.9 GB in total. With less RAM it still runs, but Windows starts swapping to disk and loading gets very slow. calculated
02Every Ming-Image file on 8 GB
| File | Size | Needed | On this card | Quality | Download |
|---|---|---|---|---|---|
| 16-bit SAFETENSORS · Comfy-Org | 12.3 GB | 14.6 GB | 6.6 GB too big | the original weights | Hugging Face → |
| Q8_0 GGUF · realrebelai | 7.3 GB | 9.6 GB | spills 1.6 GB | practically identical to the original | Hugging Face → |
| INT8 SAFETENSORS · Comfy-Org | 6.2 GB | 8.5 GB | spills 0.5 GB | practically identical to the original | Hugging Face → |
| Q6_K GGUF · realrebelai | 6.8 GB | 9.1 GB | spills 1.1 GB | very close to the original | Hugging Face → |
| Q5_K_M GGUF · realrebelai | 6.2 GB | 8.5 GB | spills 0.5 GB | close; small differences in fine detail | Hugging Face → |
| Q4_K_M GGUF · realrebelai | 5.9 GB | 8.2 GB | spills 0.2 GB | good; some loss in fine detail and text | Hugging Face → |
| Q3_K_M ← GGUF · realrebelai | 5.1 GB | 7.4 GB | fits · 0.6 GB spare | noticeable loss of detail | Hugging Face → |
| Q2_K GGUF · realrebelai | 4.7 GB | 7.0 GB | fits · 1.0 GB spare | heavy loss; a last resort | Hugging 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).
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 8 GB the encoder itself is too big for VRAM, so let it run from system RAM: slower prompt encoding, same images.
04About this GPU
The RTX 3060 Ti 8 GB (Ampere) has no FP8 compute. FP8 files still load and save memory, but ComfyUI converts them back before the maths, so there is no speed gain — Q8_0 GGUF is the closer-to-original 8-bit choice. ComfyUI can compute INT8 files natively on NVIDIA, which is worth a try where a model offers one.
RTX 3060 Ti 8 GB: 8 GB GDDR6 · 256-bit · 448 GB/s · Ampere. Everything that runs on the RTX 3060 Ti 8 GB →
05What more VRAM would change
With 10 GB you could run Ming-Image at 8-bit or better (Q8_0, 7.3 GB) with no offloading: for example on the RTX 3080 10 GB.
What changes from the RTX 3060 Ti 8 GB to the RTX 5060 Ti 16 GB →
06Measured and reported results
Nobody has sent measured numbers for this pair yet. If you run Ming-Image on a RTX 3060 Ti 8 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 RTX 3060 Ti 8 GB?
Q3_K_M (5.1 GB) from realrebelai/Ming-Image_GGUFs. Load it with Unet Loader (GGUF) from the ComfyUI-GGUF node pack.
Is FP8 faster than GGUF on the RTX 3060 Ti 8 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 RTX 3060 Ti 8 GB?
About 24.9 GB for the model file, text encoder and VAE listed on this page, and the same again free on disk. With a 8 GB card, 32 GB of system RAM or more is recommended.