deepseek-ai · text

deepseek-coder-33b-base

deepseek-ai/deepseek-coder-33b-base

deepseek-coder-33b-base at Q4_K_M is exactly 19,940,659,168 bytes (18.57 GiB / 19.94 GB) — an effective 4.784 bits per weight, not the nominal 4. Its KV cache at 32K is 7.75 GiB.

From the file· summed from 1 file(s)From the file· KV per layer
Parameters
33.3B
Architecture
llama
62 layers
Context
16,384
native (config.json)
License
other

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q2_K13.07 GiB14,028,664,8003.366TheBloke
Q3_K_S13.43 GiB14,421,901,2803.460TheBloke
Q3_K_M14.97 GiB16,074,928,0963.857TheBloke
Q3_K_L16.35 GiB17,560,367,0724.213TheBloke
Q4_017.53 GiB18,819,440,6084.515TheBloke
Q4_K_S17.59 GiB18,891,923,4244.533TheBloke
Q4_K_M18.57 GiB19,940,659,1684.784TheBloke
Q5_021.38 GiB22,958,301,1525.508TheBloke
Q5_K_S21.38 GiB22,958,301,1525.508TheBloke
Q5_K_M21.92 GiB23,535,898,5925.647TheBloke
Q6_K25.48 GiB27,355,840,4806.564TheBloke
Q8_033.00 GiB35,430,879,2008.501TheBloke

KV cache by context

computed per layer
ContextKV cache (f16)Flat formulaOverstated byFull / windowed / recurrent
4,0960.97 GiB0.97 GiB62 / 0 / 0
8,1921.94 GiB1.94 GiB62 / 0 / 0
16,3843.88 GiB3.88 GiB62 / 0 / 0
32,7687.75 GiB7.75 GiB62 / 0 / 0
65,53615.50 GiB15.50 GiB62 / 0 / 0
131,07231.00 GiB31.00 GiB62 / 0 / 0

Compare with

same modality, comparable size

Will it run on your card?

full quant x context sweep

Why other calculators give a different number

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

Architecture

from config.json
Layers
62
Attention heads
56
KV heads
8
Head dim
128
Hidden size
7168
Vocab
32,256
Sliding window
none
SWA period
MLA
no
Experts
Experts per token
use_sliding_window

Questions people ask

How much VRAM does deepseek-coder-33b-base need?
Q4_K_M is exactly 19,940,659,168 bytes (18.57 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-coder-33b-base's KV cache?
7.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-coder-33b-base 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.