QwenDGAF Coder 0.5B 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. This repository has 4 quants, from 0.4 GB (Q4_K_M) to 1.0 GB (BF16). Longer context needs more: at 32K tokens the KV cache alone adds about 0.4 GB.
Ultra‑compact 0.5B code model for local inference
QwenDGAF‑Coder‑0.5B is a 0.49B parameter model fine‑tuned from Qwen2.5‑Coder‑0.5B‑Instruct. It runs in GGUF format and supports code generation, roleplay, and tool usage. The model is lightweight and fast, suitable for microcontrollers and low‑RAM devices.
Good at
- Code generation
- Code reasoning
- Tool usage
Limits
- No vision support
- Requires 8,192 token context
- Apache‑2.0 license
Best for
- Local code assistant on Raspberry Pi
- Fast prototyping on phones
- Embedded development tools
Who it’s for. Developers needing a quick, local code assistant without heavy GPU resources. The model is ideal for edge devices and low‑power environments where speed and small footprint are priorities.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q4_K_M | 0.4 GB | 1.0 GB | Fits | Get file → | |
| Q6_K | 0.5 GB | 1.1 GB | Fits | Get file → | |
| Q8_0 | 0.5 GB | 1.1 GB | Fits | Get file → | |
| BF16 | 1.0 GB | 1.6 GB | Fits | Get file → |
For 8 GB VRAM, Q4_K_M (~0.4 GB) uses ~1 GB memory at 8 k context, Q6_K (~0.51 GB) uses ~1.1 GB, and Q8_0 (~0.53 GB) also uses ~1.1 GB. BF16 (~0.99 GB) uses ~1.6 GB. Choose Q4_K_M for the smallest footprint, Q6_K or Q8_0 for slightly higher precision, and BF16 if more memory is available.
What GPU do you need for QwenDGAF Coder 0.5B?
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 BF16 (1.0 GB file, about 1.6 GB in use).
Which QwenDGAF Coder 0.5B quant should you choose?
Q4_K_M is the usual starting point for QwenDGAF Coder 0.5B: it balances file size and quality well. Here it is a 0.4 GB file.
The Q8_0 file is 0.5 GB, about 1.3 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 QwenDGAF Coder 0.5B
How much VRAM does QwenDGAF Coder 0.5B 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 QwenDGAF Coder 0.5B on an 8 GB GPU?
Yes, with BF16: the 1.0 GB file needs about 1.6 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of QwenDGAF Coder 0.5B GGUF?
It depends on the quant: Q4_K_M is 0.4 GB, Q6_K is 0.5 GB, Q8_0 is 0.5 GB, BF16 is 1.0 GB.
What context length does QwenDGAF Coder 0.5B 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 QwenDGAF Coder 0.5B GGUF?
The files are on Hugging Face in the hecan3d/QwenDGAF-Coder-0.5B repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does QwenDGAF Coder 0.5B 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 QwenDGAF‑Coder‑0.5B on 8 GB VRAM?
Yes, the Q4_K_M quantization uses about 1 GB memory at 8 k context, well within 8 GB VRAM limits.
Does the model support image input?
No, the model has no vision capabilities.
What context length does the model support?
The model supports a full 32,768 token context length.