LLM ReferenceLLM Reference

Phi-4 Reasoning Vision 15B vs Qwen3-105B

Phi-4 Reasoning Vision 15B (2026) and Qwen3-105B (2025) are compact production models from Microsoft Research and Alibaba. Phi-4 Reasoning Vision 15B ships a not-yet-sourced context window, while Qwen3-105B ships a 128k-token context window. This comparison covers specs, pricing, capabilities, benchmarks, provider availability, and production fit. It focuses on practical selection signals rather than broad model-family marketing. The goal is to make the tradeoff clear before deeper testing.

Phi-4 Reasoning Vision 15B is safer overall; choose Qwen3-105B when provider fit matters.

Decision scorecard

Local evidence first
SignalPhi-4 Reasoning Vision 15BQwen3-105B
Decision fitVisionRAG, Agents, and Long context
Context window128k
Cheapest output--
Provider routes0 tracked0 tracked
Shared benchmarks0 rows0 rows

Decision tradeoffs

Choose Phi-4 Reasoning Vision 15B when...
  • Phi-4 Reasoning Vision 15B uniquely exposes Multimodal in local model data.
  • Local decision data tags Phi-4 Reasoning Vision 15B for Vision.
Choose Qwen3-105B when...
  • Qwen3-105B has the larger context window for long prompts, retrieval packs, or transcript analysis.
  • Qwen3-105B uniquely exposes Function calling and Tool use in local model data.
  • Local decision data tags Qwen3-105B for RAG, Agents, and Long context.

Monthly cost at traffic

Estimate token spend from the cheapest tracked input and output prices on this page.

Phi-4 Reasoning Vision 15B

Unavailable

No complete token price in local provider data

Qwen3-105B

Unavailable

No complete token price in local provider data

Cost delta unavailable until both models have sourced input and output token prices.

Switch friction

Phi-4 Reasoning Vision 15B -> Qwen3-105B
  • No overlapping tracked provider route is sourced for Phi-4 Reasoning Vision 15B and Qwen3-105B; plan for SDK, billing, or endpoint changes.
  • Check replacement coverage for Multimodal before moving production traffic.
  • Qwen3-105B adds Function calling and Tool use in local capability data.
Qwen3-105B -> Phi-4 Reasoning Vision 15B
  • No overlapping tracked provider route is sourced for Qwen3-105B and Phi-4 Reasoning Vision 15B; plan for SDK, billing, or endpoint changes.
  • Check replacement coverage for Function calling and Tool use before moving production traffic.
  • Phi-4 Reasoning Vision 15B adds Multimodal in local capability data.

Specs

Specification
Released2026-03-122025-12-15
Context window128k
Parameters15B105B
Architecture--
LicenseMicrosoft ResearchOpen Source
Knowledge cutoff-2025-02

Pricing and availability

Pricing attributePhi-4 Reasoning Vision 15BQwen3-105B
Input price--
Output price--
Providers--

Pricing not yet sourced for either model.

Capabilities

CapabilityPhi-4 Reasoning Vision 15BQwen3-105B
VisionNoNo
MultimodalYesNo
ReasoningNoNo
Function callingNoYes
Tool useNoYes
Structured outputsNoNo
Code executionNoNo

Benchmarks

No shared benchmark rows are currently sourced for this pair.

Deep dive

The capability footprint differs most on multimodal input: Phi-4 Reasoning Vision 15B, function calling: Qwen3-105B, and tool use: Qwen3-105B. Both models share the core language-model surface, so the practical split is not just feature count. Use those differences to decide whether the page is about raw model quality, agentic coding support, multimodal ingestion, or predictable structured API behavior.

Pricing coverage is uneven: Phi-4 Reasoning Vision 15B has no token price sourced yet and Qwen3-105B has no token price sourced yet. Provider availability is 0 tracked routes versus 0. Treat unknown pricing as an integration gap, then verify the route you will actually call before estimating production spend.

Choose Phi-4 Reasoning Vision 15B when provider fit are central to the workload. Choose Qwen3-105B when provider fit are more important. For production, rerun your own prompts through the exact provider, region, and tool stack you plan to ship. This keeps the decision grounded in measurable tradeoffs instead of brand-level assumptions. It also helps separate model capability from provider packaging, which can change cost and latency. For teams standardizing a stack, that distinction is often the difference between a benchmark win and a reliable deployment.

FAQ

Is Phi-4 Reasoning Vision 15B or Qwen3-105B open source?

Phi-4 Reasoning Vision 15B is listed under Microsoft Research. Qwen3-105B is listed under Open Source. License labels affect whether you can self-host, redistribute weights, or rely only on hosted APIs, so confirm the upstream license before deployment.

Which is better for multimodal input, Phi-4 Reasoning Vision 15B or Qwen3-105B?

Phi-4 Reasoning Vision 15B has the clearer documented multimodal input signal in this comparison. If multimodal input is mission-critical, validate it against the provider endpoint because model-level support and API-level exposure can differ.

Which is better for function calling, Phi-4 Reasoning Vision 15B or Qwen3-105B?

Qwen3-105B has the clearer documented function calling signal in this comparison. If function calling is mission-critical, validate it against the provider endpoint because model-level support and API-level exposure can differ.

Which is better for tool use, Phi-4 Reasoning Vision 15B or Qwen3-105B?

Qwen3-105B has the clearer documented tool use signal in this comparison. If tool use is mission-critical, validate it against the provider endpoint because model-level support and API-level exposure can differ.

When should I pick Phi-4 Reasoning Vision 15B over Qwen3-105B?

Phi-4 Reasoning Vision 15B is safer overall; choose Qwen3-105B when provider fit matters. If your workload also depends on provider fit, start with Phi-4 Reasoning Vision 15B; if it depends on provider fit, run the same evaluation with Qwen3-105B.

Continue comparing

Last reviewed: 2026-04-19. Data sourced from public model cards and provider documentation.