Whisper is far smaller than a chat model, so the weights dominate and the cache barely registers. The interesting number is how much faster than real time it runs.

Computed from this tool’s default settings — whisper model and the rest as most people start. Change them below for your own case.
This Whisper size needs about 2.54 GB and fits RTX 4090 easily. Expect roughly 11× real time, so 60 minutes of audio in around 5.5 minutes.
Memory and real-time factor for each Whisper size, on your card.
This Whisper size needs about 2.54 GB and fits RTX 4090 easily. Expect roughly 11× real time, so 60 minutes of audio in around 5.5 minutes.
| Model | Parameters | Needs | On your card |
|---|---|---|---|
| tiny | 39M | 1.08 GB | Fits |
| base | 74M | 1.15 GB | Fits |
| small | 244M | 1.49 GB | Fits |
| medium | 769M | 2.54 GB | Fits |
| large | 1,550M | 4.10 GB | Fits |
Every input moves the result for a reason. This is what each one does and where to find the value for your own machine.
| Setting | Default | What it changes |
|---|---|---|
| Whisper model | medium — 769M | 5 options, from tiny — 39M to large — 1.55B. |
| Precision | float16 | 4 options, from float32 to 4-bit. |
| Your hardware | RTX 4090 · 24 GB | The machine the model runs on. Usable memory decides what fits and memory bandwidth decides how fast it runs, so this moves every figure below. |
| Audio to transcribe | 60 minutes | Your own figure in minutes, starting from 60. Change it to match what you actually run. |
The same calculation run at a range of settings, with everything else left at its default. These are computed by the tool itself, not written by hand.
| Whisper model | Fits | Weights | Your memory | Real-time factor |
|---|---|---|---|---|
| tiny — 39M | 1.08 GB | 0.08 GB | 22.1 GB | 215× |
| base — 74M | 1.15 GB | 0.15 GB | 22.1 GB | 114× |
| small — 244M | 1.49 GB | 0.49 GB | 22.1 GB | 34× |
| medium — 769M | 2.54 GB | 1.54 GB | 22.1 GB | 11× |
| large — 1.55B | 4.10 GB | 3.10 GB | 22.1 GB | 5× |
This Whisper size needs about 1.08 GB and fits RTX 4090 easily. Expect roughly 215× real time, so 60 minutes of audio in around 0.3 minutes.
No lookup tables and no invented constants. Here is the arithmetic, so you can check it against your own numbers.
Whisper is an encoder-decoder model and much smaller than a chat LLM, so weights dominate and the cache is negligible. Memory is parameters × precision ÷ 8, plus roughly a gigabyte of runtime and audio buffers.
Throughput is quoted as a real-time factor — how many minutes of audio are processed per minute of wall clock. It is estimated from memory bandwidth in the same way as text generation, so treat it as an order of magnitude rather than a benchmark.
These are well-founded engineering estimates, not benchmark results. Your quantisation, runtime and context length all move the real number, and usable memory is an assumption rather than a specification. See the full methodology for every assumption behind these figures.
The three situations that bring people to this calculation.
Pick a model size your card handles.
Estimate wall clock for hours of audio.
Find the largest Whisper that fits.
Four steps, no account, nothing leaves your browser.
Start at the top of the panel. Every figure recalculates as you change it — there is no submit button, because watching the number move is the point.
3 further settings: precision, your hardware, audio to transcribe. Defaults are the common case, so change only what differs for you.
The large figure answers the question. The table underneath shows how the answer changes across nearby settings, which is usually where the decision actually gets made.
The arithmetic is written out above. If a number looks wrong for your hardware, the assumptions are the first place to look — usable memory and quantisation are the two that vary most.
The questions people ask about this, answered without hedging.
Large is about 1.55B parameters, so roughly 3 GB at float16 plus a gigabyte of overhead. Medium is around half that, and the smaller sizes run almost anywhere.
Large for accuracy and accented or noisy audio; small or medium is often enough for clean English speech and runs several times faster.
Yes — whisper.cpp handles it well, especially at the smaller sizes. Expect slower than real time on large, which is fine for batch transcription.
How many minutes of audio are processed per minute of wall clock. A factor of 10 means an hour of audio transcribes in six minutes.
All 50 run on the same arithmetic, so answers across them agree.
Different ways of asking the same question, all resolved above.
Sizing is only half the problem. Model Radar takes your hardware and shows which models actually run on it, ranked by what they are good at — the same arithmetic as this page, applied to every model worth running.