LLM VRAM Calculator

Instant GPU and unified-memory sizing for dense and MoE models, with KV-cache quantization and the hardware that fits.

Estimate GPU memory for a local model. Updated . Author: LLM Hardware team.

Quick presets

e.g. 7 for a 7B model, 70 for 70B

Estimated VRAM needed

— GB

—

New model dropped? We'll tell you what runs it.

Compatible Hardware

 

Apple Mac mini (M6, 16GB)

16 GB unified

—

Apple Mac mini (M6, 24GB)

24 GB unified

—

Apple Mac Studio (M5 Max, 36GB)

36 GB unified

—

Apple Mac mini (M5 Pro, 24GB)

24 GB unified

—

Apple Mac mini (M4, 16GB)

16 GB unified

—

Apple Mac mini (M4, 24GB)

24 GB unified

—

Apple Mac mini (M4 Pro, 24GB)

24 GB unified

—

Apple Mac mini (M4 Pro, 48GB)

48 GB unified

—

Apple Mac Studio (M4 Max, 64GB)

64 GB unified

—

Apple Mac Studio (M4 Max, 128GB)

128 GB unified

—

NVIDIA GeForce RTX 4060 (8GB)

8 GB VRAM

—

NVIDIA GeForce RTX 4070 (12GB)

12 GB VRAM

—

NVIDIA GeForce RTX 4090 (24GB)

24 GB VRAM

—

NVIDIA GeForce RTX 3090 (24GB)

24 GB VRAM

—

NVIDIA GeForce RTX 5090 (32GB)

32 GB VRAM

—

Intel Arc B580 (12GB)

12 GB VRAM

—

AMD Radeon RX 7900 XTX (24GB)

24 GB VRAM

—

NVIDIA RTX 4080 (16GB)

16 GB VRAM

—

NVIDIA RTX 4060 Ti (16GB)

16 GB VRAM

—

NVIDIA RTX 5080 (16GB)

16 GB VRAM

—

NVIDIA RTX 5070 (12GB)

12 GB VRAM

—

NVIDIA RTX 5070 Ti (16GB)

16 GB VRAM

—

NVIDIA RTX 4070 Ti Super (16GB)

16 GB VRAM

—

NVIDIA DGX Spark

128 GB VRAM

—

PNY GeForce RTX 5060 Ti (16GB)

16 GB VRAM

—

GMKtec EVO-X2 (Ryzen AI Max+ 395, 128GB)

128 GB unified

—

Beelink GTR9 Pro (128GB) — out of stock

128 GB unified

—

Apple Mac Studio (M5 Max, 48GB)

48 GB unified

—

Apple Mac Studio (M5 Max, 64GB)

64 GB unified

—

Apple Mac Studio (M5 Max, 128GB)

128 GB unified

—

Apple Mac Studio (M5 Ultra, 96GB)

96 GB unified

—

Beelink GTR9 Pro (128GB, OOS watchlist)

128 GB unified

—

How Much VRAM Do You Need for LLMs?

GPU VRAM (or Apple Silicon unified memory) is the primary bottleneck when running large language models locally. The model weights must fit entirely in VRAM for efficient inference — otherwise the system falls back to slow RAM offloading.

The VRAM requirement scales linearly with parameter count and quantization bit-width:

VRAM Requirements by Model Size

Model SizeQ4_K_MQ5_K_MQ8FP16Ollama tag
7B 6.2 GB 7.3 GB 10.4 GB 18.8 GB ollama run qwen3:8b is the nearby 8B tag (6.8 GB at Q4)
8B 6.8 GB 8.0 GB 11.6 GB 21.2 GB qwen3:8b, Llama 3.1 8B
14B 10.4 GB 12.5 GB 18.8 GB 35.6 GB ollama run qwen3:14b or phi4:14b
27B 18.2 GB 22.3 GB 34.4 GB 66.8 GB Qwen3.8-27B. ollama run qwen3.8:27b. Library listed 18 GB on 2026-10-03.
25.2B MoE 17.1 GB 20.9 GB 32.2 GB 62.5 GB Gemma 4 26B-A4B total params. Active is 3.8B. ollama run gemma4:26b.
32B 21.2 GB 26.0 GB 40.4 GB 78.8 GB ollama run qwen3:32b — needs 24 GB at Q4
70B 44.0 GB 54.5 GB 86.0 GB 170 GB llama3.3:70b — not one 32 GB GPU

The Formula

