Qwen3 Omni 30B A3B Captioner needs about 19.9 GB of memory at Q4_K_M (a 18.6 GB file) with an 8K context window, so it fits on a 24 GB GPU. Longer context needs more: at 32K tokens the KV cache alone adds about 3.2 GB.
Qwen3 Omni 30B A3B Captioner – audio‑only captioning model
Qwen3 Omni 30B A3B Captioner is a fine‑tuned audio captioning model based on Qwen3‑Omni‑30B‑A3B‑Instruct. It generates detailed, low‑hallucination captions for arbitrary audio inputs without text prompts. The model supports up to 65536 context tokens and is licensed under Apache‑2.0.
Good at
- Accurate multi‑speaker emotion detection
- Multilingual speech understanding
- Fine‑grained environmental sound description
Limits
- Single‑turn only – one audio input per inference
- No text prompts, only audio input and text output
- Experimental audio support in llama.cpp
Best for
- Audio captioning for media libraries
- Speech emotion analysis in call centers
- Environmental sound annotation for research
Who it’s for. Developers and researchers needing detailed audio captions without additional prompting. Suitable for applications that require accurate speaker emotion, multilingual speech, and complex sound recognition.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q4_K_M | 18.6 GB | 19.9 GB | Too big | Get file → |
The Q4_K_M quantization file is 18.56 GB and requires approximately 19.9 GB of VRAM at 8 k context. For systems with 8 GB VRAM, the model cannot be loaded. For 16 GB VRAM, it is feasible with some swapping. No other quants are available.
What GPU do you need for Qwen3 Omni 30B A3B Captioner?
These figures add the file size, an fp16 KV cache at an 8K context window (worked out from this model’s own header) and about 0.5 GB for the runtime. They are estimates, so leave a little headroom, and expect to use less context or a smaller quant if you are right at the limit.
- 4 GB VRAM: no quant fits at an 8K context.
- 6 GB VRAM: no quant fits at an 8K context.
- 8 GB VRAM: no quant fits at an 8K context.
- 12 GB VRAM: no quant fits at an 8K context.
- 16 GB VRAM: no quant fits at an 8K context.
- 24 GB VRAM: the best quant that fits is Q4_K_M (18.6 GB file, about 19.9 GB in use).
Which Qwen3 Omni 30B A3B Captioner quant should you choose?
Q4_K_M is the usual starting point for Qwen3 Omni 30B A3B Captioner: it balances file size and quality well. Here it is a 18.6 GB file.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about Qwen3 Omni 30B A3B Captioner
How much VRAM does Qwen3 Omni 30B A3B Captioner need?
About 19.9 GB at Q4_K_M with an 8K context window. That is the 18.6 GB file, plus the KV cache and roughly 0.5 GB of runtime overhead. Smaller quants need less and longer context needs more.
Can I run Qwen3 Omni 30B A3B Captioner on an 8 GB GPU?
Not at an 8K context. The smallest file needs about 19.9 GB, so you would need a larger GPU or CPU offloading.
What is the file size of Qwen3 Omni 30B A3B Captioner GGUF?
It depends on the quant: Q4_K_M is 18.6 GB.
What context length does Qwen3 Omni 30B A3B Captioner support?
The GGUF header lists a trained context length of 65,536 tokens (64K). The KV cache grows with the context you use: about 0.8 GB at 8K and 3.2 GB at 32K.
Where can I download Qwen3 Omni 30B A3B Captioner GGUF?
The files are on Hugging Face in the presencesw/Qwen3-Omni-30B-A3B-Captioner-GGUF repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does Qwen3 Omni 30B A3B Captioner use?
Hugging Face lists the license as apache-2.0. Licenses can differ between the quantized files and the original model, so check the repository and the base model before commercial use.
Can I run Qwen3 Omni 30B A3B Captioner on 8 GB VRAM?
No. The Q4_K_M quant requires about 19.9 GB VRAM at 8 k context, exceeding 8 GB.
Does the model support text prompts?
No. It accepts only one audio input per inference and outputs text captions.
Is the audio support stable in llama.cpp?
Audio support is experimental; use a recent llama.cpp build with multimodal support.