PDBQT Converter
Convert receptor PDB/PQR and ligand MOL2 material into approximate PDBQT files with validation reports and torsion-tree diagnostics.
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 format-conversion step before Vina setup. It joins receptor coordinates from PDB with receptor charge information from PQR, converts ligand MOL2 material, applies optional torsion restrictions, and creates PDBQT outputs for docking.
Use this page when
- You have a cleaned receptor PDB and matching receptor PQR.
- You have a prepared ligand MOL2 file and optional restrictions JSON.
- You need receptor PDBQT, ligand PDBQT, and conversion reports for the docking setup step.
Do not use it as
- Do not treat approximate atom typing as equivalent to a validated docking-preparation package.
- Do not ignore unknown atom type X warnings, especially near the binding site or in the ligand.
- Do not mix receptor PDB and PQR files from different cleanup versions.
At a glance
| Question | Answer |
|---|---|
| Primary job | Create docking input files in PDBQT format. |
| Main risk | Unknown atom types, mismatched PDB/PQR atoms, bad charge transfer, or wrong torsion tree. |
| Best next step | Open receptor PDBQT and ligand PDBQT in Vina Setup. |
| Reproducibility file | PDBQT outputs plus receptor and ligand report JSON files. |
Typical inputs
- Clean receptor PDB.
- Matching receptor PQR generated from that same cleaned receptor.
- Ligand MOL2 file.
- Optional restrictions JSON from Ligand Prep.
- Optional session JSON.
Typical outputs
- Receptor PDBQT.
- Ligand PDBQT.
- Receptor and ligand report JSON files.
- Split ligand MOL2 files where supported.
- Session JSON.
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 cleaned receptor PDB. Use the exact file exported from the receptor cleanup step unless you deliberately changed it after cleanup.
- Load the matching receptor PQR. It should come from the same cleaned receptor. Atom order, residue identifiers, and coordinates must be compatible enough for the converter to map charges correctly.
- Choose receptor atom typing mode. Strict mode is safer for catching unknowns. Lenient mode may produce output when strict checks are inconvenient, but it increases the need for manual review.
- Decide how to handle HETATM entries. Keep metals and ions only when they are scientifically part of the receptor model. Dropping them can break real binding chemistry. Keeping irrelevant entries can pollute the docking model.
- Convert the receptor. Read the receptor report before downloading. Pay attention to atom count, charge mapping, unknown types, retained hetero atoms, dropped records, and warnings.
- Download receptor PDBQT only if warnings are understood. If atom type X appears and the page is set to block export, fix the upstream structure or use a validated external preparation route.
- Load the ligand MOL2. Confirm that it is the same ligand reviewed in Ligand Prep, not a stale or differently protonated copy.
- Load the restrictions JSON if you created one. Check that the restrictions correspond to this exact ligand file. A mismatch can create a misleading torsion tree.
- Choose ligand typing mode and convert the ligand. Review atom typing, charge information, root selection, branches, rotatable bonds, locked torsions, and diagnostics.
- Download ligand PDBQT and ligand report JSON only after reviewing unknown types and torsion-tree diagnostics.
- Use preview and diagnostics panels to spot obvious problems. Check that receptor and ligand summaries are plausible before moving to Vina Setup.
- Save session JSON if you want to reload the conversion state later. Keep all report JSON files with the docking project.
How to interpret what you see
- Atom type X
- A fallback unknown type. Treat it as a warning that downstream scoring may be unreliable.
- Strict typing
- Prefer this when you want failures to be visible rather than silently approximated.
- Lenient typing
- Best-effort mapping. Useful for exploration, weaker for scientific confidence.
- Receptor report
- Shows what was converted, skipped, typed, or warned about.
- Ligand torsion tree diagnostics
- Shows whether the ligand mobility model is plausible and whether restrictions were applied.
- PDBQT output
- Docking input, not a chemically validated final model.
Quality-control checklist before moving on
- Receptor PDB and PQR are from the same cleaned receptor.
- Unknown receptor atom types are absent or justified.
- Required metals or cofactors were handled intentionally.
- Ligand MOL2 matches Ligand Prep output.
- Restrictions JSON matches the ligand.
- Receptor and ligand report JSON files were saved.
- PDBQT files open in Vina Setup.
Troubleshooting
| Problem | What to check |
|---|---|
| Receptor conversion reports mismatched atoms. | Regenerate PQR from the exact cleaned PDB and avoid editing either file between steps. |
| Unknown receptor atom types appear. | Check non-standard residues, metals, cofactors, names, and whether an external preparation package is needed. |
| Ligand torsion tree looks wrong. | Return to Ligand Prep and check bonds, fragments, ring perception, and restrictions. |
| Docking setup cannot load PDBQT. | Open the PDBQT in a text editor and check for empty output, malformed records, or a blocked export warning. |
| 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. Approximate format conversion, atom typing, charge transfer, and torsion handling must be validated with established docking-preparation software before use in decisions or publications.