How to Install AutoDock Vina on Windows, Mac and Linux (2026 Guide)

12 min read Complete beginner

AutoDock Vina is the most widely used free docking program in academic research — but the official documentation assumes you already know your way around a terminal. This guide doesn’t. Exact commands, what the output should look like, and what to do when something goes wrong.

Before you start: what you need

AutoDock Vina has no GUI — it runs entirely from the command line. If you’ve never opened a terminal before, that sounds intimidating. It isn’t. You’ll be running single commands, not writing code. This guide shows you the exact commands to type at each step.

Here’s what you need before installing:

• A computer running Windows 10/11, macOS 11+, or any modern Linux distribution
• About 200 MB of free disk space
• An internet connection to download the binary
• No programming experience required

There are two installation methods: via conda (recommended — handles everything automatically) or via a pre-compiled binary (simpler if you don’t already use conda). This guide covers both, starting with conda.

Installing on Windows

Method 1: pre-compiled binary (recommended for Windows)

cd C:\vina

Installing on macOS

Method 1: conda (recommended)

conda --version

If you see a version number, skip to step 2. If you see command not found, download Miniconda from docs.conda.io/en/latest/miniconda.html — choose the macOS installer for your chip (Apple Silicon / M-series Macs need the arm64 version; older Intel Macs need x86_64). Run the installer and follow the prompts. Restart Terminal when done.

conda create -n docking python=3.10 -y
conda activate docking
conda install -c conda-forge autodock-vina -y

This will download and install Vina and all its dependencies. It takes 2–5 minutes depending on your connection. You’ll see a progress bar. When it finishes, you’ll see a line ending in done.

Installing on Linux

Method 1: conda (recommended)

conda --version

If not installed, download and run the Miniconda installer:

wget https://repo.anaconda.com/miniconda/Miniconda3-latest-Linux-x86_64.sh
bash Miniconda3-latest-Linux-x86_64.sh

Follow the prompts, accept the license, confirm the install location, and say yes when asked to initialize conda. Close and reopen your terminal.

conda create -n docking python=3.10 -y
conda activate docking
conda install -c conda-forge autodock-vina -y

Method 2: pre-compiled binary (Linux alternative)

If you’d rather not use conda, download and install the binary directly — this is particularly convenient on HPC clusters where conda may not be available:

wget https://github.com/ccsb-scripps/AutoDock-Vina/releases/latest/download/vina_linux
chmod +x vina_linux
sudo mv vina_linux /usr/local/bin/vina

If you don’t have sudo access (common on HPC systems), move it to your home directory and update your PATH instead:

mkdir -p ~/bin
mv vina_linux ~/bin/vina
echo 'export PATH="$HOME/bin:$PATH"' >> ~/.bashrc
source ~/.bashrc

Verifying the installation

Regardless of your OS or method, verify Vina installed correctly with the same command:

vina --version

If the install worked, you should see output like this:

What successful installation looks like — your version number may differ.

Run one more check to confirm the help menu loads, which confirms the binary is working fully:

vina --help

You should see a list of flags and options. If you see that, you’re done — Vina is installed and ready to use.

Common errors and fixes

These are the errors that trip up most first-time installers, in rough order of how often they appear.

Error message	What it means and how to fix it
command not found: vina	Vina isn’t on your PATH. On Linux/macOS: check that your conda environment is activated (conda activate docking). On Windows: check that you added the correct folder to your PATH and restarted Command Prompt.
Permission denied	The binary isn’t executable. Run chmod +x vina (Linux/macOS) on the file. On Windows, right-click the .exe → Properties → Unblock.
“Apple cannot check it for malicious software” (macOS)	Gatekeeper is blocking the binary. Go to System Settings → Privacy & Security → scroll down → click Allow Anyway next to the Vina entry. Then re-run from Terminal.
conda: command not found	Conda isn’t initialized in your shell. Close and reopen your terminal. If that doesn’t work, run ~/miniconda3/bin/conda init bash (Linux) or ~/miniconda3/bin/conda init zsh (macOS default shell), then restart terminal.
Segmentation fault (core dumped)	Binary architecture mismatch. You probably downloaded the x86_64 binary for an ARM machine (or vice versa). Re-download the correct binary for your system architecture from the GitHub releases page.
GLIBCXX_3.4.XX not found (Linux)	Your system’s C++ library is outdated. Install a newer version: conda install -c conda-forge libstdcxx-ng inside your conda environment, then retry.
vina is not recognized as an internal or external command (Windows)	PATH wasn’t updated or Command Prompt wasn’t restarted. Close and reopen Command Prompt completely after adding to PATH. If still failing, navigate directly to the folder containing vina.exe and run it as .\vina.exe --version.

What to do next

With Vina installed, you have the engine — but you still need the inputs. The next two steps in the workflow are preparing your protein structure and preparing your ligand, both of which need to be in .pdbqt format before Vina can use them.

Here’s a quick sanity-check list before you move on:

• vina --version returns a version number without errors
• vina --help shows the full list of flags and options
• You know how to open a terminal (or Command Prompt) and navigate to a folder
• On macOS/Linux: you know to run conda activate docking at the start of each session