VRAM (GB) = parameters(B) × bytes_per_param × 1.2 + 2 GB OS

Bytes per parameter: FP16 = 2, Q8 = 1, Q5_K_M = 0.625, Q4_K_M = 0.5. The 1.2 factor covers activations and a short context (about 4K). It is not a 32K or 128K estimate. The context control above adds an approximate KV-cache allowance on top. A worked example: 8 × 0.5 × 1.2 + 2 = 6.8 GB for an 8B model at Q4_K_M. That is the same formula as llms.txt and the methodology page.

For Mixture-of-Experts models (Llama 4 Scout, Gemma 4 26B-A4B, Mixtral), use the total parameter count in the calculator — all expert weights must be loaded into VRAM even though only a fraction activate per token. Llama 4 Scout is named "17B active" but has ~109B total parameters. At Q4_K_M that is 109 × 0.5 × 1.2 + 2 = 67.4 GB. Gemma 4 26B-A4B is 3.8B active and 25.2B total, so the Q4 line is 17.1 GB, not a 4B model’s footprint. See the what-can-I-run guide and the Llama guide.

Checked 3 October 2026

Two local models and one that is not. File sizes are the bytes Hugging Face listed that day. The formula column is this site’s short-context estimate, which is larger than the file because it includes the 1.2 factor and 2 GB.

ModelWhat the card saysPublished 4-bit fileQ4 formulaPractical tier
Qwen3.8-27B 27B dense, Apache-2.0, 262K native context Unsloth UD-Q4_K_XL 17.6 GB. Ollama qwen3.8:27b listed 18 GB. 18.2 GB 24 GB GPU or 36 GB unified. Not 16 GB.
Gemma 4 26B-A4B 25.2B total, 3.8B active, Apache-2.0 Unsloth UD-Q4_K_XL 17.01 GB. Google QAT Q4_0 14.44 GB. Ollama gemma4:26b 16–19 GB. 17.1 GB 24 GB comfortable. 16 GB only for the smaller file and a short chat.
Gemma 4 E2B / E4B 2.3B / 4.5B effective, 5.1B / 8B with embeddings Unsloth Q4_K_M files 3.11 GB and 4.98 GB 5.1 GB and 6.8 GB on the with-embeddings counts 8–12 GB, including a laptop. Tags: gemma4:e2b, gemma4:e4b.

Kolibri-1 is the counterexample. Aleph Alpha’s card, dated 3 October 2026, lists about 78 GB of FP8 weights and a minimum of datacenter GPUs. Do not type 78 into this calculator and then shop for a 24 GB card. Commands and the Mac side of the same fit are on the Ollama cheat sheet, the GPU guide, and the Apple Silicon guide.

Frequently Asked Questions

How do I calculate VRAM for an LLM?

Use VRAM (GB) = parameters (B) × bytes_per_param × 1.2 + 2 GB for the OS. Bytes per parameter: FP16 = 2, Q8 = 1, Q5_K_M = 0.625, Q4_K_M = 0.5. An 8B model at Q4_K_M is 8 × 0.5 × 1.2 + 2 = 6.8 GB at a short context. Longer context adds KV cache on top. The method is on the methodology page.

How much VRAM does a 7B model need?

7 × 0.5 × 1.2 + 2 = 6.2 GB at Q4_K_M, 7 × 1.0 × 1.2 + 2 = 10.4 GB at Q8, and 7 × 2.0 × 1.2 + 2 = 18.8 GB at FP16. An 8 GB card fits Q4_K_M with a short context. Q8 needs 12 GB. Pull it with ollama pull qwen3:8b when you want that size.

How much VRAM does a 32B model need at Q4_K_M?

32 × 0.5 × 1.2 + 2 = 21.2 GB. A 24 GB GPU such as an RTX 3090 or RTX 4090 fits it at a short context. Q8 is 32 × 1.2 + 2 = 40.4 GB and does not fit one 24 GB card. The matching Ollama tag is qwen3:32b.

How much VRAM does a 70B model need?

70 × 0.5 × 1.2 + 2 = 44 GB at Q4_K_M. That does not fit a 32 GB RTX 5090. A 64 GB or larger unified-memory Mac, or two 24 GB GPUs, can hold the weights. ollama pull llama3.3:70b is the tag, not a promise that one consumer GPU can run it.

Does the 1.2 factor include a long context window?

