North Mini Code 1.0 needs about 20.1 GB of memory at Q4_K_M (a 18.7 GB file) with an 8K context window, so it fits on a 24 GB GPU. This repository has 28 quants, from 0.1 GB to 61.0 GB (BF16). Longer context needs more: at 32K tokens the KV cache alone adds about 3.3 GB.
31‑billion‑parameter code‑generation model with Mixture‑of‑Experts
North Mini Code 1.0 is a 31 B parameter decoder‑only transformer optimized for coding tasks. It uses a sparse Mixture‑of‑Experts architecture and supports a 256 K context length. The model is released under Apache 2.0 and is available in multiple GGUF quantizations.
Good at
- Code generation
- Agentic software engineering
- Terminal‑based tasks
Limits
- Requires large VRAM for high‑quality quants
- No vision or multimodal support
- Context limited to 256 K tokens
Best for
- Developers building coding assistants
- Researchers testing Mixture‑of‑Experts models
- Users with high‑end GPUs for full‑precision use
Who it’s for. The model is suited for developers and researchers who need a powerful code‑generation engine and have access to GPUs with sufficient VRAM. It is also useful for those who prefer open‑weight models under an Apache 2.0 license.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| — | 0.1 GB | 1.4 GB | Fits | Get file → | |
| IQ2_XXS | 8.5 GB | 9.8 GB | Too big | Get file → | |
| IQ2_XS | 9.4 GB | 10.7 GB | Too big | Get file → | |
| IQ2_S | 9.6 GB | 10.9 GB | Too big | Get file → | |
| IQ2_M | 10.5 GB | 11.9 GB | Too big | Get file → | |
| Q2_K | 11.1 GB | 12.4 GB | Too big | Get file → | |
| Q2_K_L | 11.2 GB | 12.5 GB | Too big | Get file → | |
| IQ3_XXS | 13.0 GB | 14.3 GB | Too big | Get file → | |
| Q3_K_S | 13.6 GB | 14.9 GB | Too big | Get file → | |
| IQ3_XS | 14.2 GB | 15.5 GB | Too big | Get file → | |
| Q3_K_M | 14.2 GB | 15.5 GB | Too big | Get file → | |
| Q3_K_L | 14.8 GB | 16.1 GB | Too big | Get file → | |
| IQ3_M | 14.9 GB | 16.2 GB | Too big | Get file → | |
| Q3_K_XL | 14.9 GB | 16.2 GB | Too big | Get file → | |
| IQ4_XS | 16.6 GB | 17.9 GB | Too big | Get file → | |
| IQ4_NL | 17.5 GB | 18.8 GB | Too big | Get file → | |
| Q4_0 | 17.5 GB | 18.8 GB | Too big | Get file → | |
| Q4_K_S | 18.1 GB | 19.4 GB | Too big | Get file → | |
| Q4_K_M | 18.7 GB | 20.1 GB | Too big | Get file → | |
| Q4_K_L | 18.9 GB | 20.2 GB | Too big | Get file → | |
| Q4_1 | 19.3 GB | 20.6 GB | Too big | Get file → | |
| Q5_K_S | 21.1 GB | 22.5 GB | Too big | Get file → | |
| Q5_K_M | 21.8 GB | 23.2 GB | Too big | Get file → | |
| Q5_K_L | 22.0 GB | 23.3 GB | Too big | Get file → | |
| Q6_K | 26.4 GB | 27.7 GB | Too big | Get file → | |
| Q6_K_L | 26.5 GB | 27.9 GB | Too big | Get file → | |
| Q8_0 | 32.4 GB | 33.8 GB | Too big | Get file → | |
| BF16 | 61.0 GB (2 parts) | 62.3 GB | Too big | Get file → |
For 8 GB VRAM, use IQ2_XXS (9.8 GB memory estimate) or Q2_K (12.4 GB). With 16 GB VRAM, Q4_K_S (19.4 GB) or Q4_K_M (20.1 GB) are suitable. For 24 GB VRAM, Q5_K_S (22.5 GB) or Q5_K_M (23.2 GB) provide higher quality.
What GPU do you need for North Mini Code 1.0?
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 the main file (0.1 GB file, about 1.4 GB in use).
- 6 GB VRAM: the best quant that fits is the main file (0.1 GB file, about 1.4 GB in use).
- 8 GB VRAM: the best quant that fits is the main file (0.1 GB file, about 1.4 GB in use).
- 12 GB VRAM: the best quant that fits is IQ2_M (10.5 GB file, about 11.9 GB in use).
- 16 GB VRAM: the best quant that fits is Q3_K_M (14.2 GB file, about 15.5 GB in use).
- 24 GB VRAM: the best quant that fits is Q5_K_L (22.0 GB file, about 23.3 GB in use).
- 32 GB VRAM: the best quant that fits is Q6_K_L (26.5 GB file, about 27.9 GB in use).
- 48 GB VRAM: the best quant that fits is Q8_0 (32.4 GB file, about 33.8 GB in use).
Which North Mini Code 1.0 quant should you choose?
Q4_K_M is the usual starting point for North Mini Code 1.0: it balances file size and quality well. Here it is a 18.7 GB file.
The Q8_0 file is 32.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 the first one in the table at 0.1 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 North Mini Code 1.0
How much VRAM does North Mini Code 1.0 need?
About 20.1 GB at Q4_K_M with an 8K context window. That is the 18.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 North Mini Code 1.0 on an 8 GB GPU?
Yes, with the smaller files: the 0.1 GB file needs about 1.4 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of North Mini Code 1.0 GGUF?
It depends on the quant: file is 0.1 GB, IQ2_XXS is 8.5 GB, IQ2_XS is 9.4 GB, IQ2_S is 9.6 GB, IQ2_M is 10.5 GB, Q2_K is 11.1 GB and 22 more.
What context length does North Mini Code 1.0 support?
The GGUF header lists a trained context length of 500,000 tokens (488K). The KV cache grows with the context you use: about 0.8 GB at 8K and 3.3 GB at 32K.
Where can I download North Mini Code 1.0 GGUF?
The files are on Hugging Face in the bartowski/North-Mini-Code-1.0-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 North Mini Code 1.0 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 North Mini Code on 8 GB VRAM?
Use the IQ2_XXS quant, which estimates 9.8 GB memory at 8 k context. It may require swapping or lower batch sizes.
Does the model support image inputs?
No, the model accepts text only and has no vision capabilities.
What license applies to this model?
The model is released under the Apache 2.0 license.