DanTagGen alpha needs about 1.7 GB of memory at Q8_0 (a 0.4 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 3 quants, from 0.3 GB (Q6_K) to 0.8 GB (F16).
DanTagGen alpha – a 400M param LLaMA model for Danbooru tag generation
DanTagGen alpha is a 0.39 billion parameter LLaMA‑based model trained from scratch. It is designed for generating tags for Danbooru images and can be run with llama.cpp or llama‑cpp‑python. The model is available in FP16, Q8_0, and Q6_K quantizations.
Good at
- Fast inference with llama.cpp
- Danbooru tag generation
- Small 400M parameter size
Limits
- No vision support
- Limited to 512‑token context
- OpenRail license restricts commercial use
Best for
- Generating tags for image datasets
- Automating metadata for art communities
- Batch tagging workflows
Who it’s for. Developers and researchers needing a lightweight Danbooru tag generator. The model is suitable for local inference on modest GPUs and can be integrated into web interfaces or batch pipelines.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q6_K | 0.3 GB | 0.9 GB | Fits | Get file → | |
| Q8_0 | 0.4 GB | 1.0 GB | Fits | Get file → | |
| F16 | 0.8 GB | 1.3 GB | Fits | Get file → |
For 8 GB VRAM, use the Q6_K quantized file (0.32 GB, ~1.6 GB memory at 8k context). If 12 GB VRAM is available, Q8_0 (0.42 GB, ~1.7 GB memory) offers higher precision. The FP16 model (0.79 GB, ~2.1 GB memory) requires the most memory.
What GPU do you need for DanTagGen alpha?
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 F16 (0.8 GB file, about 2.1 GB in use).
Which DanTagGen alpha quant should you choose?
Q8_0 (0.4 GB) is the middle option in this repository. Close to lossless. It costs roughly twice the memory of a 4-bit file, so it suits cases where you have plenty of VRAM.
If memory is tight, the smallest file is Q6_K at 0.3 GB, with the quality trade-offs that come with fewer bits. Very close to the original quality for most uses, at a clearly larger size than 4-bit.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about DanTagGen alpha
How much VRAM does DanTagGen alpha need?
About 1.7 GB at Q8_0 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 DanTagGen alpha on an 8 GB GPU?
Yes, with F16: the 0.8 GB file needs about 2.1 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of DanTagGen alpha GGUF?
It depends on the quant: Q6_K is 0.3 GB, Q8_0 is 0.4 GB, F16 is 0.8 GB.
What context length does DanTagGen alpha support?
The GGUF header lists a trained context length of 512 tokens (512). The KV cache grows with the context you use: about 0.8 GB at 8K and 0.1 GB at 512.
Where can I download DanTagGen alpha GGUF?
The files are on Hugging Face in the KBlueLeaf/DanTagGen-alpha repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does DanTagGen alpha use?
Hugging Face lists the license as openrail. 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 DanTagGen alpha on 8 GB VRAM?
Yes, the Q6_K quantized model uses about 1.6 GB of VRAM at 8k context, fitting comfortably in an 8 GB GPU.
Does this model support image input?
No, DanTagGen alpha is a text‑only model and does not process images directly.
What license applies to this model?
The model is released under the OpenRail license, which allows non‑commercial use and requires attribution.