No. The 1.2 factor plus the 2 GB OS reserve covers activations and a short context, about 4K tokens. This calculator adds an extra KV-cache allowance for 16K, 32K, and 128K. Those extras are approximate and depend on layer count and KV heads. The methodology page shows the per-token KV formula.

Why does a 13B model miss an 8 GB GPU?

13 × 0.5 × 1.2 + 2 = 9.8 GB at Q4_K_M. An 8 GB card is short. A 12 GB card such as an Intel Arc B580 or an RTX 4070 fits that Q4_K_M estimate. qwen3:14b is the nearby Ollama tag and needs 10.4 GB.

Which Ollama or LM Studio file matches a calculator result?

Pull a size tag, not a VRAM setting. If a 14B Q4_K_M fits, run ollama pull qwen3:14b and then ollama run qwen3:14b. In LM Studio, download the Q4_K_M GGUF of the same size. If ollama ps shows GPU under 100%, the weights spilled to system RAM.

How should I read Apple unified memory in this calculator?

Unified memory is shared with macOS. Treat usable memory as the catalog figure minus several GB for the OS, on top of the formula’s 2 GB reserve. A 24 GB Mac is not the same fit as a 24 GB discrete GPU. See the Apple Silicon guide for the wired-memory caveat.

Does Qwen3.8-27B fit a 24 GB GPU?

At a short context, yes. Qwen’s card lists 27B parameters and Apache-2.0. The formula is 27 × 0.5 × 1.2 + 2 = 18.2 GB at Q4_K_M. On 3 October 2026 Unsloth’s GGUF tree showed UD-Q4_K_S at 15.4 GB, UD-Q4_K_M at 16.5 GB, and UD-Q4_K_XL at 17.6 GB. Those are file sizes, smaller than the formula because the formula adds a 1.2 runtime factor and 2 GB. Ollama’s library listed qwen3.8:27b at 18 GB the same day. Q8 is 27 × 1.2 + 2 = 34.4 GB and does not fit 24 GB. A 16 GB card does not fit the 18.2 GB estimate.

How much memory does Gemma 4 26B-A4B need?

Use the total parameter count, not the active count. Google’s card lists 25.2B total and 3.8B active, Apache-2.0. All experts stay resident, so Q4_K_M is 25.2 × 0.5 × 1.2 + 2 = 17.1 GB at a short context. Unsloth’s hardware table recommends 16–18 GB at 4-bit. Their UD-Q4_K_XL file was 17.01 GB, and Google’s QAT Q4_0 GGUF was 14.44 GB. Ollama listed gemma4:26b at 16–19 GB. A 24 GB GPU is the comfortable tier. A 16 GB GPU is the edge of the file, not a comfortable context.

Can this calculator place Aleph Alpha Kolibri on a consumer GPU?

No. Aleph-Alpha/Kolibri-1, released 3 October 2026 under Apache-2.0, is a 78B MoE with 3.46B active parameters. The card’s memory footprint is about 78 GB of FP8 weights, and the minimum hardware it lists is two A100 80 GB, two H100s, or one H200, B200, or B300. A Q4 formula on 78.1B would be about 48.9 GB, which still misses every 24 GB and 32 GB gaming card, and that formula is not a published consumer quant. Treat Kolibri as a datacenter or API serve.

Does Qwen3.6-27B or Qwen3.6-35B-A3B fit a 24 GB GPU?

Qwen3.6-27B is a 27B dense model under Apache-2.0. Q4 is 27 × 0.5 × 1.2 + 2 = 18.2 GB. On 5 October 2026 Unsloth’s Q4_K_M file was 16.82 GB and UD-Q4_K_XL was 17.61 GB. Ollama listed qwen3.6:27b at 18–19 GB. A 24 GB GPU fits that Q4. A 16 GB GPU does not. Qwen3.6-35B-A3B is 35B total and 3B active. Count the total: 35 × 0.5 × 1.2 + 2 = 23.0 GB. Unsloth’s UD-Q4_K_M file was 22.13 GB, and Ollama listed qwen3.6:35b at 23–24 GB. A 24 GB card can load that file with almost no extra context. A 32 GB card is the comfortable discrete tier. Do not pull qwen3.6:latest on 16 GB: that tag was the 35B size.

How much memory does Mellum2.1 need?

