Use case
Flexible molecular docking
Model ligand binding poses while accounting for selected side-chain flexibility or learned receptor movement.
Inputs
2 required
Methods
2 connected
- 01DynamicBind
- 02FlowDock
Compare DynamicBind protein-dynamic predictions with FlowDock complex predictions from identical inputs.
Use this templateWhat is flexible molecular docking?
Flexible molecular docking is a docking method that allows selected receptor side chains, backbones, or learned protein conformational changes to respond to a ligand during pose prediction. Different methods model different degrees of flexibility.
Flexible molecular docking models receptor motion in addition to ligand translation, rotation, and torsions. A method may rotate selected pocket side chains, dock against fixed receptor conformations, or predict coupled backbone and side-chain changes around the ligand. These treatments encode different physical assumptions and should be named precisely.
Use flexible docking when a rigid receptor closes the pocket, creates unavoidable clashes, or fails to recover known binding modes. Every added degree of freedom expands the search and can reward geometrically possible but inaccessible receptor states. The aim is a constrained set of biologically supported motions, not unrestricted protein movement.
When to use flexible molecular docking
- Suitable flexible molecular docking question. Binding sites with induced fit, alternative side-chain states, or known conformational plasticity
- Required structures and evidence are available. A prepared receptor and ligand plus a justified decision about which degrees of freedom to model
Benefits of flexible molecular docking
- Practical output. Represents more receptor uncertainty
- Comparative evidence. Can recover ligand-specific conformations
- Connected analysis. Makes induced-fit hypotheses explicit
Primary limitations
- Method dependence. More flexibility increases uncertainty
- Input sensitivity. Methods represent motion differently
- Validation boundary. Predicted rearrangements need physical validation
How flexible molecular docking works
Flexible docking methods differ in the scale and timing of the receptor movement they permit.
- Flexible-side-chain docking. A selected set of pocket residues can change rotamers during docking while the backbone remains fixed. This is efficient when specific side chains are known to rearrange.
- Ensemble or conformer docking. The ligand is docked independently into several fixed receptor states. This represents discrete flexibility and keeps the provenance of each receptor conformation explicit.
- Coupled or learned flexibility. DynamicBind and related methods predict ligand placement together with protein conformational adjustment. The resulting protein movement requires the same scrutiny as the ligand pose.
Applications of flexible molecular docking
Use flexible docking when there is evidence that a single rigid receptor is an inadequate model of the binding event.
- Induced-fit pockets. Model side-chain or local backbone rearrangements associated with ligands that differ from the receptor’s crystallized state.
- Cryptic and transient sites. Explore pockets that open only in particular conformations, provided those states come from structural or simulation evidence.
- Cross-docking. Reduce the bias introduced when one ligand is docked into a receptor conformation solved with a chemically different ligand.
How to do flexible molecular docking online
ProteinIQ’s flexible workflow compares learned coupled-motion methods while keeping receptor preparation and ligand chemistry consistent.
- Identify the motion that matters. Compare available structures, known ligands, missing density, or simulation states to decide whether side chains, loops, domains, or the whole pocket require alternative treatment.
- Prepare a defensible receptor state. Repair the structure and preserve cofactors or structural waters that define the pocket. Do not use flexibility to compensate for incorrect protonation or missing chemistry.
- Prepare each ligand state. Standardize stereochemistry, protonation, tautomers, and charges. Ligand flexibility cannot correct a chemically invalid input.
- Run DynamicBind and FlowDock. Generate coupled protein–ligand predictions from the same inputs and retain model-specific confidence, coordinates, and logs.
- Inspect the predicted receptor movement. Compare the output protein with the starting structure, check clashes and strained geometry, and ask whether the motion is supported by known structures, simulations, or experiments.
How to interpret flexible molecular docking results
Evaluate the ligand pose and receptor rearrangement separately. A plausible ligand orientation paired with an unrealistic loop movement is not a reliable complex, and a large structural change should not be accepted simply because it improves a model score.
Compare predicted states with experimental ensembles or carefully sampled simulations. Short minimization can reveal severe local strain, but it does not demonstrate that a conformation is thermodynamically populated or kinetically accessible.
How the flexible molecular docking workflow works
Compare DynamicBind protein-dynamic predictions with FlowDock complex predictions from identical inputs.
- Identify flexible regions. Compare available structures, known ligands, missing density, or simulation states to decide whether side chains, loops, domains, or the whole pocket require alternative treatment.
- Prepare receptor states. Repair the structure and preserve cofactors or structural waters that define the pocket. Do not use flexibility to compensate for incorrect protonation or missing chemistry.
- Prepare the ligand. Standardize stereochemistry, protonation, tautomers, and charges. Ligand flexibility cannot correct a chemically invalid input.
- Model coupled motion. Generate coupled protein–ligand predictions from the same inputs and retain model-specific confidence, coordinates, and logs.
- Inspect structural changes. Compare the output protein with the starting structure, check clashes and strained geometry, and ask whether the motion is supported by known structures, simulations, or experiments.
Inputs and outputs
Check formats before running, then inspect and download the result from every workflow step.
Inputs
- Structural inputs.
PDBSDFSMILESA protein PDB and ligand structure, ideally supported by alternate conformations or known flexible residues. - Method context. Binding-site evidence, restraints, receptor-state provenance, known ligands, or reference complexes when available.
Outputs
- Docked structures.
PDBPDBQTSDFPredicted complexes, changed protein coordinates, pose confidence, and downloadable structures. - Review evidence. Method-native rankings, confidence, logs, interaction context, failures, and files for reproducible follow-up.
Tools for flexible molecular docking
Use these methods to prepare inputs, run the core analysis, inspect outputs, and validate the evidence described in this workflow.

