Hub Weight Census: what AI models say about themselves

We read only the safetensors headers of thousands of Hugging Face repositories (names, shapes and storage of every tensor, never the weights) and recovered each model's architecture from them. Here is what the models people actually use are made of, how that changed year by year, and where the metadata around them is wrong.

Look up a model

Type any model from the census. See what it is made of, where it sits among popular models, and which devices it fits on.

Deploy-Ready board

Models submitted by their authors and users. Each is read from its headers and placed by the memory it needs at 4-bit with an 8k context, with five checks on its metadata. Submit yours and get a badge for the model card.

Submit a modelOpens a GitHub issue; a bot replies within minutes.

Findings

Popular repos: the most downloaded, the most downloaded original releases, and recent releases from leading providers. Test fixtures (tiny random-weight repos) are left out.

Architecture by release year
% of popular original language models released that year
The Hub's parameter count, by storage format
% of repos where the count shown on the Hub differs from the logical count read from the headers. For NVFP4 the Hub counts packed bytes; other gaps can be on either side
Typical shape, by release year
Median head size and vocabulary of popular original language models
head size
vocabulary (thousands)
When there is nothing to read
Popular repos without safetensors or PyTorch weights, by what they ship instead
Memory map of popular language models
Each dot is a model: parameters (to hold) against KV cache per token (to grow with context). Lines: the most a device holds at 4-bit. Hover for the name, click to open its anatomy.

Models

The most downloaded readable models in the census. Click a name to open its full anatomy.

Params: logical parameters (quantized storage unpacked). Hub: ✓ when the Hub's own count agrees within 0.1%, otherwise our count ÷ the Hub's. KV/token: bytes of KV cache per token at 16 bit.

Data and method

Every repo: status, popularity, the architecture recovered from the weights, the values its config.json declares, the Hub's own parameter count and the raw manifest, so the results can be re-scored. Code and the frozen recovery rules are public.