youtube audiobook title parser needs about 1.0 GB of memory at Q4_K_M (a 0.4 GB file) with an 8K context window, so it fits on a 4 GB GPU. Longer context needs more: at 32K tokens the KV cache alone adds about 0.4 GB.
Fine‑tuned Qwen2.5 model for parsing YouTube and audiobook titles
youtube‑audiobook‑title‑parser is a lightweight model based on Qwen/Qwen2.5‑0.5B‑Instruct. It extracts book title, author, and channel or show name from noisy titles and outputs structured JSON. The model handles multi‑delimiter patterns, Bengali script, and episode noise.
Good at
- Parsing noisy YouTube titles
- Extracting structured JSON
- Handling Bengali script
Limits
- No vision support
- Limited to 32,768 context tokens
- Apache‑2.0 license
Best for
- YouTube title parsing
- Audiobook metadata extraction
- Bengali literature formatting
Who it’s for. Developers building media metadata pipelines or content platforms that need structured information from YouTube or audiobook titles. The model is suitable for low‑resource environments due to its small size.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q4_K_M | 0.4 GB | 1.0 GB | Fits | Get file → |
The Q4_K_M quantized file is 0.4 GB and requires about 1 GB of VRAM at 8 k context. It is suitable for 8 GB VRAM setups. For larger VRAM budgets, higher precision quantizations are not listed.
What GPU do you need for youtube audiobook title parser?
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: the best quant that fits is Q4_K_M (0.4 GB file, about 1.0 GB in use).
Which youtube audiobook title parser quant should you choose?
Q4_K_M is the usual starting point for youtube audiobook title parser: it balances file size and quality well. Here it is a 0.4 GB file.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about youtube audiobook title parser
How much VRAM does youtube audiobook title parser need?
About 1.0 GB at Q4_K_M with an 8K context window. That is the 0.4 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 youtube audiobook title parser on an 8 GB GPU?
Yes, with Q4_K_M: the 0.4 GB file needs about 1.0 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of youtube audiobook title parser GGUF?
It depends on the quant: Q4_K_M is 0.4 GB.
What context length does youtube audiobook title parser support?
The GGUF header lists a trained context length of 32,768 tokens (32K). The KV cache grows with the context you use: about 0.1 GB at 8K and 0.4 GB at 32K.
Where can I download youtube audiobook title parser GGUF?
The files are on Hugging Face in the Salahin/youtube-audiobook-title-parser repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does youtube audiobook title parser 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 this model on 8 GB VRAM?
Yes, the Q4_K_M quantized file requires approximately 1 GB of VRAM at 8 k context, fitting comfortably in an 8 GB GPU.
Does this model support vision inputs?
No, the model is a language model and does not process images or other vision data.
What license applies to this model?
The model is released under the Apache‑2.0 license.