AI DevelopmentOpen Source

Mistral Large 4: the Open-Weight Preview You Can’t Download Yet

October 14, 2026
11 min read
Weathered wooden gate standing slightly ajar in soft morning mist
Share:

On October 6, 2026, Mistral AI opened a public preview of Mistral Large 4: a Mixture-of-Experts model with about 1.05 trillion total parameters and 52 billion active, described as open-weight, multimodal and trained from scratch in Europe. You can call it through the Mistral API today. You cannot download it.

I read the launch post, the model card, the changelog and the Hugging Face repo line by line. Here are the spec sheet, what is actually new compared with Large 3, a quickstart taken from Mistral’s own docs, and what to do while the weights are still a promise. I have not run the model myself: every number below is attributed to its source.

1. What Mistral shipped, and what is still a promise

Mistral Large 4 is a granular Mixture-of-Experts model with 1.05T total and 52B active parameters plus a 1.6B vision encoder, according to Mistral’s model card (version v26.10, status Public Preview, dated October 6). Mistral says it was trained from scratch on 3,800 NVIDIA Grace Blackwell GPUs in its own European datacenters, and that the preview is served on that same infrastructure.

The word to watch is “open-weight”. Mistral’s post says it “will release the weights by the end of the month” and the model card tags the model as Open, but today nothing is downloadable and no license has been named. Treat everything about self-hosting as a plan, not a fact.

Spec sheet (checked October 14, 2026)

  • • Status: public preview since October 6, 2026, served through the Mistral API (Mistral Studio); model card version v26.10
  • • Model ID: mistral-large-4-0 on the model card and in the reasoning guide; the changelog writes mistral-large-4 — confirm with the models endpoint
  • • Size: ~1.05T total / 52B active parameters (the Hugging Face placeholder says 49B per token, 52B counting embeddings and output layers) + 1.6B vision encoder
  • • Context: 1M tokens on the model card; Vercel AI Gateway lists 524,288 and Artificial Analysis ~524K for the served preview
  • • Price: $1.36 input / $4.18 output per 1M tokens, cached input $0.14; launch sale shown as $0.68 / $2.09 (cached $0.07)
  • • Weights: promised by end of October; no license named; repo mistralai/Mistral-Large-4-1T-A52B says “Upcoming release” with no files

Weights status today

On October 14 the Hugging Face page for mistralai/Mistral-Large-4-1T-A52B is marked “Upcoming release” with a current ETA of October 31, no model files and no license field. Mistral’s own post says only “by the end of the month”. Secondary coverage mentions October 27 as a target; I could not find that date in a Mistral source.

2. What improves over Mistral Large 3

Mistral’s launch post does not compare Large 4 with Large 3, so I set the two spec sheets side by side. Large 3 (Hugging Face repo Mistral-Large-3-675B-Instruct-2512, published November 2025) is a ~675B-total / ~41B-active MoE with a 256K context window, released under Apache 2.0 according to its card.

Large 4 grows on three axes: roughly 1.5x the total parameters, about 27% more active parameters and, on paper, four times the context. It also folds reasoning into the same model. It is not cheaper: the example on Mistral’s pricing page still prices Mistral Large at $0.50 / $1.50 per 1M tokens, so even the $0.68 / $2.09 sale price is about 1.4x that, and list price about 2.7x.

The three real differences

đź§ 

Capacity

1.05T total / 52B active against 675B / 41B on Large 3. More expert capacity per token, paid for in serving cost.

📏

Context

1M tokens on the model card, 4x Large 3’s 256K. Gateways list 524,288 for the served preview, so measure before you rely on it.

🔀

Two modes, one model

reasoning_effort takes “high” or “none” per request (Mistral’s reasoning docs): chat and thinking behind one endpoint.

Golden rule

If you must self-host this month, Large 3 is still the safer pick: it has downloadable Apache 2.0 weights today. Large 4 is the one to evaluate through the API while you wait.

3. Evidence: vendor numbers and independent ones

Most numbers in Mistral’s launch post are Mistral’s own, and the post does not say which reasoning setting produced them. Read them as direction, not as a ranking.

The independent signals are thinner. Artificial Analysis scores the preview 38 on its Intelligence Index (rank 65 of 216 on its page, class median 27) and reports about 200M output tokens to run the index against a median of 85M: this is a verbose model. Simon Willison, who tried the API, puts it just behind DeepSeek V4.1 Flash on that index and says it is not Fable-class.

What Mistral reports (vendor-reported, October 6, 2026)

  • • Coding: 61.7% on DeepSWE v1.1, 28.3% on Terminal-Bench 4.0, 49.8% on its Coding Agent Index
  • • Blind human coding eval run by Surge AI: 3.74 on a 1–5 scale, second of five models, behind Claude Opus 5 (4.22)
  • • Cyber: 93% on Cybench and 82% on the reproduce-and-patch test of the Artificial Analysis Cyber Index
  • • Agentic and vision: 59.9% on AutomationBench, 42% on Dense 200 (GPT-6-Astra: 41%)

Read the fine print

These are launch-post numbers for a preview that Mistral says “continues to improve rapidly”; architecture details, more benchmarks and the post-training methodology are promised only with the weights. Mistral’s cyber claims also sit beside a statement that vetted partners and state authorities get the same model with reduced moderation, so check which configuration produced which score. And nobody has run a head-to-head on your workload yet.

4. Quickstart from Mistral’s own docs

