This model is quantized to 8-bit with a group size of 128. Compared to earlier quantized versions, the new quantized model demonstrates better tokens/s efficiency. This improvement comes from setting desc_act=False in the quantization configuration.
Over the past three months, we have continued to scale the thinking capability of Qwen3-30B-A3B, improving both the quality and depth of reasoning. We are pleased to introduce Qwen3-30B-A3B-Thinking-2507, featuring the following key enhancements:
Significantly improved performance on reasoning tasks, including logical reasoning, mathematics, science, coding, and academic benchmarks that typically require human expertise.
Markedly better general capabilities, such as instruction following, tool usage, text generation, and alignment with human preferences.
NOTE: This version has an increased thinking length. We strongly recommend its use in highly complex reasoning tasks.
image/jpeg
Model Overview
Qwen3-30B-A3B-Thinking-2507 has the following features:
Type: Causal Language Models
Training Stage: Pretraining & Post-training
Number of Parameters: 30.5B in total and 3.3B activated
Number of Paramaters (Non-Embedding): 29.9B
Number of Layers: 48
Number of Attention Heads (GQA): 32 for Q and 4 for KV
Number of Experts: 128
Number of Activated Experts: 8
Context Length: 262,144 natively.
NOTE: This model supports only thinking mode. Meanwhile, specifying enable_thinking=True is no longer required.
Additionally, to enforce model thinking, the default chat template automatically includes <think>. Therefore, it is normal for the model's output to contain only </think> without an explicit opening <think> tag.
For more details, including benchmark evaluation, hardware requirements, and inference performance, please refer to our blog, GitHub, and Documentation.
Performance
Gemini2.5-Flash-Thinking
Qwen3-235B-A22B Thinking
Qwen3-30B-A3B Thinking
Qwen3-30B-A3B-Thinking-2507
Knowledge
MMLU-Pro
81.9
82.8
78.5
80.9
MMLU-Redux
92.1
92.7
89.5
91.4
GPQA
82.8
71.1
65.8
73.4
SuperGPQA
57.8
60.7
51.8
56.8
Reasoning
AIME25
72.0
81.5
70.9
85.0
HMMT25
64.2
62.5
49.8
71.4
LiveBench 20241125
74.3
77.1
74.3
76.8
Coding
LiveCodeBench v6 (25.02-25.05)
61.2
55.7
57.4
66.0
CFEval
1995
2056
1940
2044
OJBench
23.5
25.6
20.7
25.1
Alignment
IFEval
89.8
83.4
86.5
88.9
Arena-Hard v2$
56.7
61.5
36.3
56.0
Creative Writing v3
85.0
84.6
79.1
84.4
WritingBench
83.9
80.3
77.0
85.0
Agent
BFCL-v3
68.6
70.8
69.1
72.4
TAU1-Retail
65.2
54.8
61.7
67.8
TAU1-Airline
54.0
26.0
32.0
48.0
TAU2-Retail
66.7
40.4
34.2
58.8
TAU2-Airline
52.0
30.0
36.0
58.0
TAU2-Telecom
31.6
21.9
22.8
26.3
Multilingualism
MultiIF
74.4
71.9
72.2
76.4
MMLU-ProX
80.2
80.0
73.1
76.4
INCLUDE
83.9
78.7
71.9
74.4
PolyMATH
49.8
54.7
46.1
52.6
$ For reproducibility, we report the win rates evaluated by GPT-4.1.
& For highly challenging tasks (including PolyMATH and all reasoning and coding tasks), we use an output length of 81,920 tokens. For all other tasks, we set the output length to 32,768.
Quickstart
The code of Qwen3-MoE has been in the latest Hugging Face transformers and we advise you to use the latest version of transformers.
With transformers<4.51.0, you will encounter the following error:
KeyError: 'qwen3_moe'
The following contains a code snippet illustrating how to use the model generate content based on given inputs.
python
1from transformers import AutoModelForCausalLM, AutoTokenizer
23model_name ="Qwen/Qwen3-30B-A3B-Thinking-2507"45# load the tokenizer and the model6tokenizer = AutoTokenizer.from_pretrained(model_name)7model = AutoModelForCausalLM.from_pretrained(8 model_name,9 torch_dtype="auto",10 device_map="auto"11)1213# prepare the model input14prompt ="Give me a short introduction to large language model."15messages =[16{"role":"user","content": prompt}17]18text = tokenizer.apply_chat_template(19 messages,20 tokenize=False,21 add_generation_prompt=True,22)23model_inputs = tokenizer([text], return_tensors="pt").to(model.device)2425# conduct text completion26generated_ids = model.generate(27**model_inputs,28 max_new_tokens=3276829)30output_ids = generated_ids[0][len(model_inputs.input_ids[0]):].tolist()3132# parsing thinking content33try:34# rindex finding 151668 (</think>)35 index =len(output_ids)- output_ids[::-1].index(151668)36except ValueError:37 index =03839thinking_content = tokenizer.decode(output_ids[:index], skip_special_tokens=True).strip("\n")40content = tokenizer.decode(output_ids[index:], skip_special_tokens=True).strip("\n")4142print("thinking content:", thinking_content)# no opening <think> tag43print("content:", content)44
For deployment, you can use sglang>=0.4.6.post1 or vllm>=0.8.5 or to create an OpenAI-compatible API endpoint:
Note: If you encounter out-of-memory (OOM) issues, you may consider reducing the context length to a smaller value. However, since the model may require longer token sequences for reasoning, we strongly recommend using a context length greater than 131,072 when possible.
For local use, applications such as Ollama, LMStudio, MLX-LM, llama.cpp, and KTransformers have also supported Qwen3.
Agentic Use
Qwen3 excels in tool calling capabilities. We recommend using Qwen-Agent to make the best use of agentic ability of Qwen3. Qwen-Agent encapsulates tool-calling templates and tool-calling parsers internally, greatly reducing coding complexity.
To define the available tools, you can use the MCP configuration file, use the integrated tool of Qwen-Agent, or integrate other tools by yourself.
python
1from qwen_agent.agents import Assistant
23# Define LLM4# Using Alibaba Cloud Model Studio5llm_cfg ={6'model':'qwen3-30b-a3b-thinking-2507',7'model_type':'qwen_dashscope',8}910# Using OpenAI-compatible API endpoint. It is recommended to disable the reasoning and the tool call parsing11# functionality of the deployment frameworks and let Qwen-Agent automate the related operations. For example, 12# `VLLM_USE_MODELSCOPE=true vllm serve Qwen/Qwen3-30B-A3B-Thinking-2507 --served-model-name Qwen3-30B-A3B-Thinking-2507 --tensor-parallel-size 8 --max-model-len 262144`.13#14# llm_cfg = {15# 'model': 'Qwen3-30B-A3B-Thinking-2507',16# 17# # Use a custom endpoint compatible with OpenAI API:18# 'model_server': 'http://localhost:8000/v1', # api_base without reasoning and tool call parsing19# 'api_key': 'EMPTY',20# 'generate_cfg': {21# 'thought_in_content': True,22# },23# }242526# Define Tools27tools =[28{'mcpServers':{# You can specify the MCP configuration file29'time':{30'command':'uvx',31'args':['mcp-server-time','--local-timezone=Asia/Shanghai']32},33"fetch":{34"command":"uvx",35"args":["mcp-server-fetch"]36}37}38},39'code_interpreter',# Built-in tools40]4142# Define Agent43bot = Assistant(llm=llm_cfg, function_list=tools)4445# Streaming generation46messages =[{'role':'user','content':'https://qwenlm.github.io/blog/ Introduce the latest developments of Qwen'}]47for responses in bot.run(messages=messages):48pass49print(responses)
Processing Ultra-Long Texts
To support ultra-long context processing (up to 1 million tokens), we integrate two key techniques:
Dual Chunk Attention (DCA): A length extrapolation method that splits long sequences into manageable chunks while preserving global coherence.
MInference: A sparse attention mechanism that reduces computational overhead by focusing on critical token interactions.
Together, these innovations significantly improve both generation quality and inference efficiency for sequences beyond 256K tokens. On sequences approaching 1M tokens, the system achieves up to a 3× speedup compared to standard attention implementations.
[!NOTE]
To effectively process a 1 million token context, users will require approximately 240 GB of total GPU memory. This accounts for model weights, KV-cache storage, and peak activation memory demands.
Step 1: Update Configuration File
Download the model and replace the content of your config.json with config_1m.json, which includes the config for length extrapolation and sparse attention.
The fraction of the memory used for static allocation (model weights and KV cache memory pool). Use a smaller value if you see out-of-memory errors.
--tp 4
Tensor parallelism size (matches model sharding)
--chunked-prefill-size 131072
Prefill chunk size for handling long inputs without OOM
Troubleshooting:
Encountering the error: "The model's max sequence length (xxxxx) is larger than the maximum number of tokens that can be stored in the KV cache." or "RuntimeError: Not enough memory. Please try to increase --mem-fraction-static."
The VRAM reserved for the KV cache is insufficient.
vLLM: Consider reducing the max_model_len or increasing the tensor_parallel_size and gpu_memory_utilization. Alternatively, you can reduce max_num_batched_tokens, although this may significantly slow down inference.
SGLang: Consider reducing the context-length or increasing the tp and mem-frac. Alternatively, you can reduce chunked-prefill-size, although this may significantly slow down inference.
Encountering the error: "torch.OutOfMemoryError: CUDA out of memory."
The VRAM reserved for activation weights is insufficient. You can try lowering gpu_memory_utilization or mem-frac, but be aware that this might reduce the VRAM available for the KV cache.
Encountering the error: "Input prompt (xxxxx tokens) + lookahead slots (0) is too long and exceeds the capacity of the block manager." or "The input (xxx xtokens) is longer than the model's context length (xxx tokens)."
The input is too lengthy. Consider using a shorter sequence or increasing the max_model_len or context-length.
Long-Context Performance
We test the model on an 1M version of the RULER benchmark.
Model Name
Acc avg
4k
8k
16k
32k
64k
96k
128k
192k
256k
384k
512k
640k
768k
896k
1000k
Qwen3-30B-A3B (Thinking)
70.6
96.7
94.4
94.5
93.4
82.6
78.4
74.5
70.6
63.1
60.0
56.3
51.0
48.4
47.2
48.2
Qwen3-30B-A3B-Thinking-2507 (Full Attention)
91.4
99.6
100.0
99.8
99.2
97.4
96.8
96.8
94.8
89.4
90.2
84.0
82.6
81.9
80.1
77.5
Qwen3-30B-A3B-Thinking-2507 (Sparse Attention)
91.5
100.0
99.2
99.1
98.5
97.3
97.1
96.9
95.8
89.0
89.3
85.5
84.8
80.0
79.9
79.6
All models are evaluated with Dual Chunk Attention enabled.
Since the evaluation is time-consuming, we use 260 samples for each length (13 sub-tasks, 20 samples for each).
To avoid overly verbose reasoning, we set the thinking budget to 8,192 tokens.
Best Practices
To achieve optimal performance, we recommend the following settings:
Sampling Parameters:
We suggest using Temperature=0.6, TopP=0.95, TopK=20, and MinP=0.
For supported frameworks, you can adjust the presence_penalty parameter between 0 and 2 to reduce endless repetitions. However, using a higher value may occasionally result in language mixing and a slight decrease in model performance.
Adequate Output Length: We recommend using an output length of 32,768 tokens for most queries. For benchmarking on highly complex problems, such as those found in math and programming competitions, we suggest setting the max output length to 81,920 tokens. This provides the model with sufficient space to generate detailed and comprehensive responses, thereby enhancing its overall performance.
Standardize Output Format: We recommend using prompts to standardize model outputs when benchmarking.
Math Problems: Include "Please reason step by step, and put your final answer within \boxed{}." in the prompt.
Multiple-Choice Questions: Add the following JSON structure to the prompt to standardize responses: "Please show your choice in the answer field with only the choice letter, e.g., "answer": "C"."
No Thinking Content in History: In multi-turn conversations, the historical model output should only include the final output part and does not need to include the thinking content. It is implemented in the provided chat template in Jinja2. However, for frameworks that do not directly use the Jinja2 chat template, it is up to the developers to ensure that the best practice is followed.
Citation
If you find our work helpful, feel free to give us a cite.