Use case

Structure-based virtual screening

Prepare a target structure, review a compound library, generate ranked poses with GNINA, and inspect pose-quality and ADMET results in one editable workflow.

Structure-based virtual screeningRead-only preview

Inputs

2 required

Methods

8 connected

  1. 01PDBFixer
  2. 02fpocket
  3. 03Lipinski's rule of 5
  4. 04Lead-likeness filter
  5. 05GNINA Docking
  6. 06ADMET-AI
  7. 07PoseBusters
  8. 08ProLIF

The template prepares the target with PDBFixer, reports pocket context with fpocket, reviews the compound library with Lipinski and lead-likeness methods, docks with GNINA, checks geometry with PoseBusters, calculates interactions with ProLIF, and runs ADMET-AI as a separate branch.

Use this template

What is structure-based virtual screening?

Structure-based virtual screening (SBVS) is a computational method for evaluating a compound library against the three-dimensional structure of a biological target, usually a protein. Docking algorithms sample candidate poses in a defined search region, and scoring functions rank those poses for review. The output is a target-specific shortlist and binding hypotheses, not measured affinity or confirmed activity.

SBVS differs from ligand-based screening because it can begin without known active ligands, but it requires a defensible receptor conformation and binding-site model. Target preparation, protonation, retained waters or cofactors, search-box placement, ligand states, sampling effort, and score interpretation can all change which compounds rise to the top.

Most campaigns use rigid-receptor docking for throughput, ensemble docking to represent several receptor states, or a staged design that rescales a focused subset with complementary methods. Docking scores are most defensible within one consistent setup. Pose plausibility, interactions, controls, diversity, and experimental follow-up remain separate evidence.

When to use structure-based virtual screening

  • A suitable target structure is available. Start from an experimental structure or a model that has been reviewed for the binding site and conformational state relevant to the screen.
  • You need target-specific poses. Use docking when candidate binding geometry and target interactions matter, not only molecular similarity to known ligands.
  • You want an inspectable shortlist. Keep preparation settings, ranked poses, score tables, pose checks, predictive endpoints, and files together for review and handoff.

Benefits of structure-based virtual screening

  • Reduces the experimental screening burden. A computational ranking can narrow a large library to a smaller set for closer review and physical testing.
  • Adds target-specific structural evidence. Predicted poses provide a three-dimensional hypothesis for how a compound may fit within a binding site and interact with nearby residues.
  • Applies one reproducible setup across a library. Using consistent preparation, docking, and scoring settings makes it easier to compare candidates within the same screening run.
  • Supports hit review and follow-up design. Ranked poses can be inspected alongside compound properties, pose checks, and predictive endpoints before selecting compounds for assays.

Primary limitations

  • Results depend on target-structure quality. Missing atoms, incorrect protonation, an unsuitable conformational state, or an inaccurate predicted structure can distort the binding site and the resulting poses.
  • Binding-site selection may be uncertain. Automatically detected pockets are hypotheses. A poorly supported docking region can produce plausible-looking rankings that are not relevant to the biological mechanism.
  • Scoring functions are approximations. Docking scores simplify solvation, entropy, receptor flexibility, and other physical effects. They can produce false positives and false negatives and should not be read as measured affinity.
  • Protein flexibility is only partly represented. A single receptor structure captures one conformational state, while real targets may adopt multiple states or reorganize when a ligand binds.
  • Experimental validation remains necessary. A computational shortlist identifies candidates for follow-up. Binding, activity, selectivity, safety, and efficacy still require appropriate experiments.

Molecular docking and virtual screening

Molecular docking is the calculation at the center of many structure-based virtual screening protocols: it generates candidate protein–ligand poses and assigns method-specific scores. Docking-based virtual screening repeats that calculation across a compound library under a consistent receptor, search-space, sampling, and scoring setup.

The terms are related but not interchangeable. One docking run may examine a single ligand, while a docking virtual screening campaign also includes target and library preparation, failure handling, ranking, pose review, shortlist selection, and validation. Tools such as GNINA, AutoDock Vina, and SMINA support the docking stage; their scores should remain in the context of the engine and setup that produced them.

Core structure-based screening approaches

