FunAudioLLM · audio asr

Fun-ASR-MLT-Nano-2512

FunAudioLLM/Fun-ASR-MLT-Nano-2512

Fun-ASR-MLT-Nano-2512 at Q4_K_M is exactly 556,975,168 bytes (0.52 GiB / 0.56 GB) — an effective 5.370 bits per weight, not the nominal 4.

From the file· summed from 1 file(s)
Parameters
830M
Architecture
funasr_nano
Context
—
native (config.json)
License
other

Shipped quantizations

● exact bytes, summed from published files
QuantSize●Exact bytes●Effective bpw●Tensors●Publisher
Q4_K_M0.52 GiB556,975,1685.370—handy-computer
Q5_K_M0.59 GiB631,129,1526.085—handy-computer
Q6_K0.64 GiB690,744,3846.659—handy-computer
Q8_00.83 GiB891,271,2328.593—handy-computer
F161.55 GiB1,667,504,19216.076—handy-computer
BF161.55 GiB1,667,504,19216.076—handy-computer

Compare with

same modality, comparable size
vs nemotron-3.5-asr-streaming-0.6bvs parakeet-unified-en-0.6bvs parakeet-tdt-0.6b-v3vs whisper-mediumvs whisper-large-v3vs canary-180m-flashAll 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 Q4_K_M at roughly 0.43 GiB. The real file is 0.52 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 Fun-ASR-MLT-Nano-2512 need?
Q4_K_M is exactly 556,975,168 bytes (0.52 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
Which quantization of Fun-ASR-MLT-Nano-2512 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.