Receptor PDB Clean

Receptor cleanup documentation

Clean receptor PDB files, select chains and non-protein records, export reference ligands, and prepare receptor input before protonation and charge assignment.

Step-by-step documentationLocal browser fileVersion 0.14.4-alpha

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.

Weiss AKH. Receptor PDB Clean. akhw.at local browser tools, version 0.14.4-alpha, build 2026-06-12-tools5. PHP documentation: docs/receptor-clean.php.

What this page is supposed to do

This page is the receptor cleanup step. It helps users decide which model, chains, waters, ions, cofactors, ligands, hydrogens, and alternate locations should be retained before external protonation and PQR generation.

Use this page when

  • You have a receptor PDB file and need a cleaner receptor for docking preparation.
  • You need to remove waters, select chains, keep relevant metals or cofactors, or export a reference ligand.
  • You want a cleanup report before sending the receptor to a PQR workflow.

Do not use it as

  • Do not remove biologically essential cofactors, metals, ligands, or chains without checking the system.
  • Do not assume automatic cleanup knows what matters for the binding site.
  • Do not use a cleaned PDB for docking until protonation, charges, and PDBQT conversion have been handled.

At a glance

QuestionAnswer
Primary jobPrepare a structurally sensible receptor PDB for the next step.
Main riskRemoving a required biological component or keeping an artefact.
Best next stepSend the clean receptor PDB to Receptor PQR Handoff or an equivalent protonation workflow.
Reproducibility fileCleanup report JSON and session JSON.

Typical inputs

  • Receptor PDB file.
  • Optional PDB code fetch if the page supports fetching.
  • Optional saved session JSON.
  • Manual keep or remove overrides for residues and objects.

Typical outputs

  • Clean receptor PDB.
  • Reference ligand PDB when selected.
  • Cleanup report JSON.
  • Session JSON with cleanup choices.

Where it fits in the docking workflow

  1. 0
    Ligand Draw

    Create or import a ligand starting structure.

  2. 1
    Ligand Prep

    Inspect ligand chemistry, metadata, and torsion restrictions.

  3. 2
    Receptor PDB Clean

    Clean a receptor PDB and decide what to keep.

  4. 3
    Receptor PQR Handoff

    Assign receptor protonation and charges with an external PQR workflow.

  5. 4
    PDBQT Converter

    Convert cleaned receptor and prepared ligand material to docking-ready PDBQT.

  6. 5
    Vina Setup

    Define the docking box and export a Vina-style configuration.

  7. 6
    Vina Run

    Run or emulate docking and inspect poses, scores, and warnings.

Step-by-step use

  1. Load the receptor PDB. Use the fetch field only when the target code is correct and you are comfortable with the fetched structure version. Otherwise upload the exact project file.
  2. Check the inventory. Look at model count, chains, non-protein residues, waters, ions, ligands, alternate locations, hydrogens, and zero-occupancy atoms.
  3. Select protein chains deliberately. Keep chains that define the binding site, biological interface, or required structural context. Remove chains only if they are not part of the intended receptor model.
  4. Choose cleanup rules. Removing waters and hydrogens is common before a later protonation workflow, but exceptions exist. Do not remove structural waters, metals, or cofactors if they are required for ligand recognition.
  5. Handle alternate locations. Highest occupancy or prefer altloc A are convenience rules. Inspect important active-site residues manually when alternate conformations occur near the binding site.
  6. Decide what to do with non-protein residues. Use keep metals and keep common cofactors only after verifying that those records are chemically meaningful for the target system.
  7. Use planned removals preview. Review what will disappear before exporting. This is the last easy point to catch accidental removal of ligands, ions, cofactors, or chains.
  8. Use manual object selection for special cases. Force keep or force remove individual objects when the automatic rule is not appropriate. Record why in notes or in the project log.
  9. Refresh the structure preview. Compare kept and removed atoms if the page provides a faded removed-atom view.
  10. Export the clean receptor PDB. Also export the cleanup report JSON and session JSON so another user can understand what changed.
  11. Export a reference ligand PDB if the original structure contains a bound ligand that should guide grid placement later.
  12. Continue to PQR handoff or another validated protonation and charge assignment route.

How to interpret what you see

Protein chain selection
Defines the receptor context used downstream.
Waters
May be crystallographic artefacts or mechanistically important. Decide based on the project, not only on defaults.
Metals and ions
Can be essential for binding or catalysis. Bad handling can invalidate docking.
Reference ligand
Useful for placing the docking box, not necessarily the ligand used for docking.
Cleanup report
A reproducibility record of automatic and manual changes.

Quality-control checklist before moving on

Troubleshooting

ProblemWhat to check
Fetched structure is not the intended one.Upload the exact local PDB file instead of relying on fetch.
A required metal disappears.Enable keeping metals or manually force keep that object, then refresh the preview and export again.
Too many non-protein residues remain.Use the non-protein inventory and manual selection rather than removing all objects blindly.
Exported PDB later fails in PQR tools.Check malformed records, alternate locations, chain identifiers, missing atoms, or non-standard residues.
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

Copyright and disclaimer

Copyright © 2026 Alexander Weiss, akhw.at. All rights reserved.

Research workflow helper only. Receptor preparation, biological assembly choice, residue completion, protonation, charge assignment, and docking readiness must be validated with established scientific software before use in decisions or publications.