H2O Danube3 500m Base 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 24 quants, from 0.1 GB (IQ1_S) to 0.4 GB (Q6_K).
H2O Danube3 500m Base – 500 M parameter Llama‑style model
H2O Danube3 500m Base is a 500 million parameter foundation model based on the Llama architecture. It supports a context length of 8 192 tokens and is released under the Apache‑2.0 license. The model is available in multiple GGUF quantizations for efficient inference.
Good at
- Text completion
- Prompt‑based generation
- Lightweight inference
Limits
- No vision support
- Limited to 8 192 token context
- Requires GPU for best performance
Best for
- Embedded devices with low VRAM
- Rapid prototyping of language tasks
- Educational demonstrations
Who it’s for. Developers and researchers needing a small, open‑source LLM for local deployment. The model is suitable for projects that require offline inference and a permissive license.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| IQ1_S | 0.1 GB | 1.0 GB | Fits | Get file → | |
| IQ1_M | 0.1 GB | 1.0 GB | Fits | Get file → | |
| IQ2_XXS | 0.2 GB | 1.1 GB | Fits | Get file → | |
| IQ2_XS | 0.2 GB | 1.1 GB | Fits | Get file → | |
| IQ2_S | 0.2 GB | 1.1 GB | Fits | Get file → | |
| IQ2_M | 0.2 GB | 1.1 GB | Fits | Get file → | |
| Q2_K | 0.2 GB | 1.1 GB | Fits | Get file → | |
| IQ3_XXS | 0.2 GB | 1.1 GB | Fits | Get file → | |
| IQ3_XS | 0.2 GB | 1.1 GB | Fits | Get file → | |
| IQ3_S | 0.2 GB | 1.1 GB | Fits | Get file → | |
| Q3_K_S | 0.2 GB | 1.1 GB | Fits | Get file → | |
| IQ3_M | 0.2 GB | 1.2 GB | Fits | Get file → | |
| Q3_K_M | 0.3 GB | 1.2 GB | Fits | Get file → | |
| Q3_K_L | 0.3 GB | 1.2 GB | Fits | Get file → | |
| IQ4_XS | 0.3 GB | 1.2 GB | Fits | Get file → | |
| Q4_0 | 0.3 GB | 1.2 GB | Fits | Get file → | |
| Q4_0 | 0.3 GB | 1.2 GB | Fits | Get file → | |
| Q4_0 | 0.3 GB | 1.2 GB | Fits | Get file → | |
| Q4_0 | 0.3 GB | 1.2 GB | Fits | Get file → | |
| Q4_K_S | 0.3 GB | 1.2 GB | Fits | Get file → | |
| Q4_K_M | 0.3 GB | 1.2 GB | Fits | Get file → | |
| Q5_K_S | 0.4 GB | 1.3 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 → |
For 4 GB VRAM, use IQ1_S or IQ1_M (file size 0.14 GB or 0.15 GB, memory ~1 GB). For 8 GB VRAM, IQ2_M or Q3_K_M (file size 0.20 GB or 0.26 GB, memory ~1.1–1.2 GB). For 16 GB VRAM, Q5_K_M or Q6_K (file size 0.37 GB or 0.42 GB, memory ~1.3 GB). Estimates are approximate.
What GPU do you need for H2O Danube3 500m Base?
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 Q6_K (0.4 GB file, about 1.3 GB in use).
Which H2O Danube3 500m Base quant should you choose?
Q4_K_M is the usual starting point for H2O Danube3 500m Base: it balances file size and quality well. Here it is a 0.3 GB file.
If memory is tight, the smallest file is IQ1_S at 0.1 GB, with the quality trade-offs that come with fewer bits. Use it only when memory is very tight. Expect a clear drop in quality, which is usually worse on small models and easier to live with on large ones.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about H2O Danube3 500m Base
How much VRAM does H2O Danube3 500m Base 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 H2O Danube3 500m Base on an 8 GB GPU?
Yes, with Q6_K: the 0.4 GB file needs about 1.3 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of H2O Danube3 500m Base GGUF?
It depends on the quant: IQ1_S is 0.1 GB, IQ1_M is 0.1 GB, IQ2_XXS is 0.2 GB, IQ2_XS is 0.2 GB, IQ2_S is 0.2 GB, IQ2_M is 0.2 GB and 18 more.
What context length does H2O Danube3 500m Base 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 H2O Danube3 500m Base GGUF?
The files are on Hugging Face in the mradermacher/h2o-danube3-500m-base-i1-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 H2O Danube3 500m Base 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 H2O Danube3 500m Base on 8 GB VRAM?
Yes, quantizations such as IQ2_M or Q3_K_M use about 1.1–1.2 GB of VRAM at 8 192 context length.
Does the model support image inputs?
No, the model has no vision capabilities.
What license applies to this model?
The model is released under the Apache‑2.0 license.