Skip to main content
Ranked roundup

Best Open-Source LLM in 2026

This ranking is for teams choosing an open-weights model to actually deploy: self-hosted for data sovereignty, fine-tuned for a domain, or served through a private cloud where a proprietary API is not an option. That decision looks nothing like a benchmark leaderboard. The license gets read before anything gets benchmarked, the weights have to fit hardware you can realistically rent or rack, and the family has to still be maintained a year after you commit.

A note on the phrase everyone argues about: most of these are open-weights models under genuine open-source licenses (Apache 2.0 or MIT applied to the weights), while Llama 4 ships under a conditional community license that is not open source in the OSI sense. We rank six current-generation general-purpose families. The order optimizes for production adoption, and each verdict says exactly when a lower-ranked option beats the winner.

TL;DR

For most teams putting an open-weights model into production in 2026, the best open-source LLM is Qwen 3. One Apache 2.0 family covers 0.6B to 235B parameters with a shared chat template and per-request reasoning control, which is the shape adoption actually takes: legal clears one license, infrastructure standardizes one stack, and you pick the size per workload. If you want the most capable open weights available and can serve a 753B-parameter model, GLM-5.2 is the pick: MIT licensed and within a point of Claude Opus 4.8 on Z.ai's published agentic coding benchmark. Choose DeepSeek R1 and V3 to own frontier-grade reasoning on the most battle-tested MIT stack, Gemma 4 when the model must run on a phone or a single GPU, Mistral Large 3 when European sovereignty and open multimodality drive the decision, and Llama 4 only after your counsel has read its license.

How this ranking was made

Verified July 6, 2026

We ranked for production adoption of open-weights models: self-hosting, fine-tuning, and private deployment, not for API-shopping or leaderboard bragging rights. Every parameter count, context window, license clause, date, and price on this page was pulled from vendor announcements, official Hugging Face model cards, license texts, and live pricing pages, all fetched on the verification date shown here; nothing is quoted from memory or from third-party listicles. Benchmark numbers are the vendors' own published claims and are labeled as such; we have not independently reproduced them. BearPlex deploys and fine-tunes several of these families in client systems, which is where the operational judgments come from. No vendor paid for placement, and the winner is not something BearPlex sells: every model here has freely downloadable weights. We excluded proprietary API-only models (GPT-5, Claude, Gemini), specialist single-domain models, and families without a current 2025-2026 generation.

License and commercial terms

What the license actually permits: commercial use, fine-tuning, redistribution, and whether conditions like attribution or user-count gates survive legal review.

Capability, claims separated from facts

Vendor-published benchmark results and independent practitioner reports, weighted by how much of the claim can be traced to a primary source.

Deployment footprint

What it takes to hold and serve the weights: total versus active parameters, disk size, and whether the vendor's hardware claims map to hardware you can rent.

Family range

Whether one license and one toolchain covers edge, mid-size, and flagship deployments, including distills and refresh cadence.

Ecosystem and staying power

Inference-stack support, quantization availability, release cadence through mid-2026, and the odds the family is still maintained when you re-evaluate next year.

All 6 at a glance

Dimension#1 Qwen 3#2 GLM-5.2#3 DeepSeek V3 / R1#4 Gemma 4#5 Mistral Large 3#6 Llama 4
LicenseApache 2.0MITMITApache 2.0Apache 2.0Llama 4 Community License (700M MAU gate, attribution)
Flagship architecture235B MoE, 22B active (plus 7 smaller sizes)753B MoE, ~40B activeR1: 671B MoE, 37B active; V3.2: 685B31B dense; 26B MoE at 3.8B active675B MoE, 41B active + 2.5B vision encoderMaverick: 400B MoE, 17B active; Scout: 109B
Context window32K native (131K YaRN); 262K native on 2507 refresh1M128K128K (edge) to 256K256KMaverick 1M; Scout 10M (vendor claim)
Multimodal inputNo, text onlyNo, text onlyNo, text onlyImages + video; audio on E2B, E4B, 12B UnifiedImages (2.5B vision encoder)Images (native early fusion)
Cheapest verified entry pointFree download; 0.6B runs on laptop-class hardwareZ.ai API: $1.40 in / $4.40 out per 1M tokensFree download; first-party API now serves V4 onlyFree download; E2B runs offline on phones (vendor claim)Mistral API: $0.50 in / $1.50 out per 1M tokensFree download; Scout on one H100 at Int4 (vendor claim)
Standout verified fact (July 2026)8 models, ~36T training tokens, 119 languages, one licenseTerminal-Bench 2.1: 81.0 vs Opus 4.8's 85.0 (vendor-published)R1-0528: AIME 2025 87.5, up from 70.0 (vendor-published)12B Unified added text + audio + image at 256K (June 3, 2026)NVFP4 checkpoint runs on one 8xH100 node; trained on 3,000 H200sScout advertises a 10M-token context window