DynamicBind
Predict ligand-specific protein conformational change

FlowDock
Generate flexible flow-based complexes

AutoDock Vina
Model selected flexible side chains

DiffDock-L
Provide a complementary pose hypothesis

AlphaFlow
Generate alternative protein conformations

MDGen
Explore structural dynamics

OpenMM
Relax selected complexes

GROMACS
Run longer molecular-dynamics checks

PDBFixer
Repair receptor structures

PDB2PQR
Prepare protonation context

PoseBusters
Check pose plausibility

ProLIF
Track interaction changes
Other molecular docking workflows
Compare related approaches based on the molecular system, available evidence, required inputs, and decision you need to support.
Protein–ligand docking
Predict small-molecule binding poses in a protein target and inspect scoring and interaction evidence.
Protein–protein docking
Predict how two protein partners assemble into a biomolecular complex.
Antibody–antigen docking
Explore antibody recognition orientations with antibody-aware interface evidence.
Peptide–protein docking
Model a flexible peptide partner against a protein receptor.
Blind docking
Search a protein broadly when the relevant binding site is unknown.
Ensemble docking
Dock against multiple receptor conformations instead of one static structure.
Consensus docking
Compare poses and rankings from multiple docking methods.
AI molecular docking
Use learned diffusion or flow models to predict protein–ligand complexes.
Frequently asked questions
Use the smallest flexibility model supported by structural or biochemical evidence. Selected side chains are appropriate for local rotamer changes, an ensemble is appropriate for known discrete states, and coupled-motion models are useful when induced fit is central. Unconstrained motion increases both search cost and opportunities for unrealistic structures.
Binding sites with induced fit, alternative side-chain states, or known conformational plasticity
A protein PDB and ligand structure, ideally supported by alternate conformations or known flexible residues.
Accuracy depends on target class, input preparation, conformational coverage, method domain, and the evaluation criterion. Benchmark against relevant known complexes and report pose accuracy separately from ranking or affinity claims.
Public computational support may start near $55–$169 per labor hour, while longer simulations add compute cost. These public rates are service examples rather than universal prices; scope, preparation, number of systems, methods, compute, interpretation, and experimental work change the total.
ProteinIQ Plus is $29 per month and Pro is $99 per month. Compute-heavy runs also consume credits according to the selected tool and workload; a separately scoped done-for-you engagement is available when experimental design, data preparation, interpretation, or reporting needs expert support.
Flexible docking predicts possible coupled conformational changes; it does not prove that a state is populated or kinetically accessible. Compare with structural ensembles, simulations, and experimental evidence.
Start with a workflow you can inspect and edit
Add your inputs, review the settings, and keep every structure, score, table, and file connected to the step that produced it.