Compounds
Name
Compound type
Version
Size
File
Compounds (csv)
original
01.2026
67.91 MB
Compounds (csv)
standardized
01.2026
59.47 MB
Compounds (csv)
nonisomeric
01.2026
49.33 MB
Compounds (sdf)
original
01.2026
487.51 MB
Compounds (sdf)
standardized
01.2026
422.56 MB
Compounds (sdf)
nonisomeric
01.2026
372.4 MB
Targets & activities
Name
Compound type
Version
Size
File
Targets and activities (csv)
original
01.2026
64.77 MB
Targets and activities (csv)
standardized
01.2026
64.53 MB
Targets and activities (csv)
nonisomeric
01.2026
63.66 MB
Targets and activities (xlsx)
original
01.2026
72.34 MB
Targets and activities (xlsx)
standardized
01.2026
66.61 MB
Targets and activities (xlsx)
nonisomeric
01.2026
56.3 MB
Chemical probes
Name
Compound type
Version
Size
File
Chemical probes (xlsx)
standardized
01.2026
1.09 MB
Compound ID mapping
Name
Compound type
Version
Size
File
Compound ID mapping (csv)
original
01.2026
50.92 MB
Compound ID mapping (csv)
standardized
01.2026
45.92 MB
Compound ID mapping (csv)
nonisomeric
01.2026
35.05 MB
Database dump
Name
Version
Size
File
SQLite database (zip)
01.2026
430.19 MB
PostgreSQL database dump (zip)
01.2026
262.42 MB
# To restore the data from the PostgreSQL dump, first, you need to extract (unzip) the dump and create an empty database:
CREATE DATABASE database_name WITH OWNER username;
# Then you can restore the dump using:
pg_restore --no-owner -h HOST -p PORT -U USERNAME -d database_name /path/to/pd_dump.sql
Please be aware that internal database IDs are not preserved and may change from version to version. The only IDs that are consistently preserved are compounds' PDIDs, which can be used to link to P&D.