SMILES to MOL2
v1.5Generate MOL2 files from SMILES strings for docking, scoring, and modeling workflows.
SMILES to MOL2 is a small-molecule format conversion workflow that turns a line notation into a three-dimensional Tripos MOL2 structure file. A SMILES string defines molecular connectivity and any explicitly written stereochemistry, but it has no atomic coordinates. MOL2 adds a 3D conformer and atom and bond records that molecular modeling programs can read.
MOL2 is useful when a workflow requires a ligand structure file rather than a SMILES string, including visualization, docking preparation, and molecular mechanics pipelines. The generated geometry is a starting conformer, not an experimentally determined pose or a validated bound-state structure. Programs with a required charge model, atom-typing scheme, or protonation convention should still be given their own ligand-preparation step.
ProteinIQ converts one SMILES string or a small named batch into separate 3D MOL2 files. SMILES can be pasted, supplied in a supported text file, or retrieved from PubChem by name or CID. The result includes one downloadable .mol2 file for each successful entry and a curated Run log that summarizes conversion status and failures.
| Input | Accepted form | Notes |
|---|---|---|
SMILES | One valid SMILES string per line | The interface accepts up to 10 entries in a batch. For example, aspirin can be entered as CC(=O)Oc1ccccc1C(=O)O. |
| Named SMILES | name<TAB>SMILES | The supplied name is used for the output filename and molecule title. For example, aspirin\tCC(=O)Oc1ccccc1C(=O)O. |
| File upload | .txt, .csv, .tsv, .smi, or .smiles | Use one record per line. A CSV or TSV whose first row names a smiles column is read by column: SMILES come from that column and names from a name, id, title, or compound column. Without a header, name,SMILES and SMILES,name rows both work. |
| PubChem lookup | Compound name or PubChem CID | Retrieved records are converted as SMILES input. |
The submitted SMILES controls the chemistry of the output. Explicit stereochemistry, formal charges, salt fragments, and the chosen tautomer are retained only to the extent that they are present and valid in that SMILES. A structure that has already been drawn or standardized differently will need a correspondingly different input string.
| Setting | Default | Effect |
|---|---|---|
Add hydrogens | On | Adds explicit hydrogen atoms before generating coordinates. Keep this on for most 3D ligand workflows, especially when hydrogen positions matter downstream. |
Optimize geometry | On | Runs up to 500 iterations of UFF force-field optimization after conformer generation. Turning it off returns the embedded coordinates without this refinement. |
| Result | Contents |
|---|---|
Individual .mol2 file | One successful input structure, named from the supplied compound name or input label. Each file contains one generated conformer. |
run.log | A curated run record with the input count, selected settings, conversion phases, successful and failed entry counts, and stable failure guidance. |
Entries are processed independently. A malformed SMILES or a molecule that cannot be embedded does not prevent other entries in the batch from producing files. There is no combined multi-record MOL2 download, so workflows needing a particular multi-molecule layout should use the per-compound files deliberately.
The workflow first parses the SMILES with RDKit. With Add hydrogens enabled, hydrogens are added before geometry generation. RDKit then uses the ETKDGv3 conformer-generation method, which combines distance geometry with experimental torsion preferences and macrocycle-aware settings. The run uses a fixed random seed; if the initial embedding fails, it retries from random coordinates with the same method and seed.
With Optimize geometry enabled, RDKit applies Universal Force Field (UFF) minimization to the generated conformer. If UFF has no parameters for an atom or does not converge within 500 iterations, that entry keeps its file and its row carries a warning. The molecule is then written to an intermediate MOL file and converted to MOL2 with Open Babel. This last conversion produces the MOL2 representation, including its atom and bond records, from the generated structure.
The result is a single deterministic starting conformer for the submitted molecular graph. It is appropriate for format handoff and initial inspection, but it does not search a conformer ensemble, predict a binding pose, or rank conformations by population.
MOL2 is often requested by older docking, parameterization, and visualization workflows because it carries a structured atom and bond table. SMILES to SDF is usually the more portable alternative when the next program accepts SDF or when a multi-record batch file is useful. SMILES to InChI is appropriate when a workflow needs a canonical text identifier rather than 3D coordinates.
MOL2 files should be checked against a docking engine's ligand-preparation requirements. Docking software can require a target-specific protonation state, force-field-specific partial charges, or its own atom typing. Converting format does not establish those modeling choices.
Extract canonical SMILES strings from MOL2 ligand files for cheminformatics workflows.
Generate SMILES strings from InChI identifiers for search, filtering, and modeling workflows.
Extract canonical SMILES strings from MDL MOL ligand files for cheminformatics workflows.
Convert ligand and peptide PDB coordinates to SDF with RDKit bond perception.
Export ligand poses from Meeko-prepared PDBQT to SDF while recovering chemical connectivity.
Convert SDF ligands to PDBQT with Meeko, preserving supplied coordinates.
Extract canonical SMILES strings from SDF ligand files, one record at a time or in batch.
Generate InChI identifiers from SMILES strings for registration and interoperability workflows.
Generate 3D PDB files from SMILES strings for visualization and small-molecule workflows.
Generate 3D ligand coordinates from SMILES and prepare PDBQT files with Meeko.