Granite-4.0-H-Tiny needs about 6.8 GB of memory at Q4_K_M (a 4.3 GB file) with an 8K context window, so it fits on a 8 GB GPU. This repository has 27 quants, from 1.9 GB (TQ1_0) to 13.9 GB (BF16). Longer context needs more: at 32K tokens the KV cache alone adds about 8.1 GB.
Granite‑4.0‑H‑Tiny: 7B parameter long‑context instruction model
Granite‑4.0‑H‑Tiny is a 7B parameter model fine‑tuned for instruction following and tool‑calling. It supports a 1,048,576 token context window and is released under Apache 2.0. The model is available in multiple GGUF quantizations for varied memory budgets.
Good at
- Instruction following
- Tool‑calling
- Multilingual dialog
Limits
- Large context requires high VRAM
- No vision support
- Apache 2.0 license
Best for
- Enterprise AI assistants
- RAG applications
- Code completion
Who it’s for. Developers building AI assistants or enterprise applications that need robust instruction following and tool‑calling. The model is suitable for users who can manage the memory requirements of the chosen quantization.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| TQ1_0 | 1.9 GB | 4.5 GB | Fits | Get file → | |
| IQ1_S | 2.1 GB | 4.6 GB | Fits | Get file → | |
| IQ1_M | 2.2 GB | 4.8 GB | Fits | Get file → | |
| IQ2_XXS | 2.4 GB | 4.9 GB | Fits | Get file → | |
| IQ2_M | 2.5 GB | 5.0 GB | Fits | Get file → | |
| Q2_K | 2.6 GB | 5.2 GB | Fits | Get file → | |
| Q2_K_L | 2.6 GB | 5.2 GB | Fits | Get file → | |
| Q2_K_XL | 2.7 GB | 5.2 GB | Fits | Get file → | |
| IQ3_XXS | 3.0 GB | 5.5 GB | Fits | Get file → | |
| Q3_K_S | 3.1 GB | 5.6 GB | Fits | Get file → | |
| Q3_K_XL | 3.2 GB | 5.7 GB | Fits | Get file → | |
| Q3_K_M | 3.4 GB | 5.9 GB | Fits | Get file → | |
| IQ4_XS | 3.8 GB | 6.3 GB | Fits | Get file → | |
| IQ4_NL | 4.0 GB | 6.5 GB | Fits | Get file → | |
| Q4_0 | 4.0 GB | 6.5 GB | Fits | Get file → | |
| Q4_K_S | 4.0 GB | 6.5 GB | Fits | Get file → | |
| Q4_K_XL | 4.1 GB | 6.6 GB | Fits | Get file → | |
| Q4_K_M | 4.3 GB | 6.8 GB | Fits | Get file → | |
| Q4_1 | 4.4 GB | 6.9 GB | Fits | Get file → | |
| Q5_K_S | 4.8 GB | 7.3 GB | Tight | Get file → | |
| Q5_K_M | 5.0 GB | 7.5 GB | Tight | Get file → | |
| Q5_K_XL | 5.0 GB | 7.5 GB | Tight | Get file → | |
| Q6_K | 5.7 GB | 8.2 GB | Too big | Get file → | |
| Q6_K_XL | 6.0 GB | 8.6 GB | Too big | Get file → | |
| Q8_0 | 7.4 GB | 9.9 GB | Too big | Get file → | |
| Q8_K_XL | 8.3 GB | 10.8 GB | Too big | Get file → | |
| BF16 | 13.9 GB | 16.4 GB | Too big | Get file → |
For 8 GB VRAM, use Q4_0 (4.01 GB file, ~6.5 GB VRAM). For 12 GB VRAM, Q5_K_M (4.97 GB file, ~7.5 GB VRAM) or Q6_K (5.73 GB file, ~8.2 GB VRAM). Higher‑precision Q8_0 (7.39 GB file, ~9.9 GB VRAM) offers better quality if memory allows.
What GPU do you need for Granite-4.0-H-Tiny?
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: the best quant that fits is Q3_K_M (3.4 GB file, about 5.9 GB in use).
- 8 GB VRAM: the best quant that fits is Q5_K_XL (5.0 GB file, about 7.5 GB in use).
- 12 GB VRAM: the best quant that fits is Q8_K_XL (8.3 GB file, about 10.8 GB in use).
- 16 GB VRAM: the best quant that fits is Q8_K_XL (8.3 GB file, about 10.8 GB in use).
- 24 GB VRAM: the best quant that fits is BF16 (13.9 GB file, about 16.4 GB in use).
Which Granite-4.0-H-Tiny quant should you choose?
Q4_K_M is the usual starting point for Granite-4.0-H-Tiny: it balances file size and quality well. Here it is a 4.3 GB file.
The Q8_0 file is 7.4 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 TQ1_0 at 1.9 GB, with the quality trade-offs that come with fewer bits. Lower bit counts mean smaller files and more quality loss.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about Granite-4.0-H-Tiny
How much VRAM does Granite-4.0-H-Tiny need?
About 6.8 GB at Q4_K_M with an 8K context window. That is the 4.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 Granite-4.0-H-Tiny on an 8 GB GPU?
Yes, with Q5_K_XL: the 5.0 GB file needs about 7.5 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of Granite-4.0-H-Tiny GGUF?
It depends on the quant: TQ1_0 is 1.9 GB, IQ1_S is 2.1 GB, IQ1_M is 2.2 GB, IQ2_XXS is 2.4 GB, IQ2_M is 2.5 GB, Q2_K is 2.6 GB and 21 more.
What context length does Granite-4.0-H-Tiny support?
The GGUF header lists a trained context length of 1,048,576 tokens (1024K). The KV cache grows with the context you use: about 2.0 GB at 8K and 8.1 GB at 32K.
Where can I download Granite-4.0-H-Tiny GGUF?
The files are on Hugging Face in the unsloth/granite-4.0-h-tiny-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-4.0-H-Tiny 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‑4.0‑H‑Tiny on 8 GB VRAM?
Yes, using the Q4_0 quantization which requires about 6.5 GB VRAM at 8k context.
Does the model support image input?
No, Granite‑4.0‑H‑Tiny does not have vision capabilities.
What license applies to this model?
The model is released under the Apache 2.0 license.