The ranking

Qwen 3

Qwen Team (Alibaba)

Eight Apache 2.0 models from 0.6B to 235B with one chat template: the family that turns model choice into a sizing decision.

Qwen 3 wins because choosing an open-source LLM for production is a portfolio decision, not a single-model bet. The family ships eight models under plain Apache 2.0: six dense checkpoints from 0.6B to 32B and two Mixture-of-Experts models, topped by Qwen3-235B-A22B (235B total, 22B active, 128 experts with 8 active per token). Pretraining spans roughly 36 trillion tokens across 119 languages and dialects, double the prior generation. The signature feature is hybrid thinking: one checkpoint reasons step-by-step when thinking mode is on and answers immediately when it is off, so inference-time reasoning cost becomes a per-request dial. The family has also kept moving: the 2507 refresh of the flagship ships as a dedicated non-thinking instruct checkpoint with native 262,144-token context, up from 32,768 native on the original. What this buys in practice is continuity: prototype on the 4B, ship the 32B, scale to the MoE flagship without changing license review, chat template, or serving stack. Its honest limits: the family is text-only, and the flagship is no longer the single most capable open model on vendor coding benchmarks; GLM-5.2 is.

Best for

  • Regulated on-prem and private-cloud deployments where legal reviews one license and engineering standardizes one stack
  • Products that need multiple model sizes (edge assistant, mid-size workhorse, flagship escalation) from one family
  • Multilingual products: pretraining spans 119 languages and dialects
  • Fine-tuning programs that want Apache 2.0 freedom with no attribution or naming conditions

Not for

  • Squeezing out the last few points on agentic coding benchmarks, where GLM-5.2 leads the open field
  • Vision or audio inputs: the Qwen 3 family covered here is text-only
  • Native context windows past 262K tokens, where GLM-5.2 and the Llama 4 line go further
License

Apache 2.0, all eight models

Sizes

0.6B / 1.7B / 4B / 8B / 14B / 32B dense + 30B-A3B / 235B-A22B MoE

Flagship

235B total, 22B active (128 experts, 8 active)

Context

32,768 native (131,072 with YaRN); 262,144 native on the 2507 refresh

Training

~36T tokens, 119 languages and dialects

Pricing

Free and open weights under Apache 2.0 at every size, with no usage gates, attribution, or naming conditions. The cost is entirely your serving infrastructure, from laptop-class hardware for the 0.6B to a multi-GPU node for the 235B flagship (roughly 235GB of weights at 8-bit, firmly multi-GPU territory).

GLM-5.2

Z.ai (Zhipu AI)

The capability frontier of open weights: MIT licensed, 1M-token context, and within a point of Claude Opus 4.8 on the vendor's agentic coding benchmark.

GLM-5.2 is the strongest answer yet to the question every CTO asks quarterly: are we still paying frontier API prices for work an open model can do? Announced June 17, 2026 with weights on Hugging Face under plain MIT, it is a 753B-parameter Mixture-of-Experts model (roughly 40B active per token) with a 1M-token context window, up from GLM-5.1's 200K. Z.ai's published numbers put it within a point of Claude Opus 4.8 on FrontierSWE and at 81.0 on Terminal-Bench 2.1 against Opus 4.8's 85.0, with SWE-bench Pro at 62.1; treat those as vendor claims, but Simon Willison's independent day-after assessment called it probably the most powerful text-only open weights LLM. The architecture earns its keep at long context: an IndexShare scheme shares one indexer across every four sparse attention layers for a claimed 2.9x per-token FLOPs reduction at 1M tokens, and a multi-token-prediction layer claims up to 20% better speculative-decoding acceptance. The costs are equally concrete: about 1.51TB of BF16 weights means multi-node serving or aggressive quantization, and there is no vision input at all.

