abce991 Oct 31, 2018
1 contributor

Users who have contributed to this file

137 lines (94 sloc) 3.66 KB

Download ITK

This page documents how to download ITK. See our CONTRIBUTING guide for more information.

Download ITK Release Assets

ITK release tarballs, including:

  • Source code
  • Regression test data
  • Doxygen documentation
  • ITK's Software Guide
  • ITK's Examples

can be downloaded from ITK's GitHub Releases page.

Linux Package Distributions

ITK packages exist for many Linux distributions. For Debian and Ubuntu, they can be obtained running

   $ sudo apt-get install libinsighttoolkit4-dev

This will give you the libraries and development headers.

For information on other ITK packages and packages for other distributions, see this blog post.


ITK Python wheels are available through the Python Package Index (PyPI).

To install the ITK Python wheel, use

   $ python -m pip install --upgrade pip
   $ python -m pip install itk

Additionally, wheels for external modules may also be available through the Python Package Index (PyPI).

Check the ITKPythonPackage website for further information.

Download ITK Sources with Git

First, download and install Git.

Note that the software must be compiled from source using CMake and your favorite C++ compiler. The toolkit can be installed, but it is not necessary; it can be used directly from its build directory. See the ITK Software Guide for further information on configuring and building ITK.


Clone ITK using the commands

   $ git clone
   $ cd ITK

The latest stable release can be cloned into a local repositiory using

   $ git clone -b release ITKLatestRelease

where ITKLatestRelease is the name of the local repository created.

Additionally, specific releases can be cloned using the tags, for example:

   $ git clone -b v4.13.1 ITK-4.13.1

where v4.13.1 corresponds to ITK 4.13.1, and the ITK-4.13.1 is the name of the local repository created.


Users that have made no local changes and simply want to update a clone with the latest changes may run

   $ git checkout master
   $ git pull --rebase upstream master

Avoid making local changes unless you have read our developer instructions.


After cloning, your local repository will be configured to follow the upstream master branch by default. This means you will have access to cutting edge features, but along with these may come cutting edge bugs 😬. One may create a local branch to track the upstream release branch instead, which should guarantee only bug fixes to the functionality available in the latest release:

   $ git checkout --track -b release origin/release

This local branch will always follow the latest release. Use the [#update] instructions to update it.

Alternatively, one may checkout a specific release tag using

   $ git checkout v4.13.1

Release tags never move. Repeat the command with a different tag to get a different release. One may list available tags using:

   $ git tag