Qwen3.8 27B pi needs about 1.8 GB of memory at Q4_K_M (a 1.1 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 24 quants, from 1.1 GB (Q4_K_M) to 53.8 GB (BF16). Longer context needs more: at 32K tokens the KV cache alone adds about 0.7 GB.
Qwen3.8‑27B‑pi: a 27 B parameter vision‑language model fine‑tuned for coding loops
Qwen3.8‑27B‑pi is a 27 B parameter dense model built on the Qwen3.8 architecture. It supports vision, coding, reasoning, and tool use. The model is fine‑tuned for the Pi agent harness, focusing on iterative code editing and tool feedback.
Good at
- Vision‑language understanding
- Coding with tool integration
- Reasoning and planning
Limits
- Requires 8 k context for memory estimates
- Large VRAM needed for higher precision quants
- No native support for larger context lengths
Best for
- Iterative code debugging
- Automated code review
- Tool‑driven task execution
Who it’s for. Developers and researchers needing a model that can read code repositories, edit files, run tools, and respond to feedback. The model is suitable for building autonomous coding agents.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q4_K_M | 1.1 GB | 1.8 GB | Fits | Get file → | |
| Q4_0 | 2.0 GB | 2.7 GB | Fits | Get file → | |
| Q8_0 | 2.1 GB | 2.7 GB | Fits | Get file → | |
| Q8_0 | 3.2 GB | 3.8 GB | Fits | Get file → | |
| BF16 | 3.9 GB | 4.5 GB | Fits | Get file → | |
| BF16 | 5.9 GB | 6.6 GB | Fits | Get file → | |
| IQ2_XS | 9.1 GB | 9.8 GB | Too big | Get file → | |
| IQ2_S | 9.4 GB | 10.0 GB | Too big | Get file → | |
| IQ2_M | 10.0 GB | 10.7 GB | Too big | Get file → | |
| Q2_K | 10.7 GB | 11.4 GB | Too big | Get file → | |
| IQ3_XS | 12.0 GB | 12.6 GB | Too big | Get file → | |
| Q3_K_S | 12.1 GB | 12.7 GB | Too big | Get file → | |
| IQ3_M | 12.6 GB | 13.2 GB | Too big | Get file → | |
| Q3_K_M | 13.3 GB | 14.0 GB | Too big | Get file → | |
| Q3_K_L | 14.3 GB | 15.0 GB | Too big | Get file → | |
| IQ4_XS | 15.1 GB | 15.8 GB | Too big | Get file → | |
| Q4_K_S | 15.6 GB | 16.3 GB | Too big | Get file → | |
| IQ4_NL | 15.8 GB | 16.5 GB | Too big | Get file → | |
| Q4_K_M | 16.5 GB | 17.2 GB | Too big | Get file → | |
| Q5_K_S | 18.7 GB | 19.3 GB | Too big | Get file → | |
| Q5_K_M | 19.2 GB | 19.9 GB | Too big | Get file → | |
| Q6_K | 22.1 GB | 22.8 GB | Too big | Get file → | |
| Q8_0 | 28.6 GB | 29.3 GB | Too big | Get file → | |
| BF16 | 53.8 GB | 54.5 GB | Too big | Get file → |
For 8 GB VRAM, use Q4_K_M (1.14 GB, ~1.8 GB RAM) or Q4_0 (2.01 GB, ~2.7 GB RAM). For 16 GB VRAM, Q5_K_M (19.23 GB file, ~19.9 GB RAM) or Q6_K (22.08 GB, ~22.8 GB RAM) provide higher quality. Higher precision quants such as BF16 require >30 GB VRAM.
What GPU do you need for Qwen3.8 27B pi?
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 Q8_0 (3.2 GB file, about 3.8 GB in use).
- 6 GB VRAM: the best quant that fits is BF16 (3.9 GB file, about 4.5 GB in use).
- 8 GB VRAM: the best quant that fits is BF16 (5.9 GB file, about 6.6 GB in use).
- 12 GB VRAM: the best quant that fits is Q2_K (10.7 GB file, about 11.4 GB in use).
- 16 GB VRAM: the best quant that fits is IQ4_XS (15.1 GB file, about 15.8 GB in use).
- 24 GB VRAM: the best quant that fits is Q6_K (22.1 GB file, about 22.8 GB in use).
- 32 GB VRAM: the best quant that fits is Q8_0 (28.6 GB file, about 29.3 GB in use).
- 48 GB VRAM: the best quant that fits is Q8_0 (28.6 GB file, about 29.3 GB in use).
Which Qwen3.8 27B pi quant should you choose?
Q4_K_M is the usual starting point for Qwen3.8 27B pi: it balances file size and quality well. Here it is a 1.1 GB file.
The Q8_0 file is 2.1 GB, about 1.8 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.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about Qwen3.8 27B pi
How much VRAM does Qwen3.8 27B pi need?
About 1.8 GB at Q4_K_M with an 8K context window. That is the 1.1 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 Qwen3.8 27B pi on an 8 GB GPU?
Yes, with BF16: the 5.9 GB file needs about 6.6 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of Qwen3.8 27B pi GGUF?
It depends on the quant: Q4_K_M is 1.1 GB, Q4_0 is 2.0 GB, Q8_0 is 2.1 GB, Q8_0 is 3.2 GB, BF16 is 3.9 GB, BF16 is 5.9 GB and 18 more.
What context length does Qwen3.8 27B pi support?
The GGUF header lists a trained context length of 262,144 tokens (256K). The KV cache grows with the context you use: about 0.2 GB at 8K and 0.7 GB at 32K.
Where can I download Qwen3.8 27B pi GGUF?
The files are on Hugging Face in the bytkim/Qwen3.8-27B-pi-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 Qwen3.8 27B pi 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 Qwen3.8‑27B‑pi on 8 GB VRAM?
Yes, with Q4_K_M or Q4_0 quantizations the model fits within 8 GB VRAM and uses about 2 GB of RAM.
Does the model support longer than 8 k context?
The provided quantizations are estimated for 8 k context; larger contexts may exceed memory limits.
Is the model licensed for commercial use?
It is released under the Apache‑2.0 license, allowing commercial deployment.