What Is Qwen3.8 27B? Architecture, Benchmarks, and Local Setup
A 27B dense vision-language model with Apache-2.0 open weights and vendor-reported benchmark scores.
The Qwen3.8-27B release is an open-weight, 27-billion parameter dense vision-language model published under the Apache-2.0 software license. The Qwen team's Hugging Face repository for the model was created on August 5, 2026. The card describes a native vision-language model that understands images and videos and is designed to carry complex, multi-step tasks through to completion. For engineering teams evaluating a self-hosted qwen3.8 27b deployment, the release provides open access to weights without commercial license fees.
Built on the architectural foundation of Qwen3.5, the model provides a native context length of 262,144 tokens that scales up to 1,000,000 tokens through rotary position embedding (RoPE) scaling. The Qwen team describes the release as its most capable open-model generation to date, trained with multi-token prediction (MTP) and a hidden layout of 16 repeating blocks, each holding three Gated DeltaNet layers followed by one Gated Attention layer. The card lists gains in coding, professional work, research, and long-horizon agentic tasks.
At Layer3Labs, we build and operate AI systems inside other people's businesses. Because the model card publishes no memory footprints or hardware requirements, engineering teams must evaluate local serving engines and verify memory demands on their own target infrastructure.
What Qwen3.8-27B Is Good For
Qwen3.8-27B is an open-weight dense vision-language model designed for agentic coding, computer use, and long-horizon office workflows. The card describes it as designed to carry complex, multi-step tasks through to completion with greater reliability.
Across software engineering tasks, the Qwen team reports an evaluation score of 61.7 on SWE-bench Pro using the Claude Code harness with a 256K context window. On Terminal Bench 2.1 for agentic terminal execution, the card reports a score of 73.0. For competitive programming, the model achieves 90.3 on LiveCodeBench v6.
The card also reports computer-use and browser-use results. The system scores 84.3 on OSWorld-Verified for computer control and 64.8 on WebArena-Verified for autonomous browser execution. For professional workplace tasks, the card lists a score of 70.7 on CoWorkBench, an internal evaluation measuring multi-domain work across finance, law, medical, and computer science domains.
- Developer: The Qwen team
- Architecture: 27B dense causal language model with native vision encoder
- Software license: Apache-2.0 open weights
- Context window: 262,144 tokens native, extensible to 1,000,000 tokens with YaRN RoPE scaling
- Input modalities: Text, static images, and videos up to hour-scale length
- Weight cost: Free download from Hugging Face
- Hosted status: Managed Qwen Cloud API listed as coming soon as of October 2026
Inference Engines and Local Deployment Options for Qwen3.8 27B
Local deployment of Qwen3.8 27B requires downloading the open weights from Hugging Face and serving them through an execution engine such as vLLM, SGLang, TokenSpeed, or Hugging Face Transformers. The Qwen team recommends dedicated inference engines like SGLang, vLLM, and TokenSpeed for production or high-throughput serving environments. The model card explicitly notes that inference efficiency and throughput vary significantly across different serving frameworks.
For application integration, the checkpoint supports the standard Chat Completions application programming interface (API) style using the OpenAI Python software development kit (SDK). Developers can configure local endpoints pointing to the model identifier Qwen/Qwen3.8-27B. For general setup steps, see how to set up and run a local LLM in 2026.
Financial costs for local operation depend entirely on self-hosted hardware. The weights are free under the Apache-2.0 license, but the card publishes no hardware requirement, no video random access memory (VRAM) figure, and no price for running it. While an official managed service with a default 1,000,000 token window is planned for Qwen Cloud, hosting fees remain unpublished as of October 2026.
- Serving frameworks: SGLang, vLLM, and TokenSpeed recommended for high-throughput production
- General library: Hugging Face Transformers supported directly
- API convention: OpenAI Python SDK compatible Chat Completions format
- Hosting requirements: No VRAM or graphics processing unit (GPU) requirements published on the card
- Managed alternative: Qwen Cloud service listed as coming soon with built-in tools
Thinking Controls and Reasoning Effort Configuration
Qwen3.8-27B incorporates adjustable reasoning controls through a reasoning effort parameter that regulates analytical depth before generating an output. Thinking mode is enabled by default on the checkpoint, and developers can disable it per request, and preserve_thinking is also on by default.
The model card defines three distinct reasoning effort settings for controlling generation. The default setting is xhigh, which targets complex technical assignments demanding thorough analysis. The medium setting balances accuracy against generation latency, while the low setting optimizes for operational speed and reduced token consumption.
The Qwen team includes a specific operational warning regarding lower reasoning levels in multi-turn agentic workflows. Faster per-turn responses under low reasoning effort do not always reduce overall task completion time. Insufficient analysis can lead to more failures and repeated retries, which may increase total latency and token consumption.
- xhigh reasoning effort: Default level designed for complex multi-step reasoning and deep analysis
- medium reasoning effort: Intermediate configuration balancing generation speed and task precision
- low reasoning effort: Fast reasoning configuration prioritizing execution speed and lower token counts
- Sampling in thinking mode: Recommended temperature of 1.0, top_p of 0.95, and top_k of 20
- Sampling in instruct mode: Recommended temperature of 0.7, top_p of 0.80, and presence_penalty of 1.5
- Output length boundaries: Reasoning content up to 262,144 tokens and final output up to 131,072 tokens
Benchmark Performance Across Qwen3.8 27B and Rival Architectures
Vendor-reported benchmarks indicate that Qwen3.8 27B posts gains over Qwen3.6-27B while trailing Qwen3.7-Plus and Opus4.6 Max on multidisciplinary academic reasoning. On scientific reasoning, Qwen3.8-27B achieves 89.2 on Graduate-Level Google-Proof Q&A (GPQA) Diamond, placing behind Qwen3.7-Plus at 90.3 and Opus4.6 Max at 91.3.
On multidisciplinary reasoning judged by GPT-4o on Humanity's Last Exam (HLE), Qwen3.8-27B reaches 30.8. This score surpasses Qwen3.6-27B at 24.0, but trails Qwen3.7-Plus at 34.7 and Opus4.6 Max at 40.0. Similarly, on Terminal Bench 2.1, Qwen3.8-27B scores 73.0 compared to 78.2 for Opus4.6 Max.
On the card's table, Qwen3.8-27B is ahead of Opus4.6 Max on SWE-bench Pro and OSWorld-Verified. On SWE-bench Pro, Qwen3.8-27B scores 61.7, exceeding the officially reported 53.4 for Opus4.6 Max and 57.6 for Qwen3.7-Plus. The card's table puts Qwen3.6-27B at 53.5 on SWE-bench Pro and 63.4 on Terminal Bench 2.1; the Qwen3.8-27B vs Qwen3.6-27B page lines the two models up row by row.
- SWE-bench Pro: 61.7 for Qwen3.8-27B vs 53.5 for Qwen3.6-27B and 53.4 for Opus4.6 Max
- Terminal Bench 2.1: 73.0 for Qwen3.8-27B vs 63.4 for Qwen3.6-27B and 78.2 for Opus4.6 Max
- OSWorld-Verified: 84.3 for Qwen3.8-27B vs 63.9 for Qwen3.6-27B and 72.7 for Opus4.6 Max
- LiveCodeBench v6: 90.3 for Qwen3.8-27B vs 83.9 for Qwen3.6-27B and 88.8 for Opus4.6 Max
- GPQA Diamond: 89.2 for Qwen3.8-27B vs 87.8 for Qwen3.6-27B and 91.3 for Opus4.6 Max
- HLE: 30.8 for Qwen3.8-27B vs 24.0 for Qwen3.6-27B and 40.0 for Opus4.6 Max
Enterprise Implementation and Verification Steps for Qwen3.8 27B
Qwen3.8-27B is released under the Apache-2.0 license, and the card says the checkpoint works with Hugging Face Transformers, vLLM, SGLang and TokenSpeed. The card also describes native image and video understanding, from STEM diagrams and documents to hour-scale videos.
Before deploying the checkpoint into production, engineering teams must complete concrete technical verifications. Legal counsel should examine the Apache-2.0 terms on the official model card to verify compliance with organizational policies. Technical leads must also benchmark memory consumption and token generation speeds directly on target hardware, as the card lists no official hardware specifications. A r/LocalLLaMA thread titled "Engineer / developer observations of Gemma4-31B, Qwen3.8-27B, and 6.1-Sol for software engineering work" exists. Its contents were not read for this page, and community speed claims are unverified, so test on your own hardware.
Begin by downloading the checkpoint from the official repository, deploying it on a test cluster, and checking its accuracy on your own tasks.
- Verify legal terms: Confirm commercial compatibility of the Apache-2.0 license with internal legal counsel
- Measure local resource use: Benchmark VRAM occupancy across Transformers, vLLM, and SGLang directly on test servers
- Assess agentic retries: Test whether low or xhigh reasoning effort provides better net latency on internal workflows
- Audit vision accuracy: Validate native image and document extraction on proprietary files before workflow integration
What you need to run Qwen3.8-27B yourself
Qwen3.8-27B needs real memory, but it is within reach of a high-end workstation or a couple of professional GPUs — and many teams simply rent instead of buying. Match the path below to whether you want to own the hardware or pay by the hour.
| Path | What it is | Best for | Get started |
|---|---|---|---|
| Call the hosted API | Use Qwen3.8-27B as a pay-per-token API — zero hardware | Most teams; getting started | OpenRouter |
| Rent GPUs by the hour | Spin up an H100 / A100 for a few dollars an hour | Flexible self-hosting without buying cards | RunPod |
| Local on unified memory | One Mac with enough unified memory to hold a 4-bit quant | A single quiet on-prem box | Apple Mac Studio (M4 Max, 128GB) |
| Local on a workstation GPU | One 48GB pro card, or two 24GB consumer cards | Power users who want hardware they own | NVIDIA RTX 6000 Ada (48GB) |
To put Qwen3.8-27B to work once it is live, connect a coding client like Cursor (via OpenRouter) or a local runner such as Ollama.
Frequently Asked Questions
- According to the official model card, Qwen3.8-27B is strongest at agentic coding, computer use, and long-horizon office workflows. Vendor-reported scores place it at 61.7 on SWE-bench Pro, 73.0 on Terminal Bench 2.1, 84.3 on OSWorld-Verified, and 90.3 on LiveCodeBench v6.
- Yes, the Qwen3.8-27B model weights are free to download from Hugging Face, and the card carries an Apache-2.0 license tag. Have counsel read the license terms before commercial use.
- The model weights carry zero licensing cost, but operational costs depend on your own hosting infrastructure. The official model card does not publish a hardware requirement, a VRAM figure, or a price for running it, and the official Qwen Cloud hosted API is listed as coming soon as of October 2026.
- You can run Qwen3.8-27B locally by loading the checkpoint through Hugging Face Transformers or dedicated high-throughput serving engines like vLLM, SGLang, and TokenSpeed. The model card supports an OpenAI-compatible Python software development kit (SDK) interface calling model identifier Qwen/Qwen3.8-27B.
- The Qwen team does not publish video random access memory (VRAM) specifications or hardware minimums on the official model card. Because requirements are not published, deployment teams must measure memory usage directly on their specific target hardware.
- No, Qwen3.8-27B is not a mixture-of-experts model. The model card describes it as a dense causal language model with 27 billion parameters, featuring 64 layers and a hidden dimension of 5120.
- Yes, Qwen3.8-27B includes a native vision encoder that processes both static images and video inputs. The model card highlights capabilities ranging from science, technology, engineering, and mathematics (STEM) diagrams and visual documents to hour-scale video files.
Plan Your Local Model Architecture
At Layer3Labs, we build custom agents, enterprise integrations, and advisory engagements for small and mid-sized business workflows.
Book a Consultation