explainx / blog
Model parameters are the learned numbers inside a neural net—roughly, how big the model is. Here is a clear picture of total vs active parameters, why frontier APIs often hide counts, and a table of top models with public figures (Meta Llama 4) next to the undisclosed front tier.
Apr 22, 2026
Context length is the cap on 'how much the model can read at once,' not the same as how many parameters it has. This guide defines the window, input vs max output, long-context tradeoffs, and what Anthropic, OpenAI, Google, and Meta publish today.
Apr 22, 2026
If you have ever seen
Jun 29, 2026
For the first time, more U.S. businesses on Ramp pay for Anthropic than OpenAI — 34.4% vs 32.3% in April 2026, with Anthropic quadrupling share in a year while OpenAI grew 0.3%. The viral X thread tied it to loop engineering and Dario Amodei's claim that some Anthropic engineers barely write code anymore. Here is what the index actually counts, what it does not, and why workflow beats chat.
Parameters (often billions of parameters, or B / bn) are the usual shorthand for how big a neural language model is in terms of learned weights. They are not the same as tokens (text units) and not the same as context length (how much text fits in one request)—but all three get compared when people discuss GPT-class, Claude-class, Gemini-class, and open weights like Llama.
This article hews to what vendors publish in 2026 and to one open line with full public tables: Meta’s Llama 4 on the official model card. Frontier APIs often list behavior and limits without a single headline parameter count; we cover why below.
A transformer-style LLM is a stack of layers that transform vectors representing tokens. Pretraining and fine-tuning adjust the entries of large weight matrices (and related biases) so the model improves at next-token prediction, tool use, or multimodal tasks—depending on the architecture.
Parameter count is how many of those scalar weights sit in the shipped checkpoint. Some model cards also break out separate totals for a tokenizer, vision tower, or audio encoder—read the specific card for the SKU you run.
Scaling laws in research usually relate loss to compute, data, and size together; a headline “B” count is one line in a larger system.
In a dense model, “70B parameters” generally means on the order of 70B weights on the main path of each token (implementation details aside).
In an MoE design, many parallel feedforward experts exist, but a router sends each token to one or a few of them. Cards often list total parameters (all experts) and activated parameters (roughly what runs for a typical forward pass).
Meta Llama 4 (from the model card table, April 2025 release; confirm on GitHub for updates):
| Model | Activated (per card) | Total (per card) | Context length (per card) |
|---|---|---|---|
| Llama 4 Scout (17B × 16E) | 17B | 109B | 10M tokens |
| Llama 4 Maverick (17B × 128E) | 17B | 400B | 1M tokens |
E denotes expert count in Meta’s notation. Scout and Maverick share the same activated width in this table but differ in total size and in context length by design. Always re-read the model card for the exact checkpoint you deploy.
If you see a billion-scale number for a closed model in a third-party post, treat it as analysis or speculation unless the vendor or a vetted system card states it.
Parameter and architecture details change with each release. Prefer the model card and API docs of the specific checkpoint you use.
