Qwen_Qwen3.8 27B needs about 19.5 GB of memory at Q4_K_M (a 16.8 GB file) with an 8K context window, so it fits on a 24 GB GPU. This repository has 3 quants, from 16.8 GB (Q4_K_M) to 29.0 GB (Q8_0). Longer context needs more: at 32K tokens the KV cache alone adds about 8.7 GB.
Qwen3.8-27B: 27B‑parameter vision‑language model with 262,144‑token context
Qwen3.8-27B is a 27‑billion‑parameter dense model that supports vision and language tasks. It offers a 262,144‑token context window and is compatible with llama.cpp, vLLM, and other inference engines. The model is released under Apache‑2.0 and is community‑quantized by lmstudio‑community.
Good at
- Vision‑language understanding
- Long‑horizon reasoning
- Agentic task execution
Limits
- No native vision support in some harnesses
- Large VRAM requirement for full precision
- Requires 8‑k context for memory estimates
Best for
- Complex multi‑step task planning
- Image‑based code generation
- Video analysis
Who it’s for. Developers needing a large, vision‑enabled model for research or production. The model is suitable for teams that can allocate sufficient GPU memory and use llama.cpp or compatible frameworks.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q4_K_M | 16.8 GB | 19.5 GB | Too big | Get file → | |
| Q6_K | 22.4 GB | 25.1 GB | Too big | Get file → | |
| Q8_0 | 29.0 GB | 31.7 GB | Too big | Get file → |
For 8 GB VRAM use Q4_K_M (16.81 GB file, ~19.5 GB memory at 8 k context). For 12 GB VRAM use Q6_K (22.43 GB file, ~25.1 GB memory). For 16 GB VRAM use Q8_0 (29.05 GB file, ~31.7 GB memory). Estimates are approximate.
What GPU do you need for Qwen_Qwen3.8 27B?
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: no quant fits at an 8K context.
- 8 GB VRAM: no quant fits at an 8K context.
- 12 GB VRAM: no quant fits at an 8K context.
- 16 GB VRAM: no quant fits at an 8K context.
- 24 GB VRAM: the best quant that fits is Q4_K_M (16.8 GB file, about 19.5 GB in use).
- 32 GB VRAM: the best quant that fits is Q8_0 (29.0 GB file, about 31.7 GB in use).
Which Qwen_Qwen3.8 27B quant should you choose?
Q4_K_M is the usual starting point for Qwen_Qwen3.8 27B: it balances file size and quality well. Here it is a 16.8 GB file.
The Q8_0 file is 29.0 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.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about Qwen_Qwen3.8 27B
How much VRAM does Qwen_Qwen3.8 27B need?
About 19.5 GB at Q4_K_M with an 8K context window. That is the 16.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 Qwen_Qwen3.8 27B on an 8 GB GPU?
Not at an 8K context. The smallest file needs about 19.5 GB, so you would need a larger GPU or CPU offloading.
What is the file size of Qwen_Qwen3.8 27B GGUF?
It depends on the quant: Q4_K_M is 16.8 GB, Q6_K is 22.4 GB, Q8_0 is 29.0 GB.
What context length does Qwen_Qwen3.8 27B support?
The GGUF header lists a trained context length of 262,144 tokens (256K). The KV cache grows with the context you use: about 2.2 GB at 8K and 8.7 GB at 32K.
Where can I download Qwen_Qwen3.8 27B GGUF?
The files are on Hugging Face in the lmstudio-community/Qwen3.8-27B-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 Qwen_Qwen3.8 27B 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 on 8 GB VRAM?
Only with Q4_K_M quantization; memory usage is ~19.5 GB at 8 k context, so 8 GB VRAM is insufficient.
Does the model support image input?
Yes, it is a native vision‑language model that understands images and videos.
What license applies to this model?
The model is released under the Apache‑2.0 license.