Qwen3.5 35B A3B vs Qwen3.8 2.4T A95B
At a Glance
| Compare | Qwen3.5 35B A3BQwen | |
|---|---|---|
| Pricing and Limits | ||
| Input priceFrom · USD / 1M tokens | $0.14Deepinfra ↗ · Sep 21, 2026 | $2.00Deepinfra ↗ · Sep 21, 2026 |
| Output priceFrom · USD / 1M tokens | $1.00Deepinfra ↗ · Sep 21, 2026 | $6.00Deepinfra ↗ · Sep 21, 2026 |
| Context windowMaximum documented tokens | 262K | 262K |
| Model facts checked | Aug 28, 2026View model evidence → | Aug 28, 2026View model evidence → |
Token prices are the lowest available sourced USD rates; input and output may use different providers. Cost ranking estimates output spend on LiveBench, not a full request bill. Ranking methodology →
Available Benchmarks
Side-by-Side Facts
| Field | Qwen3.5-35B-A3B | Qwen3.8-2.4T-A95B |
|---|---|---|
| Developer | Qwen | Qwen |
| Family | Qwen3 5 35b A3b | Qwen3 8 2 4t A95b |
| Model | Qwen3.5-35B-A3B | Qwen3.8-2.4T-A95B |
| Version | Qwen3.5-35B-A3B | Qwen3.8-2.4T-A95B |
| Lifecycle | active | active |
| Released | Unknown | Unknown |
| Knowledge cutoff | Unknown | Unknown |
| Input modalities | Text, Image | Text |
| Output modalities | Text | Text |
| Context window | 262K | 262K |
| Total parameters | 36B | 2.4T |
| Active parameters | 3B | 95B |
| License | apache-2.0 | other |
| Open weights | Yes | Yes |
| API available | Yes | Yes |
| Self-hostable | Yes | Yes |
| Provider access | Deepinfra (Standard), Hugging Face (Standard), Openrouter (Standard), Together Ai (Standard) | Deepinfra (Standard), Fireworks Ai (Standard), Hugging Face (Standard), Openrouter (Standard), Together Ai (Standard) |
| Capabilities | chat, generation, reasoning, tools | chat, generation, reasoning, tools |
Qwen3.5 35B A3B Capabilities
Qwen3.8 2.4T A95B Capabilities
Primary Evidence
Sources and Freshness
Questions
Qwen3.5 35B A3B vs Qwen3.8 2.4T A95B FAQs
Is Qwen3.5 35B A3B or Qwen3.8 2.4T A95B better for coding?+
This comparison does not currently contain a protocol-matched coding benchmark for both Qwen3.5 35B A3B and Qwen3.8 2.4T A95B, so Model Markets cannot name a coding leader from pricing, context size, or capability labels alone.
Which is cheaper, Qwen3.5 35B A3B or Qwen3.8 2.4T A95B?+
Qwen3.5 35B A3B is $0.14 and Qwen3.8 2.4T A95B is $2.00 per million tokens, so Qwen3.5 35B A3B is cheaper on this metric. Qwen3.5 35B A3B is $1.00 and Qwen3.8 2.4T A95B is $6.00 per million tokens, so Qwen3.5 35B A3B is cheaper on this metric.
Which has a larger context window, Qwen3.5 35B A3B or Qwen3.8 2.4T A95B?+
Neither model has a larger sourced context window in this comparison. Qwen3.5 35B A3B is 262K and Qwen3.8 2.4T A95B is 262K.
Which performs better in benchmarks, Qwen3.5 35B A3B or Qwen3.8 2.4T A95B?+
There is no overall benchmark winner: At least two independently verified, protocol-matched benchmarks are required for an overall winner.
Can Qwen3.5 35B A3B or Qwen3.8 2.4T A95B be self-hosted?+
Both models have the same recorded self-hosting status: supported. Qwen3.5 35B A3B is open weight; Qwen3.8 2.4T A95B is open weight.
Can Qwen3.5 35B A3B and Qwen3.8 2.4T A95B understand images?+
Qwen3.5 35B A3B is documented with image input; Qwen3.8 2.4T A95B is not documented with image input. This reflects supported input modalities, not vision quality.
Which can generate longer answers, Qwen3.5 35B A3B or Qwen3.8 2.4T A95B?+
Neither has a larger sourced maximum output. Qwen3.5 35B A3B is — and Qwen3.8 2.4T A95B is —.
Do Qwen3.5 35B A3B and Qwen3.8 2.4T A95B support reasoning and tool use?+
Qwen3.5 35B A3B: reasoning, tool calling, and image input. Qwen3.8 2.4T A95B: reasoning and tool calling. Feature support does not establish relative quality.
Which is available from more inference providers, Qwen3.5 35B A3B or Qwen3.8 2.4T A95B?+
Qwen3.5 35B A3B has 4 sourced provider routes; Qwen3.8 2.4T A95B has 5, so Qwen3.8 2.4T A95B has broader tracked availability.
Which offers better value, Qwen3.5 35B A3B or Qwen3.8 2.4T A95B?+
There is no universal value winner. Compare the input and output prices above with the matched benchmark result for your workload: cheaper tokens can be offset by different quality, token usage, latency, or provider availability.