Mistral Small 3.2 24B vs Sarvam 30B
Mistral Small 3.2 24B (2025) and Sarvam 30B (2026) are compact production models from MistralAI and Sarvam.ai. Mistral Small 3.2 24B ships a 128k-token context window, while Sarvam 30B ships a 66k-token context window. This comparison covers specs, pricing, API access, capabilities, benchmarks, input and output token costs, and production fit for coding and agent workloads. It focuses on practical selection signals rather than broad model-family marketing.
Sarvam 30B is safer overall; choose Mistral Small 3.2 24B when coding workflow support matters.
Decision scorecard
Local evidence first| Signal | Mistral Small 3.2 24B | Sarvam 30B |
|---|---|---|
| Best for | multimodal apps and tool-calling agents | tool-calling agents |
| Decision fit | Coding, RAG, and Agents | Agents and JSON / Tool use |
| Context window | 128k | 66k |
| Cheapest output | - | - |
| Provider routes | 1 tracked | 0 tracked |
| Shared benchmarks | 0 rows | 0 rows |
Decision tradeoffs
- Mistral Small 3.2 24B has the larger context window for long prompts, retrieval packs, or transcript analysis.
- Mistral Small 3.2 24B has broader tracked provider coverage for fallback and procurement flexibility.
- Mistral Small 3.2 24B uniquely exposes Vision, Multimodal, and Structured outputs in local model data.
- Local decision data tags Mistral Small 3.2 24B for Coding, RAG, and Agents.
- Local decision data tags Sarvam 30B for Agents and JSON / Tool use.
Monthly cost at traffic
Estimate token spend from the cheapest tracked input and output route or tier on this page.
Mistral Small 3.2 24B
Unavailable
No complete token price in local provider data
Sarvam 30B
Unavailable
No complete token price in local provider data
Cost delta unavailable until both models have sourced input and output token prices.
Switch friction
- No overlapping tracked provider route is sourced for Mistral Small 3.2 24B and Sarvam 30B; plan for SDK, billing, or endpoint changes.
- Check replacement coverage for Vision, Multimodal, and Structured outputs before moving production traffic.
- No overlapping tracked provider route is sourced for Sarvam 30B and Mistral Small 3.2 24B; plan for SDK, billing, or endpoint changes.
- Mistral Small 3.2 24B adds Vision, Multimodal, and Structured outputs in local capability data.
Specs
| Specification | ||
|---|---|---|
| Released | 2025-06-01 | 2026-03-22 |
| Context window | 128k | 66k |
| Parameters | 24B | 30B (2.4B active) |
| Architecture | Decoder Only | Mixture of Experts |
| License | Apache 2.0(OSI) | Apache 2.0(OSI) |
| Openness | Open source | Open source |
| Commercial use | Commercial use allowed | Commercial use allowed |
| Knowledge cutoff | 2023-10 | 2025-06 |
Pricing and availability
| Pricing attribute | Mistral Small 3.2 24B | Sarvam 30B |
|---|---|---|
| Input price | - | - |
| Output price | - | - |
| Providers | - |
Pricing not yet sourced for either model.
Capabilities
| Capability | Mistral Small 3.2 24B | Sarvam 30B |
|---|---|---|
| Vision | Yes | No |
| Multimodal | Yes | No |
| Reasoning | No | No |
| Function calling | Yes | Yes |
| Tool use | Yes | Yes |
| Structured outputs | Yes | No |
| Code execution | Yes | No |
| IDE integration | No | No |
| Computer use | No | No |
| Parallel agents | No | No |
Benchmarks
No shared benchmark rows are currently sourced for this pair.
Deep dive
The capability footprint differs most on vision: Mistral Small 3.2 24B, multimodal input: Mistral Small 3.2 24B, structured outputs: Mistral Small 3.2 24B, and code execution: Mistral Small 3.2 24B. Both models share function calling and tool use, 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: Mistral Small 3.2 24B has no token price sourced yet and Sarvam 30B has no token price sourced yet. Provider availability is 1 tracked routes versus 0. Treat unknown pricing as an integration gap, then verify the route you will actually call before estimating production spend.
Choose Mistral Small 3.2 24B when coding workflow support, larger context windows, and broader provider choice are central to the workload. Choose Sarvam 30B 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.
FAQ
Which has a larger context window, Mistral Small 3.2 24B or Sarvam 30B?
Mistral Small 3.2 24B supports 128k tokens, while Sarvam 30B supports 66k tokens. That gap matters most for long documents, large codebases, retrieval-heavy agents, and conversations where earlier context must remain visible.
Is Mistral Small 3.2 24B or Sarvam 30B open source?
Mistral Small 3.2 24B is listed under Apache 2.0. Sarvam 30B is listed under Apache 2.0. 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 vision, Mistral Small 3.2 24B or Sarvam 30B?
Mistral Small 3.2 24B has the clearer documented vision signal in this comparison. If vision is mission-critical, validate it against the provider endpoint because model-level support and API-level exposure can differ.
Which is better for multimodal input, Mistral Small 3.2 24B or Sarvam 30B?
Mistral Small 3.2 24B 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, Mistral Small 3.2 24B or Sarvam 30B?
Both Mistral Small 3.2 24B and Sarvam 30B expose function calling. The better choice depends on benchmark fit, context budget, pricing, and whether your provider route exposes the same capability surface.
Where can I run Mistral Small 3.2 24B and Sarvam 30B?
Mistral Small 3.2 24B is available on Venice AI. Sarvam 30B is available on the tracked providers still being sourced. Provider coverage can affect latency, region availability, compliance posture, and fallback options.
Continue comparing
Last reviewed: 2026-05-19. Data sourced from public model cards and provider documentation.