Ligand Prep
Inspect, clean, annotate, and prepare ligand MOL2 material and torsion restrictions before docking conversion.
How to cite this tool
Use this citation text and add the date accessed if the file is hosted online or shared through a repository.
What this page is supposed to do
This page is the ligand quality-control step. It is meant to slow the user down before PDBQT conversion by making atoms, bonds, charge notes, protonation notes, and rotatable-bond restrictions visible.
Use this page when
- You have a MOL2 ligand file from Ligand Draw, an external structure service, or another preparation package.
- You need to inspect candidate torsions and decide which bonds should remain movable or locked.
- You want to export a ligand session JSON and restrictions JSON for later conversion.
Do not use it as
- Do not use visual cleanup as a replacement for chemical preparation, pKa estimation, conformer generation, or charge assignment.
- Do not lock torsions only to force a preferred docking result.
- Do not proceed when atom counts, bonds, total charge, or warnings do not match the intended ligand.
At a glance
| Question | Answer |
|---|---|
| Primary job | Inspect ligand file and define torsion policy. |
| Main risk | Chemistry may look valid visually while charges, atom types, or protonation are wrong. |
| Best next step | Use the MOL2 and restrictions JSON in PDBQT Converter. |
| Reproducibility file | Session JSON, restrictions JSON, exported MOL2 copy, and notes. |
Typical inputs
- MOL2 ligand file.
- Optional session JSON previously saved by this page.
- Optional manual metadata such as name, total charge, protonation note, tags, and notes.
Typical outputs
- Cleaned or copied MOL2 material where the page provides export.
- Ligand session JSON.
- Restrictions JSON for later docking or conversion steps.
- Diagnostics about atoms, torsions, and possible issues.
Where it fits in the docking workflow
- 0Ligand Draw
Create or import a ligand starting structure.
- 1Ligand Prep
Inspect ligand chemistry, metadata, and torsion restrictions.
- 2Receptor PDB Clean
Clean a receptor PDB and decide what to keep.
- 3Receptor PQR Handoff
Assign receptor protonation and charges with an external PQR workflow.
- 4PDBQT Converter
Convert cleaned receptor and prepared ligand material to docking-ready PDBQT.
- 5Vina Setup
Define the docking box and export a Vina-style configuration.
- 6Vina Run
Run or emulate docking and inspect poses, scores, and warnings.
Step-by-step use
- Load the MOL2 file. If the page provides a demo ligand, use it only for learning the interface, not as a scientific input.
- Read the status panel. Fix file-format problems before editing metadata. A malformed MOL2 can lead to misleading atom, bond, and torsion displays.
- Check ligand metadata. Enter a clear name, total charge, protonation note, tags, and free-text notes. These fields help later review but do not automatically validate the chemistry.
- Inspect the 3D viewer. Rotate the ligand, check separated fragments, unusual bond lengths, missing groups, unexpected hydrogens, and geometry that is clearly not intended.
- Review quick stats. Confirm atom count, element distribution, charge information, and any warning counts against the source record for the molecule.
- Run or review torsion detection. The page identifies candidate rotatable bonds for workflow control. It is not a full chemical force-field optimization.
- Decide the restrictions policy. Leave chemically reasonable single bonds movable unless there is a clear reason to lock them, such as a constrained scaffold, known ring handling issue, or a deliberate teaching example.
- Use the torsion list filter. Review all candidate torsions, then check allowed, locked, and blocked groups separately. Make sure each locked bond has a reason in the notes.
- Use the atom inspector for unclear atoms. Confirm atom names, element assignment, residue or molecule identifiers, charge fields, and connectivity around important functional groups.
- Use minimization only as a convenience if the page supports it. Do not treat it as a replacement for a validated conformer-generation or quantum or force-field workflow.
- Export restrictions JSON and the MOL2 copy. Save the session JSON as the reproducibility record for how the ligand was inspected and restricted.
- Move to PDBQT Converter with the exported MOL2 and restrictions JSON. Keep all intermediate files because conversion warnings often require returning to this page.
How to interpret what you see
- Allowed torsion
- A bond that the workflow may treat as movable.
- Locked torsion
- A bond you deliberately fixed. This reduces search space but can bias the result.
- Blocked by rules
- A bond the page considers unsuitable for rotation because of ring, chemistry, or rule-based criteria.
- Session JSON
- The page state. It helps reproduce choices but is not a scientific validation certificate.
- Restrictions JSON
- A downstream control file for torsion handling. It should stay paired with the exact ligand file used to create it.
Quality-control checklist before moving on
- MOL2 opened without parse warnings.
- Ligand name and intended state are recorded.
- Total charge is intentional.
- Torsion locks are justified.
- Restrictions JSON corresponds to the same ligand file.
- Exported files are saved in the project folder.
Troubleshooting
| Problem | What to check |
|---|---|
| The ligand does not appear in the viewer. | Check that the uploaded file is MOL2 text and not an SDF, PDB, or compressed file with the wrong extension. |
| Torsion count seems too high. | Check for disconnected fragments, bad bond orders, missing aromatic typing, or incorrect ring perception. |
| Torsion count seems too low. | Check whether bonds are encoded as aromatic, amide-like, ring bonds, or otherwise blocked by the rules. |
| Charges do not match expectation. | Return to the chemical preparation source. Do not fix charge problems by editing labels only. |
| The page opens but looks unstyled. | The documentation expects the package assets folder at ../assets. If you copied only the docs folder, place it back inside the full tools directory. |
| Special characters display as garbled text. | Serve the page as UTF-8 and keep the PHP header at the top of the file. Do not resave the file in a legacy encoding. |
| A button does nothing. | Check whether a file must be loaded first, whether the browser blocked a popup, or whether a required external service is offline. |
| The output seems scientifically wrong. | Stop the workflow. Check the input format, warnings, protonation state, atom typing, grid placement, and whether the tool is only a helper for that step. |
Practical notes
- Keep the original input files unchanged. Save all exports into a project folder with a clear date and version note.
- Do not use a generated result only because the page produced it. Inspect warnings, inputs, assumptions, and output format before moving to the next step.
- For publication, reporting, or operational decisions, validate the result with established scientific software and cite the final software versions and settings.
- Treat browser storage as temporary. Export session JSON or report files whenever you need a reproducible record.
Copyright and disclaimer
Copyright © 2026 Alexander Weiss, akhw.at. All rights reserved.
Research workflow helper only. Chemical preparation, protonation, atom typing, charge assignment, conformer quality, and torsion decisions must be validated with established scientific software before use in decisions or publications.