JetBrains lists Mellum2.1 Thinking as 12B total and 2.5B active, Apache-2.0. Count the total: 12 × 0.5 × 1.2 + 2 = 9.2 GB at Q4. On 11 October 2026 the community Q4_K_M file was 8,819,358,432 bytes (8.82 GB). A 12 GB GPU fits the formula. An 8 GB GPU does not. Q8 is 16.4 GB and misses a 16 GB card. The official card still says Ollama and LM Studio builds are coming soon, so there is no ollama run tag on this page. Weights: https://huggingface.co/JetBrains/Mellum2.1-12B-A2.5B-Thinking

How much memory does Qwen3.8-Flash-Next need?

Count 125B plus the 51B n-gram table plus the 4B MTP head, which is 180B. Q4 is 180 × 0.5 × 1.2 + 2 = 110 GB. On 9 October 2026 Unsloth’s UD-Q4_K_XL shards summed to 111.33 GB and UD-IQ4_XS summed to 93.68 GB. A 32 GB RTX 5090 does not fit either file. A 128 GB unified box fits UD-IQ4_XS with room and holds UD-Q4_K_XL only with a short context. Qwen Cloud’s Qwen3.8-Flash API is not this file. The Ollama tag qwen3.8:27b is the 27B model, not Flash-Next.

How much memory does Liquid d1-3B need?

Liquid’s card lists 3.12B total parameters. The SigLIP2 vision encoder is inside that total, so do not add 400M on top. Q4 is 3.12 × 0.5 × 1.2 + 2 = 3.9 GB. Q8 is 3.12 × 1.2 + 2 = 5.7 GB. BF16 is 3.12 × 2.4 + 2 = 9.5 GB. On 12 October 2026 the GGUF repo Content-Length was Q4_K_M 1,674,456,672 bytes, Q8_0 2,874,781,280 bytes, and BF16 5,403,160,160 bytes. Those files were not re-fetched on 13 October. They are smaller than the formula because the formula adds 1.2 and 2 GB. The published command is llama-server -hf LiquidAI/d1-3B-GGUF:Q8_0, then POST /v1/systemone. There is no official ollama run tag. d1 is a decision model, not a chat model. d1-omni-600M is 587M total, and Q4 is 0.587 × 0.5 × 1.2 + 2 = 2.4 GB. Weights: https://huggingface.co/LiquidAI/d1-3B

Where do Granite 4.2 3B, 8B, and 30B fit?

IBM’s cards list 3B, 8B, and 30B, Apache-2.0. Official GGUF sizes on 5 October 2026: granite-4.2-3b Q4_K_M 2.24 GB, granite-4.2-8b Q4_K_M 5.35 GB and Q8_0 9.35 GB, granite-4.2-30b Q4_K_M 17.72 GB. Our VRAM formula is higher because it adds the 1.2 factor and 2 GB: 3.8 GB, 6.8 GB, and 20.0 GB at Q4. An 8 GB card fits the 3B and the 8B Q4 file. It does not fit the 8B Q8 file. A 16 GB card does not fit the 30B Q4 file. A 24 GB card does. Ollama tags are granite4.2:3b (2.2 GB), granite4.2:8b (5.3 GB), and granite4.2:30b (18 GB).

How much memory does LFM2.5-24B-A2B need?

Count 24.0B total, not the 2.45B active count. Q4 is 24 × 0.5 × 1.2 + 2 = 16.4 GB and misses a 16 GB GPU. Q5 is 20.0 GB and fits 24 GB. Q8 is 24 × 1.2 + 2 = 30.8 GB and fits 32 GB with about 1 GB left. BF16 is 59.6 GB and fits 128 GB unified. On 13 October 2026 the Q4_K_M file was 14,526,258,464 bytes and the Q8_0 file was 25,493,732,640 bytes. The command is llama-cli -hf LiquidAI/LFM2.5-24B-A2B-GGUF. There is no ollama run tag. ollama run lfm2.5 is the 8B model, whose Q4 is 7.0 GB. Weights: https://huggingface.co/LiquidAI/LFM2.5-24B-A2B

How much memory does ColGrep-Agent-2B need?

The safetensors count is 2,516,756,480 parameters (2.52B). The name is 2B. It is a code-search agent, not a general chat model. Q4 is 2.51675648 × 0.5 × 1.2 + 2 = 3.5 GB. Q8 is 2.51675648 × 1.2 + 2 = 5.0 GB. Both fit an 8 GB GPU. BF16 is 8.0 GB and is the edge of 8 GB. On 13 October 2026 Q8_0 was 2,679,710,912 bytes. The README calls the default Q8 approximately 2.5 GB; quote the byte count. The install command is colgrep --install-agent. There is no ollama run tag. Weights: https://huggingface.co/lightonai/colgrep-agent-2B

