How to Install AutoDock Vina on Windows 10 and 11: A Step-by-Step Guide for Beginners (Vina 1.2.7 + AutoDockTools)

To install AutoDock Vina on Windows 10 or 11, download vina_1.2.7_win.exe from the ccsb-scripps GitHub release, put it in a folder such as C:\Vina, add that folder to your PATH, then run vina --version in Command Prompt. Install MGLTools 1.5.7 separately for AutoDockTools. The Python bindings are Linux and Mac only.

Most Windows students lose their first afternoon of docking to a step that has nothing to do with docking. They search for an installer, find a blog post with screenshots of a setup wizard, download an MSI, and end up with AutoDock Vina 1.1.2 from 2011 sitting in C:\Program Files. Meanwhile the current release ships as a single bare executable with no wizard at all. This guide covers what actually ships today, how to make Windows find it, what to install alongside it, and what to do when a locked-down lab laptop refuses. Written by the StemSkills Lab team, from 10+ years in sequence and structural bioinformatics, drug discovery and design, and multiscale molecular modeling.

What exactly are you installing, and why is there no setup wizard?

AutoDock Vina is a command-line program. The current release, v1.2.7, was published on 26 February 2025 and attaches ten platform binaries to its GitHub release page. Two of them are for Windows:

• vina_1.2.7_win.exe, about 1.2 MB, the docking engine itself.
• vina_split_1.2.7_win.exe, about 0.7 MB, a helper that splits a multi-model output file into one file per pose.

There is no .msi, no .zip, and no installer. The 1.1.2 era MSI that half the tutorials on the internet still show you was retired several major versions ago. That single Windows binary is not a niche download either: at the time of writing, GitHub reports over 113,000 downloads of vina_1.2.7_win.exe, which is more than every Linux and Mac binary in that release combined.

Two programs commonly get confused here. Vina does the docking. AutoDockTools (ADT), which is the graphical front end used to add hydrogens, assign Gasteiger charges, set rotatable bonds, and write PDBQT files, ships inside MGLTools and is installed separately. You need both for a normal workflow, and neither one installs the other.

The scientific basis is worth knowing before you type a single command. Vina’s scoring function and search were introduced by Trott and Olson, Journal of Computational Chemistry 31(2):455-461, a paper Crossref now records at more than 34,000 citations. The 1.2.x line you are installing was described by Eberhardt, Santos-Martins, Tillack and Forli, Journal of Chemical Information and Modeling 61(8):3891-3898, 2021, which added the Vinardo and AutoDock4 scoring options, macrocycle sampling, batch mode, and the Python bindings. If you are new to the method rather than the software, start with our pillar guide to molecular docking first.

How do you install the AutoDock Vina 1.2.7 executable on Windows?

Five steps, and none of them involve a wizard.

1. Download the binary. Open the AutoDock-Vina releases page, expand Assets under v1.2.7, and click vina_1.2.7_win.exe. Grab vina_split_1.2.7_win.exe while you are there.
2. Create a home for it. Make a folder at C:\Vina. Avoid C:\Program Files: it needs administrator rights to write into, and the space in the folder name causes trouble later with scripts that do not quote their paths.
3. Rename the files. Move both downloads into C:\Vina and rename them to vina.exe and vina_split.exe. Every tutorial, script, and paper you will read assumes the short names.
4. Clear the security prompt once. Windows SmartScreen flags any unsigned executable it has not seen before. The first time you run it you may get a blue “Windows protected your PC” panel. Click More info, then Run anyway. If the file came from the official ccsb-scripps repository, this is expected behaviour for an unsigned academic binary, not a warning about the file itself.
5. Verify. Open Command Prompt, then run:

cd C:\Vina
vina.exe --version

You should see the version banner. If you do, Vina is installed. What you do not yet have is the ability to call it from any other folder, which is the next step and the one that produces the single most common beginner error.

How do you add vina.exe to your PATH so the command works anywhere?

PATH is the list of folders Windows searches when you type a command. Until C:\Vina is on that list, typing vina outside that folder gives you this:

'vina' is not recognized as an internal or external command,
operable program or batch file.

To fix it permanently:

1. Press the Windows key, type environment, and open Edit the system environment variables.
2. Click Environment Variables.
3. Under User variables, select Path and click Edit. Editing the user variable rather than the system one avoids needing admin rights, which matters on a university machine.
4. Click New, type C:\Vina, and click OK on all three dialogs.
5. Close every open Command Prompt window and open a fresh one. PATH is read when a shell starts, so an already-open terminal will keep failing no matter what you changed.

Now test from somewhere else entirely:

cd %USERPROFILE%\Desktop
vina --help

A wall of options starting with --receptor and --ligand means you are done. There is also vina --help_advanced, which lists the scoring-function weights and sampling internals you will eventually want when you start tuning runs.

Why does pip install vina fail on Windows?

Because it was never built for Windows. The official installation page states the platform limitation plainly under the heading “Python bindings (Linux and Mac only)”, and adds a second point students routinely miss: “Currently, the python bindings and the binary installation are two separate processes. The installation of the python bindings does not include the Vina executable, and vice versa” (AutoDock Vina documentation, Installation).

So on Windows, pip install -U numpy vina is not the route. Two practical consequences:

• Any tutorial that starts with from vina import Vina will not run natively on Windows. You need WSL, Linux, macOS, or a cloud notebook for that.
• Even on Linux, installing the Python module does not give you the vina command, and installing the binary does not give you the module. If you want both, install both.

This is also why the command-line route is the better first thing to learn. Everything in the published literature is reproducible from the CLI, and it is what you will use for batch docking of multiple ligands anyway.

How do you install AutoDockTools (MGLTools 1.5.7) on Windows?

MGLTools is a separate download from the Scripps Center for Computational Structural Biology. Go to the MGLTools downloads page and take mgltools_win32_1.5.7_Setup.exe, listed at roughly 80 MB. Despite the win32 in the filename, this is the current build for Windows, patched most recently in the October to November 2022 round of updates.

This one does have an installer. Run it, accept the default location, and you get three things you will use:

• AutoDockTools for receptor and ligand preparation, launched from the Start menu.
• The Python Molecular Viewer for looking at structures.
• The utility scripts under Lib\site-packages\AutoDockTools\Utilities24\, including prepare_receptor4.py and prepare_ligand4.py.

MGLTools ships its own Python interpreter so it cannot collide with an Anaconda install you already have. In the patched builds it is named MGLPython plus its version, specifically to keep it distinct from your system Python. When you call the utility scripts, call them through that interpreter rather than through python, and get into the habit of changing directory into the folder holding your structure files before you run them. Path handling is the most common source of “file not found” errors with these scripts.

A practical note on ordering: prepare the receptor and ligand into PDBQT files first, then define your search box, then dock. If you have not chosen a site yet, work through finding the protein binding site and downloading a structure from the RCSB PDB before you touch Vina at all.

What does a first real docking command look like?

The official basic docking tutorial docks imatinib into c-Abl kinase with a box centred on the known site. Its Vina call, using a small config file for the box, is:

vina --receptor 1iep_receptor.pdbqt --ligand 1iep_ligand.pdbqt ^
     --config 1iep_receptor.box.txt ^
     --exhaustiveness=32 --out 1iep_ligand_vina_out.pdbqt

where 1iep_receptor.box.txt contains the box definition:

center_x = 15.190
center_y = 53.903
center_z = 16.917
size_x = 20.0
size_y = 20.0
size_z = 20.0

Note the caret ^ at the end of each line. That is the Windows Command Prompt line-continuation character. The backslash you see in the official docs is the Linux and macOS equivalent, and pasting it into Command Prompt is the reason a copied command silently truncates. Alternatively, put the whole command on one line and forget about continuations entirely.

--exhaustiveness controls how much search effort goes into each ligand, with 8 as the default and 32 used in the official tutorial. Higher values cost proportionally more time and give more reproducible results. Once this works, the natural next step is flexible side-chain docking.

What are the options when a native install is blocked?

