Orbit 3.2 Nano needs about 4.3 GB of memory at Q4_K_M (a 1.8 GB file) with an 8K context window, so it fits on a 6 GB GPU. This repository has 23 quants, from 0.0 GB to 5.4 GB (BF16). Longer context needs more: at 32K tokens the KV cache alone adds about 8.1 GB.
Orbit 3.2 Nano – 2.7B parameter LFM2 model fine‑tuned for Indonesian QA
Orbit 3.2 Nano is a 2.7B parameter LFM2 model fine‑tuned on the Indonesian Dolod‑15k‑Indonesia closed QA dataset. It supports reasoning and tool use and is licensed under Apache‑2.0. The model can handle up to 131072 context tokens.
Good at
- Closed‑domain Indonesian QA
- Reasoning with tool calls
- Short‑conv efficient inference
Limits
- No vision support
- Not suitable for medical or legal decisions
- Requires 8k context for memory estimates
Best for
- Document‑based question answering
- Indonesian language instruction following
- Tool‑enabled task automation
Who it’s for. Researchers and developers needing a lightweight Indonesian LLM for QA and reasoning tasks. The model is free for research and commercial use under Apache‑2.0, but should not be deployed in high‑stakes production without oversight.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| — | 0.0 GB | 2.5 GB | Fits | Get file → | |
| IQ2_M | 1.0 GB | 3.5 GB | Fits | Get file → | |
| Q2_K | 1.1 GB | 3.6 GB | Fits | Get file → | |
| IQ3_XXS | 1.2 GB | 3.7 GB | Fits | Get file → | |
| Q3_K_S | 1.2 GB | 3.8 GB | Fits | Get file → | |
| IQ3_XS | 1.2 GB | 3.8 GB | Fits | Get file → | |
| Q3_K_M | 1.3 GB | 3.8 GB | Fits | Get file → | |
| Q3_K_L | 1.4 GB | 3.9 GB | Fits | Get file → | |
| IQ3_M | 1.4 GB | 4.0 GB | Fits | Get file → | |
| IQ4_XS | 1.6 GB | 4.1 GB | Fits | Get file → | |
| Q4_0 | 1.6 GB | 4.1 GB | Fits | Get file → | |
| Q4_K_S | 1.7 GB | 4.2 GB | Fits | Get file → | |
| Q4_1 | 1.7 GB | 4.3 GB | Fits | Get file → | |
| IQ4_NL | 1.8 GB | 4.3 GB | Fits | Get file → | |
| Q4_K_M | 1.8 GB | 4.3 GB | Fits | Get file → | |
| Q4_K_L | 1.9 GB | 4.4 GB | Fits | Get file → | |
| Q5_K_S | 2.0 GB | 4.5 GB | Fits | Get file → | |
| Q5_K_M | 2.1 GB | 4.6 GB | Fits | Get file → | |
| Q6_K_S | 2.3 GB | 4.8 GB | Fits | Get file → | |
| Q6_K | 2.4 GB | 4.9 GB | Fits | Get file → | |
| Q6_K_L | 2.5 GB | 5.0 GB | Fits | Get file → | |
| Q8_0 | 2.9 GB | 5.4 GB | Fits | Get file → | |
| BF16 | 5.4 GB | 7.9 GB | Tight | Get file → |
For 8 GB VRAM, use Q4_K_M (1.75 GB) or Q5_K_M (2.08 GB) – memory usage is approximately 4.3 GB or 4.6 GB at 8k context. For 4 GB VRAM, IQ2_M (1 GB) or Q2_K (1.07 GB) are suitable, using about 3.5 GB or 3.6 GB. Larger models like Q8_0 or BF16 require more than 5 GB VRAM.
What GPU do you need for Orbit 3.2 Nano?
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 IQ3_M (1.4 GB file, about 4.0 GB in use).
- 6 GB VRAM: the best quant that fits is Q8_0 (2.9 GB file, about 5.4 GB in use).
- 8 GB VRAM: the best quant that fits is BF16 (5.4 GB file, about 7.9 GB in use).
Which Orbit 3.2 Nano quant should you choose?
Q4_K_M is the usual starting point for Orbit 3.2 Nano: it balances file size and quality well. Here it is a 1.8 GB file.
The Q8_0 file is 2.9 GB, about 1.6 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 the first one in the table at 0.0 GB, with the quality trade-offs that come with fewer bits.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about Orbit 3.2 Nano
How much VRAM does Orbit 3.2 Nano need?
About 4.3 GB at Q4_K_M with an 8K context window. That is the 1.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 Orbit 3.2 Nano on an 8 GB GPU?
Yes, with BF16: the 5.4 GB file needs about 7.9 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of Orbit 3.2 Nano GGUF?
It depends on the quant: file is 0.0 GB, IQ2_M is 1.0 GB, Q2_K is 1.1 GB, IQ3_XXS is 1.2 GB, Q3_K_S is 1.2 GB, IQ3_XS is 1.2 GB and 17 more.
What context length does Orbit 3.2 Nano support?
The GGUF header lists a trained context length of 131,072 tokens (128K). 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 Orbit 3.2 Nano GGUF?
The files are on Hugging Face in the bartowski/OpenPathAI_Orbit-3.2-Nano-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 Orbit 3.2 Nano 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 Orbit 3.2 Nano on 8 GB VRAM?
Yes, the Q4_K_M quant (1.75 GB) uses about 4.3 GB of VRAM at 8k context, which fits within an 8 GB GPU.
Does the model support vision tasks?
No, Orbit 3.2 Nano only supports text input and has no vision capabilities.
What license applies to this model?
The model is released under the Apache‑2.0 license, allowing free use, modification, and commercial distribution.