Downloads

MITK applications

Installation Requirements

Windows installers should be run as administrator.

For Linux users before MITK 2016.11: The environment variable QT_PLUGIN_PATH has to be set to point to the Qt 5 plugins directory in order to run the application for MITK 2015.05 and MITK 2016.03. One of the typical paths is listed within the example commando

 bash:~/$ export QT_PLUGIN_PATH=/usr/lib/x86_64-linux-gnu/qt5/plugins 

Another typical path is something like

 bash:~/$ export QT_PLUGIN_PATH=/opt/Qt/5.7/gcc_64/plugins 

When not set, the attempt to run the application terminates with following error message: This application failed to start because it could not find or load the Qt platform plugin "xcb".

If you see error messages similar to this one: Caused by: ctkPluginException: The plugin "~/MITK-2015.5.2-linux64/bin/plugins/liborg_blueberry_ui_qt_help.so" could not be loaded: Cannot load library ~/MITK-2015.5.2-linux64/bin/plugins/liborg_blueberry_ui_qt_help.so: (libQt5Help.so.5: cannot open shared object file: No such file or directory) You will need to install missing Qt packages (in this case libqt5help5).

For Windows users: You need to install the appropriate Microsoft VC redistributable. MITK Version 2016.03 and newer include the redistributable installer within the installation package.

The Visual C++ Redistributable Packages for Visual Studio 2013 can be found at https://www.microsoft.com/en-US/download/details.aspx?id=40784 The Visual C++ Redistributable Packages for Visual Studio 2015 can be found at https://www.microsoft.com/de-de/download/details.aspx?id=48145

MITK Workbench

MITK releases include binary installers for Linux, macOS, and Windows. Please note that these installers only contain an application demonstrating MITK's capabilities, not the MITK SDK.

MITK Release	Sources	Installers	Documentation	Supported Platforms
2018.04.2	Archive Archive (Windows/CRLF) Git tag v2018.04.2	Windows Linux macOS	Doxygen Build Instructions	Supported Platforms
2018.04.2 with Nvidia AI-Assisted Annotation	Nvidia AI-Assisted Annotation Client @ Github.com	Windows Linux macOS	Additional Build Instructions
2018.04	Archive Archive (Windows/CRLF) Git tag v2018.04	Windows Linux macOS	Doxygen Build Instructions	Supported Platforms
2016.11	Archive Archive (Windows/CRLF) Git tag v2016.11	Windows Linux	Doxygen Build Instructions	Supported Platforms
2016.03.0	Archive Archive (Windows/CRLF) Git tag v2016.03.0	Windows Linux macOS	Doxygen Build Instructions	Supported Platforms
2015.05.2	Archive Archive (Windows/CRLF) Git tag v2015.05.2	Windows Linux macOS	Doxygen Build Instructions	Supported Platforms
2015.05.0	Archive Archive (Windows/CRLF) Git tag v2015.05.0	Windows Linux macOS	Doxygen Build Instructions	Supported Platforms

Previous releases

Some older releases can be found at the MITK SourceForge project site.

Nightly built installers can be found here. Caution! These are automatically generated untested developer versions!

MITK Diffusion

Please download the latest installers for MITK Diffusion directly on the MITK Diffusion site.

MITK 3M3

MITK 3M3 was a binary-only release in 2009. It is no longer supported nor available.

Special Releases

Recent releases of special applications can be found here.

MITK Source Code

We recommend to use the source code archive from the latest MITK release (see table above) or to check out the corresponding git tag.

If you need bug fixes or features which are not yet included in a MITK release, you can also clone the Git repository at:

https://phabricator.mitk.org/source/mitk.git

Before updating to a current development version, you can check the status of the MITK continuous integration system.

For details about Git, see also Mitk & Git.

Getting Started

See the Developer Tutorial. Build instructions in general are also available in the MITK documentation.

Extending MITK

Since MITK v2018.04, we provide a new and easy extension mechanism for MITK with the completely restructured MITK Project Template. This project includes examples for modules, plugins, and external dependencies, that you can use as a template to start your own components in your own, separate repository.