Best for

  • Agentic coding and long-horizon tool-use workloads where open-weights capability matters most
  • Teams replacing a proprietary frontier model for text work and willing to verify vendor benchmarks on their own tasks
  • 1M-token context workloads: whole-repository analysis, long document chains, extended agent sessions

Not for

  • Anything needing vision or audio input: GLM-5.2 is text-only
  • Teams without multi-node GPU capacity or a trusted host: 1.51TB of BF16 weights is a real barrier
  • Buyers who need independently reproduced benchmarks before committing; the headline numbers are Z.ai's own
License

MIT

Architecture

753B MoE, ~40B active per token, text-only

Context

1M tokens (GLM-5.1 was 200K)

Vendor benchmarks

Terminal-Bench 2.1: 81.0 (Opus 4.8: 85.0); SWE-bench Pro: 62.1

Weights on disk

~1.51TB BF16 (per Simon Willison, June 17, 2026)

Pricing

Weights are free under MIT. Z.ai's API serves GLM-5.2 at $1.40 per million input tokens, $0.26 per million cached input tokens, and $4.40 per million output tokens (docs.z.ai, verified July 2026). Self-hosting means roughly 1.51TB of BF16 weights, so budget a multi-node cluster or a quantized deployment.

DeepSeek V3 / R1

DeepSeek-AI

The proven MIT pair: the workhorse and the reasoning model that made open chain-of-thought real, now the best-understood self-hosting stack in the field.

The V3 and R1 line remains the reference implementation for owning your own reasoning. R1 is a 671B-parameter MoE with 37B active and 128K context under MIT, trained from DeepSeek-V3-Base, and the R1-0528 refresh is the checkpoint to run: DeepSeek's published numbers show AIME 2025 rising from 70.0 to 87.5 and LiveCodeBench from 63.5 to 73.3, with system prompts properly supported and function calling improved. V3.2 (685B) added DeepSeek Sparse Attention for long-context efficiency, and the distill ladder (six models from 1.5B to 70B, the Qwen-based ones under Apache 2.0, plus an R1-0528 distill onto Qwen3-8B) covers hardware budgets normal companies have. Rank three comes with an honest asterisk: this is now the previous generation. DeepSeek's V4 line shipped in April 2026 with its own MIT open weights on Hugging Face (V4-Pro at 1.6T total and 49B active, 1M context), and the first-party API's deepseek-chat and deepseek-reasoner names are scheduled for deprecation on July 24, 2026, already mapping to V4-Flash. That cuts both ways. You are not buying the frontier; you are buying eighteen months of tooling, quantizations, deployment guides, and known failure modes, which is exactly what a production self-hosting decision should weigh.

Best for

  • Teams that want to own a serious reasoning model outright under MIT, with the deepest community deployment knowledge available
  • Routing architectures that pair a fast generalist (V3 line) with a reasoning escalation path (R1) from one lineage
  • Distill-based deployments: R1's reasoning style at 8B to 70B scales on single-node hardware

Not for

  • Teams that want the current DeepSeek generation: V4 (also MIT, open weights) has superseded this line, including on DeepSeek's own API
  • First-party hosted use: the legacy API names deprecate on July 24, 2026, so running V3.2 or R1 means self-hosting or third-party hosts
  • Multimodal workloads: the line is text-only
License

MIT (R1 and current V3 line)

R1 architecture

671B MoE, 37B active, 128K context

R1-0528 refresh

AIME 2025: 70.0 to 87.5; LiveCodeBench: 63.5 to 73.3 (vendor)

V3.2

685B, DeepSeek Sparse Attention for long context

Distills

1.5B to 70B (Qwen-based under Apache 2.0), plus R1-0528 onto Qwen3-8B

