BFWR AI Tools

Ollama models and VRAM requirements

The question Ollama does not answer for you is whether a model will actually fit before you pull several gigabytes to find out. Every model below carries the memory it needs at Q4 and Q8 — weights plus KV cache plus the overhead the framework reserves — and the command that fetches it. They range from 2.5GB to 400GB at Q4.

All 30 models, smallest first

Q4 is what ollama run gives you by default for most tags. Q8 roughly doubles the memory for a quality difference most people cannot pick out in ordinary use — start at Q4 and move up only if you have a reason.

ModelQ4 VRAMQ8 VRAMPull command
Meta Llama 3.2 3B Instruct
3.21B · General
2.5GB4.2GBollama run llama3.2:3b
Qwen 2.5 Coder 7B Instruct
7.6B · Coding
5.5GB9.5GBollama run qwen2.5-coder:7b
DeepSeek R1 Distill Llama 8B
8.0B · Reasoning
5.8GB9.8GBollama run deepseek-r1:8b
Llama 3.1 8B Instruct
8.03B · General
6GB10GBollama run llama3.1:8b
Qwen3 8B
8.2B · General
6.4GB10.7GBollama run qwen3:8b
Google Gemma 2 9B
9.24B · General
7GB11.5GBollama run gemma2:9b
Gemma 4 12B
12B · General
8.7GB14.7GBollama run gemma4:12b
Mistral NeMo 12B Instruct
12.2B · General
9GB15GBollama run mistral-nemo:12b
DeepSeek R1 Distill Qwen 14B
14.8B · Reasoning
10.5GB17.5GBollama run deepseek-r1:14b
Qwen 2.5 Coder 14B Instruct
14.7B · Coding
10.5GB17GBollama run qwen2.5-coder:14b
Microsoft Phi-4 14B
14.7B · Reasoning
10.5GB17.5GBollama run phi4:14b
Mistral Codestral 22B
22.2B · Coding
15GB26GBollama run codestral:22b
OpenAI gpt-oss-20b
20.9B (3.6B active) · Reasoning
15.3GB24.2GBollama run gpt-oss:20b
Mistral Small 3 24B
24.0B · General
16GB28GBollama run mistral-small:24b
Gemma 4 26B-A4B (MoE)
26.5B (3.8B active) · General
17.4GB30.1GBollama run gemma4:26b
Google Gemma 2 27B
27.2B · General
18GB32GBollama run gemma2:27b
Qwen3.8 27B
27.8B · General
18.2GB31.5GBollama run qwen3.8:27b
Qwen3-Coder 30B-A3B Instruct
30.5B (3.3B active) · Coding
19.8GB34.3GBollama run qwen3-coder:30b
Gemma 4 31B
31.3B · General
20.3GB35.2GBollama run gemma4:31b
DeepSeek R1 Distill Qwen 32B
32.5B · Reasoning
21.5GB38GBollama run deepseek-r1:32b
Qwen 2.5 Coder 32B Instruct
32.5B · Coding
21.5GB38GBollama run qwen2.5-coder:32b
Cohere Command R 35B
35.0B · RAG
23GB40GBollama run command-r:35b
Qwen3.6 35B-A3B (MoE)
36B (3B active) · General
23.1GB40.2GBollama run qwen3.6:35b
Llama 3.3 70B Instruct
70.6B · General
42GB78GBollama run llama3.3:70b
DeepSeek R1 Distill Llama 70B
70.6B · Reasoning
45GB80GBollama run deepseek-r1:70b
Qwen 2.5 72B Instruct
72.7B · General
45GB82GBollama run qwen2.5:72b
OpenAI gpt-oss-120b
116.8B (5.1B active) · Reasoning
66.5GB125.8GBollama run gpt-oss:120b
Llama 4 Scout (17B active, 16 experts)
109B (17B active) · General
66.9GB117.5GBollama run llama4:16x17b
DeepSeek V4-Flash
284B (13B active) · Reasoning
171.9GB303GB(not in the Ollama library; use llama.cpp or vLLM)
DeepSeek V3 671B MoE
671B (37B active) · General
400GB740GBollama run deepseek-v3:671b

Figures are the minimum to load at that quantization. For a specific context length, the VRAM calculator splits the requirement into weights, KV cache and overhead — long context can add several gigabytes on top of these numbers.

What fits your GPU

Start from the memory you have. Each tier scores every model against what a card that size realistically gives you once the display and the framework have taken their share.

On a Mac the GPU shares unified memory rather than having its own pool — the Mac VRAM optimizer works out how much of your RAM it can address. To start from a specific machine, the hardware matrix profiles real devices against every model.

Ollama or something else?

  • LM Studio: An application. Browse, download, chat, inspect — no terminal needed.

    Ollama vs LM Studio
  • llama.cpp: The engine. Total control, manual setup, newest features first.

    llama.cpp vs Ollama
  • vLLM: Many users, NVIDIA-class GPU, whole model resident.

    Ollama vs vLLM

New to this entirely? The local LLM starting guide covers hardware, runner and first model in order.

Common questions

How much VRAM does Ollama need?
Ollama itself is a thin service; the memory goes to whichever model you load. At Q4_K_M — the default for most Ollama tags — a 3B model needs under 3GB, an 8B model around 6GB and a 70B model over 40GB. The table on this page lists the requirement for every model, and the figure includes the KV cache and framework overhead, not just the weights.
What happens if a model does not fit in my VRAM?
Ollama will still run it. It loads as many layers onto the GPU as fit and runs the rest on the CPU against system RAM, which works but is far slower because those layers run at system memory bandwidth. This is why Ollama can run models larger than your card, and why doing so is often unpleasant.
Which quantization does ollama run use by default?
For most model tags the default is a 4-bit quantization, usually Q4_K_M. You can request another by appending it to the tag. Q8_0 roughly doubles the memory for a quality difference most people cannot detect in ordinary use, so Q4 is the usual starting point.
Does Ollama use the GPU automatically?
Yes, where it can. It detects CUDA on NVIDIA, ROCm on supported AMD cards and Metal on Apple Silicon, and offloads as many layers as the available memory allows. On a Mac the GPU draws from unified memory rather than a separate pool, so the usable figure is roughly 70% of total RAM.
Is Ollama better than LM Studio?
They are not competing on capability — both run the same GGUF models on the same hardware. Ollama is a background service with a command line and an HTTP API, which is what you want when another application calls the model. LM Studio is a desktop app with a model browser and chat window, which is what you want when you are the one talking to it.

Guides that go deeper

Choosing a runner, what each quantization costs, and how memory is sized.