Home / Models / Qwen3.8-27B

How to Run Qwen3.8-27B Locally — Setup Guide (September 2026)

Qwen3.8-27B is Alibaba's current 27B dense flagship — the direct successor to Qwen3.6-27B, with vision input and a thinking mode. Its hybrid-linear attention means only 16 of its 64 layers keep a growing KV cache, which is why a 262K context window costs a fraction of what it would on a conventional 27B, and why the whole thing fits a 16 GB card at a Q3/IQ4-class quant.

Numbers you can trust

We don't print guessed speeds. Every measured number on this page came from TurboLLM's own auto-tuner running Qwen3.8-27B on real hardware — labeled as such. When you run it yourself, TurboLLM benchmarks it on your exact GPU and shows a VRAM-fit verdict before you load, and the real measured tokens/sec once it's running.

Does it fit your GPU?

27.8B dense parameters, Apache-2.0, with a hybrid attention stack: 48 linear-attention layers that hold a near-constant state plus 16 full-attention layers that keep the real KV cache. Vision input needs the separate mmproj file from the same repo alongside the weights.

Qwen3.8-27B
Alibaba · GGUF
Dense · hybrid linear attention · vision
toolsthinkingcodevision
VRAMFit
16 GBUD-Q3_K_XL (13.2 GB) or UD-IQ4_XS (14.3 GB) fully in VRAM · UD-Q4_K_M (16.5 GB) with a light nudge to system RAM · 262K context
24 GBUD-Q4_K_M (16.5 GB) or UD-Q5_K_M (19.8 GB) fully in VRAM with room for long context · 262K context
32 GBUD-Q6_K (22.0 GB) fully in VRAM · 262K context
48 GB+Q8_0 (29.1 GB) fully in VRAM · 262K context
unsloth/Qwen3.8-27B-GGUF
View on Hugging Face →

How to run it

  1. Install TurboLLM

    npx turbollm — no install step, works on Windows, macOS, and Linux. It detects your GPU and auto-provisions a matching llama-server build (no CUDA toolkit, no Python, no compiler).

  2. Get the model

    Paste unsloth/Qwen3.8-27B-GGUF into TurboLLM's in-app Hugging Face search — it lists every quant with a VRAM-fit verdict against your real free VRAM, and downloads are resumable and SHA-256 verified.

  3. Let auto-fit pick the setup

    Flip the auto-fit toggle and TurboLLM chooses the GPU/CPU layer split (and, for a Mixture-of-Experts model, the expert-offload split) for your card — the same manual flag-hunting every other guide walks you through by hand.

  4. Load it

    TurboLLM benchmarks the model on your exact GPU as it loads and shows the real measured tokens/sec — not a number copied from someone else's card.

  5. Use it

    Chat in the built-in UI, or point any OpenAI- or Anthropic-compatible tool (including Claude Code) at TurboLLM's local API — see the API docs.

One honest caveat

Vision is a separate download. The GGUF weights alone are text-only — you also need the mmproj-F16 file (0.9 GB) from the same repo before images work. TurboLLM pairs it for you when it is present in the repo, but if you copied a single .gguf in by hand, that is why image input is missing.

FAQ

Will Qwen3.8-27B run on my GPU?

Check the VRAM table above for the tier closest to your card. If you're not sure which tier you're in, or want picks tailored to your exact hardware, use What can I run? — enter your VRAM (or Apple unified memory) and it suggests the model, quant, and offload split that fits, the same logic TurboLLM's auto-fit runs when you load a model.

Which quant should I use for Qwen3.8-27B?

Pick the highest quant that fits your VRAM with room left over for the KV cache and compute buffer — not just the model weights. As a starting point, Q4_K_M is usually the sweet spot (small quality loss for a large size drop); step up to Q5_K_M/Q6_K/Q8_0 if you have headroom, or down to Q3_K_M/an IQ quant if you don't. TurboLLM shows a VRAM-fit verdict for every quant against your card's real free VRAM before you download — see Quantization explained for what the letters and numbers actually mean, or llama.cpp flags that actually matter for the other settings worth knowing.

Why does Qwen3.8-27B suddenly get slow or stutter?

The usual cause is silent VRAM spill: once a model's weights plus its KV cache stop fitting in VRAM, the driver quietly offloads the overflow to system RAM over PCIe, and that path runs 5–10× slower with no error message — just a sudden slowdown. TurboLLM's auto-fit sizes the quant and GPU/CPU split against your card's real free VRAM (including KV-cache growth at your chosen context) specifically to avoid this, and shows a VRAM-fit verdict before you load rather than after it's already crawling. Full mechanics in VRAM spill explained.

How is running Qwen3.8-27B on TurboLLM different from Ollama or LM Studio?

All three can run Qwen3.8-27B as a GGUF. The differences show up around the edges: TurboLLM auto-tunes the quant and GPU/CPU split against your card's measured free VRAM rather than a fixed default, shows real generation speed instead of a guess, and lets you add a community fork — like the one behind this page, where relevant — without compiling anything yourself. Ollama and LM Studio each ship one blessed runtime you can't swap out. If your current setup already works well for you, there's no need to switch.

Run it now

$ npx turbollm

One command detects your GPU, provisions the right engine, and opens the UI. New here? Start with Install & first run and Quantization explained. On different hardware, see RTX 5070 Ti, RTX 5080, RTX 4090 or RTX 3090. Also see how to run it or how to run it.