# AutoDock Vina vs smina vs GNINA vs DiffDock: which docking engine to use

> AutoDock Vina, smina and GNINA are three generations of one search-and-score program. DiffDock is a different kind of method. Learn how they relate, what each needs from you, where the published benchmarks put them, how AutoDock differs from AutoDock Vina, and which engine to start with, with a first run walked through.

## Which docking engine should you use?

Use AutoDock Vina when you know where the ligand binds and want a fast, standard answer. Use GNINA when the same job needs better pose ranking, and DiffDock when you do not know the pocket. smina is Vina for people who want to change the scoring function; it is rarely the right first run.

The deciding fact is what you already know about the site (Figure 1). Vina, smina and GNINA are one family: GNINA is a fork of smina, and smina is a fork of Vina. All three move a ligand around inside a search box you define and score each pose with a Vina-style function. GNINA adds neural networks to the scoring.

![Flowchart: if you do not know where the ligand binds, use DiffDock; if you do, choose smina when you need custom scoring terms or per-atom energies, otherwise start with AutoDock Vina and add GNINA when the top poses disagree](/images/guides/vina-vs-smina-vs-gnina-vs-diffdock/decision.webp "**Figure 1. Which engine to start with.** Credits are typical ProteinIQ prices for one drug-sized ligand at default settings.")

DiffDock is a different kind of method. It needs no box, starts from random placements across the whole protein and [generates poses by diffusion](/use-cases/ai-molecular-docking), then ranks them with a learned confidence. That makes it the better tool when the pocket is the unknown, and the weaker one when the pocket is known and the pose must be physically clean.

  <caption><strong>Table 1. The four engines side by side.</strong> Licenses from each project's repository or page; ProteinIQ credits from the tool pages, for a typical single drug-sized ligand at default settings.</caption>
  <thead>
    <tr>
      <th scope="col">Engine</th>
      <th scope="col">How it finds poses</th>
      <th scope="col">How it ranks them</th>
      <th scope="col">Needs a search box</th>
      <th scope="col">License</th>
      <th scope="col">Typical ProteinIQ run</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>[AutoDock Vina](/app/autodock-vina)</td>
      <td>Stochastic search with local optimization</td>
      <td>Vina empirical score (Vinardo and AutoDock4 optional)</td>
      <td>Yes</td>
      <td>Apache 2.0</td>
      <td>20 credits</td>
    </tr>
    <tr>
      <td>[smina](/app/smina)</td>
      <td>Vina's search</td>
      <td>Vina, Vinardo, dkoes or your own terms</td>
      <td>Yes</td>
      <td>GPL 2.0</td>
      <td>20 credits</td>
    </tr>
    <tr>
      <td>[GNINA](/app/gnina)</td>
      <td>Vina's search</td>
      <td>Empirical score plus CNN pose score and affinity</td>
      <td>Yes, or whole protein</td>
      <td>Apache 2.0 and GPL 2.0</td>
      <td>20 credits</td>
    </tr>
    <tr>
      <td>[DiffDock](/app/diff-dock)</td>
      <td>Reverse diffusion from random poses</td>
      <td>Learned confidence model</td>
      <td>No</td>
      <td>MIT</td>
      <td>50 credits</td>
    </tr>
  </tbody>

## Docking terms you need first

Docking software shares a small vocabulary, and the engines below use it in the same way. Table 2 defines the six terms that matter most for choosing between them.

  <caption><strong>Table 2. Six docking terms.</strong></caption>
  <thead>
    <tr>
      <th scope="col">Term</th>
      <th scope="col">What it means</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>Pocket</td>
      <td>The cavity on the protein where the ligand sits, usually the active site</td>
    </tr>
    <tr>
      <td>Pose</td>
      <td>One predicted position, orientation and shape of the ligand in the pocket</td>
    </tr>
    <tr>
      <td>Search box</td>
      <td>The cube you draw around the pocket; Vina, smina and GNINA only look inside it</td>
    </tr>
    <tr>
      <td>Blind docking</td>
      <td>Docking with no box, so the method has to find the pocket as well as the pose</td>
    </tr>
    <tr>
      <td>[RMSD](/guides/rmsd)</td>
      <td>The average distance in ångströms between a predicted pose and the crystal pose; under 2 Å counts as a success</td>
    </tr>
    <tr>
      <td>Exhaustiveness</td>
      <td>How long the search runs; higher is slower and finds the best pose more reliably</td>
    </tr>
  </tbody>

