DeepSeek-R1 Distill Qwen 14B VRAM Requirements

14.77B parameters, 48 layers, 8 key-value heads. At Q4_K_M with a 8K context it needs 10.0 GB — 29 of 30 accelerators here can hold it.

Your setup

About 22.1 GB of that is usable for a model.

The usual choice for running locally. Quality loss is small and it is what most GGUF downloads default to.

8K tokens max 128K

Longer context costs memory linearly — this model uses 192.0 KB per token.

Running DeepSeek-R1 Distill Qwen 14B

10.0 GB of memory needed

Runs comfortably on a GeForce RTX 4090

Weights
7.7 GB
KV cache
1.5 GB
Headroom
12.1 GB
Max context
72K
10.0 GB used 22.1 GB usable

Where the memory goes

DeepSeek-R1 Distill Qwen 14B memory breakdown
Component Memory
Model weights (Q4_K_M)7.7 GB
KV cache at 8K tokens1.5 GB
Runtime allowance0.8 GB
Total10.0 GB

Weights are only half the question

A 14.8B model at Q4_K_M is 7.7 GB of weights. That part is fixed — it is the file on disk, and it does not change while the model runs. What changes is the key-value cache, which grows with every token of context you give it.

DeepSeek-R1 Distill Qwen 14B spends 192.0 KB per token. At 8K that is 1.5 GB, comfortably smaller than the weights. At its full 128K it is 24.0 GB — larger than the weights themselves. That is the trap: the model loads fine and then fills the card once a conversation gets long.

The reason the cache is as small as it is comes down to grouped-query attention. DeepSeek-R1 Distill Qwen 14B has 40 query heads but only 8 key-value heads, and the cache is sized by the latter. Calculators that use the query head count overstate it 5-fold, which is where the wildly pessimistic numbers people quote usually come from. Despite the name this is a Qwen2 architecture — R1's reasoning distilled into Qwen2.5 14B, not a DeepSeek model shape. That matters for planning: reasoning models spend thousands of tokens thinking before they answer, so the KV cache, not the weights, is what usually decides whether a long session fits. Its config carries a sliding_window value but sets use_sliding_window to false, so none is applied here.

By quantisation

DeepSeek-R1 Distill Qwen 14B memory by quantisation
Format Bits/weight Weights Total at 8K
FP16 / BF161627.5 GB29.8 GB
Q8_08.514.6 GB16.9 GB
Q6_K6.611.3 GB13.6 GB
Q5_K_M5.59.5 GB11.8 GB
Q4_K_M4.57.7 GB10.0 GB
Q3_K_M3.96.7 GB9.0 GB

By context length

DeepSeek-R1 Distill Qwen 14B memory by context length at Q4_K_M
Context KV cache Total
2K tokens0.4 GB8.9 GB
4K tokens0.8 GB9.3 GB
8K tokens1.5 GB10.0 GB
16K tokens3.0 GB11.5 GB
32K tokens6.0 GB14.5 GB
64K tokens12.0 GB20.5 GB
128K tokens24.0 GB32.5 GB

Will it run on your hardware?

