mistral
24B parameters
Commercial OK
Reviewed June 2026

Mistral Small 3.2 24B

Iterative refresh of Mistral Small 3 24B. Same architecture; improved instruction following and tool-call reliability. Apache 2.0.

License: Apache 2.0·Released Mar 8, 2026·Context: 131,072 tokens
BLK · VERDICT

Our verdict

OP · Eruo Fredoline|VERIFIED JUN 12, 2026
unrated

Positioning

Mistral Small 3.2 24B is a dense 24-billion-parameter model from Mistral AI, released under the permissive Apache 2.0 license. It is an iterative refresh of the earlier Mistral Small 3 24B, retaining the same architecture while improving instruction-following and tool-call reliability. With a 131,072-token context window, it targets consumer-tier multilingual instruction-following tasks, making it a strong candidate for local deployment on single-GPU setups.

Strengths

  • Apache 2.0 license: Permissive licensing allows unrestricted commercial use, modification, and redistribution, making it ideal for proprietary applications.
  • Large 128K context window: The 131,072-token context enables processing of long documents, extended conversations, or complex multi-turn tasks without truncation.
  • Consumer-friendly size: At 24B dense parameters, the model fits within consumer GPU memory at common quantizations (e.g., Q4_K_M ~13.5 GB plus overhead), enabling local inference on a single 24GB GPU.
  • Improved instruction following: This refresh specifically targets better adherence to instructions and more reliable tool-call behavior, enhancing practical utility for agentic workflows.

Limitations

  • No community benchmarks available: We do not yet have independent, community-reported benchmark scores for this model. Published vendor metrics should be treated as best-case until verified by third parties.
  • Dense architecture at 24B: Unlike Mixture-of-Experts models that activate only a fraction of parameters, this dense model uses all 24B parameters per forward pass, resulting in higher compute and memory requirements relative to MoE models of similar total parameter count.
  • Quantization trade-offs: Running at lower quantizations (e.g., Q4_K_M) reduces memory footprint but may degrade output quality compared to FP16. Operators should test their specific use case to find the acceptable balance.
  • No multimodal support: This model is text-only; it does not natively process images or other modalities, limiting its applicability in vision-language tasks.

What it takes to run this locally

At FP16 precision, the model requires 48 GB of disk space and roughly 48 GB of GPU memory, exceeding consumer GPU capacity. However, quantized versions drastically reduce the memory requirement: Q8_0 (26 GB), Q6_K (19.8 GB), Q5_K_M (17.1 GB), Q4_K_M (13.5 GB), Q3_K_M (11.7 GB), and Q2_K (~7.8 GB). For typical use with a 131K context, add ~30-50% for KV cache and framework overhead. This means a single 24GB consumer GPU (e.g., RTX 4090) can run the Q4_K_M quant comfortably, while Q3_K_M or Q2_K may fit on 12-16GB cards. For FP16 or Q8_0, a workstation GPU with 48GB or dual consumer GPUs would be necessary.

Should you run this locally?

Yes if you need a permissively licensed, dense 24B model for instruction-following or tool-calling tasks and have a single 24GB GPU (or can use Q3_K_M on 12-16GB). The Apache 2.0 license makes it particularly attractive for commercial deployment without legal overhead.

No if you require multimodal capabilities, need the absolute lowest memory footprint (consider MoE models with smaller active parameters), or are risk-averse to using a model without independent benchmark validation.

Catalog cross-links

Overview

Iterative refresh of Mistral Small 3 24B. Same architecture; improved instruction following and tool-call reliability. Apache 2.0.

Family & lineage

How this model relates to others in its lineage. Family members share architecture and training-data roots; parent / children edges record direct distillation or fine-tune relationships.

Family siblings (mistral-small-3)
Mistral Small 3.2 24B24B
You are here
Mistral Small 3 24B24B
Consumer

Strengths

  • Apache 2.0
  • Strong instruction following — Mistral tradition
  • European multilingual

Weaknesses

  • No reasoning-mode toggle

Prompting kit

From model card
source

Tested patterns for getting the most out of Mistral Small 3.2 24B locally. Local models are pickier about prompt structure than cloud models — what works on Claude or GPT-5 often fails here.

Recommended system prompt

You are a precise and helpful assistant. Answer directly. For tool calls, emit valid JSON; for text answers, keep them concise unless detail is requested.

Quirks to know

  • Mistral Small 3.2 is tuned to be a 'workhorse' model — Mistral's release notes position it as a drop-in for Mistral Medium at much lower inference cost. Quality stays high on instruction-following and tool use.
  • 128K context window per the model card. Per Mistral's docs, full 128K retention is reliable; degradation only starts past 96K on synthetic long-context evals.
  • Native function calling — declare tools as JSON schemas in the system prompt or in the tools= argument of your runtime's chat API. The 3.2 release specifically improved tool-call reliability over 3.1.
  • Multilingual: officially supports dozens of languages with strong performance on Western European and CJK tier. Lower-resource languages are weaker than Gemma or Qwen.
  • Per Mistral's docs, for tool-calling and reasoning workloads, use a low temperature (0.15-0.3). For chat or creative writing, 0.7 is the standard default.

Chat template

Mistral Instruct v7

Uses Mistral's [INST]...[/INST] markers extended with system-prompt support. The tokenizer_config.json ships the canonical template — apply that rather than hand-rolling because v7 has tool-result tokens that earlier versions don't.

Tool calling

✓ Supported(openai-compatible)

Per the model card, Mistral's tool-call format is OpenAI-compatible: declare tools as JSON schemas, the model emits tool_calls in the assistant turn, and you reply with tool role for results. Works in vLLM, llama.cpp, and the official Mistral Python client.

Sampler settings

temperature
0.15
top_p
1

Mistral's recommended default for the 3.2 release. Per the model card: low temperature is intended for tool use and reasoning. Raise to ~0.7 for creative or open-ended chat.

Browse prompting kits for every model →/prompting

Quantization variants

Each quantization trades model quality for file size and VRAM. Q4_K_M is the most popular starting point.

QuantizationFile sizeVRAM required
Q4_K_M14.0 GB18 GB

Get the model

HuggingFace

Original weights

huggingface.co/mistralai/Mistral-Small-3.2-24B-Instruct

Source repository — direct quantization required.

Hardware that runs this

Cards with enough VRAM for at least one quantization of Mistral Small 3.2 24B.

Compare alternatives

Models worth comparing

Same parameter band, plus what's one tier above and below — so you can decide what actually fits your hardware.

Frequently asked

What's the minimum VRAM to run Mistral Small 3.2 24B?

18GB of VRAM is enough to run Mistral Small 3.2 24B at the Q4_K_M quantization (file size 14.0 GB). Higher-quality quantizations need more.

Can I use Mistral Small 3.2 24B commercially?

Yes — Mistral Small 3.2 24B ships under the Apache 2.0, which permits commercial use. Always read the license text before deployment.

What's the context length of Mistral Small 3.2 24B?

Mistral Small 3.2 24B supports a context window of 131,072 tokens (about 131K).

Source: huggingface.co/mistralai/Mistral-Small-3.2-24B-Instruct

Reviewed by RunLocalAI Editorial. See our editorial policy for how we research and verify model claims.

Related — keep moving

Before you buy

Verify Mistral Small 3.2 24B runs on your specific hardware before committing money.