Those confusing letters after a model's name decide how fast it runs and whether it works on your hardware at all. Here's the plain-English guide to picking the right quant format.
GGUF, EXL2, AWQ — which quantization format should you use?
Short answer: for most people running AI at home, use GGUF. It runs on everything — CPU, Apple Silicon, and NVIDIA, AMD, or Intel GPUs — and it's the format behind Ollama and LM Studio, so if you're using those, you're already using GGUF. Choose EXL2 only if you have an NVIDIA card and want maximum speed; choose AWQ if you're running a production GPU server. Those letters after a model's name aren't random — they decide how fast it runs and whether it works on your hardware at all — so here's the plain-English guide to picking right.
What the formats actually are
Quantization shrinks a model by storing its weights at lower precision (e.g. 4-bit instead of 16-bit), which cuts VRAM use dramatically for a small quality loss. The format is how that's packaged, and there are three that matter. GGUF is llama.cpp's format — a single .gguf file with the model and metadata bundled in. Its superpower is universal hardware support: it's the only one that runs efficiently on CPU-only or partial-GPU systems, and it works on Apple Silicon and every GPU brand. That's why it dominates home use. EXL2 is ExLlamaV2's format: NVIDIA-only, but the fastest option, and it supports arbitrary bit-widths (like 4.25 or 5.0 bpw) so you can precisely target your VRAM — plus a 4-bit cache that quarters context memory. AWQ is the production pick: it integrates natively with server engines like vLLM and TGI, loads fastest, and holds quality close to full precision. There's also EXL3 (newer, still maturing) and GPTQ (older), but those three cover the real decisions.
GGUF vs EXL2 vs AWQ
GGUF
Format
CPU, Mac, any GPU
Hardware
Personal/home use — the default
EXL2
Format
NVIDIA only
Hardware
Max speed on an NVIDIA card
AWQ
Format
GPU (vLLM/TGI)
Hardware
Production servers
Format
Hardware
Best for
GGUF
CPU, Mac, any GPU
Personal/home use — the default
EXL2
NVIDIA only
Max speed on an NVIDIA card
AWQ
GPU (vLLM/TGI)
Production servers
The format decides speed and hardware compatibility — GGUF for home, EXL2 for NVIDIA speed, AWQ for servers. · Unsplash
So which should you pick?
Here's the honest decision tree. If you're running AI at home — chatting, coding help, general use — use GGUF and stop thinking about it. It works on your hardware whatever it is, it's what Ollama and LM Studio use, and the speed is perfectly good for personal use. If you have an NVIDIA GPU and you're chasing every last token per second — say you're running a heavily-used local assistant and speed matters — EXL2 is worth the switch to ExLlamaV2; it's meaningfully faster and its 4-bit cache helps with long context. If you're deploying a production server for multiple users, AWQ with vLLM is the standard. On the quant level (the Q4/Q5/Q8 in the filename): Q4_K_M is the sweet spot for GGUF — near-lossless quality at a quarter the memory — so grab that unless you have spare VRAM and want Q5/Q6. For the overwhelming majority of readers, the answer is simply: GGUF, Q4_K_M, done.
Quick answers
What is the difference between GGUF and EXL2?
GGUF is llama.cpp's format — a single file that runs on virtually any hardware (CPU, Apple Silicon, and NVIDIA, AMD, or Intel GPUs), making it the default for home use and the format behind Ollama and LM Studio. EXL2 is ExLlamaV2's format: it's NVIDIA-only (no CPU, AMD, or Mac support) but the fastest option for GPU inference, with precise bit-width control and a 4-bit cache that reduces context memory. Use GGUF for compatibility and ease; use EXL2 for maximum speed on an NVIDIA card.
Which quantization format is best for running AI locally?
For most home users, GGUF is best — it runs on any hardware, powers Ollama and LM Studio, and delivers good speed with no fuss. Choose EXL2 only if you have an NVIDIA GPU and want the fastest possible inference, and AWQ if you're running a production server with vLLM or TGI. On quantization level, Q4_K_M is the standard sweet spot: near-lossless quality at roughly a quarter of the memory. The simple recommendation for personal use is GGUF at Q4_K_M.
What does Q4_K_M mean in a model name?
It describes the quantization: 'Q4' means 4-bit precision (the weights are stored at 4 bits instead of the original 16), and 'K_M' is a specific GGUF method that balances quality and size well. Q4_K_M is the sweet-spot quantization for local AI — it uses about a quarter of the memory of the full model while keeping quality nearly indistinguishable for most tasks. Higher numbers (Q5, Q6, Q8) mean more precision and larger size; lower ones mean smaller and slightly lower quality. Q4_K_M is the safe default.