Type o1 mini instruct needs about 1.6 GB of memory at Q4_K_M (a 0.8 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 13 quants, from 0.0 GB to 2.5 GB (F16). Longer context needs more: at 32K tokens the KV cache alone adds about 1.1 GB.
Type o1 mini instruct – a compact 1.24B‑parameter instruct model
Type o1 mini instruct is a 1.24B‑parameter llama architecture model fine‑tuned for general‑purpose instruction. It supports a 131072‑token context and is released under the MIT license.
Good at
- General chat and multi‑turn conversation
- Python coding assistance
- Creative writing and content generation
Limits
- No vision support
- Requires llama.cpp with --jinja flag
- Large context length may need more VRAM
Best for
- Lightweight assistant tasks
- Educational Q&A
- Tool‑call style web search workflows
Who it’s for. Developers and hobbyists who need a small, versatile instruct model for everyday assistant use. The model is ideal for projects that require clear, well‑structured answers across many domains.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| — | 0.0 GB | 0.8 GB | Fits | Get file → | |
| Q2_K | 0.6 GB | 1.3 GB | Fits | Get file → | |
| Q3_K_S | 0.6 GB | 1.4 GB | Fits | Get file → | |
| Q3_K_M | 0.7 GB | 1.5 GB | Fits | Get file → | |
| Q3_K_L | 0.7 GB | 1.5 GB | Fits | Get file → | |
| IQ4_XS | 0.7 GB | 1.5 GB | Fits | Get file → | |
| Q4_K_S | 0.8 GB | 1.5 GB | Fits | Get file → | |
| Q4_K_M | 0.8 GB | 1.6 GB | Fits | Get file → | |
| Q5_K_S | 0.9 GB | 1.7 GB | Fits | Get file → | |
| Q5_K_M | 0.9 GB | 1.7 GB | Fits | Get file → | |
| Q6_K | 1.0 GB | 1.8 GB | Fits | Get file → | |
| Q8_0 | 1.3 GB | 2.1 GB | Fits | Get file → | |
| F16 | 2.5 GB | 3.2 GB | Fits | Get file → |
For 8 GB VRAM, Q4_K_M (0.81 GB) or Q5_K_M (0.91 GB) are suitable, using about 1.6–1.7 GB of VRAM at 8 k context. If memory is tighter, Q3_K_S (0.64 GB) or Q3_K_M (0.69 GB) can be used, estimating 1.4–1.5 GB VRAM. For the highest quality, Q8_0 (1.32 GB) or F16 (2.48 GB) provide better performance but require more memory.
What GPU do you need for Type o1 mini 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: the best quant that fits is F16 (2.5 GB file, about 3.2 GB in use).
Which Type o1 mini instruct quant should you choose?
Q4_K_M is the usual starting point for Type o1 mini instruct: it balances file size and quality well. Here it is a 0.8 GB file.
The Q8_0 file is 1.3 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 Type o1 mini instruct
How much VRAM does Type o1 mini instruct need?
About 1.6 GB at Q4_K_M with an 8K context window. That is the 0.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 Type o1 mini instruct on an 8 GB GPU?
Yes, with F16: the 2.5 GB file needs about 3.2 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of Type o1 mini instruct GGUF?
It depends on the quant: file is 0.0 GB, Q2_K is 0.6 GB, Q3_K_S is 0.6 GB, Q3_K_M is 0.7 GB, Q3_K_L is 0.7 GB, IQ4_XS is 0.7 GB and 7 more.
What context length does Type o1 mini instruct 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.3 GB at 8K and 1.1 GB at 32K.
Where can I download Type o1 mini instruct GGUF?
The files are on Hugging Face in the kd13/Type-o1-mini-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 Type o1 mini instruct use?
Hugging Face lists the license as mit. 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 Type o1 mini instruct on 8 GB VRAM?
Yes, using Q4_K_M or Q5_K_M quants will fit within 8 GB VRAM, estimating 1.6–1.7 GB usage at 8 k context.
Does this model support vision tasks?
No, the model has no vision capabilities.
What chat template does it use?
It uses a custom Harmony‑style chat template; llama.cpp requires the --jinja flag.