Skip to content
VRAMwise

Quantization explained: GGUF Q4 vs Q5 vs Q8

Quantization is a deliberate quality/size trade. Local LLM users meet it as Q4_K_M, Q5_K_M, Q8_0 file names.

What changes

Lower-bit quants store weights with less precision, shrinking download size and VRAM. Higher-bit quants keep more fidelity and cost memory.

Different models degrade differently. A coding model and a chat model will not show the same Q4 vs Q8 gap on your prompts.

How VRAMwise treats sizes

When our model table has published GGUF sizes per quant, the fit checker uses those numbers. When you only know parameter count, the quant compare tool uses transparent planning stand-ins labeled as such.

Practical order

General information, not personalized advice.

Apple contrast
Catalog exits
Methodology paths

Frequently asked questions

What is GGUF?

A common packaging format for local LLM weights used by llama.cpp-style runtimes.

Does Q4 always fit better?

Usually smaller than Q5/Q8, so yes for VRAM — but quality and edge-case behavior differ by model.

Why not params × 0.5 bytes?

Because published GGUF files include layout and quant schemes that naive formulas miss. We prefer tabled file sizes when available.

Is Q8 always higher quality?

Often closer to full precision, at a large size cost. Measure on your prompts.

Advice?

Educational only.

Quantization Explained: GGUF Q4 vs Q5 vs Q8 — by VRAMwise ↗