How we know what we know.

Evidence levels

Every value, application, supply link and milestone carries one of four evidence levels. The glyphs are shape-coded so they never rely on color alone.

EV spec databases (EV Database, EVSpecs and similar) are graded community-reported: they are curated, but they mix measured, estimated and inferred values and rarely cite primary sources. Regulatory filings reported by the press are graded documented.

Conflicting sources

When sources disagree, all values are stored. The value shown first is the one from the most specific source for that pack, for example a code-specific community figure ahead of a generic regulatory figure whose mapping to the pack is inferred. Every alternative stays visible with its own evidence and sources. When the alternatives carry comparable evidence, no primary value is chosen: the field reads Disputed, and charts draw the full range with a hatched pattern.

Capacity definitions

• Gross capacity: the total energy of the pack, including the buffer below 0% displayed charge. Regulators, Tesla's battery management system and community tools each define this slightly differently. That is the most common reason figures disagree by a few percent.
• Usable capacity: the energy available between 100% and 0% displayed charge, when new.
• Tesla does not publish gross or usable capacity for most packs. Badge numbers such as “85” or “100” are marketing labels, shown as such.

Identification limits

A VIN identifies the manufacturer, model, model year and plant, but not the cell supplier or pack code. The finder therefore matches on model, production year (and optionally month), variant, factory and market, and returns every pack documented for that combination. It explains switchovers, parallel suppliers and missing coverage. The definitive identifiers are the high-voltage battery label's part number, Tesla service records, and in Europe the variant field (D.2) on the registration certificate or Certificate of Conformity.

Supply-chain rules

• Where cells are made, where packs are assembled and where vehicles are built are recorded separately.
• A connection is drawn only when reporting supports it, with its own evidence level.
• When a supplier is documented but its plant isn't, the relationship starts from a company-level marker at the supplier's headquarters. It is drawn dashed and labelled as such. It never stands for a factory.

How this edition was compiled

The initial dataset (data as of 2026-10-28) was compiled from published reporting located through web research. During compilation, several primary references, including the Akkuwiki, Tesla's service and investor sites and EV Database, could not be opened directly, so their content was reviewed through search excerpts. 102 of 102 sources are therefore marked pending direct review, and every pack record carries the status initial research until it is checked against its primary sources.

The Akkuwiki is used as a research reference only. No tables were scraped or reproduced. Where it informs a value, it is cited.

Coverage gaps

The database is not complete. Known gaps include:

• Model S 40/60/70 kWh packs (2012–2016) and Model X 60D/75D/90D are not yet documented with cell-level data.
• The 2021+ Model S/X pack's cell count and series/parallel layout are unverified.
• Shanghai Model 3 Standard Range Plus builds from December 2019 to October 2020 have no documented pack.
• The Cybertruck Long Range RWD (2025), the Model 3 Standard and US-market Model Y Standard packs are not yet documented.
• Tesla Semi and Cybercab batteries are out of scope until reliable pack data is published.
• Verified DC charging curves are not yet included for any pack.
• Most Tesla-specific prismatic and Blade cell dimensions are unpublished.

Know something that fills a gap? Send it with a source.

Data model

The dataset is normalized: vehicles → generations → variants, linked to battery packs through applications that carry factory, market, period, variant code and evidence. Packs reference a cell, a family and a cell manufacturer. Manufacturing sites connect to Tesla factories through supply links. Every factual field stores its value, evidence level, sources, notes and any conflicting alternatives. The data is version-controlled JSON, validated with Zod at build time. For hosting it in a database, the project ships a PostgreSQL schema (db/schema.sql) that keeps every conflicting value as its own claim, plus an exporter that generates matching seed data from the JSON.