What each engine asks you to bring differs mainly in the pocket (Table 3). Every engine takes a protein structure and a ligand; the question is whether you have to say where to look.

  <caption><strong>Table 3. What each engine needs from you on ProteinIQ.</strong></caption>
  <thead>
    <tr>
      <th scope="col">Engine</th>
      <th scope="col">Protein</th>
      <th scope="col">Ligand</th>
      <th scope="col">Pocket</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>AutoDock Vina</td>
      <td>PDB ID or file</td>
      <td>SMILES, PubChem compound or file</td>
      <td>Box from a bound ligand, chosen residues, coordinates or the whole protein</td>
    </tr>
    <tr>
      <td>smina</td>
      <td>PDB ID or file</td>
      <td>SMILES, PubChem compound or file</td>
      <td>Reference ligand, manual box of 10 to 50 Å per axis, or the whole receptor</td>
    </tr>
    <tr>
      <td>GNINA</td>
      <td>PDB ID or file</td>
      <td>SMILES, PubChem compound or file</td>
      <td>Reference ligand, or the whole protein</td>
    </tr>
    <tr>
      <td>DiffDock</td>
      <td>Structure, PDB ID or sequence (folded with ESMFold first)</td>
      <td>SMILES or file</td>
      <td>None</td>
    </tr>
  </tbody>

## AutoDock Vina: the baseline

![AutoDock Vina on ProteinIQ with imatinib docked into the c-Abl kinase domain from PDB 1IEP, with the form on the left and five ranked poses on the right, the best at -12.512 kcal/mol](/images/guides/vina-vs-smina-vs-gnina-vs-diffdock/autodock-vina.webp "**Figure 2. Imatinib docked into c-Abl kinase with AutoDock Vina.** The receptor came from the RCSB by PDB ID and the ligand from PubChem. The quote of 22 credits reflects imatinib's 37 heavy atoms.")

[AutoDock Vina](/app/autodock-vina) comes from Oleg Trott and Arthur Olson at Scripps Research, and it is still the program most published docking studies use. A run needs a receptor, a ligand and a box around the pocket. Version 1.2 added simultaneous docking of several ligands, hydrated docking, zinc metalloprotein parameters, the AutoDock4 scoring option and Python bindings.

Its strength is that it is fast, free and expected by reviewers. Its poses hold up better than its scores. On the Astex Diverse set in the PoseBusters study, Vina given a box around the crystal ligand placed 58% of ligands within 2 Å, and 56% were also physically valid. The kcal/mol number is a [Vina score](/guides/vina-score): useful for comparing poses of one ligand, not something you can convert to a Kd.

Preparing the inputs is the usual stumbling block when you run it locally: both molecules must be converted to PDBQT files and the box coordinates chosen by hand. The hosted tool does both for you, and the [AutoDock Vina tutorial](/guides/autodock-vina-tutorial) walks through the local route step by step. In the public [imatinib and c-Abl example](/app/autodock-vina?jobId=cge7gsamwpeuxmhkandolpdw), the top pose scores −12.512 kcal/mol.

## smina: Vina with the scoring function exposed

![SMINA on ProteinIQ with the c-Abl and imatinib example loaded, showing the scoring function, docking mode, pose output format, exhaustiveness and per-atom interaction energy controls before the job is run](/images/guides/vina-vs-smina-vs-gnina-vs-diffdock/smina.webp "**Figure 3. The SMINA form with the c-Abl and imatinib example loaded.** The controls specific to smina are the docking mode (full docking, minimize only, local search only or score only) and per-atom interaction energies, next to the choice of scoring function.")

