70/100

Moderate evidence

GainPublished recordScienceGood Space

AlphaFold Protein Structure Database in 2024: providing structure coverage for over 214 million protein sequences

Truvace record
TRV-2026-1205raw data (JSON)
Version
v3Revised
First published
Evidence type
Official statistics
Sources
1 sourcePeer-reviewed
sha256
f51e6e95f86b…check it

The AlphaFold Database Protein Structure Database (AlphaFold DB, https://alphafold.ebi.ac.uk) has significantly impacted structural biology by amassing over 214 million predicted protein structures, expanding from the initial 300k structures released in 2021. Enabled by the groundbreaking AlphaFold2 artificial intelligence (AI) system, the predictions archived in AlphaFold DB have been integrated into primary data resources such as PDB, UniProt, Ensembl, InterPro and MobiDB. Our manuscript details subsequent enh…

The gain

The AlphaFold database's authors report it grew from 300,000 predicted protein structures in 2021 to over 214 million, with predictions now integrated into PDB, UniProt, Ensembl, InterPro and MobiDB.

Sources

1 on file
  1. Nucleic Acids Researchdoi:10.1093/nar/gkad1011
    Peer-reviewed2023-10-18

Cite this record

v3

Truvace Impact Record TRV-2026-1205, v3: “AlphaFold Protein Structure Database in 2024: providing structure coverage for over 214 million protein sequences.” Truvace, 2026-11-05. /record/TRV-2026-1205 (accessed on the day you copy it). sha256 f51e6e95f86bd473…

Change history

3 versions

Every change made to this record since it was first published, and why.

  1. Revisedv3f51e6e95f86b…

    Voice pass: plainer wording and study attribution; no facts or figures changed.

  2. Revisedv2004afe656c2e…

    Editorial pass: sharper headline; gain/problem restated as concrete outcomes.

  3. Publishedv1dc83984f3542…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-1205 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.