danube3-500M needs about 1.2 GB of memory at Q4_K_M (a 0.3 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 5 quants, from 0.3 GB (Q4_K_M) to 1.0 GB (F16).
Danube 500M chat model in GGUF format
Danube 500M is a 0.514 billion‑parameter llama‑based model. It supports a 8192‑token context window and is released under the Apache‑2.0 license. The model is available in several llama.cpp quantizations.
Good at
- Chat‑style dialogue
- Lightweight inference
- Fast token generation
Limits
- No vision support
- Limited to 8192‑token context
- Requires GPU or CPU with enough VRAM
Best for
- Quick prototyping
- Embedded chatbots
- Low‑resource inference
Who it’s for. Developers needing a small, chat‑capable model that runs on modest hardware. The model is suitable for applications where speed and low memory footprint are priorities.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q4_K_M | 0.3 GB | 1.2 GB | Fits | Get file → | |
| Q5_K_M | 0.4 GB | 1.3 GB | Fits | Get file → | |
| Q6_K | 0.4 GB | 1.3 GB | Fits | Get file → | |
| Q8_0 | 0.5 GB | 1.4 GB | Fits | Get file → | |
| F16 | 1.0 GB | 1.9 GB | Fits | Get file → |
For 8 GB VRAM, use Q4_K_M (0.32 GB, ~1.2 GB VRAM) or Q5_K_M (0.37 GB, ~1.3 GB VRAM). If 12 GB VRAM is available, Q6_K (0.42 GB, ~1.3 GB VRAM) or Q8_0 (0.55 GB, ~1.4 GB VRAM) provide higher quality. F16 (1.03 GB, ~1.9 GB VRAM) offers the best quality but needs more memory.
What GPU do you need for danube3-500M?
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 (1.0 GB file, about 1.9 GB in use).
Which danube3-500M quant should you choose?
Q4_K_M is the usual starting point for danube3-500M: it balances file size and quality well. Here it is a 0.3 GB file.
The Q8_0 file is 0.5 GB, about 1.7 times the size of Q4_K_M. It keeps the weights closer to the original, which only matters if you have the memory to spare.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about danube3-500M
How much VRAM does danube3-500M need?
About 1.2 GB at Q4_K_M with an 8K context window. That is the 0.3 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 danube3-500M on an 8 GB GPU?
Yes, with F16: the 1.0 GB file needs about 1.9 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of danube3-500M GGUF?
It depends on the quant: Q4_K_M is 0.3 GB, Q5_K_M is 0.4 GB, Q6_K is 0.4 GB, Q8_0 is 0.5 GB, F16 is 1.0 GB.
What context length does danube3-500M support?
The GGUF header lists a trained context length of 8,192 tokens (8K). The KV cache grows with the context you use: about 0.4 GB at 8K and 0.4 GB at 8K.
Where can I download danube3-500M GGUF?
The files are on Hugging Face in the h2oai/h2o-danube3-500m-chat-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 danube3-500M 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 and Q5_K_M quantizations fit within 8 GB VRAM, using approximately 1.2–1.3 GB of memory at 8192 context.
Does this model support vision tasks?
No, the model has no vision capabilities and is designed solely for text generation.
What license applies to this model?
The model is released under the Apache‑2.0 license, allowing free use and modification.