Peptide–protein docking

What is peptide–protein docking?

Peptide–protein docking is a computational method for placing a peptide against a protein receptor and generating candidate bound conformations. It searches both the peptide's orientation on the receptor and, to varying degrees, its flexible backbone and side chains.

A peptide can adopt many shapes before binding. Its bound structure may differ markedly from an isolated starting model, so one arbitrary peptide conformation can restrict the search. Known motifs or receptor-site evidence can guide docking, while unknown sites require broader surface exploration.

The output is a proposed complex with residue contacts and a method-specific rank. It is not a measurement of affinity or cellular activity. Terminal charges, phosphorylation, cyclization and noncanonical residues can change the interface, and a tool may not represent every modification correctly.

When to use peptide–protein docking

Docking is useful when a peptide interaction needs a structural hypothesis:

• A short motif has a proposed receptor site.
• Mutations identify residues that may contact a peptide.
• You want to compare alternative peptide orientations.
• A bound complex is needed to choose follow-up structural tests.

Strengths and limitations

Peptide docking can connect sequence-level evidence to specific receptor contacts. Restraints help concentrate sampling around a known motif or site, while a broad search can reveal alternative surface placements.

Backbone flexibility makes the search substantially harder than rigid protein docking. An idealized starting peptide may be far from the bound conformation, and approximate scores can favor a plausible-looking but wrong interface. Compare multiple starting conformations when the peptide shape is uncertain.

How peptide–protein docking works

The featured ProteinIQ workflow runs LightDock on the receptor and peptide PDB inputs.

Tool	Search	Useful evidence
LightDock	Swarms distributed around the receptor, optionally restrained	Broad search when the binding region is uncertain; known motif or site residues can guide the interface

Starting peptide conformations

PeptideBuilder can construct an extended or idealized helical peptide PDB from a sequence. It builds coordinates; it does not predict the peptide's free or bound fold. Choose a starting shape supported by evidence when possible, or run several plausible conformations separately.

LightDock treats supplied interface residues as restraints and otherwise searches the whole receptor surface. It can add limited normal-mode flexibility, but a highly disordered peptide remains a difficult target.

Applications of peptide–protein docking

Docking can propose how a signaling motif, regulatory tail or peptide binder contacts its receptor. A contact map can guide alanine substitutions or competition assays, especially when independent data already identify the binding region.

The method can also compare a native motif with a designed variant. Preserve the chemistry and terminal state for each sequence, and avoid attributing a score difference to affinity without experimental calibration. A changed pose may reflect starting conformation or sampling rather than a genuine mechanism.

How to do peptide–protein docking online

1. Prepare the receptor. Choose a biologically relevant structure and inspect missing residues near the proposed interface.
2. Build peptide inputs. Supply a peptide PDB with the intended sequence and termini; make separate starting models if its backbone state is unknown.
3. Add site evidence. Record motif and receptor residues supported by experiment, then use them as LightDock restraints only when justified.
4. Run the docking workflow. Connect the receptor and peptide structures to LightDock.
5. Review alternative complexes. Group poses by receptor site and peptide direction, then inspect contacts and steric clashes.
6. Check structural quality. Use MolProbity for geometry and compare with a native complex using DockQ only when one exists.

How to interpret peptide–protein docking results

A LightDock rank is meaningful within that program's settings, not as an affinity scale. A peptide may score well because it makes many contacts while adopting an unrealistic backbone. Inspect its conformation and receptor accessibility before using rank.

If different starting conformations yield incompatible answers, report that sensitivity. Peptide docking supports prioritization of contact and orientation hypotheses; it does not confirm binding, activity, safety or function.

How the peptide–protein docking workflow works

Dock the peptide against the receptor with LightDock, then inspect the resulting complexes.

1. Prepare the receptor. Upload the biologically relevant PDB structure, select the correct chain and state, and inspect the proposed binding region for missing residues or cofactors.
2. Build peptide conformers. Create one or more starting peptide structures with the correct sequence, stereochemistry, terminal state, cyclization, and modifications.
3. Add binding-site evidence. Record motif positions, receptor residues, cross-links, or competition data. Use uncertain evidence as a comparison condition rather than a hard fact.
4. Dock and refine. Run a global swarm-based search from the receptor and peptide inputs, retaining all clusters and method-native scores. Add residue restraints only when the site evidence is credible.
5. Cluster and inspect. Review peptide backbone geometry, recurring contacts, restraint satisfaction, clashes, and dependence on the starting conformer before export.

Inputs and outputs

Check formats before running, then inspect and download the result from every workflow step.

Inputs

Structural inputs

PDBSDFSMILES

A receptor PDB and one or more peptide PDB conformations, optionally with binding-site restraints.

Method context

Binding-site evidence, restraints, receptor-state provenance, known ligands, or reference complexes when available.

Outputs

Docked structures

PDBPDBQTSDF

Ranked protein–peptide complexes, clusters, residue contacts, and method-native scores.

Review evidence

Method-native rankings, confidence, logs, interaction context, failures, and files for reproducible follow-up.