This article was accepted into the corpus but its outbound wikilinks were never NER-processed — typical at the deepest BFS hop or when the run's entity cap was reached. No expansion funnel to show.
| MOL2 | |
|---|---|
| Name | MOL2 |
| Extension | .mol2 |
| Mime | chemical/x-mol2 |
| Owner | Tripos |
| Released | 1990s |
| Genre | chemical file format |
MOL2
MOL2 is a file format used for representing three-dimensional descriptions of small molecules and macromolecular fragments. Initially developed by the Tripos International software group during the 1990s, it provides a flexible, ASCII-based schema for encoding atom coordinates, bonds, substructure information, and atom typing. The format became widely adopted across cheminformatics and molecular modeling communities, influencing software such as SYBYL, OpenEye Scientific Software, AutoDock, RDKit, and Amber toolchains.
MOL2 originated at Tripos International for use with the SYBYL molecular modeling suite and was formalized to carry detailed chemical topology and atom type annotations. Its design balances human readability with machine parsability, making it useful for workflows spanning structure generation in Corina, geometry optimization with Gaussian (software), and docking preparations for AutoDock Vina. The format emphasizes per-atom metadata that supports diverse atom-typing schemes, enabling interoperability among tools like OpenBabel, RDKit, MOE (software), and GROMACS converters.
A MOL2 file is an ASCII text file composed of tagged sections, each beginning with '@<' followed by a section name. Key mandatory blocks include '@
The format permits custom tags and free-text headers, enabling projects like Protein Data Bank pre-processing pipelines and virtual screening stacks to store provenance and processing metadata. Despite informal standardization, variations exist due to differing implementations in proprietary suites like SYBYL and open tools like OpenBabel, which has led to community-driven de facto conventions captured in documentation from Tripos International and third-party repositories.
MOL2 encodes both geometric and chemical information: Cartesian coordinates, element and formal charge, atom type strings that often reflect force field or valence state, and bond topology with order or aromatic flags. Atom typing schemes used in MOL2 commonly relate to Tripos force field types, which have mappings to broader systems such as MMFF94, AMBER atom types, and CHARMM nomenclature via conversion layers in tools like RDKit or OpenBabel. The '@
Partial charge fields are frequently present and used by molecular mechanics packages and docking engines; these may be computed by programs such as Gaussian (software), MOPAC, or empirical methods embedded in MOE (software). MOL2 supports aromaticity flags and bond typing that enable recognition of conjugated systems by cheminformatics platforms such as ChemAxon and OpenEye Scientific Software, although exact aromaticity perception can vary among implementations.
A wide ecosystem reads and writes MOL2, including both proprietary and open-source projects. Notable readers/writers include SYBYL, OpenBabel, RDKit, OpenEye toolkits, AutoDock utilities, and molecular viewers such as PyMOL and UCSF Chimera. Force field parameterization workflows in AMBER and CHARMM often employ MOL2 as an interchange format for ligands and small molecules, with tools like acpype and antechamber generating MOL2 files as intermediate artifacts. Virtual screening pipelines integrate MOL2 support in batch processing via command-line utilities from OpenEye Scientific Software and converters embedded in Schrödinger (company) suites.
Interoperability extensions and plugins exist for database systems like ZINC (database) and cheminformatics platforms such as Chembl exporters, enabling MOL2 export for large compound libraries. The format’s simplicity makes it amenable to scripting and parsing in general-purpose languages supported by scientific computing ecosystems including Python (programming language), Perl, and C++.
MOL2 is used extensively for ligand preparation in structure-based drug discovery, enabling transfer of 3D geometries and atom types into docking programs like AutoDock Vina and scoring workflows using Glide or DOCK. It serves as an interchange format between quantum chemistry packages (e.g., Gaussian (software), ORCA (software)) and molecular mechanics engines (AMBER, GROMACS), facilitating charge derivation and parameter assignment. Cheminformatics tasks—such as fragment assembly, virtual library enumeration in ZINC (database), and compound registration in corporate systems like ChemSpider or internal ELNs—use MOL2 for preserving topology alongside metadata.
In computational workflows for structure-based design, MOL2 files carry substructure annotations that aid in pharmacophore modeling with tools like LigandScout and in free-energy calculations orchestrated by platforms such as FEP+ and GROMACS-based alchemical pipelines.
MOL2’s flexibility yields variability: different implementations may use divergent atom typing conventions, aromaticity encodings, and optional block semantics, causing mismatches between software like SYBYL and OpenBabel. The format lacks a formal, single authoritative standard body, which can complicate unambiguous mapping to force fields such as MMFF94 or AMBER without intermediate conversion steps. Large macromolecular assemblies and explicit crystallographic symmetry are not the format’s primary focus compared to formats like PDB or mmCIF, which provide richer macromolecular metadata and experimental annotations. Users often rely on conversion utilities and validation routines within ecosystems like RDKit and OpenBabel to reconcile differences and ensure fidelity when exchanging data across platforms.
Category:Chemical file formats