CausalLM · text

14B

CausalLM/14B

14B at Q4_0 is exactly 8,176,548,512 bytes (7.62 GiB / 8.18 GB) — an effective 4.617 bits per weight, not the nominal 4. Its KV cache at 32K is 25.00 GiB.

From the file· summed from 1 file(s)From the file· KV per layer
Parameters
14.2B
Architecture
llama
40 layers
Context
8,192
native (config.json)
License
wtfpl

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q4_07.62 GiB8,176,548,5124.617TheBloke
Q4_18.39 GiB9,013,279,3925.090TheBloke
Q5_09.17 GiB9,850,010,2725.562TheBloke
Q5_19.95 GiB10,686,741,1526.035TheBloke
Q8_014.02 GiB15,058,954,9128.504TheBloke

KV cache by context

computed per layer
ContextKV cache (f16)Flat formulaOverstated byFull / windowed / recurrent
4,0963.13 GiB3.13 GiB40 / 0 / 0
8,1926.25 GiB6.25 GiB40 / 0 / 0
16,38412.50 GiB12.50 GiB40 / 0 / 0
32,76825.00 GiB25.00 GiB40 / 0 / 0
65,53650.00 GiB50.00 GiB40 / 0 / 0
131,072100.00 GiB100.00 GiB40 / 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_0 at roughly 7.42 GiB. The real file is 7.62 GiB, because a quantization is a mixture and some tensors are always kept at higher precision.

Architecture

from config.json
Layers
40
Attention heads
40
KV heads
40
Head dim
128
Hidden size
5120
Vocab
152,064
Sliding window
none
SWA period
MLA
no
Experts
Experts per token
use_sliding_window

Questions people ask

How much VRAM does 14B need?
Q4_0 is exactly 8,176,548,512 bytes (7.62 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
How large is 14B's KV cache?
25.00 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 14B 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.