Model Comparison

Qwen3.5-397B-A17B vs Qwen2.5 14B Instruct

Qwen3.5-397B-A17B significantly outperforms across most benchmarks.

Performance Benchmarks

Comparative analysis across standard metrics

3 benchmarks

Qwen3.5-397B-A17B outperforms in 3 benchmarks (GPQA, MMLU-Pro, MMLU-Redux), while Qwen2.5 14B Instruct is better at 0 benchmarks.

Qwen3.5-397B-A17B significantly outperforms across most benchmarks.

Fri Apr 17 2026 • llm-stats.com

Arena Performance

Human preference votes

Pricing Analysis

Price comparison per million tokens

Cost data unavailable.

Lowest available price from all providers
Fri Apr 17 2026 • llm-stats.com
Alibaba Cloud / Qwen Team
Qwen3.5-397B-A17B
Input tokens$0.60
Output tokens$3.60
Best providerNovita
Alibaba Cloud / Qwen Team
Qwen2.5 14B Instruct
Input tokens$0.00
Output tokens$0.00
Best providerUnknown Organization
Notice missing or incorrect data?Start an Issue

Model Size

Parameter count comparison

382.3B diff

Qwen3.5-397B-A17B has 382.3B more parameters than Qwen2.5 14B Instruct, making it 2600.7% larger.

Alibaba Cloud / Qwen Team
Qwen3.5-397B-A17B
397.0Bparameters
Alibaba Cloud / Qwen Team
Qwen2.5 14B Instruct
14.7Bparameters
397.0B
Qwen3.5-397B-A17B
14.7B
Qwen2.5 14B Instruct

Context Window

Maximum input and output token capacity

Only Qwen3.5-397B-A17B specifies input context (262,144 tokens). Only Qwen3.5-397B-A17B specifies output context (64,000 tokens).

Alibaba Cloud / Qwen Team
Qwen3.5-397B-A17B
Input262,144 tokens
Output64,000 tokens
Alibaba Cloud / Qwen Team
Qwen2.5 14B Instruct
Input- tokens
Output- tokens
Fri Apr 17 2026 • llm-stats.com

Input Capabilities

Supported data types and modalities

Qwen3.5-397B-A17B supports multimodal inputs, whereas Qwen2.5 14B Instruct does not.

Qwen3.5-397B-A17B can handle both text and other forms of data like images, making it suitable for multimodal applications.

Qwen3.5-397B-A17B

Text
Images
Audio
Video

Qwen2.5 14B Instruct

Text
Images
Audio
Video

License

Usage and distribution terms

Both models are licensed under Apache 2.0.

Both models share the same licensing terms, providing consistent usage rights.

Qwen3.5-397B-A17B

Apache 2.0

Open weights

Qwen2.5 14B Instruct

Apache 2.0

Open weights

Release Timeline

When each model was launched

Qwen3.5-397B-A17B was released on 2026-02-16, while Qwen2.5 14B Instruct was released on 2024-09-19.

Qwen3.5-397B-A17B is 17 months newer than Qwen2.5 14B Instruct.

Qwen3.5-397B-A17B

Feb 16, 2026

2 months ago

1.4yr newer
Qwen2.5 14B Instruct

Sep 19, 2024

1.6 years ago

Knowledge Cutoff

When training data ends

Neither model specifies a knowledge cutoff date.

Unable to compare the recency of their training data.

No cutoff dates available

Outputs Comparison

Notice missing or incorrect data?Start an Issue discussion

Key Takeaways

Alibaba Cloud / Qwen Team

Qwen3.5-397B-A17B

View details

Alibaba Cloud / Qwen Team

Larger context window (262,144 tokens)
Supports multimodal inputs
Higher GPQA score (88.4% vs 45.5%)
Higher MMLU-Pro score (87.8% vs 63.7%)
Higher MMLU-Redux score (94.9% vs 80.0%)
Alibaba Cloud / Qwen Team

Qwen2.5 14B Instruct

View details

Alibaba Cloud / Qwen Team

Detailed Comparison

AI Model Comparison Table
Feature
Alibaba Cloud / Qwen Team
Qwen3.5-397B-A17B
Alibaba Cloud / Qwen Team
Qwen2.5 14B Instruct

FAQ

Common questions about Qwen3.5-397B-A17B vs Qwen2.5 14B Instruct

Qwen3.5-397B-A17B significantly outperforms across most benchmarks. Qwen3.5-397B-A17B is made by Alibaba Cloud / Qwen Team and Qwen2.5 14B Instruct is made by Alibaba Cloud / Qwen Team. The best choice depends on your use case — compare their benchmark scores, pricing, and capabilities above.
Qwen3.5-397B-A17B scores MMLU-Redux: 94.9%, HMMT 2025: 94.8%, C-Eval: 93.0%, HMMT25: 92.7%, IFEval: 92.6%. Qwen2.5 14B Instruct scores GSM8k: 94.8%, HumanEval: 83.5%, MBPP: 82.0%, MATH: 80.0%, MMLU-Redux: 80.0%.
Qwen3.5-397B-A17B supports 262K tokens and Qwen2.5 14B Instruct supports an unknown number of tokens. A larger context window lets you process longer documents, conversations, or codebases in a single request.
Key differences include multimodal support (yes vs no). See the full comparison above for benchmark-by-benchmark results.