Mistral’s ‘Le Chonk’ Has a Trillion Parameters. The Weights Are Still Coming.
Mistral Large 4 is available as an API preview, with weights promised by month’s end. We explain its scale, temporary discount and deployment questions.

Mistral gave its new trillion-parameter model a cheerful nickname: “le Chonk.” The more consequential detail is a date. You can try the API preview now, but the company says the downloadable weights will arrive by the end of October.
Mistral Large 4 entered public preview on October 6. The launch announcement describes a multimodal model aimed at coding, agentic work and enterprise tasks. It is a significant new candidate for teams evaluating alternatives to the largest model providers.
For those teams, three questions matter more than the nickname: what can we use today, what would it cost on our workload, and what control would a later weights release actually give us?
“Open weights” is a future delivery in this launch
Mistral’s October 6 changelog calls Large 4 a public preview and explicitly says open weights are coming soon. It also announces a two-week, 50% launch discount.
That makes this a good moment for evaluation. It does not make it the moment to tell a customer that you already have a self-hosted copy.
There are several different milestones hiding inside a phrase like “we support this model.” A team might have tried a hosted API, received downloadable files, made those files run, or operated a service reliably under real traffic. Each is useful. None proves that the next one is finished.
If local deployment is a requirement, keep the planned release separate from the available product in your schedule. A preview result can inform a decision without becoming a promise about a future installation.
One trillion parameters does not mean one trillion work at once
The model documentation lists approximately 1.05 trillion total parameters and a mixture-of-experts design. In that architecture, a subset of model components participates for a given token. Total size and active computation therefore describe different things.
An everyday analogy is a large workshop with specialized stations. A particular job visits some stations rather than using every tool simultaneously. That can change the work required per step; it does not make the rest of the workshop cease to exist. For more background, see our plain-English explanation of language models.
For a sense of scale, storing 1.05 trillion values at a hypothetical four bits each would require approximately 525GB in raw weight data. That is our arithmetic: 1.05 trillion × 4 ÷ 8. It excludes metadata and runtime overhead, and it is not an announced Large 4 deployment requirement.
The point is to avoid an easy misunderstanding. An efficient active path does not establish that the complete model fits on an ordinary laptop. Actual hosting requirements will need to be assessed against the released artifacts and supported software.
The launch price is an invitation to test, not a permanent budget
At the time of research, Mistral’s model page showed discounted rates of $0.68 per million input tokens and $2.09 per million output tokens. The corresponding undiscounted rates were $1.36 and $4.18. Prices are in US dollars.
Take a hypothetical job with 10,000 uncached input tokens and 2,000 billable output tokens. At the displayed discount, the token charge would be:
(0.01 × $0.68) + (0.002 × $2.09) = $0.01098.
One thousand identical jobs would cost $10.98 in those token charges. At the displayed undiscounted rates, the same fixed counts would cost $21.96. This excludes retries, external tools and any other charges; it is a calculator example, not a measurement of a real agent.
For a short experiment, a temporary discount is welcome. For a product plan, price both periods. Otherwise, a team can mistake a launch promotion for a durable improvement in its operating costs.
A million-token window still needs a reason to be filled
Mistral lists a one-million-token context window. That describes input capacity; it does not by itself establish that every fact in a long collection will be used correctly. The model page provides the context specification.
Imagine a company evaluating the model on a folder of support procedures. A useful test would include an old procedure, the revision that replaced it, and a question that depends on noticing the change. Simply finding a familiar phrase would not be enough.
I would score the answer, the evidence it cites and whether it recognizes missing information. I would also try a question the folder cannot answer. A fluent response to that last question may reveal more than another successful summary.
These are proposed evaluation cases. We have not run Large 4, verified its benchmark claims independently or assessed its eventual self-hosting performance.
Why the release deserves attention
Mistral says it trained the model on 3,800 NVIDIA Grace Blackwell GPUs in its European data centers. That is a vendor statement about development and infrastructure, rather than independent proof of comparative quality. The announcement describes that investment.
Our view is that the meaningful competition here includes control: who operates the service, what can be customized, and what happens when a provider changes access or pricing. Those are useful questions even when a model is not first on every benchmark.
For now, the concrete opportunity is to test a preview against a real job and keep the results. When the weights arrive, there will be a separate question to answer: whether operating them yourself offers enough benefit to justify the work.
Quick answers
Can I download Large 4’s weights today?
The sources reviewed for this article describe a hosted preview with weights planned for the end of October. Recheck the release status before making deployment plans.
Does a larger parameter count guarantee better answers?
No. Treat size as an architectural characteristic and compare actual results on the tasks you care about.
Researched October 8, 2026, using Mistral’s announcement, model documentation and changelog. Prices and specifications are vendor-reported. Storage and API-cost calculations are illustrative analysis by The Bot Post. AI-assisted analysis; no hands-on model testing is claimed.
About the author
UbedullaFounder & Editor
Founder and editor of The Bot Post, covering AI news and technology.


