burtenshaw GemmaCoder3 12B needs about 11.0 GB of memory at Q4_K_M (a 7.3 GB file) with an 8K context window, so it fits on a 12 GB GPU. This repository has 25 quants, from 4.0 GB (IQ2_S) to 23.5 GB (BF16). Longer context needs more: at 32K tokens the KV cache alone adds about 12.9 GB.
GemmaCoder3 12B fine‑tuned for coding and reasoning
burtenshaw GemmaCoder3 12B is a 11.8B‑parameter model based on Gemma architecture. It is fine‑tuned on open‑r1/codeforces‑cots with TRL and SFT. The model supports 131072 token context and is available in multiple GGUF quantizations.
Good at
- Coding tasks
- Reasoning prompts
- Long‑context generation
Limits
- No vision support
- License not specified
- Large VRAM needed for higher quants
Best for
- Code completion
- Algorithmic problem solving
- Debugging assistance
Who it’s for. Developers and researchers needing a large language model focused on code and reasoning. The model is suitable for local deployment via llama.cpp or LM Studio.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| IQ2_S | 4.0 GB | 7.7 GB | Tight | Get file → | |
| IQ2_M | 4.3 GB | 8.0 GB | Too big | Get file → | |
| Q2_K | 4.8 GB | 8.5 GB | Too big | Get file → | |
| IQ3_XXS | 4.8 GB | 8.5 GB | Too big | Get file → | |
| Q2_K_L | 5.0 GB | 8.7 GB | Too big | Get file → | |
| IQ3_XS | 5.2 GB | 8.9 GB | Too big | Get file → | |
| Q3_K_S | 5.5 GB | 9.2 GB | Too big | Get file → | |
| IQ3_M | 5.7 GB | 9.4 GB | Too big | Get file → | |
| Q3_K_M | 6.0 GB | 9.7 GB | Too big | Get file → | |
| Q3_K_L | 6.5 GB | 10.2 GB | Too big | Get file → | |
| IQ4_XS | 6.6 GB | 10.3 GB | Too big | Get file → | |
| Q3_K_XL | 6.7 GB | 10.4 GB | Too big | Get file → | |
| IQ4_NL | 6.9 GB | 10.6 GB | Too big | Get file → | |
| Q4_0 | 6.9 GB | 10.6 GB | Too big | Get file → | |
| Q4_K_S | 6.9 GB | 10.7 GB | Too big | Get file → | |
| Q4_K_M | 7.3 GB | 11.0 GB | Too big | Get file → | |
| Q4_K_L | 7.5 GB | 11.3 GB | Too big | Get file → | |
| Q4_1 | 7.6 GB | 11.3 GB | Too big | Get file → | |
| Q5_K_S | 8.2 GB | 12.0 GB | Too big | Get file → | |
| Q5_K_M | 8.4 GB | 12.2 GB | Too big | Get file → | |
| Q5_K_L | 8.7 GB | 12.4 GB | Too big | Get file → | |
| Q6_K | 9.7 GB | 13.4 GB | Too big | Get file → | |
| Q6_K_L | 9.9 GB | 13.6 GB | Too big | Get file → | |
| Q8_0 | 12.5 GB | 16.2 GB | Too big | Get file → | |
| BF16 | 23.5 GB | 27.3 GB | Too big | Get file → |
For 8 GB VRAM, use IQ2_S (file size 4.02 GB, memory 7.7 GB) or IQ2_M (4.31 GB, 8 GB). If 12 GB VRAM is available, Q3_K_S (5.46 GB, 9.2 GB) or Q4_K_S (6.94 GB, 10.7 GB) provide better quality. For 16 GB VRAM, Q4_K_M (7.3 GB, 11 GB) or Q5_K_S (8.23 GB, 12 GB) are recommended. Estimates are approximate.
What GPU do you need for burtenshaw GemmaCoder3 12B?
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: no quant fits at an 8K context.
- 6 GB VRAM: no quant fits at an 8K context.
- 8 GB VRAM: the best quant that fits is IQ2_M (4.3 GB file, about 8.0 GB in use).
- 12 GB VRAM: the best quant that fits is Q5_K_S (8.2 GB file, about 12.0 GB in use).
- 16 GB VRAM: the best quant that fits is Q6_K_L (9.9 GB file, about 13.6 GB in use).
- 24 GB VRAM: the best quant that fits is Q8_0 (12.5 GB file, about 16.2 GB in use).
- 32 GB VRAM: the best quant that fits is BF16 (23.5 GB file, about 27.3 GB in use).
Which burtenshaw GemmaCoder3 12B quant should you choose?
Q4_K_M is the usual starting point for burtenshaw GemmaCoder3 12B: it balances file size and quality well. Here it is a 7.3 GB file.
The Q8_0 file is 12.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.
If memory is tight, the smallest file is IQ2_S at 4.0 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 burtenshaw GemmaCoder3 12B
How much VRAM does burtenshaw GemmaCoder3 12B need?
About 11.0 GB at Q4_K_M with an 8K context window. That is the 7.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 burtenshaw GemmaCoder3 12B on an 8 GB GPU?
Yes, with IQ2_M: the 4.3 GB file needs about 8.0 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of burtenshaw GemmaCoder3 12B GGUF?
It depends on the quant: IQ2_S is 4.0 GB, IQ2_M is 4.3 GB, Q2_K is 4.8 GB, IQ3_XXS is 4.8 GB, Q2_K_L is 5.0 GB, IQ3_XS is 5.2 GB and 19 more.
What context length does burtenshaw GemmaCoder3 12B support?
The GGUF header lists a trained context length of 131,072 tokens (128K). The KV cache grows with the context you use: about 3.2 GB at 8K and 12.9 GB at 32K.
Where can I download burtenshaw GemmaCoder3 12B GGUF?
The files are on Hugging Face in the bartowski/burtenshaw_GemmaCoder3-12B-GGUF repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
Can I run this model on 8 GB VRAM?
Yes, use IQ2_S or IQ2_M quantizations. They fit within 8 GB VRAM with approximate memory usage of 7.7 GB and 8 GB respectively.
Does this model support vision tasks?
No, the model has no vision capabilities.
What is the context length of this model?
The model supports a context length of 131072 tokens.