Convert
This is normalized to a safe ID when you run.
Drop source file here or click to upload
# API example will render hereRequired. This is the run name shown in your dashboard, job history, and downloads.
The current backend-compatible transport field still resolves to PDB or CIF, but the exact source format you choose here is also sent separately for backend routing.
The exact requested output format is sent to the backend as metadata, even when the strict compatibility field is still PDB or CIF.
Optional routing hint for the backend. Useful when the file extension is ambiguous.
Backend hint for sequence parsing and validation when converting to or from sequence-like formats.
Optional backend preference for how coordinates should be handled when a structure representation is involved.
How the backend should name the converted output file.
Upload the source content to convert. The frontend sends the raw text as file_content plus the file name and file format metadata.
Keep original chain labels where possible during structural conversion.
Include ligands, ions, waters, and other HETATM-style records when relevant.
If the source contains multiple models or frames, the backend can be told to use only the first one.
Backend hint to clean common formatting issues and normalize text output where possible.
Useful for sequence or line-notation inputs such as FASTA or SMILES when the target is structural.
conversion.from and conversion.to stay compatible with the current backend transport,
while the exact requested formats are also sent as input_format and output_format.
# API example will render here