Pricing

Weights are free under MIT. The first-party API has moved to the V4 generation: deepseek-chat and deepseek-reasoner deprecate July 24, 2026 and map to V4-Flash ($0.14 per million input tokens on cache miss, $0.28 per million output, verified July 2026). Running V3.2 or R1 itself today means self-hosting or a third-party host.

Gemma 4

Google

The edge and single-GPU default: Google's first Apache 2.0 Gemma generation, from phone-class models with native audio to a 31B flagship on one H100.

Gemma 4 owns the deployment slot the giant MoEs above it cannot touch: models that run where the data lives. Launched March 31, 2026 as the first Gemma generation under plain Apache 2.0, the family spans E2B and E4B edge models (effective 2B and 4B footprints, 128K context, native audio input, offline on phones, Raspberry Pi, and Jetson-class hardware per Google), a 26B MoE activating only 3.8B parameters per token, and a 31B dense flagship with 256K context whose unquantized bfloat16 weights Google states fit a single 80GB H100. All sizes process images and video natively, and the family is trained on over 140 languages. The cadence since launch is the strongest signal: Multi-Token Prediction variants landed April 16, 2026, and Gemma 4 12B Unified arrived June 3, 2026 with text, audio, and image input at 256K context, closing the mid-range audio gap. Google's launch claim of the number-three open-model Arena ranking for the 31B is a vendor claim, but the honest positioning does not depend on it: this is the family you shortlist when the constraint is local, and the ceiling you accept is that a 31B dense model is not a 753B frontier MoE.

Best for

  • On-device and offline products: phones, browsers, embedded hardware, field deployments
  • Single-GPU self-hosting where the entire model must fit one 80GB H100
  • Multimodal input on a budget: image and video at every size, audio on the edge models and 12B Unified
  • Enterprises that needed Apache 2.0 before a Gemma-family model could clear legal

Not for

  • Frontier-grade text capability: the big MoEs above it are in a different weight class
  • Contexts past 256K tokens
License

Apache 2.0 (first Gemma generation to use it)

Sizes

E2B / E4B / 26B MoE (3.8B active) / 31B dense, plus 12B Unified (June 3, 2026)

Context

128K on edge models, up to 256K on the larger ones

Modalities

Images + video at all sizes; native audio on E2B, E4B, and 12B Unified

Hardware

31B fits a single 80GB H100 in bfloat16 (Google); edge models run offline on phones

Pricing

Free weights under Apache 2.0 for every size. The published deployment targets run from phones and Raspberry Pi-class devices for E2B and E4B to a single 80GB H100 for the 31B flagship, which makes it the cheapest serious self-hosting bill in this roundup.

Mistral Large 3

Mistral AI

Europe's open flagship: Apache 2.0, 675B MoE with built-in vision, and the only place frontier scale, a permissive license, and an EU vendor meet.

Mistral Large 3 is the model you evaluate when the first requirement is a jurisdiction, not a benchmark. Released December 2, 2025 as the flagship of the Mistral 3 family, it is a sparse MoE with 675B total and 41B active parameters including a 2.5B vision encoder, a 256K context window, and a plain Apache 2.0 license across the whole family, which also includes Ministral 3 at 14B, 8B, and 3B as a same-license distill ladder. Two release details matter operationally: the weights ship in FP8 with an NVFP4 checkpoint that Mistral states runs on a single 8xA100 or 8xH100 node via vLLM, and Mistral's hosted API prices it at $0.50 per million input tokens and $1.50 per million output tokens, well under Z.ai's hosted rate for GLM-5.2. Mistral's claim of debuting at number two among open non-reasoning models on LMArena is a vendor claim from launch. What keeps it at rank five is the field, not the model: GLM-5.2 out-benchmarks it on published coding evals, Qwen 3 out-ladders it on family range, and its ecosystem is smaller than either. But for EU-sovereignty deployments that need open multimodal capability with a European vendor behind it, nothing else on this list checks all three boxes.

Best for

  • EU data-sovereignty deployments where an American or Chinese vendor is a procurement problem
  • Open-weights multimodal work: it is the only frontier-scale entry here with built-in image understanding
  • Teams that want a same-vendor, same-license ladder (Ministral 3B/8B/14B) under the flagship