How much memory does Reflection Beam need?

Count the total, not the 23.4B active count. The BF16 safetensors total on 17 October 2026 was 501,267,612,352 parameters (501.3B). Q4 is 501.3 × 0.5 × 1.2 + 2 = 302.8 GB. That misses 128 GB and 256 GB. Unsloth’s UD-Q4_K_XL files summed to 306,533,349,412 bytes (306.5 GB). The smallest Unsloth file, UD-IQ1_S, summed to 103,059,961,380 bytes (103.1 GB): it can sit on 128 GB and does not fit 96 GB. NVFP4 safetensors summed to 293,634,877,368 bytes (273.5 GiB) and are a Blackwell checkpoint, not a Mac file. ollama run beam is the cloud tag beam:cloud, not a local download. Weights: https://huggingface.co/reflection/Beam-1.0-501B-A23B

Where do Granite Switch 4.1 8B and 30B fit?

These are Apache-2.0 bundles of a Granite 4.1 base, two adapters, and a speech encoder, released 14 October 2026. Safetensors totals that day: 8,776,400,896 (8.78B) and 29,989,814,272 (29.99B). Q4 is 7.3 GB and 20.0 GB. The 8B fits an 8 GB GPU. Its Q8 is 12.5 GB and misses 12 GB. The 30B misses 16 GB and fits 24 GB. There is no ollama run granite-switch tag. ollama run granite4.1:8b is the older base model, not this bundle. Weights: https://huggingface.co/ibm-granite/granite-switch-4.1-8b and https://huggingface.co/ibm-granite/granite-switch-4.1-30b

How much memory does NVIDIA Dory 1.0 4B need?

The BF16 card lists 3,975,229,440 parameters (3.98B). Q4 is 3.98 × 0.5 × 1.2 + 2 = 4.4 GB. Q8 is 6.8 GB. Both fit 8 GB. The published Q5_K_M GGUF was 3,673,288,864 bytes on 17 October 2026. There is no Ollama tag. The card’s local path is a llama.cpp fork, not ollama run. Weights: https://huggingface.co/nvidia/NVIDIA-Nemotron-Labs-Dory1.0-4B-GGUF

Embed This Calculator

Add the VRAM calculator to your blog or documentation site. Copy the snippet below — no signup required.

<iframe src="https://llmhardware.io/embed/vram-calculator" width="100%" height="420" style="border:none;border-radius:10px;" loading="lazy" title="LLM VRAM Calculator"></iframe>
<p><a href="https://llmhardware.io/guides" target="_blank" rel="noopener">Calculator by LLMHardware.io</a></p>

Keep the credit line. Calculator by LLMHardware.io should stay linked to the guide hub. The embed at /embed/vram-calculator is noindex. This page, /vram-calculator, is the indexable copy. The iframe footer says “Powered by llmhardware.io” and links to /guides.

Related Guides

Already know the card and the model? The Can I run it? checker shows the Q4, Q8 and FP16 verdict for one GPU or Mac with a shareable link.

Quick Reference & Citations

Agent stacks add a browser, a tool process, and a longer KV cache on top of the weights. Those extras are not inside the 1.2 factor. The VRAM guide for local agents walks 7B, 14B, 27B, 30B, 32B, and 70B. For the 111.33 GB Q4 file, use the Qwen3.8-Flash-Next hardware page and the Strix Halo guide. LFM2.5-24B-A2B Q4 is 16.4 GB: the fit table is on the LFM hardware page. ColGrep-Agent-2B Q8 is 5.0 GB and is covered on the local coding guide.

Citeable facts

Key fact: An 8B model at Q4_K_M needs 6.8 GB at a short context.

How we got it: 8 × 0.5 × 1.2 + 2. Bytes per parameter: FP16 = 2, Q8 = 1, Q5_K_M = 0.625, Q4_K_M = 0.5. Same formula as llms.txt.

Checked:

Key fact: A 32B model at Q4_K_M needs 21.2 GB, so a 24 GB GPU fits a short context and a 16 GB GPU does not.

How we got it: 32 × 0.5 × 1.2 + 2. The 1.2 factor is a short-context allowance, not a 32K KV-cache estimate.

Checked:

Key fact: Qwen3.8-27B at Q4_K_M needs 18.2 GB. Gemma 4 26B-A4B, counted at its 25.2B total, needs 17.1 GB. Neither is a 16 GB fit once KV cache starts.