The receptor model and sampling strategy should match the biological question. Adding complexity is useful only when validation shows that it improves recovery or pose quality.

  • Focused rigid-receptor docking. Screen one prepared receptor state in a supported pocket when throughput and a consistent search space matter most.
  • Ensemble docking. Run compounds against several justified receptor conformations and keep conformation-specific poses and scores visible.
  • Consensus review. Compare complementary docking or rescoring methods without averaging unrelated raw scores unless the combination rule has been validated.

Structure-based virtual screening applications

SBVS is useful when the target structure contributes information that a ligand-only comparison cannot provide. Common applications include focused hit discovery in a known pocket, analog prioritization, allosteric-site exploration, and selecting compounds for experimental counter-screens.

The method is weakest when the relevant receptor state or pocket is unknown, the site depends strongly on induced fit, or structures omit essential partners such as cofactors, membranes, metals, or ordered waters. In those cases, the campaign should narrow its claim or compare several explicitly justified setups.

How to do structure-based virtual screening online

Pilot the complete protocol on a small validation set before committing the full library. This exposes preparation and pocket errors while they are still cheap to correct.

  1. Select the receptor state. Choose an experimental structure or reviewed model whose chains, ligands, cofactors, and conformation match the intended binding question.
  2. Define and prepare the pocket. Repair the receptor, document protonation and retained components, and justify the docking region from structural or biochemical evidence.
  3. Standardize the ligand library. Preserve identifiers while resolving salts, stereochemistry, protonation, tautomers, duplicates, and invalid structures.
  4. Validate docking settings. Test search-space placement, sampling effort, and scoring on known ligands, decoys, or pose-recovery examples when suitable evidence exists.
  5. Run and inspect the screen. Dock under one reproducible setup, retain failed compounds, and review native scores together with poses, interactions, and geometry checks.
  6. Select a diverse shortlist. Balance rank, pose plausibility, chemical diversity, liabilities, and assay feasibility before orthogonal calculations and experiments.

How structure-based virtual screening works

SBVS usually combines target preparation, compound-library review, molecular docking, scoring, pose-quality checks, and shortlist selection. Each stage affects the reliability of the final ranking, so its settings and outputs should remain available for review.

  1. Provide target evidence. Submit a compatible protein sequence for SPRINT and a reviewed PDB structure for the structure-based branch.
  2. Run target-aware ranking. Rank the submitted SMILES library with SPRINT and retain its native cosine similarity alongside compound identifiers.
  3. Prepare and dock. Repair the receptor with PDBFixer and dock the library independently with GNINA.
  4. Review independent evidence. Check GNINA geometry with PoseBusters, calculate residue-level interactions with ProLIF, and review descriptors and ADMET predictions.
  5. Compare and shortlist. Compare the branches without treating their raw scores as interchangeable, then export a diverse shortlist for orthogonal review.

Inputs and outputs

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

Inputs

  • Target structure. PDB The main template accepts a PDB receptor. If the source structure is CIF, convert it to PDB before starting the run.
  • Compound library. SMILES Submit a SMILES library directly. Convert existing SDF with SDF to SMILES or MOL2 with MOL2 to SMILES before launching; use the ligand-preparation variant to generate or repair structure files from SMILES.
  • Binding-site context. Known pocket coordinates or a reference ligand can inform manual docking setup and review, but they are not required inputs on this template.

Outputs

  • Prepared target and pocket results. PDB JSON Download the fixed receptor and preparation provenance, plus fpocket pocket files and metrics.
  • Property and rule tables. CSV JSON SMILES Inspect per-compound Lipinski and lead-likeness results with the values and warnings returned by each step.
  • Docking poses and scores. SDF CSV JSON Review ranked docking poses with GNINA CNN score, CNN affinity (pKd), and Vina score (kcal/mol).
  • Pose and ADMET review. CSV JSON Inspect downloadable PoseBusters validation tables and ADMET-AI prediction tables as separate evidence layers.
  • Run record. LOG FILES Retain settings, node-level results, logs, and downloadable files for review or handoff.

Tools for structure-based virtual screening

Use these methods to prepare inputs, run the core analysis, inspect outputs, and validate the evidence described in this workflow.

Frequently asked questions

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.

Run this workflow