openai · audio asr

whisper-base

openai/whisper-base

whisper-base at Q4_K_M is exactly 58,870,848 bytes (0.05 GiB / 0.06 GB) — an effective 6.488 bits per weight, not the nominal 4.

From the file· summed from 1 file(s)From the file· KV per layer
Parameters
73M
Architecture
whisper
6 layers
Context
native (config.json)
License
apache-2.0

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q2_K0.03 GiB29,925,3463.298oxide-lab
Q3_K0.03 GiB37,095,1584.088oxide-lab
Q4_00.04 GiB42,225,0244.653oxide-lab
Q4_00.04 GiB46,471,0665.121oxide-lab
Q4_K0.04 GiB46,471,0665.121oxide-lab
Q4_10.04 GiB46,705,3125.147oxide-lab
Q4_10.05 GiB50,883,2585.607oxide-lab
Q5_K0.05 GiB55,295,4506.094oxide-lab
Q5_00.05 GiB55,295,4506.094oxide-lab
Q4_K_M0.05 GiB58,870,8486.488handy-computer
Q5_10.06 GiB59,707,6426.580oxide-lab
Q5_K_M0.06 GiB63,786,0487.029handy-computer
Q6_K0.06 GiB64,671,3587.127oxide-lab
Q6_K0.06 GiB67,865,6647.479handy-computer
Q8_00.07 GiB78,067,3288.603oxide-lab
Q8_00.08 GiB81,768,6029.011oxide-lab
Q8_00.08 GiB84,962,8809.363handy-computer
F160.14 GiB151,145,76016.657handy-computer
F320.27 GiB292,335,90432.216handy-computer

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 0.04 GiB. The real file is 0.05 GiB, because a quantization is a mixture and some tensors are always kept at higher precision.

Architecture

from config.json
Layers
6
Attention heads
KV heads
Head dim
Hidden size
Vocab
51,865
Sliding window
none
SWA period
MLA
no
Experts
Experts per token
use_sliding_window

Questions people ask

How much VRAM does whisper-base need?
Q4_K_M is exactly 58,870,848 bytes (0.05 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
Which quantization of whisper-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.