How we got it: 27 × 0.5 × 1.2 + 2 = 18.2. 25.2 × 0.5 × 1.2 + 2 = 17.1. File sizes checked on Unsloth and Google GGUF repos the same day: Qwen UD-Q4_K_XL 17.6 GB, Gemma UD-Q4_K_XL 17.01 GB, Google QAT Q4_0 14.44 GB.

Checked:

Key fact: A 70B model at Q4_K_M needs 44 GB and does not fit one 32 GB RTX 5090. Qwen3.8-Flash-Next at the full 180B count needs 110 GB. Mellum2.1 at Q4 needs 9.2 GB and does fit a 12 GB GPU.

How we got it: 70 × 0.5 × 1.2 + 2 = 44. 180 × 0.5 × 1.2 + 2 = 110. 12 × 0.5 × 1.2 + 2 = 9.2. Unsloth UD-Q4_K_XL for Flash-Next summed to 111.33 GB on 2026-10-09. ASUS TUF RTX 5090 OC ASIN B0DS2X13PH is 32 GB. On 17 October 2026 the page still said currently unavailable, with See All Buying Options and no new buy box.

Checked:

Key fact: Beam at Q4 needs 302.8 GB and does not fit 128 GB. Granite Switch 4.1 8B at Q4 needs 7.3 GB and fits 8 GB. Dory 1.0 4B at Q4 needs 4.4 GB and fits 8 GB.

How we got it: 501.3 × 0.5 × 1.2 + 2 = 302.8. 8.78 × 0.5 × 1.2 + 2 = 7.3. 3.98 × 0.5 × 1.2 + 2 = 4.4. Hugging Face safetensors counts on 2026-10-17. Unsloth Beam UD-IQ1_S summed to 103,059,961,380 bytes. ollama run beam is beam:cloud.

Checked:

Key fact: Liquid d1-3B is 3.12B total. Q4 is 3.9 GB and fits an 8 GB GPU. The Q4_K_M file was 1,674,456,672 bytes.

How we got it: 3.12 × 0.5 × 1.2 + 2 = 3.87, shown as 3.9. HEAD Content-Length on LiquidAI/d1-3B-GGUF on 2026-10-12, not re-fetched on 13 October. Command: llama-server -hf LiquidAI/d1-3B-GGUF:Q8_0. No official ollama run tag. d1-omni Q4 is 2.4 GB from 0.587B total.

Checked:

Key fact: LFM2.5-24B-A2B at Q4 needs 16.4 GB and misses 16 GB. Q8 needs 30.8 GB. ColGrep-Agent-2B at Q8 needs 5.0 GB and fits 8 GB.

How we got it: 24.0 × 0.5 × 1.2 + 2 = 16.4. 24.0 × 1.2 + 2 = 30.8. ColGrep safetensors count 2,516,756,480. 2.51675648 × 1.2 + 2 = 5.02, shown as 5.0. Q4_K_M file for the 24B was 14,526,258,464 bytes on 2026-10-13. ColGrep Q8_0 was 2,679,710,912 bytes the same day.

Checked:

Key fact: Qwen3.6-27B at Q4 needs 18.2 GB. Qwen3.6-35B-A3B, counted at 35B total, needs 23.0 GB. Granite 4.2-30B at Q4 needs 20.0 GB, and IBM’s Q4_K_M file is 17.72 GB.

How we got it: 27 × 0.5 × 1.2 + 2 = 18.2. 35 × 0.5 × 1.2 + 2 = 23.0. 30 × 0.5 × 1.2 + 2 = 20.0. Unsloth files the same day: Qwen3.6-27B Q4_K_M 16.82 GB, Qwen3.6-35B-A3B UD-Q4_K_M 22.13 GB. IBM granite-4.2-8b Q4_K_M is 5.35 GB, so an 8 GB card fits that file and does not fit either Qwen3.6 Q4.

Checked:

Methodology — parameter math, quantization bytes, and the source list.

Sources & last reviewed

Last reviewed by the LLM Hardware team. The date changes only when the numbers or sources on this page change.

Model cards (parameter counts)

Quantization and runtime docs

GPU and Mac memory specs

VRAM estimates use params × bytes per parameter × 1.2 + 2 GB (Q4_K_M ≈ 0.5 bytes), explained on the methodology page. Found a mismatch? Tell us on the contact page.