David Koes's group at the University of Pittsburgh built smina as a fork of Vina for scoring function development and fast energy minimization. It keeps Vina's search and adds a choice of built-in scoring functions, user-defined scoring files and per-atom term output. In the CSAR 2011 exercise, Koes and colleagues used it to fit a custom function that sampled low-RMSD poses better than Vina's default when cross-docking.

Vina 1.2 has absorbed much of what once set smina apart. It now offers Vinardo, a Vina-based function with different terms and weights, alongside AutoDock4 scoring, and it can score or locally optimize a pose without a full search. What smina still adds is custom scoring: your own terms and weights, the dkoes functions and a table of how each atom contributes to the score.

That makes smina the right choice for a narrow set of jobs. Rescoring or minimizing poses from another program with a Vina-family function, testing a modified scoring function and extracting per-atom terms for analysis are all easier there. For a first docking run it adds nothing over Vina. It also adds little to a consensus: Vina, Vinardo and smina share one set of assumptions, so agreement between them is weak evidence.

## GNINA: the same search with a second opinion

![GNINA on ProteinIQ with JQ1 docked into the BRD4 bromodomain from PDB 3MXF, with a table of eight poses ranked by CNN affinity and a CNN affinity of 6.306 pK for the selected pose](/images/guides/vina-vs-smina-vs-gnina-vs-diffdock/gnina.webp "**Figure 4. JQ1 docked into the first BRD4 bromodomain with GNINA.** The CNN score estimates whether a pose is correct; the CNN affinity is a predicted pK. Poses here are ordered by CNN affinity.")

[GNINA](/app/gnina) (pronounced NEE-na) keeps the smina search and scores every pose twice, with the empirical function and with 3D convolutional neural networks (CNNs) trained on crystal structures. The networks give two outputs: a CNN score from 0 to 1 for how likely the pose is correct, and a CNN affinity in pK units. The [GNINA CNN score](/guides/gnina-cnn-score) guide covers how to read them.

The gain is in choosing the right pose. In the GNINA 1.0 redocking tests, the top-ranked pose was within 2 Å of the crystal pose 73% of the time, against 58% for Vina; in the harder cross-docking test the figures were 37% and 27%. The search itself is unchanged, so GNINA cannot rank a pose the search never produced.

The trade-off is flexibility on the hosted side. The command-line program is built with CUDA 12.0 or newer and also offers [covalent docking](/guides/covalent-docking) and flexible residues. The hosted version runs on a GPU and docks one ligand into one rigid receptor, without covalent or flexible-residue options and without manual box coordinates.

## DiffDock: no box required

![DiffDock-L on ProteinIQ with imatinib blind-docked into c-Abl kinase from PDB 1IEP, with the form on the left and ten poses ranked by confidence on the right, the best at -0.201](/images/guides/vina-vs-smina-vs-gnina-vs-diffdock/diffdock.webp "**Figure 5. Imatinib blind-docked into c-Abl kinase with DiffDock-L.** No search box was set. In this redocking test against the crystal structure, all ten poses landed within 1 Å of the crystal pose.")

DiffDock treats docking as generation. Gabriele Corso and colleagues at MIT start each sample from a random position, orientation and set of torsion angles, refine it by reverse diffusion, and rank the results with a separate confidence model. The protein stays rigid, and the ligand's 3D geometry is regenerated from its chemistry, so uploaded coordinates do not change the result.

The blind-docking benchmark is where it earns its place (Figure 6). On PDBBind, with every method asked to find the pocket as well as the pose, DiffDock placed the top-ranked pose within 2 Å for 35.0% of complexes with 10 samples and 38.2% with 40, against 22.9% for GNINA, 21.8% for Glide and 18.7% for SMINA. The authors report about 10 s per complex for DiffDock on a GPU, against roughly 127 s for GNINA on 16 CPU cores.

