Name / Structure / SMILES / InChI Converter

Overview

Normalize names, formulas, SMILES, and identifiers into a shared conversion workspace. It is in the Draw, Identity, and Visualization category and is intended to turn molecular drawings, names, identifiers, or formulas into reusable chemical identity records.

When To Use It

• You need a focused workflow for name / structure / smiles / inchi converter without leaving ChemistryAtlas.
• You want a result that can be saved, shared, or chained into another chemistry app.
• You want the calculation assumptions and limitations visible next to the output.

Inputs

• text - Chemistry input - type: textarea - Use formulas, names, SMILES-like text, reactions, or key=value options. Heavier engines will plug into this same app surface.

Recommended Workflow

• Start by pasting a name, SMILES, InChI, formula, or exported Ketcher structure; normalize the identity; then send the result into property, safety, spectra, or reaction tools.
• Start with the smallest representative input, confirm the parser understood it, then scale to a larger list or workflow.
• Save the generated report when the result will feed a notebook entry, route review, model comparison, or team discussion.

Outputs

• A Markdown-style chemistry report with parsed inputs, assumptions, and calculated or predicted results.
• Structured tables when the app returns multiple compounds, reagents, routes, peaks, candidates, or model rows.
• Warnings, fallback notes, and sidecar availability messages when a specialized engine is not installed or not reachable.

Method And Backend Notes

This app has a runnable ChemistryAtlas backend path. Backend type: database. ChemistryAtlas roadmap MVP: runnable report now; specialist cheminformatics/model backend plugs into this app surface next. This tool is part of the draw-once ChemistryAtlas identity layer. When Ketcher is available in the UI, exported SMILES or molfile data can be reused by downstream apps.

How To Interpret Results

• Treat identifiers and descriptors as the canonical handoff record for later ChemistryAtlas work; verify ambiguous names and salts before committing them to an ELN or purchasing workflow.
• Compare results across related molecules, controls, blanks, literature examples, or known reactions whenever possible.
• For decisions that affect safety, synthesis scale-up, biological testing, purchasing, or publication, verify with primary data and expert review.

Example Input

caffeine
aspirin

Common Checks Before Acting

• Confirm names, salts, stereochemistry, tautomers, protonation state, and hydration state.
• Check units, concentrations, equivalent definitions, and significant figures.
• Record external database versions, model versions, sidecar availability, and any manual edits made after the app output.

Related Apps

• Compound Card (compound-card)
• Structure Editor (structure-editor)
• Structure Standardizer (structure-standardizer)

Acknowledgements And Validation

• ChemistryAtlas documentation and UI were prepared for chemistry discovery workflows.
• Where available, calculations may use open-source cheminformatics, reaction-informatics, spectra, docking, or machine-learning engines such as RDKit-family tooling, ASKCOS-style sidecars, ChemProp, ms-pred/ICEBERG, PyScreener, and MolPAL.
• Always verify important results against primary literature, official SDS records, instrument software, validated models, and local laboratory procedures.