granite 20b code instruct needs about 13.5 GB of memory at Q4_K_M (a 12.8 GB file) with an 8K context window, so it fits on a 16 GB GPU. This repository has 14 quants, from 7.9 GB (Q2_K) to 21.5 GB (Q8_0).
Granite 20B Code Instruct – 20B parameter code‑focused model
Granite 20B Code Instruct is a 20B parameter model fine‑tuned from Granite‑20B‑Code‑Base‑8K for instruction following and coding tasks. It supports 8192 token context and is released under Apache 2.0. The model is available in multiple GGUF quantizations.
Good at
- Coding instruction following
- Logical reasoning for code
- Tool‑aware code generation
Limits
- No vision support
- Not recommended for new projects
- Requires 8K context for full capability
Best for
- Building coding assistants
- Generating code snippets
- Debugging code with instructions
Who it’s for. Developers and researchers needing a code‑centric LLM for instruction‑driven code generation. It is suitable for historical or scientific use cases rather than new production deployments.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q2_K | 7.9 GB | 8.6 GB | Too big | Get file → | |
| IQ3_XS | 8.7 GB | 9.4 GB | Too big | Get file → | |
| IQ3_S | 8.9 GB | 9.7 GB | Too big | Get file → | |
| Q3_K_S | 8.9 GB | 9.7 GB | Too big | Get file → | |
| IQ3_M | 9.6 GB | 10.3 GB | Too big | Get file → | |
| Q3_K_M | 10.6 GB | 11.3 GB | Too big | Get file → | |
| IQ4_XS | 11.1 GB | 11.8 GB | Too big | Get file → | |
| Q4_K_S | 11.7 GB | 12.4 GB | Too big | Get file → | |
| Q3_K_L | 11.7 GB | 12.5 GB | Too big | Get file → | |
| Q4_K_M | 12.8 GB | 13.5 GB | Too big | Get file → | |
| Q5_K_S | 14.0 GB | 14.7 GB | Too big | Get file → | |
| Q5_K_M | 14.8 GB | 15.5 GB | Too big | Get file → | |
| Q6_K | 16.6 GB | 17.4 GB | Too big | Get file → | |
| Q8_0 | 21.5 GB | 22.2 GB | Too big | Get file → |
For 8 GB VRAM, use Q4_K_S (file size 11.67 GB, estimated 12.4 GB memory). For 16 GB VRAM, Q5_K_M (file size 14.81 GB, estimated 15.5 GB memory) offers a good balance. Higher‑quality Q6_K (file size 16.63 GB, estimated 17.4 GB memory) is suitable for 24 GB VRAM setups.
What GPU do you need for granite 20b code instruct?
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: no quant fits at an 8K context.
- 12 GB VRAM: the best quant that fits is IQ4_XS (11.1 GB file, about 11.8 GB in use).
- 16 GB VRAM: the best quant that fits is Q5_K_M (14.8 GB file, about 15.5 GB in use).
- 24 GB VRAM: the best quant that fits is Q8_0 (21.5 GB file, about 22.2 GB in use).
Which granite 20b code instruct quant should you choose?
Q4_K_M is the usual starting point for granite 20b code instruct: it balances file size and quality well. Here it is a 12.8 GB file.
The Q8_0 file is 21.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 Q2_K at 7.9 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 granite 20b code instruct
How much VRAM does granite 20b code instruct need?
About 13.5 GB at Q4_K_M with an 8K context window. That is the 12.8 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 granite 20b code instruct on an 8 GB GPU?
Not at an 8K context. The smallest file needs about 8.6 GB, so you would need a larger GPU or CPU offloading.
What is the file size of granite 20b code instruct GGUF?
It depends on the quant: Q2_K is 7.9 GB, IQ3_XS is 8.7 GB, IQ3_S is 8.9 GB, Q3_K_S is 8.9 GB, IQ3_M is 9.6 GB, Q3_K_M is 10.6 GB and 8 more.
What context length does granite 20b code instruct 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.2 GB at 8K and 0.2 GB at 8K.
Where can I download granite 20b code instruct GGUF?
The files are on Hugging Face in the mradermacher/granite-20b-code-instruct-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 granite 20b code instruct 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 Granite 20B Code Instruct on 8 GB VRAM?
Use the Q4_K_S quant, which requires about 12.4 GB memory at 8K context. 8 GB VRAM is insufficient for full inference.
Does this model support image input?
No, the model has no vision capabilities.
Is this model suitable for new production projects?
No, the model is deprecated and not recommended for new projects; newer Granite releases are advised.