The preview speaks the same chat-completions API as every other Mistral model. Install the official SDK (mistralai on PyPI, 3.2.0 released October 9, 2026, Python 3.10+; the JavaScript package @mistralai/mistralai is at 2.7.0) and create an API key in Mistral Studio.

Before you wire it into anything, do two things: list the models your key can see, and read the context window the API actually reports. The model ID appears as mistral-large-4-0 on the model card and in the reasoning guide, and as mistral-large-4 in the changelog, so let the API settle it.

Step 1: confirm the ID and the real context window

Uses models.list() from the Python SDK; the API reference documents id, aliases and max_context_length.

# pip install mistralai
import os
from mistralai.client import Mistral

with Mistral(api_key=os.environ["MISTRAL_API_KEY"]) as mistral:
    res = mistral.models.list()
    for m in res.data:
        if m.id.startswith("mistral-large-4"):
            print(m.id, m.aliases, m.max_context_length)

Step 2: one call with reasoning on

reasoning_effort accepts “high” or “none” in Mistral’s docs. With “high”, content is a list of thinking and text chunks.

import os
from mistralai.client import Mistral
from mistralai.client.models import TextChunk, ThinkChunk

client = Mistral(api_key=os.environ["MISTRAL_API_KEY"])

resp = client.chat.complete(
    model="mistral-large-4-0",   # confirm with models.list()
    messages=[{"role": "user", "content": "Find the race condition in this handler: ..."}],
    reasoning_effort="high",     # documented values: "high" | "none"
)

content = resp.choices[0].message.content
if isinstance(content, str):     # "none" returns a plain string
    print(content)
else:                            # "high" returns thinking + text chunks
    for chunk in content:
        if isinstance(chunk, TextChunk):
            print(chunk.text)    # the final answer
        elif isinstance(chunk, ThinkChunk):
            pass                 # reasoning trace: keep in history, do not show

print(resp.usage)                # see how many tokens "high" really cost

Multi-turn and streaming

Mistral’s reasoning guide says to append the whole assistant message, thinking chunk included, back into the history: stripping it saves tokens but lowers quality. When streaming, delta.content is a list of chunks while the model thinks and becomes a plain string once the answer starts.

5. Honest limits

Large 4 is a preview with open-weight intentions. These are the limits I would put in front of a team before they pick it.

Limits to know

  • • No weights and no license: self-hosting, fine-tuning and any compliance review wait for Mistral’s files. I found no Mistral page that names the license.
  • • The preview may not be the final model: Mistral says it “continues to improve rapidly”, and one third-party write-up reports the released weights may differ from the preview. Date your evals.
  • • Context is not settled: 1M on the card, 524,288 on Vercel’s gateway listing and ~524K on Artificial Analysis. Mistral’s pages list no maximum output and no rate limits for this model.
  • • Verbose reasoning: about 200M output tokens to run Artificial Analysis’s index against an 85M median, so the per-token price understates the cost per task.
  • • Coarse control: the docs accept only “high” and “none”, with no middle setting.
  • • Not a frontier-coding replacement: in Mistral’s own blind coding eval it is second of five behind Claude Opus 5, and the independent index puts it just behind DeepSeek V4.1 Flash.
  • • Regions: Mistral says it will be available “across multiple regions worldwide”, plus a European deployment it runs end to end, but the model page lists no regions today.

6. What to do before the weights ship

Treat the next two weeks as a free evaluation window, not as a migration. Nothing below needs the weights.

Evaluation checklist

  1. 1. Call models.list() and record the ID, aliases and max_context_length you actually get; keep the model ID in an environment variable, not in code.
  2. 2. Replay 30–50 real prompts from your own traffic with reasoning_effort at “none” and at “high”, and log completion tokens per task, not just quality.
  3. 3. Budget at list price ($1.36 / $4.18 per 1M): the changelog says “50% off for 2 weeks” with no calendar date, which counted from October 6 lands around October 20.
  4. 4. Put it behind a gateway with a fallback to the model you run today, so the preview can change or vanish without an outage.
  5. 5. Do not buy GPUs or sign a self-hosting plan until the license text and the weight files exist; then re-run step 2 against the released checkpoint.

Self-hosting math

Back-of-envelope arithmetic, not a Mistral figure: 1.05T parameters is roughly 1.05 TB at 8 bits per weight and about 525 GB at 4 bits, before KV cache and activations. Even the compressed version is multi-GPU datacenter territory, so for most teams the API is the realistic way to use this model for now.

Verdict

Mistral Large 4 is a credible, EU-hosted, trillion-class model with a clear open-weight promise and a coding profile that Mistral’s own numbers place below the best closed models. As of October 14 it is a preview you can test, not an open model you can run.

Evaluate it through the API this week with your own prompts and token accounting, keep your current model as the fallback, and come back when the weights and a named license appear. If they do not land by the end of October, plan as if it were a hosted model.

Sources for this post

Primary first, independent after

  • • Mistral launch post (Oct 6, 2026)
  • • Mistral docs: Mistral Large 4 model card, changelog and reasoning guide
  • • Hugging Face: Mistral-Large-4-1T-A52B placeholder and Mistral-Large-3 card
  • • Artificial Analysis and Simon Willison (independent)
  • • PyPI and Vercel AI Gateway listings (SDK version, served context)
Diego Rodriguez

Diego Rodriguez

Senior Full-Stack & AI Engineer

Diego has 10+ years of experience building production-grade AI-powered applications, from LLM orchestration and RAG pipelines to ML-driven risk detection and algorithmic trading systems.

Learn more about Diego →