Qwen/Qwen3-8B
Qwen3-8B
Qwen3-8B
Updated Sep 9, 2026
Parameters
8.2B
Context
40,960
License
apache-2.0
Updated
Sep 9, 2026
Intelligence benchmarks
Composite scores from sourced benches. Color is paired with the number — green is not a grade by itself.
Intelligence
67.1
Composite of sourced benchmarks on this listing.
Intelligence index — Qwen3-8B vs the field
Open-weight models in this directory. Proprietary scores are not invented here.
Standard benchmarks
Each row is a sourced number. Open the source before you treat it as a ranking.
Will it run on your hardware?
Runs on your 24 GB — best at FP8
Dashed line is your 24 GB budget
Run it locally
Copy-paste. Then read the how-to if you have not set up a runtime yet.
weights
Hugging Face
huggingface-cli download Qwen/Qwen3-8B
Download, then load with llama.cpp or a GGUF conversion.
OpenAI-compatible API
vLLM
vllm serve Qwen/Qwen3-8B
Best when you already have a GPU server and want an HTTP endpoint.
How to run Qwen3-8B locally · Guides for first-time local setup
Deep dive
Notes, sources, and the write-up on this listing.
Finding a dependable open-weight model that handles both rapid conversational chat and deep analytical reasoning on consumer hardware has historically required juggling multiple checkpoints. Enter Qwen3-8B local deployments, which bridge this divide by packing roughly 8.2 billion parameters into a dense architecture capable of seamless mode-switching.
Built by the team at Qwen, this checkpoint arrives under the permissive Apache 2.0 license, allowing developers and researchers to inspect, fine-tune, and deploy the weights without restrictive proprietary clauses. Whether you are upgrading from smaller variants like Qwen2.5-3B-Instruct or comparing it against legacy releases such as Qwen2.5-7B-Instruct , this generation introduces native dual-mode execution that fundamentally changes how an 8B model behaves under the hood.
By incorporating both a deliberative thinking mode and an instantaneous standard dialogue mode into a single set of weights, it eliminates the need to run separate reasoning-specialized models for math tasks and quick chat applications.
At its technical foundation, Qwen3-8B features 36 transformer layers backed by Grouped-Query Attention, utilizing 32 query heads and 8 key-value heads to optimize memory bandwidth during inference. The non-embedding parameter footprint sits around 6.95 billion, striking an optimal balance that fits comfortably on mainstream consumer graphics cards when paired with standard quantization techniques.
While lightweight models like Qwen3-0.6B or Qwen2.5-1.5B-Instruct serve edge devices and latency-critical scripts, and massive setups like Qwen3.6-35B-A3B-NVFP4 demand enterprise accelerators, the 8-billion-parameter tier remains the sweet spot for single-GPU desktop workstations. The model supports a native context window of 32,768 tokens, which can be extended significantly via YaRN for long-form document ingestion.
Developers interacting with the official repository at Hugging Face will find a fully integrated Hugging Face transformers configuration ready for immediate text generation, local inference, and API serving.
Hardware Requirements, Memory Footprint, and Quantization Strategies
Running an 8.2B dense model locally requires careful planning around VRAM capacity, system RAM, and the specific quantization format you choose. In unquantized FP16, the model weights alone demand roughly 16.4 gigabytes of memory, pushing it past the threshold of standard 16 GB consumer GPUs once context overhead and the KV cache are factored into the equation.
To achieve smooth, real-time generation speeds on popular hardware such as an RTX 4070 or RTX 3060 12GB, practitioners rely on quantization. A 4-bit quantization format (such as Q4_K_M) compresses the model footprint significantly, letting the entire parameter set occupy around 5.5 to 6 gigabytes. This leaves ample headroom for context caching and system desktop rendering without triggering memory swapping.
When configuring your local environment using runners like Ollama , llama.cpp , or vLLM , monitoring your GPU allocation via system utilities is essential. If your token generation speeds drop drastically or memory usage overflows into shared system RAM, your context window or quantization level is too aggressive for your hardware tier.
For users with 24 GB of VRAM, stepping up to an FP8 or Q8_0 quant yields maximum fidelity while keeping inference latency exceptionally low. Always match your GGUF file or safetensors loading script to the exact parameter constraints of your machine rather than forcing uncompressed weights onto a constrained card.
Dual-Mode Architecture: Thinking versus Non-Thinking Execution
The defining innovation of the Qwen3 generation is its native dual-mode execution pipeline, which allows a single model checkpoint to alternate between deliberate logical reasoning and rapid conversational responses. When `enable_thinking=True` is passed through the chat template, the model enters its reasoning phase, generating a structured chain of thought enclosed within ` ` and ` ` XML tags prior to outputting its final answer.
This mode mirrors the deliberative style of specialized reasoning models, excelling at complex mathematical problem-solving, multi-step code generation, and intricate logical deduction. Benchmark evaluations highlight its strength here, showing competitive scores in complex reasoning domains.
Conversely, setting `enable_thinking=False` deactivates the internal reasoning trace entirely, snapping the model's behavior back to the lightning-fast efficiency seen in standard instruct checkpoints. This non-thinking mode is ideal for high-throughput customer support scripts, creative writing, role-playing, and general multi-turn dialogue where latency matters more than deep mathematical proofing. Furthermore, users can dynamically switch modes mid-conversation by injecting routing commands like `/think` or `/no_think` directly into user prompts.
This flexibility ensures that developers do not need to maintain two distinct model binaries in production; one versatile 8B file adapts dynamically to whatever query type the user submits.
Multilingual Mastery, Agentic Workflows, and Practical Application
Beyond its dual-mode reasoning capabilities, Qwen3-8B demonstrates robust performance across more than 100 languages and dialects, making it an exceptional engine for globalized applications, cross-lingual translation, and regional dialect interpretation. Its post-training alignment ensures strong instruction-following characteristics, reducing instances of hallucination and format drift during multi-turn exchanges.
In benchmark evaluations, it achieves an MMLU score of 76.89, an MMLU-Pro score of 56.73, and a GSM8K score of 89.84, underscoring its solid academic and logical foundation. Furthermore, its coding proficiency is reflected in an MBPP score of 69.80, while structured output adherence is validated by an IFStruct score of 79.75.
Agentic integration is another major focus for this architecture. The model is specifically optimized to interface with external tools, APIs, and function-calling frameworks in both thinking and non-thinking modes. Developers building autonomous agent loops can rely on its precise JSON formatting and predictable tool-use syntax to orchestrate multi-step workflows.
Whether you are building a local RAG pipeline that digests dense technical documentation or setting up a local coding assistant inside your IDE, Qwen3-8B delivers the reasoning depth and speed required for production-grade open-source deployments.
What makes Qwen3-8B special
- Dense architecture. 8.2B parameters.
- Context window. 40,960 tokens native.
- License. apache-2.0 — permissive for local use.
- Modalities. text
- Weights. Use the Hugging Face repo with vLLM or llama.cpp.
- Use cases. general-chat
Frequently asked
Quick answers to common questions.
Will Qwen3-8B run on an 8 GB graphics card?
Running this model on an 8 GB card is extremely tight and generally requires aggressive 4-bit quantization (such as Q4_K_M) alongside a restricted context window. Because modern operating systems and display drivers consume several gigabytes of VRAM independently, you may experience memory spillover into system RAM, which severely degrades generation speed. Always verify your VRAM budget before attempting a load.
How much VRAM do I need for smooth inference?
For comfortable local execution at standard context lengths, a GPU with 12 GB to 16 GB of VRAM is recommended when using Q4 or Q5 quantization. If you prefer running unquantized FP16 weights or maintaining a full 32k context window without offloading, a 24 GB card or multi-GPU setup is necessary to prevent memory bottlenecks.
Where can I download the official weights and GGUF files?
The official safetensors repository is hosted at Hugging Face under `Qwen/Qwen3-8B`. For local GGUF runners, community-contributed and official quantized files can also be found on Hugging Face repositories maintained by trusted converters.
Can I serve Qwen3-8B using Ollama or vLLM?
Yes. The model is fully supported by modern versions of Ollama, llama.cpp, SGLang, and vLLM. For vLLM and SGLang deployments, you can leverage native reasoning parsers to cleanly separate the internal thinking tokens from the final generated output.
What is the native context length supported by the model?
The architecture supports a native context window of 32,768 tokens out of the box. Through advanced positional embedding techniques like YaRN, this window can be extended further, though doing so increases memory consumption for the KV cache proportionally.
What license governs the use of Qwen3-8B?
The model is released under the Apache 2.0 license, making it highly permissive for both commercial integration and academic research. Be sure to review the full license terms in the model repository before shipping derivative products. How to run Qwen3-8B locally starts with a VRAM check, then a runner choice, then one clean load at Q4. Running Qwen3-8B on your own hardware requires selecting a compatible inference engine, downloading an appropriate quantization level that matches your available VRAM, and configuring your chat templates correctly to handle the dual-mode reasoning features. This step-by-step runbook outlines the path from initial setup to active local generation.
1. Verify Hardware and Select Your Quantization
Before downloading gigabytes of weights, check your GPU VRAM. If you have a 12 GB or 16 GB card, target a 4-bit or 5-bit GGUF variant (such as `Q4_K_M`) to keep model memory under 7 GB. If you have 24 GB of VRAM or more, you can comfortably run 8-bit quants or FP16 weights. Ensure your drivers and CUDA toolkit are fully up to date.
2. Choose Your Local Inference Backend
For a quick desktop chat experience, install Ollama or LM Studio and pull the Qwen3-8B model tag. If you prefer fine-grained control over generation parameters, system prompt injection, and tensor parallelism, build llama.cpp from source or configure vLLM for high-throughput API serving. For vLLM deployments, remember to pass the appropriate reasoning parser flag so that internal ` ` blocks are correctly handled.
3. Load the Model and Set Your Parameters
When initiating your first inference session, apply the recommended sampling configurations provided by the authors. For thinking mode (`enable_thinking=True`), use a temperature around 0.6 with a TopP of 0.95 and TopK of 20, avoiding greedy decoding to prevent repetitive loops. For standard non-thinking mode (`enable_thinking=False`), a temperature of 0.7 with TopP of 0.8 works best.
4. Test and Monitor Performance
Send a test prompt—such as a complex coding problem or a multilingual translation task—and monitor your tokens-per-second output alongside VRAM usage. If generation is sluggish or memory swapping occurs, reduce your active context window or switch to a lower bit-width quantization format. Always bind local server instances strictly to localhost unless authenticated proxy security is in place.
Will Qwen3-8B run on 8 GB?
Often at Q4 if the calculator on this page says it fits. 8 GB is tight once the desktop, context, and KV cache share the same pool. Trust the VRAM chart, not a screenshot.
How much VRAM does Qwen3-8B need?
Qwen3-8B is about 8.2B (dense). Q4_K_M is the default local starting point. Raise quant only after you have headroom; drop context if the card starts using shared memory.
Compare and pair with
Nearby parameter counts and cards that can hold Q4.