MOL2 to SMILES icon

MOL2 to SMILES

RDKit/OpenBabel (unpinned)

Extract canonical SMILES strings from MOL2 ligand files for cheminformatics workflows. Learn more

Input

0 credits

Output

Configure inputs to begin

Set options on the left, then click “Submit job”.

What is MOL2 to SMILES?

MOL2 to SMILES is a small-molecule format converter for turning Tripos MOL2 ligand structures into canonical SMILES text. A MOL2 record holds a molecular graph alongside three-dimensional coordinates, atom types, partial charges, and substructure information. SMILES keeps the molecular graph in a compact line notation, which makes it practical for compound registration, library deduplication, descriptor calculation, and ligand-based workflows.

The converter reads and sanitizes the submitted structure with RDKit, then writes RDKit canonical, isomeric SMILES. Canonical output is useful when comparing molecules represented by different atom orders, but it is not a universal identifier. A different cheminformatics toolkit can write a different canonical string for the same molecule, and salts, tautomers, protonation states, and unspecified stereochemistry remain distinct chemical representations.

MOL2 should remain the working format when coordinates, Tripos atom types, or charge assignments matter. When a workflow needs connectivity rather than geometry, SMILES is the more portable handoff. For example, converted ligands can be passed to molecular descriptor calculation or used to screen a library with the PAINS filter.

How to use MOL2 to SMILES online

ProteinIQ converts each submitted .mol2 ligand into a canonical SMILES string. It accepts one pasted MOL2 block or up to 10 uploaded MOL2 files, and returns a .smi file for every successful conversion. A multi-file job also returns a named TSV batch when at least two ligands convert, plus a curated Run log that records the outcome counts for the submitted entries.

Input

InputAccepted contentLimits and requirements
LigandA pasted MOL2 block or .mol2 fileUp to 10 inputs and 50 MB per file. A ligand must contain @<TRIPOS>MOLECULE and @<TRIPOS>ATOM sections. Multi-atom structures also need a @<TRIPOS>BOND section with counts consistent with their atom and bond records.
Job nameOptional label for the conversion jobDefaults to MOL2 to SMILES batch.

MOL2 records need meaningful three-dimensional coordinates. A multi-atom input whose atoms all occupy the same position is rejected before conversion. Submit each molecule as its own pasted block or file when converting a collection.

No conversion settings are required. The input record defines the chemical representation, including formal charges and any stereochemistry that its atom types, bond definitions, and coordinates allow RDKit to interpret. RDKit's MOL2 reader expects the atom-typing scheme used by Corina; files written with other schemes, including some legacy Tripos dbtranslate output, may not parse reliably.

Results and downloads

The result data has one row per submitted ligand. A failed ligand does not prevent other files in the same job from being converted.

Result fieldMeaning
input_nameThe submitted ligand name used to identify the output.
source_formatThe detected source format, mol2 for this tool.
statussuccess when a SMILES string was written, otherwise failed.
smilesThe canonical SMILES string for a successful conversion.
output_fileThe generated .smi filename for a successful conversion.
errorParsing or sanitization detail when the input could not be converted.
DownloadContentsWhen available
<ligand-name>.smiOne canonical SMILES string followed by a newlineFor each successful ligand
batch.smi.tsvTab-separated name and smiles columnsWhen at least two ligands convert successfully
run.logCurated run record with the input format, conversion phases, successful and failed entry counts, and stable failure guidanceFor every job

The .smi files are convenient for individual downstream jobs. batch.smi.tsv retains each input name next to its SMILES value, which is useful for importing a small library into a spreadsheet or workflow. Successful results are also available as ligand-SMILES artifacts in ProteinIQ workflows.

How the conversion works

RDKit first constructs a molecular graph from the MOL2 atom and bond blocks, then sanitizes that graph before writing the result. Sanitization checks that valence, aromaticity, and related chemical features can be assigned consistently. If direct MOL2 parsing fails, ProteinIQ retries by translating the structure to SDF with Open Babel and then parsing the translated record.

Before exporting text, the converter removes ordinary explicit hydrogen atoms and asks RDKit for canonical SMILES with isomeric information enabled. The result can represent connectivity, bond orders, aromaticity, formal charge, isotopes, and specified stereochemistry. It does not retain the input coordinates, Tripos atom types, partial charges, substructure records, or other MOL2 annotations.

For example, an aspirin MOL2 structure can be written as CC(=O)Oc1ccccc1C(=O)O. Many valid non-canonical SMILES spellings can describe the same molecular graph. RDKit canonicalization selects one RDKit-specific spelling; it does not standardize a salt form, select a preferred tautomer, neutralize charge, or infer missing stereochemistry.

Reading failures and choosing the next step

Common failures come from a truncated file, atom or bond counts that do not match the records, missing bond connectivity, unsupported atom typing, or a structure that cannot be sanitized. The Run log records the failed-entry count for the affected inputs.

Format conversion does not repair chemical identity. It does not choose the protonation state appropriate for a target pH, split or remove counterions, or fix incorrect bond orders. Ligand Fixer is appropriate when a MOL2 ligand needs structural preflight and repair. The repaired structure should be inspected before its SMILES is used in later analysis.

SMILES to MOL2 creates a coordinate-bearing MOL2 file from a trusted SMILES string. That reverse conversion generates a new three-dimensional conformer, so it cannot reconstruct the original MOL2 coordinates, charges, or atom types from a SMILES string.

Table of contents

Related tools

SMILES to MOL2

SMILES to MOL2

Convert SMILES strings into 3D MOL2 files for docking and molecular modeling workflows.

format-conversionsmall-molecule+3
InChI to SMILES

InChI to SMILES

Convert InChI strings into SMILES with batch support and downloadable outputs.

format-conversionsmall-molecule+2
MOL to SMILES

MOL to SMILES

Convert MDL MOL ligand files into canonical SMILES strings for registration, filtering, and downstream analysis.

format-conversionsmall-molecule+2
SDF to SMILES

SDF to SMILES

Convert SDF ligand files, including multi-record batches, into SMILES strings.

format-conversionsmall-molecule+3
SMILES to InChI

SMILES to InChI

Convert SMILES strings into InChI strings with batch support and downloadable outputs.

format-conversionsmall-molecule+2
SMILES to PDB

SMILES to PDB

Convert SMILES strings into 3D PDB files for molecular visualization and downstream docking preparation.

format-conversionsmall-molecule+3
SMILES to SDF

SMILES to SDF

Convert single SMILES strings or small batches into 3D SDF files with downloadable per-entry files and a combined batch output.

format-conversionsmall-molecule+3
Open Babel

Open Babel

Run Open Babel in the browser to convert chemical and structure files, with coordinate, hydrogen, and pH options where the WASM runtime supports them.

format-conversionsmall-molecule+4
PDB to SDF Converter

PDB to SDF Converter

Convert Protein Data Bank files to Structure Data Format

format-conversionsmall-molecule+2
SDF to PDB Converter

SDF to PDB Converter

Convert Structure Data Format files to Protein Data Bank format

format-conversionsmall-molecule+2