granite 3.1 1b a400m concision needs about 3.6 GB of memory at F16 (a 2.7 GB file) with an 8K context window, so it fits on a 4 GB GPU. Longer context needs more: at 32K tokens the KV cache alone adds about 1.6 GB.
Granite 3.1 1B A400M Concision – a 1.33B parameter long‑context model
Granite 3.1 1B A400M Concision is a 1.33B parameter model fine‑tuned for long‑context instruction following. It supports 131072 context tokens and is optimized for function‑calling tasks. The model is released under Apache‑2.0.
Good at
- Long‑context instruction following
- Function‑calling
- Multilingual dialog
Limits
- No vision support
- Requires 3.6 GB VRAM at 8 k context
- Only F16 quant available
Best for
- AI assistants in business
- Long document summarization
- Code‑related tasks
Who it’s for. Developers building AI assistants or tools that need to process long documents or perform function‑calling. The model is suitable for multilingual use cases and can be fine‑tuned for additional languages.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| F16 | 2.7 GB | 3.6 GB | Fits | Get file → |
The only available quant is F16, with a file size of 2.67 GB and an estimated memory usage of 3.6 GB at 8 k context. This is the recommended quant for systems with at least 4 GB VRAM. For tighter budgets, no other quant is provided.
What GPU do you need for granite 3.1 1b a400m concision?
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 (2.7 GB file, about 3.6 GB in use).
Which granite 3.1 1b a400m concision quant should you choose?
F16 (2.7 GB) is the middle option in this repository. The unquantized model. It gives original quality and needs the most memory, so it is mainly for conversion or reference.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about granite 3.1 1b a400m concision
How much VRAM does granite 3.1 1b a400m concision need?
About 3.6 GB at F16 with an 8K context window. That is the 2.7 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 3.1 1b a400m concision on an 8 GB GPU?
Yes, with F16: the 2.7 GB file needs about 3.6 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of granite 3.1 1b a400m concision GGUF?
It depends on the quant: F16 is 2.7 GB.
What context length does granite 3.1 1b a400m concision support?
The GGUF header lists a trained context length of 131,072 tokens (128K). The KV cache grows with the context you use: about 0.4 GB at 8K and 1.6 GB at 32K.
Where can I download granite 3.1 1b a400m concision GGUF?
The files are on Hugging Face in the ziaddddd/granite-3.1-1b-a400m-concision 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 3.1 1b a400m concision 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 3.1 1B A400M Concision on 8 GB VRAM?
Yes, the F16 quant requires approximately 3.6 GB VRAM at 8 k context, leaving headroom for CPU and other processes.
Does this model support vision tasks?
No, the model does not include vision capabilities.
What license applies to this model?
The model is released under the Apache‑2.0 license.