How much VRAM does DeepSeek-R1-Distill-Qwen-7B need?

Q4_K_M is exactly 4,683,073,216 bytes (4.36 GiB) in weights. Add the KV cache, which depends on context length, plus roughly half a gigabyte of runtime overhead.

How large is DeepSeek-R1-Distill-Qwen-7B's KV cache?

1.75 GiB at 32K context with an f16 cache, computed per layer from the model's architecture. Quantizing the cache to q8_0 roughly halves it.

deepseek-ai · text

DeepSeek-R1-Distill-Qwen-7B

deepseek-ai/DeepSeek-R1-Distill-Qwen-7B

DeepSeek-R1-Distill-Qwen-7B at Q4_K_M is exactly 4,683,073,216 bytes (4.36 GiB / 4.68 GB) — an effective 4.919 bits per weight, not the nominal 4. Its KV cache at 32K is 1.75 GiB.

From the file· summed from 1 file(s)From the file· KV per layer

Parameters

7.6B

Architecture

qwen2

28 layers

Context

131,072

native (config.json)

License

—

Shipped quantizations

● exact bytes, summed from published files

Quant	Size●	Exact bytes●	Effective bpw●	Tensors●	Publisher
IQ2_M	2.59 GiB	2,780,342,240	2.921	—	bartowski
Q2_K	2.81 GiB	3,015,939,808	3.168	—	unsloth
Q2_K	2.81 GiB	3,015,940,064	3.168	—	bartowski
Q2_K_L	2.93 GiB	3,143,673,568	3.302	—	unsloth
IQ3_XS	3.12 GiB	3,346,255,840	3.515	—	bartowski
Q3_K_S	3.25 GiB	3,492,368,352	3.669	—	bartowski
Q2_K_L	3.30 GiB	3,548,164,064	3.727	—	bartowski
IQ3_M	3.33 GiB	3,574,011,872	3.754	—	bartowski
Q3_K_M	3.55 GiB	3,808,390,880	4.001	339	unsloth
Q3_K_M	3.55 GiB	3,808,391,136	4.001	339	bartowski
Q3_K_L	3.81 GiB	4,088,458,944	4.295	—	lmstudio-community
Q3_K_L	3.81 GiB	4,088,459,232	4.295	—	bartowski
IQ4_XS	3.93 GiB	4,218,472,416	4.431	339	bartowski
IQ4_NL	4.13 GiB	4,437,813,216	4.662	—	bartowski
Q4_0	4.14 GiB	4,444,121,056	4.668	339	bartowski
Q4_K_S	4.15 GiB	4,457,768,928	4.683	—	bartowski
Q4_K_M	4.36 GiB	4,683,073,216	4.919	339	lmstudio-community
Q4_K_M	4.36 GiB	4,683,073,248	4.919	339	unsloth
Q4_K_M	4.36 GiB	4,683,073,504	4.919	—	bartowski
Q4_1	4.54 GiB	4,873,283,552	5.119	—	bartowski
Q4_K_L	4.74 GiB	5,087,563,744	5.344	—	bartowski
Q5_K_S	4.95 GiB	5,315,176,416	5.583	—	bartowski
Q5_K_M	5.07 GiB	5,444,830,944	5.720	339	unsloth
Q5_K_M	5.07 GiB	5,444,831,200	5.720	—	bartowski
Q5_K_L	5.38 GiB	5,781,196,768	6.073	—	bartowski
Q6_K	5.82 GiB	6,254,198,464	6.570	339	lmstudio-community
Q6_K	5.82 GiB	6,254,198,496	6.570	339	unsloth
Q6_K	5.82 GiB	6,254,198,752	6.570	339	bartowski
Q6_K_L	6.07 GiB	6,518,181,856	6.847	—	bartowski
Q8_0	7.54 GiB	8,098,524,864	8.507	339	lmstudio-community
Q8_0	7.54 GiB	8,098,524,896	8.507	339	unsloth
Q8_0	7.54 GiB	8,098,525,152	8.507	—	bartowski
F16	14.19 GiB	15,237,852,896	16.007	339	unsloth
F16	14.19 GiB	15,237,853,152	16.007	339	bartowski
F32	28.38 GiB	30,468,419,264	32.006	—	bartowski

KV cache by context

computed per layer

Context	KV cache (f16)●	Flat formula	Overstated by	Full / windowed / recurrent
4,096	0.22 GiB	0.22 GiB	—	28 / 0 / 0
8,192	0.44 GiB	0.44 GiB	—	28 / 0 / 0
16,384	0.88 GiB	0.88 GiB	—	28 / 0 / 0
32,768	1.75 GiB	1.75 GiB	—	28 / 0 / 0
65,536	3.50 GiB	3.50 GiB	—	28 / 0 / 0
131,072	7.00 GiB	7.00 GiB	—	28 / 0 / 0

Compare with

same modality, comparable size

vs gemma-4-E4B-it vs Qwen3-4B vs Qwen3-8B vs HyperCLOVAX-SEED-Text-Instruct-1.5B vs Llama-3.2-1B-Instruct vs llama-3-youko-8b All alternatives →Will it fit on my card? →

Why other calculators give a different number

A parameters × bits ÷ 8 estimate puts Q4_K_M at roughly 3.99 GiB. The real file is 4.36 GiB, because a quantization is a mixture and some tensors are always kept at higher precision.

Architecture

from config.json

Layers

Attention heads

KV heads

Head dim

128

Hidden size

3584

Vocab

152,064

Sliding window

4096

SWA period

—

MLA

Experts

—

Experts per token

—

use_sliding_window

false

This model declares a sliding window but sets use_sliding_window: false, so the window is not applied. Honouring the field without the flag understates KV for the whole family.

Questions people ask

How much VRAM does DeepSeek-R1-Distill-Qwen-7B need?: Q4_K_M is exactly 4,683,073,216 bytes (4.36 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
How large is DeepSeek-R1-Distill-Qwen-7B's KV cache?: 1.75 GiB at 32K context with an f16 cache, computed per layer. Quantizing the cache to q8_0 roughly halves it, which is often the difference between a context length fitting and not.
Which quantization of DeepSeek-R1-Distill-Qwen-7B should I use?: Q4_K_M is the usual default. Pick the largest quantization that fits your card at the context you actually need — the table above gives exact sizes for every one published.