Not for

  • Peak agentic coding performance, where GLM-5.2's published numbers lead
  • Teams that need the largest possible community: the tooling ecosystem trails Qwen and Llama
License

Apache 2.0, entire Mistral 3 family

Architecture

675B MoE, 41B active, incl. 2.5B vision encoder

Context

256K tokens

Family

Ministral 3 at 3B / 8B / 14B under the same license

Hosted API

$0.50 in / $1.50 out per 1M tokens (verified July 2026)

Pricing

Free weights under Apache 2.0, shipped in FP8 with an NVFP4 checkpoint sized for a single 8-GPU node. Mistral's hosted API prices Large 3 at $0.50 per million input tokens and $1.50 per million output tokens (mistral.ai, verified July 2026).

Llama 4

Meta

The famous name with the conditional license: capable multimodal MoE weights, ranked last because every alternative above it asks less of your lawyers.

Llama 4 sits last not because the models are weak but because the deal around them is the worst on this page. The April 5, 2025 release brought two natively multimodal MoE models: Scout (109B total, 17B active, 16 experts) with a claimed 10M-token context window and an Int4 fit on a single H100, and Maverick (400B total, 17B active, 128 experts) with a 1M-token context, both distilled from the still-training Behemoth (288B active, roughly 2T total). The instruct models cover 12 languages with an August 2024 knowledge cutoff. The problem is the Llama 4 Community License. It is free for almost everyone, but it is not open source in the OSI sense: a 700M monthly-active-user gate (measured on the release date), a mandatory and prominently displayed Built with Llama attribution on products that contain the materials, a requirement that distributed derivative models carry Llama at the start of their name, and redistribution paperwork. In 2024 those conditions were the price of frontier open weights. In mid-2026, Apache 2.0 and MIT alternatives match or beat Llama 4 across this list, so the conditions need a justification they no longer have. Pick it for the ecosystem or a specific capability fit, and read the license first.

Best for

  • Teams already invested in the Llama toolchain and fine-tuning ecosystem
  • Extreme-context experiments: Scout's 10M-token claim is the largest window advertised by anyone on this list
  • Multimodal (text plus image) workloads on a single-H100 budget via Scout at Int4

Not for

  • White-label products, where mandatory Built with Llama attribution travels with the model
  • Companies distributing fine-tuned derivatives under their own brand names: the Llama naming clause forbids it
  • Anyone who can get the capability they need under Apache 2.0 or MIT, which in 2026 is nearly everyone
License

Llama 4 Community License (not OSI open source)

Models

Scout: 109B total / 17B active; Maverick: 400B total / 17B active

Context

Scout: 10M claimed; Maverick: 1M

Modalities

Native multimodal (text + image), 12 languages on instruct

License conditions

700M MAU gate, Built with Llama attribution, Llama-prefix naming on derivatives

Pricing

Free to download from llama.com and Hugging Face under the Llama 4 Community License, with no fee at any scale below the 700M MAU gate. Distribution obligations (license copy, notice text, prominent Built with Llama attribution, derivative naming) are the real cost; budget legal review time.

When none of these is the answer

If you are reaching for open weights because the API bill feels high, do the arithmetic before committing. At modest volume, hosted access to these same models (Mistral Large 3 at $0.50 in and $1.50 out per million tokens, GLM-5.2 at $1.40 and $4.40) costs less per month than one dedicated GPU node, and a hosted frontier API may cost less than either once engineering time is counted. Self-hosting earns its keep in specific conditions: data that cannot leave your infrastructure, sustained token volume that beats per-token pricing, a fine-tuned model you need to own outright, or a jurisdiction requirement no vendor satisfies. If none of those describe you, the honest answer is that you may not need an open-source LLM at all yet.

And if one of them does describe you, the model choice is the smallest part of the work. The decisions that determine whether the system ships are the evaluation harness that replaces leaderboard trust, the routing between a cheap small model and an expensive big one, the fine-tuning versus RAG call, the serving stack, and the exit path for when this page's ranking changes next quarter. That is model engineering rather than model shopping, and it is the work BearPlex does for clients: evaluation, fine-tuning, deployment, and the model decision made against your constraints instead of a vendor's benchmark chart.