![Bar chart of the share of PDBBind complexes whose top-ranked pose is within 2 Å of the crystal pose in blind docking: SMINA 18.7%, Glide 21.8%, GNINA 22.9%, DiffDock with 10 samples 35%, DiffDock with 40 samples 38.2%](/images/charts/blind-docking-top-1-pdbbind.webp "**Figure 6. Blind docking on PDBBind.** Top-ranked pose within 2 Å RMSD of the crystal ligand, crystal protein structures, original DiffDock model. The search-based programs searched the whole protein. Source: Corso et al. (2023), Table 1.")

Predicted structures are where the gap widens. Starting from [ESMFold](/app/esmfold) models instead of crystal structures, DiffDock still reached 21.7% top-1 success in that table, while GNINA and SMINA fell to low single digits. The current DiffDock-L model, the one the hosted tool runs, raised PDBBind top-1 to 43.0% and accuracy on unseen protein domains from 7.1% to 22.6%.

The catch is geometry. In PoseBusters, the original DiffDock placed 72% of Astex Diverse ligands within 2 Å, but only 47% were both close and physically valid. In the example above, all ten poses are close to the crystal ligand, yet the confidence value of −0.201 is on a scale of its own and cannot be compared with Vina's kcal/mol.

## Why the winner depends on the benchmark

DiffDock leads the Vina family when the pocket is unknown, and Vina leads on physical validity when the pocket is given. Both results are correct, because the benchmarks ask different questions (Table 4).

  <caption><strong>Table 4. Published top-1 success within 2 Å, by what each program was given.</strong> The rows come from different test sets and cannot be ranked against one another. Sources: Corso et al. (2023), McNutt et al. (2021), Buttenschoen et al. (2024).</caption>
  <thead>
    <tr>
      <th scope="col">Benchmark</th>
      <th scope="col">What the program had to find</th>
      <th scope="col">Results</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>PDBBind, crystal protein</td>
      <td>Pocket and pose (blind)</td>
      <td>SMINA 18.7%, GNINA 22.9%, DiffDock 35.0%</td>
    </tr>
    <tr>
      <td>PDBBind, ESMFold protein</td>
      <td>Pocket and pose (blind)</td>
      <td>DiffDock 21.7%; GNINA and SMINA in the low single digits</td>
    </tr>
    <tr>
      <td>GNINA redocking</td>
      <td>Pose in a known pocket</td>
      <td>Vina 58%, GNINA 73%</td>
    </tr>
    <tr>
      <td>GNINA cross-docking</td>
      <td>Pose in a known pocket, receptor from another complex</td>
      <td>Vina 27%, GNINA 37%</td>
    </tr>
    <tr>
      <td>Astex Diverse, PoseBusters</td>
      <td>Pose in a known pocket (Vina); blind (DiffDock)</td>
      <td>Vina 58% (56% also valid); DiffDock 72% (47% also valid)</td>
    </tr>
  </tbody>

When the search methods must find the pocket themselves, a box that covers the whole protein dilutes their search and DiffDock wins. When the pocket is given, the picture shifts. On Astex Diverse, DiffDock's poses are close to the crystal more often (72% against 58%), but a smaller share of them are also physically valid (47% against 56%).

GNINA's rescoring lifts the search-based result to 73% in its own redocking test, though that is a different test set and not directly comparable. Choose the engine for the question you actually have, then check the pose.

## AutoDock vs AutoDock Vina

"AutoDock" is a family of programs from Scripps Research, and the bare name usually means AutoDock4, last released as 4.2.6 in 2014. AutoDock4 precomputes interaction grids with AutoGrid, searches with a Lamarckian genetic algorithm and scores poses with a force field of van der Waals, hydrogen bond, electrostatic and desolvation terms. It needs partial charges on both molecules and a grid map for every atom type.

AutoDock Vina is a separate program from 2010 with its own empirical scoring function and a Monte Carlo search with BFGS local optimization. With Vina scoring it needs no grid maps or partial charges. Trott and Olson reported that it found correct binding modes more often than AutoDock 4 while running about two orders of magnitude faster, which is why it replaced AutoDock4 as the default for most projects.

