Model identity matters
Pin the exact checkpoint and revision used in production. Family names can contain base, instruct, reasoning, quantized and provider-specific variants with different behavior.
Qwen3-235B-A22B is a large text Mixture-of-Experts reasoning model developed by Qwen / Alibaba in the Qwen3 family. It has 235B parameters with 22B/token active parameters, supports 32,768 native · 131,072 with YaRN of context, accepts Text and produces Text. Its primary role is reasoning, multilingual generation, agents, mathematics and coding.
OpenWeightModels separates the base checkpoint from its legal conditions and from each deployment implementation. This page is designed as an operational reference for people, search systems and AI agents—not as a single-number leaderboard.
Qwen3-235B-A22B is a large text Mixture-of-Experts reasoning model developed by Qwen / Alibaba in the Qwen3 family. It has 235B parameters with 22B/token active parameters, supports 32,768 native · 131,072 with YaRN of context, accepts Text and produces Text. Its primary role is reasoning, multilingual generation, agents, mathematics and coding.
The model belongs to the Qwen3 family and was released by Qwen / Alibaba. Its documented input is Text and its output is Text. The published context envelope is 32,768 native · 131,072 with YaRN, although a provider or runtime can expose a smaller operating limit.
For SEO and machine-readable retrieval, OpenWeightModels classifies it as a large text Mixture-of-Experts reasoning model whose primary application area is reasoning, multilingual generation, agents, mathematics and coding. This definition describes the model itself; licensing eligibility and the practical serving stack are analyzed separately below.
Official Hugging Face model ↗Qwen3 GitHub ↗Official GPTQ Int4 ↗Qwen3-235B-A22B is useful to evaluate because it combines a specific architecture, license and operating envelope rather than simply adding another row to a model leaderboard.
Qwen3 combines pretraining and post-training with a strong emphasis on reasoning, code, mathematics, multilingual instruction following and agent capabilities. Its dual interaction modes let applications trade deliberate reasoning against lower-latency direct answers.
From an infrastructure perspective, the key sizing facts are 235B total parameters, 22B/token active parameters and 32,768 native · 131,072 with YaRN of context. These values should be read together: weight memory, active compute and KV-cache growth describe different resource constraints.
From a governance perspective, the checkpoint is distributed under Apache License 2.0. OpenWeightModels records that independently from the fact that the weights are downloadable, because “open weight” is an access classification—not a universal statement about commercial, redistribution or derivative-work rights.
Pin the exact checkpoint and revision used in production. Family names can contain base, instruct, reasoning, quantized and provider-specific variants with different behavior.
Tool calling, structured output, safety layers, quotas and maximum context can be added or restricted by the serving layer. Store them as deployment records, not as unconditional properties of the weights.
Licenses, provider availability and runtime compatibility can change independently. Production reviews should use the official source links and a dated internal record.
Values describe the named checkpoint/family release unless a deployment implementation is explicitly named. Where the publisher does not document a value, OpenWeightModels avoids inventing one.
Qwen3-235B-A22B uses sparse expert routing rather than activating its complete parameter pool for every token. The distinction between 235B total parameters and 22B/token active parameters is central to capacity planning: active parameters influence compute per token, while the complete expert set still affects storage, model loading, sharding and network topology.
This is why OpenWeightModels never maps the active-parameter figure directly to a dense-model hardware class. A sparse model can be computationally efficient per token and still require datacenter-class memory and interconnect to keep all experts available.
Publisher-documented architecture details for this checkpoint include the elements below. These details are more useful for deployment planning than a parameter count alone because attention layout, expert routing, modality encoders and context design can affect throughput and memory independently.
94 layers
128 experts with 8 activated experts per token
GQA with 64 query heads and 4 KV heads
Hybrid thinking and non-thinking interaction modes
Native 32K context with documented YaRN extension to 131K
Training provenance matters because two checkpoints with similar architecture can behave very differently after data selection, instruction tuning, reinforcement learning or domain specialization.
Qwen3 combines pretraining and post-training with a strong emphasis on reasoning, code, mathematics, multilingual instruction following and agent capabilities. Its dual interaction modes let applications trade deliberate reasoning against lower-latency direct answers.
OpenWeightModels distinguishes facts explicitly published by the developer from inference based on model behavior. Dataset composition, cutoff dates and training compute are shown only when the publisher exposes them; absence of a number is not silently filled with an estimate.
Capability claims are treated as task-level evidence, not permission to deploy autonomously. Tool access, code execution and external actions always depend on the surrounding application.
Qwen3-235B-A22B is relevant to reasoning. Capability should be validated against the exact checkpoint, prompt format and runtime rather than inferred only from family branding or a benchmark headline.
Qwen3-235B-A22B is relevant to multilingual generation. Capability should be validated against the exact checkpoint, prompt format and runtime rather than inferred only from family branding or a benchmark headline.
Qwen3-235B-A22B is relevant to agents. Capability should be validated against the exact checkpoint, prompt format and runtime rather than inferred only from family branding or a benchmark headline.
Qwen3-235B-A22B is relevant to mathematics. Capability should be validated against the exact checkpoint, prompt format and runtime rather than inferred only from family branding or a benchmark headline.
Qwen3-235B-A22B is relevant to coding. Capability should be validated against the exact checkpoint, prompt format and runtime rather than inferred only from family branding or a benchmark headline.
Qwen3-235B-A22B is relevant to custom deployment. Capability should be validated against the exact checkpoint, prompt format and runtime rather than inferred only from family branding or a benchmark headline.
OpenWeightModels records benchmark evidence without collapsing heterogeneous evaluations into an overall ranking. Scores can change with checkpoint revision, prompt, sampling, scaffold, precision and evaluator version.
Where a publisher reports a useful, clearly attributable metric it is shown below. Otherwise the passport points back to the official evaluation tables instead of manufacturing a cross-model score.
| Evaluation | Metric / setup | Value | Qualification |
|---|---|---|---|
| Publisher evaluation | Model-card evidence | Not normalized | OpenWeightModels does not invent a single composite score for Qwen3-235B-A22B. Use the official model card for checkpoint-specific benchmarks and conditions. |
Apache License 2.0 is the controlling license/terms classification recorded for this checkpoint. OpenWeightModels keeps the legal layer separate from technical availability.
Includes an express patent grant. Model-specific acceptable-use policies, if separately published, are not automatically part of Apache 2.0.
Permissive open-source software license. This summary supports comparison only; the linked official text remains authoritative.
| Question | Classification | Practical meaning |
|---|---|---|
| Commercial use | Allowed | Commercial eligibility follows the named license/terms; provider and jurisdictional conditions may add requirements. |
| Modification / fine-tuning | Allowed | Weight adaptation and derivative work rights are summarized from the official license type. |
| Redistribution | Allowed with license/notice conditions | Redistribution is a separate question from the ability to download and run weights. |
| Hosted inference | License-dependent | Running a hosted service may count as distribution or trigger provider/model-specific terms; verify the official text for this checkpoint. |
| Open-weight classification | Yes | Weights are publicly obtainable; this label does not imply identical licensing freedom across models. |
Deployment is recorded as a set of implementations rather than one “self-hostable: yes” flag. A runtime can change context support, quantization, API shape, tool parsers, throughput and hardware requirements without changing the underlying model identity.
For Qwen3-235B-A22B, the most relevant documented or established routes are listed below.
| Route | Type | Qualification |
|---|---|---|
| Transformers | Self-hosted | Direct checkpoint loading and generation. |
| SGLang | Serving | Qwen recommends SGLang for large multi-GPU and quantized deployments. |
| vLLM | Serving | Qwen documents vLLM with reasoning parsers and OpenAI-compatible endpoints. |
| GPTQ/AWQ ecosystem | Quantized serving | Official and ecosystem quantizations lower weight memory; support varies by runtime. |
Direct checkpoint loading and generation.
Qwen recommends SGLang for large multi-GPU and quantized deployments.
Qwen documents vLLM with reasoning parsers and OpenAI-compatible endpoints.
Official and ecosystem quantizations lower weight memory; support varies by runtime.
The 235B total parameter set remains datacenter-scale despite 22B active parameters. Expert/tensor parallelism and reduced precision are central to realistic serving. Qwen specifically recommends SGLang or vLLM for its GPTQ multi-GPU path.
Real memory use includes model weights, KV cache, activations/buffers, multimodal encoders when applicable, framework overhead and batching. A published “fits on” statement is meaningful only together with precision, context, batch and host/GPU topology.
BF16/FP16 maximize fidelity but increase weight memory. FP8, INT8 and 4-bit variants can substantially lower memory, with support and quality depending on the quantization recipe and runtime.
32,768 native · 131,072 with YaRN is a model/configuration reference, not a promise that every machine or provider can serve that context at practical latency. KV-cache growth often becomes the dominant long-context constraint.
Large dense models need tensor/pipeline parallelism; large MoE models add expert-routing and communication requirements. Smaller checkpoints can often avoid these operational complexities.
Base, instruct, reasoning, FP8, GGUF and provider-hosted variants can have different behavior, memory and provenance. Production systems should pin an exact model/revision rather than only the family name.
| Variant | Purpose | Precision / form | Status |
|---|---|---|---|
| Qwen3-235B-A22B | Base published model | BF16 | Official |
| GPTQ-Int4 | Reduced-memory inference | 4-bit | Official Qwen |
| Other AWQ/FP8 variants | Optimized deployment | Varies | Publisher/ecosystem |
Qwen3-235B-A22B is most relevant when the application specifically values reasoning, multilingual generation, agents, mathematics and coding. That should be balanced against its hardware class, context behavior, license and modality requirements.
A smaller model can be operationally superior when latency, privacy, device deployment or predictable cost matter more than peak benchmark capability. Conversely, a larger sparse model may justify its complexity when the workload benefits from higher capacity, sophisticated reasoning or agent behavior.
The selection decision should therefore compare at least five dimensions: required task quality, data/control requirements, legal eligibility, serving cost and ecosystem/runtime support. OpenWeightModels exposes these dimensions separately so a model is not selected on benchmark reputation alone.
A high-quality passport gives limitations the same visibility as capabilities. These are model- and deployment-selection notes, not generic disclaimers.
YaRN-extended context is not identical to native-context behavior; long-context quality and cost should be tested.
Thinking mode can materially increase output length, latency and serving cost.
MoE active parameters do not represent complete storage requirements.
Tool use depends on prompting/runtime integrations rather than a single universal API behavior.
Last full review: 29 September 2026. Publisher model cards, repositories and license texts are preferred. Runtime claims are attached to the relevant runtime/provider rather than inferred from the base checkpoint.
Where documentation conflicts or a field is ambiguous, the passport uses the more conservative interpretation and explains the discrepancy instead of silently selecting the largest number.
Material changes to license, model revision, runtime support or provider limits should update both the field and this history.
Gold-standard Passport v2.0 created with SEO/GEO definition, architecture, training, capability, evaluation, license, deployment, hardware, variants, limitations and source review.
Qwen3-235B-A22B is a large text Mixture-of-Experts reasoning model developed by Qwen / Alibaba in the Qwen3 family. It has 235B parameters with 22B/token active parameters, supports 32,768 native · 131,072 with YaRN of context, accepts Text and produces Text. Its primary role is reasoning, multilingual generation, agents, mathematics and coding.
OpenWeightModels classifies it as open-weight because weights are publicly available. The exact legal classification depends on Apache License 2.0; weight availability should not be used as a substitute for reading those terms.
Our license classification is Allowed. Review the official license and any separate use policy, provider terms and jurisdictional rules before production use.
The documented reference in this passport is 32,768 native · 131,072 with YaRN. A runtime/provider may expose a different maximum or a smaller recommended operating range.
Yes, the open weights enable independent deployment where the license permits it. Practical feasibility depends on 235B of weights, precision, context length and the runtime routes listed above.