microsoft · audio asr

VibeVoice-Large

microsoft/VibeVoice-Large

VibeVoice-Large at Q3_K is exactly 6,166,410,816 bytes (5.74 GiB / 6.17 GB) — an effective 5.280 bits per weight, not the nominal 3.

From the file· summed from 1 file(s)
Parameters
9.3B
Architecture
vibevoice-asr
Context
—
native (config.json)
License
mit

Shipped quantizations

● exact bytes, summed from published files
QuantSize●Exact bytes●Effective bpw●Tensors●Publisher
Q3_K5.74 GiB6,166,410,8165.280—cstr
Q4_K6.73 GiB7,225,646,2726.187—cstr
Q4_06.73 GiB7,225,646,2726.187—cstr
Q5_K7.66 GiB8,222,675,1367.040—cstr
Q6_K8.64 GiB9,282,214,7207.948—cstr
Q8_010.44 GiB11,213,761,7289.601—cstr
F1617.41 GiB18,691,478,11216.004—cstr

Compare with

same modality, comparable size
vs nemotron-3.5-asr-streaming-0.6bvs parakeet-unified-en-0.6bvs cohere-transcribe-03-2026vs parakeet-tdt-0.6b-v3vs whisper-mediumvs Voxtral-Mini-4B-Realtime-2602All alternatives →Will it fit on my card? →

Will it run on your card?

full quant x context sweep
By VRAM:8GB12GB16GB24GB32GB48GB
Radeon RX 6500 XT 4GBGeForce RTX 3050 6GBGeForce RTX 5050 8GBGeForce RTX 3080 10GBGeForce RTX 2080 Ti 11GBGeForce RTX 5070 12GBGeForce RTX 5060 Ti 16GBApple M3 Pro 18GBGeForce RTX 3080 Ti 20GBGeForce RTX 5090 D V2 24GBGeForce RTX 5090 D 32GBApple M5 Max 36GBApple M5 Pro 48GBApple M5 Max 64GBApple M3 Ultra 96GBApple M5 Max 128GBApple M2 Ultra 192GBApple M3 Ultra 256GBApple M3 Ultra 512GB

Why other calculators give a different number

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

Architecture

Architecture unavailable — this repository is gated and no ungated mirror was found. Exact file sizes above are still authoritative; only the KV math needs the config.

Questions people ask

How much VRAM does VibeVoice-Large need?
Q3_K is exactly 6,166,410,816 bytes (5.74 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
Which quantization of VibeVoice-Large 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.