The two have since converged. Vina 1.2 can evaluate poses with the AutoDock4 force field through AutoGrid maps, though the search stays Vina's. To use AutoDock4's genetic algorithm at scale, [AutoDock-GPU](/app/autodock-gpu) is its GPU implementation, reported at up to 56 times the speed of single-threaded AutoDock4.

For a new project, start with Vina. Reach for AutoDock4 scoring or AutoDock-GPU when you need the force-field function, want to repeat a published AutoDock4 protocol, or are screening a very large library on a GPU. When a paper says it used "AutoDock", check which program and version before comparing its numbers with yours.

## Choosing an engine for your target

Table 5 turns Figure 1 into a lookup, with the follow-up step for each situation.

  <caption><strong>Table 5. Choosing a docking engine by situation.</strong></caption>
  <thead>
    <tr>
      <th scope="col">Situation</th>
      <th scope="col">Start with</th>
      <th scope="col">Then</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>Known pocket, one dependable answer</td>
      <td>[AutoDock Vina](/app/autodock-vina)</td>
      <td>Rescore with GNINA and check the pose</td>
    </tr>
    <tr>
      <td>Known pocket, top pose keeps landing wrong</td>
      <td>[GNINA](/app/gnina)</td>
      <td>Compare the CNN scores of the top few poses</td>
    </tr>
    <tr>
      <td>Unknown pocket</td>
      <td>[DiffDock](/app/diff-dock)</td>
      <td>Redock in the proposed pocket with Vina or GNINA</td>
    </tr>
    <tr>
      <td>Predicted or unbound protein</td>
      <td>DiffDock</td>
      <td>Compare with [DynamicBind](/app/dynamic-bind) if the pocket may need to move</td>
    </tr>
    <tr>
      <td>Custom scoring terms or per-atom contributions</td>
      <td>[smina](/app/smina)</td>
      <td>Validate the function against known binders</td>
    </tr>
    <tr>
      <td>Thousands of ligands</td>
      <td>Vina through the [API](/docs/api), or [AutoDock-GPU](/app/autodock-gpu)</td>
      <td>CNN-rescore only the top fraction with GNINA</td>
    </tr>
  </tbody>

The engines combine better than they compete. A typical sequence lets DiffDock propose the site on a protein whose pocket is unknown, docks the ligand there with Vina, rescores the poses with GNINA and runs [PoseBusters](/app/posebusters) on the survivors. The [blind docking](/use-cases/blind-docking) page covers the first step, and [consensus docking](/use-cases/consensus-docking) explains when agreement between programs is worth trusting.

Before trusting any of them on a new target, redock the native ligand: take a protein structure that already has a ligand bound, remove the ligand, dock it back and measure the [RMSD](/guides/rmsd) to the crystal pose. If an engine cannot reproduce that pose within 2 Å on your protein, its prediction for a new ligand deserves less weight.

## Your first docking run

The quickest way to learn the difference is to dock a known drug into its own crystal structure, where the right answer exists. Imatinib in the c-Abl kinase domain (PDB 1IEP) is the example used throughout this guide.

1. Open [AutoDock Vina](/app/autodock-vina) and leave the task on single ligand.
2. Enter 1IEP as the receptor. The tool fetches it from the RCSB by PDB ID.
3. Search for imatinib as the ligand, which fetches it from PubChem, or paste its SMILES string.
4. Leave the binding pocket on its automatic setting, which builds the search box around the ligand already in the crystal structure, and run the job.
5. Read the pose table. The top pose should score about −12.5 kcal/mol, and the RMSD column shows how far each other pose sits from pose 1.

To run the same job locally with Meeko and the `vina` command, the [AutoDock Vina tutorial](/guides/autodock-vina-tutorial) covers every step and the settings behind each one.

Then try the same inputs in another engine to see what changes. DiffDock needs no box and returns a confidence instead of kcal/mol; GNINA adds a CNN score to the same kind of table. The Send to tool button on a result passes the poses to another tool such as [PoseBusters](/app/posebusters), which checks that bond lengths, clashes and geometry are physically sensible.