Managed lab machines, corporate antivirus, and accounts without write access to C:\ all break the native route. Three fallbacks work, and they are not equivalent.

WSL is the option most students should take. It gives you a real Ubuntu environment alongside Windows, which means the Linux commands in the Vina docs, in GROMACS tutorials, and in most published methods sections run unmodified. Per Microsoft’s documentation, you need Windows 10 version 2004 (build 19041) or later, or Windows 11. Open PowerShell as administrator and run:

wsl --install

That single command enables the required components, installs the Linux kernel, sets WSL 2 as the default, and installs Ubuntu (Microsoft Learn, How to install Linux on Windows with WSL). Restart, create your Linux username, and then the official pip route works: pip install -U numpy vina.

On PyRx, be careful with old advice. Version 0.8 and earlier are still free but are no longer supported, and the current Academic and Pro licences are paid. Any tutorial that calls PyRx “free software” is describing a version that stopped being maintained years ago.

Which errors will you actually hit, and how do you fix them?

• 'vina' is not recognized as an internal or external command. PATH is not set, or your Command Prompt was open before you set it. Add C:\Vina to the user Path variable and open a new terminal window.
• “Windows protected your PC” blocks the download or the run. SmartScreen does not trust an unsigned binary it has not seen. Click More info then Run anyway. If corporate antivirus quarantines the file outright, you cannot override that yourself, so use WSL or Colab instead of fighting it.
• A tutorial tells you to run an MSI and there is no MSI. That tutorial predates 1.2.0. Use the release assets listed above.
• ERROR: Could not find a version that satisfies the requirement vina from pip on Windows. Expected. The bindings are Linux and Mac only.
• Your pasted command runs with half the arguments missing. You copied a Linux command with trailing backslashes. Use ^ in Command Prompt, or put everything on one line.
• Output PDBQT holds nine poses in one file. That is normal. Run vina_split --input out.pdbqt to write one file per pose before you analyse interactions.
• Docking finishes instantly with no poses. Your search box does not contain the ligand or the site. Check the centre coordinates against the receptor, and confirm both inputs are genuinely PDBQT and not renamed PDB files.

If you are working out where docking fits into a larger skill set, our computational biology skills roadmap lays out the sequence most students follow from structure preparation through docking to molecular dynamics.

Frequently asked questions

Is AutoDock Vina free for students?

Yes. Vina is open source under the Apache License 2.0 and free to download and use, including for academic research and teaching. MGLTools and AutoDockTools are also free from the Scripps Center for Computational Structural Biology. Only third-party GUI wrappers such as current PyRx versions charge a licence fee.

Do I need to install Python to run AutoDock Vina on Windows?

Not for Vina itself. The Windows executable is self-contained and takes its input from PDBQT files and command-line flags. You will want Python for analysis and for the MGLTools utility scripts, but MGLTools ships its own interpreter, so no separate Python install is required to prepare files.

What is the difference between AutoDock4 and AutoDock Vina?

They are different programs from the same lab. AutoDock4 uses a semi-empirical free-energy force field and requires precomputed grid maps from AutoGrid. Vina uses its own scoring function with a faster search and multithreading. Vina 1.2.x can also read AutoDock4 maps if you set --scoring ad4.

Can I run AutoDock Vina without the command line?

Partly. AutoDockTools can set up a docking run and write the configuration for you, and GUI wrappers such as PyRx or Chimera interfaces can launch Vina behind the scenes. Learning the command line is still worth it, because batch screening, cluster jobs, and reproducible methods sections all depend on it.

Should I use WSL instead of the native Windows executable?

Use WSL if you plan to follow Linux tutorials, use the Python bindings, or later run GROMACS. Use the native executable if you only need docking and prefer working with Windows folders and the AutoDockTools GUI. Nothing stops you from having both on one laptop.

How long should a single docking run take?

A drug-sized ligand in a 20 x 20 x 20 angstrom box at default exhaustiveness typically finishes in seconds to a couple of minutes on a modern laptop. Raising exhaustiveness to 32 raises the cost roughly fourfold. Use --cpu to control how many threads Vina uses.