Which accelerators run DeepSeek-R1 Distill Qwen 14B at Q4_K_M
Accelerator Memory Runs it Headroom Max context
GeForce RTX 509032 GBYes19.4 GB111K
GeForce RTX 409024 GBYes12.1 GB72K
GeForce RTX 309024 GBYes12.1 GB72K
GeForce RTX 508016 GBYes4.7 GB33K
GeForce RTX 4080 SUPER16 GBYes4.7 GB33K
GeForce RTX 5070 Ti16 GBYes4.7 GB33K
GeForce RTX 4070 Ti SUPER16 GBYes4.7 GB33K
GeForce RTX 507012 GBYes1.0 GB13K
GeForce RTX 407012 GBYes1.0 GB13K
GeForce RTX 3060 12GB12 GBYes1.0 GB13K
GeForce RTX 4060 Ti 16GB16 GBYes4.7 GB33K
GeForce RTX 308010 GBNo—4K
Radeon RX 7900 XTX24 GBYes12.1 GB72K
Radeon RX 7900 XT20 GBYes8.4 GB53K
Radeon RX 9070 XT16 GBYes4.7 GB33K
2× RTX 3090 (48 GB)48 GBYes34.2 GB128K
2× RTX 4090 (48 GB)48 GBYes34.2 GB128K
4× RTX 3090 (96 GB)96 GBYes78.3 GB128K
Mac (M4 Max, 64 GB)64 GBYes38.0 GB128K
Mac (M4 Max, 128 GB)128 GBYes86.0 GB128K
Mac (M4 Pro, 48 GB)48 GBYes26.0 GB128K
Mac (M4, 24 GB)24 GBYes6.1 GB40K
Mac (M3 Max, 128 GB)128 GBYes86.0 GB128K
Mac Studio (M2 Ultra, 192 GB)192 GBYes134.0 GB128K
Mac (M1 Max, 32 GB)32 GBYes11.4 GB69K
Mac (M2, 16 GB)16 GBYes0.7 GB12K
NVIDIA A100 40GB40 GBYes28.0 GB128K
NVIDIA A100 80GB80 GBYes66.0 GB128K
NVIDIA H100 80GB80 GBYes66.0 GB128K
NVIDIA L40S 48GB48 GBYes35.6 GB128K

At Q4_K_M with a 8K context. "Only just" means the model uses more than 95% of usable memory — it will load and then fall over as soon as anything else touches the device.

Frequently asked questions

How much VRAM does DeepSeek-R1 Distill Qwen 14B need?
About 10.0 GB at Q4_K_M with a 8K context — 7.7 GB of weights, 1.5 GB of key-value cache and a 0.8 GB runtime allowance. Unquantised at FP16 it needs 29.8 GB, which is why almost nobody runs it that way locally.
What GPU do I need to run DeepSeek-R1 Distill Qwen 14B?
The smallest card here that runs it is the GeForce RTX 5070 with 12 GB. 29 of the 30 accelerators on this page can hold it at the default quantisation. Apple Silicon deserves a mention: unified memory means a Mac can hold models no consumer graphics card can, though it runs them more slowly.
Does context length change how much memory DeepSeek-R1 Distill Qwen 14B needs?
Yes, and linearly. This model spends 192.0 KB per token of context, so 8K costs 1.5 GB and its full 128K costs 24.0 GB. On a model with a long context window the cache can end up larger than the quantised weights, which catches people out — the weights fit and then the conversation does not.
Why is the cache smaller than other calculators say?
Because DeepSeek-R1 Distill Qwen 14B uses grouped-query attention: 8 key-value heads shared across 40 query heads. The cache is sized by the key-value head count, not the query head count, so using the latter overstates it by a factor of 5. Plenty of calculators still get this wrong.
Which quantisation should I use?
Q4_K_M is the usual answer — the quality loss is small and it is what most GGUF downloads default to. Step up to Q5_K_M or Q6_K if you have memory to spare, since quality improves and the cost is modest. Q8_0 is effectively lossless at half the size of FP16. Drop to Q3_K_M only to fit a larger model that otherwise would not run at all; a bigger model at a rougher quantisation usually beats a smaller one at a fine quantisation.

Architecture: Hugging Face config.json. GGUF K-quant effective bit widths as produced by llama.cpp.

An estimate of memory, not a benchmark. It counts model weights, the key-value cache at the context you choose, and a fixed runtime allowance. Actual usage moves with the runtime, the batch size, whether flash attention is on, and how much the operating system has already taken from a shared memory pool. Treat a result within a gigabyte of your card's capacity as 'probably not' rather than 'just fits'.

Data on this page last verified . How these figures are calculated

    ↑↓ to move ↵ to open