What the family record covers
The official Qwen3 repository documents multiple dense and mixture-of-experts sizes, plus instruct and thinking variants. It also documents local and production serving paths across several inference frameworks.
A Qwen3 record is therefore a family map, not one performance profile. Evaluation must name the checkpoint, revision, quantization, inference framework, context settings, prompt mode, and hardware or hosted endpoint.
Documented access paths
- Official Qwen model repositories and named model hubs
- Self-managed inference through supported open serving frameworks
- Provider-hosted access is a separate deployment whose live catalog must be checked
Capabilities to verify
- Multilingual instruction following in the languages the workflow actually serves
- Thinking versus instruct behavior on the same acceptance set
- Tool-call formatting under the chosen serving framework
- Quality and resource impact of checkpoint size and quantization
Decision questions
- Which Qwen3 checkpoint and revision are within the deployment budget?
- Should thinking and instruct workloads use separate pinned variants?
- Which serving framework and prompt template will be treated as production configuration?
Evaluation cautions
- Qwen3 family members are not interchangeable across sizes and modes.
- Third-party model labels may not map cleanly to the official checkpoint name.
- Self-hosting shifts availability, security, and upgrade responsibility to the operator.
Related decisions
Move from a family name to the product, provider, workflow, comparison, or protocol that defines the real choice.
Sources checked
Open the original pages before relying on a time-sensitive product decision.