Three habits save first-time users the most trouble. Do not compare scores across engines, because kcal/mol, CNN pK values and diffusion confidences are on different scales. Look at the next few poses as well as the top one. And treat every score as a ranking aid, not a measured binding affinity.

## What each engine costs and limits on ProteinIQ

ProteinIQ prices jobs in credits, and a free account gets 200 credits a month. A single drug-sized ligand costs 20 credits in Vina, smina and GNINA and 50 in DiffDock, but the ways the price grows differ (Table 6).

  <caption><strong>Table 6. Hosted prices and limits on ProteinIQ.</strong> Credit figures are from each tool's pricing page for drug-sized ligands at the stated exhaustiveness.</caption>
  <thead>
    <tr>
      <th scope="col">Engine</th>
      <th scope="col">Typical single ligand</th>
      <th scope="col">What raises the price</th>
      <th scope="col">Hosted limits</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>AutoDock Vina</td>
      <td>20 credits at exhaustiveness 8</td>
      <td>Exhaustiveness 32 costs 40 and 64 costs 57; co-docking five ligands costs 500</td>
      <td>Up to 10 ligands in a batch, 5 in co-docking</td>
    </tr>
    <tr>
      <td>smina</td>
      <td>20 credits at exhaustiveness 8, 16 or 32</td>
      <td>Multi-record ligand files: 100 records cost 221 credits at exhaustiveness 8</td>
      <td>Exhaustiveness up to 32; ligands with metals refused</td>
    </tr>
    <tr>
      <td>GNINA</td>
      <td>20 credits with default CNN rescoring</td>
      <td>Full CNN scoring of every pose costs 1,865 credits for JQ1; ligands over 20 rotatable bonds raise the quote</td>
      <td>One ligand and one rigid receptor per job</td>
    </tr>
    <tr>
      <td>DiffDock</td>
      <td>50 credits</td>
      <td>Nothing: the price is flat across settings and receptor size</td>
      <td>Rigid protein; each run starts from new random poses</td>
    </tr>
  </tbody>

The practical consequence is that GNINA's default rescoring is nearly free to add, while its slowest scoring modes are not. If you plan to screen, rescore the top slice of a Vina run, not the whole library.

## Frequently asked questions

### Is smina the same as AutoDock Vina?

No. smina is a fork of Vina maintained by David Koes's group, built to support custom scoring functions and fast minimization. It uses Vina's search, so poses come out similarly, but it can score with functions Vina does not ship and report per-atom contributions.

### Is GNINA better than AutoDock Vina?

For choosing among poses, yes in the published tests: top-ranked poses within 2 Å rose from 58% to 73% in redocking and from 27% to 37% in cross-docking. It shares Vina's search, so it will not find poses Vina misses, and installing it locally means a CUDA-enabled Linux build.

### Is DiffDock better than AutoDock Vina?

It depends on what you give them. DiffDock wins when the pocket is unknown, because it searches the whole protein quickly, but Vina places ligands more validly when you supply the pocket. Use DiffDock to find the site and Vina or GNINA to refine it.

### Is AutoDock the same as AutoDock Vina?

No. AutoDock usually means AutoDock4, which uses grid maps, a genetic algorithm and a force-field score. Vina is a separate 2010 program with its own score and search, reported about two orders of magnitude faster. Vina 1.2 can also use the AutoDock4 scoring function.

### Which docking engine is fastest?

DiffDock reported about 10 s per complex on a GPU for blind docking, against roughly 127 s for GNINA with 16 CPU cores. That compares a whole-protein search; once a pocket is defined, Vina, smina and GNINA are fast enough that the choice rests on accuracy rather than speed.

### Do I need a GPU to run these?

Not on ProteinIQ, where the GPU engines run on hosted hardware. Locally, DiffDock needs a CUDA GPU, GNINA is built with CUDA and runs best on one, and Vina and smina run on a CPU.
