Skip to main content

ChEMBL 28 Released!

 We are pleased to announce the release of ChEMBL_28. This version of the database, prepared on 15/01/2021 contains:

* 2,680,904 compound records
* 2,086,898 compounds (of which 2,066,376 have mol files)
* 17,276,334 activities
* 1,358,549 assays
* 14,347 targets
* 80,480 documents

Data can be downloaded from the ChEMBL FTP site:

Please see ChEMBL_26 release notes for full details of all changes in this release:


This release includes several new deposited data sets:

Donated Chemical Probes data from SGC Frankfurt (src_id = 54)
SARS-CoV-2 screening data from the Fraunhofer Institute (src_id = 52)
Antimicrobial screening data sets from CO-ADD (src_id = 40)
Plasmodium screening data from the UCSD Winzeler lab (src_id = 51)
MMV pathogen box screening data (src_id = 34)

Curated data sets:

Drug safety warning information:
Safety-related information for approved drugs has been curated to include the assignment of toxicity classes (e.g., Cardiotoxicity, Hepatotoxicity Teratogenicity etc), based on their withdrawn status and/or black box warning information described on medicinal product labels. Two new tables have been included in ChEMBL to hold this information: DRUG_WARNING and WARNING_REFS and a new web service endpoint is also available: For more information about this data set and the methods used, please see:
This information can be seen on the Compound Report Card for the relevant drugs e.g.,

Metabolism Pathways:
Further metabolic pathways have been curated from the Journal of Drug Metabolism and Disposition and are included in the METABOLISM table. This dataset comprises more than 900 additional reactions in pathways for 98 distinct drugs/compounds. Where available, this information is displayed on the Compound Report Card e.g.,

Prodrug active ingredients (src_id = 53):
Compound records have now been included for active ingredients that are formed through metabolic activation of prodrugs. These active ingredients have also been updated in the molecule_hierarchy (as the ACTIVE_MOLREGNO) to link them to the corresponding prodrug (PARENT_MOLREGNO).

The following data sources have also been updated:

Scientific Literature, Patent Bioactivity Data, USP Dictionary of USAN and International Drug Names, Clinical Candidates, WHO Anatomical Therapeutic Chemical Classification, Orange Book, Manually Added Drugs


  • Advanced search with a list of molecule or target ChEMBL IDs is now available (see separate blog post for more details):
  • Assay parameters and activity properties included on Browse Activities view (these columns are hidden initially and need to be added with the 'Show/hide columns' button). Since there can be multiple parameters/properties for an assay/activity, these columns show a concatenated list.
  • Variant sequences information included on Assay Report Card and Browse Activities view e.g.,
  • Obsolete or downgraded ChEMBL IDs now resolve to a message page that indicates the status of each entity. For example,  indicates that the compound has been permanently removed from the database and indicates that the compound is currently downgraded in ChEMBL_28. If a user is not sure what type of entity a given ChEMBL ID corresponds to, they can now use a single URL with any type of ChEMBL ID (compound/target/assay/document/cell/tissue) and it will resolve to the correct Report Card page e.g., or Furthermore, if the wrong report card URL is used for a valid ChEMBL ID, it will be redirected to the correct Report Card page (e.g., will redirect to, since CHEMBL25 is a compound).


Columns Added:

VARIANT_ID NUMBER(9,0) Foreign key to VARIANT_SEQUENCES table, indicating that the drug targets a specific variant form of the protein.

Columns Removed:

The following columns are deprecated (replaced by the new tables below) and will be removed in a future release:

Tables Added:

WARNING_ID NUMBER(9,0 Primary key for the drug warning
RECORD_ID NUMBER(9,0) Foreign key to the compound_records table
MOLREGNO NUMBER(9,0) Foreign key to molecule_dictionary table
WARNING_TYPE VARCHAR2(20 BYTE) Description of the drug warning type (e.g., withdrawn vs black box warning)
WARNING_CLASS VARCHAR2(100 BYTE) High-level class of the drug warning
WARNING_DESCRIPTION VARCHAR2(4000 BYTE) Description of the drug warning
WARNING_COUNTRY VARCHAR2(1000 BYTE) List of countries/regions associated with the drug warning
WARNING_YEAR NUMBER(4,0) Year the drug was first shown the warning

WARNREF_ID NUMBER(9,0) Primary key for the warning reference
WARNING_ID NUMBER(9,0) Foreign key to the drug_warning table
REF_TYPE VARCHAR2(50 BYTE) Type/source of reference
REF_ID VARCHAR2(4000 BYTE) Identifier for the reference in the source
REF_URL VARCHAR2(4000 BYTE) Full URL linking to the reference


The following changes have been made to web services:
Assay, Activity and Mechanism endpoints now include variant sequence information

Download formats:
Please note, from ChEMBL_29 onward, we will no longer be able to provide Oracle 10g/11g/12c dumps. Only Oracle 19c dumps will be provided (in addition to the usual PostgreSQL/MySQL/SQLite dumps).

Funding acknowledgements:

Work contributing to ChEMBL28 was funded by the Wellcome Trust, EMBL Member States, Open Targets, National Institutes of Health (NIH), EU Innovative Medicines Initiative 2 (IMI2) and EU Horizon 2020 programmes. Please see for more details.

If you require further information about ChEMBL, please contact us:

# To receive updates when new versions of ChEMBL are available, please sign up to our mailing list:
# For general queries/feedback or to report any problems with data, please email:
# For details of upcoming webinars, please see:


Popular posts from this blog

A python client for accessing ChEMBL web services

Motivation The CheMBL Web Services provide simple reliable programmatic access to the data stored in ChEMBL database. RESTful API approaches are quite easy to master in most languages but still require writing a few lines of code. Additionally, it can be a challenging task to write a nontrivial application using REST without any examples. These factors were the motivation for us to write a small client library for accessing web services from Python. Why Python? We choose this language because Python has become extremely popular (and still growing in use) in scientific applications; there are several Open Source chemical toolkits available in this language, and so the wealth of ChEMBL resources and functionality of those toolkits can be easily combined. Moreover, Python is a very web-friendly language and we wanted to show how easy complex resource acquisition can be expressed in Python. Reinventing the wheel? There are already some libraries providing access to ChEMBL d

ChEMBL 29 Released

  We are pleased to announce the release of ChEMBL 29. This version of the database, prepared on 01/07/2021 contains: 2,703,543 compound records 2,105,464 compounds (of which 2,084,724 have mol files) 18,635,916 activities 1,383,553 assays 14,554 targets 81,544 documents Data can be downloaded from the ChEMBL FTP site: .  Please see ChEMBL_29 release notes for full details of all changes in this release: New Deposited Datasets EUbOPEN Chemogenomic Library (src_id = 55, ChEMBL Document IDs CHEMBL4649982-CHEMBL4649998): The EUbOPEN consortium is an Innovative Medicines Initiative (IMI) funded project to enable and unlock biology in the open. The aims of the project are to assemble an open access chemogenomic library comprising about 5,000 well annotated compounds covering roughly 1,000 different proteins, to synthesiz

Identifying relevant compounds in patents

  As you may know, patents can be inherently noisy documents which can make it challenging to extract drug discovery information from them, such as the key targets or compounds being claimed. There are many reasons for this, ranging from deliberate obfuscation through to the long and detailed nature of the documents. For example, a typical small molecule patent may contain extensive background information relating to the target biology and disease area, chemical synthesis information, biological assay protocols and pharmacological measurements (which may refer to endogenous substances, existing therapies, reaction intermediates, reagents and reference compounds), in addition to description of the claimed compounds themselves.  The SureChEMBL system extracts this chemical information from patent documents through recognition of chemical names, conversion of images and extraction of attached files, and allows patents to be searched for chemical structures of interest. However, the curren

Julia meets RDKit

Julia is a young programming language that is getting some traction in the scientific community. It is a dynamically typed, memory safe and high performance JIT compiled language that was designed to replace languages such as Matlab, R and Python. We've been keeping an an eye on it for a while but we were missing something... yes, RDKit! Fortunately, Greg very recently added the MinimalLib CFFI interface to the RDKit repertoire. This is nothing else than a C API that makes it very easy to call RDKit from almost any programming language. More information about the MinimalLib is available directly from the source . The existence of this MinimalLib CFFI interface meant that we no longer had an excuse to not give it a go! First, we added a BinaryBuilder recipe for building RDKit's MinimalLib into Julia's Yggdrasil repository (thanks Mosè for reviewing!). The recipe builds and automatically uploads the library to Julia's general package registry. The build currently targe

New Drug Warnings Browser

As mentioned in the announcement post of  ChEMBL 29 , a new Drug Warnings Browser has been created. This is an updated version of the entity browsers in ChEMBL ( Compounds , Targets , Activities , etc). It contains new features that will be tried out with the Drug Warnings and will be applied to the other entities gradually. The new features of the Drug Warnings Browser are described below. More visible buttons to link to other entities This functionality is already available in the old entity browsers, but the button to use it is not easily recognised. In the new version, the buttons are more visible. By using those buttons, users can see the related activities, compounds, drugs, mechanisms of action and drug indications to the drug warnings selected. The page will take users to the corresponding entity browser with the items related to the ones selected, or to all the items in the dataset if the user didn’t select any. Additionally, the process of creating the join query is no