See how BearPlex ships model engineering
FAQ

Common questions

For most production adopters, Qwen 3: eight Apache 2.0 models from 0.6B to 235B parameters with one chat template and per-request reasoning control, which means one legal review and one serving stack cover every deployment size. If you specifically want the most capable open weights available and can serve 753B parameters, GLM-5.2 leads on published capability. The best choice is conditional, which is exactly why this page ranks six families instead of crowning one.

Five of the six families here ship weights under genuine open-source licenses: Apache 2.0 for Qwen 3, Gemma 4, and Mistral Large 3, and MIT for GLM-5.2 and DeepSeek. Those permit commercial use, modification, and redistribution without conditions. Llama 4 is the exception: its Community License is free for almost everyone but carries a 700M monthly-active-user gate, mandatory attribution, and derivative naming rules, so it is open weights but not open source in the OSI sense. The distinction matters most for white-label products and distributed fine-tunes.

On the vendors' own published benchmarks, the gap has closed to within noise on some workloads: Z.ai reports GLM-5.2 within a point of Claude Opus 4.8 on FrontierSWE and at 81.0 versus 85.0 on Terminal-Bench 2.1. Those are vendor claims, not independent reproductions, and proprietary models still lead on multimodality and polish. The practical answer: the gap is now small enough that an evaluation on your actual workload, not a leaderboard, should make the call.

It spans four orders of magnitude, which is the point of choosing deliberately. Gemma 4's E2B runs offline on phones and Raspberry Pi-class devices per Google, Qwen 3's small dense models run on laptop-class hardware, Gemma 4's 31B and Llama 4 Scout (at Int4) each fit a single 80GB H100 per their vendors, and the frontier MoEs are multi-GPU to multi-node: GLM-5.2's BF16 weights alone are about 1.51TB on disk. Active-parameter counts set your per-token compute, but total parameters set your memory bill, and memory is usually what you run out of first.

Yes, for almost every company, with conditions. The Llama 4 Community License grants free commercial use unless your products exceeded 700 million monthly active users as of the release date, in which case you must request a separate license from Meta. If you distribute the model or a product containing it, you must prominently display Built with Llama, ship the license and notice text, and any distributed fine-tuned derivative must have Llama at the start of its name. Free, yes; unconditional, no.

Start from the arithmetic: hosted per-token access to these same open models is cheap (Mistral Large 3 at $0.50 in and $1.50 out per million tokens as of July 2026), so self-hosting wins only when something structural demands it: data that cannot leave your infrastructure, sustained volume beyond per-token economics, an owned fine-tune, or a sovereignty requirement. Many teams land on a hybrid, prototyping against a hosted endpoint and moving to self-hosted serving once the workload and the compliance picture are proven.

GLM-5.2, on the strength of the published numbers: 81.0 on Terminal-Bench 2.1 against Claude Opus 4.8's 85.0, and 62.1 on SWE-bench Pro against Opus 4.8's 69.2, per Z.ai. It was rolled out first through Z.ai's coding subscription, which tells you the lane it was built for. DeepSeek R1-0528 is the strongest owned-reasoning alternative (LiveCodeBench 73.3 per DeepSeek), and Qwen 3's hybrid thinking mode makes it the practical pick when the same deployment must serve coding and general traffic.

Yes, with clear eyes. The V4 generation has superseded the line, and DeepSeek's own API deprecates the deepseek-chat and deepseek-reasoner names on July 24, 2026. But the weights remain MIT licensed, and eighteen months of community quantizations, deployment guides, and known failure modes make V3 and R1 the best-understood self-hosting stack in the open-weights field. For a production system, boring and documented is a feature. Evaluate V4, whose weights are also openly downloadable under MIT, for new builds; do not rush to rip out a working R1 deployment.

Get a recommendation tailored to your situation

BearPlex ships production systems on several of the options above. We'll tell you which fits your case in a 30-minute scoping call.