ImageJ2 (ImageJ)
Maintainer Curtis Rueden
Source on GitHub
Development status active

ImageJ2's Mission

  • Design the next generation of ImageJ, driven by the needs of the community.
  • Collaborate across organizations, fostering open development through sharing and reuse.
  • Broaden ImageJ's usefulness and relevance across many disciplines of the scientific community.
  • Maintain backwards compatibility with existing ImageJ functionality.
  • Unify online resources to a central location for the ImageJ community.
  • Lead ImageJ development with a clear vision.
See also these presentation slides about ImageJ.
ImageJ2 is a new version of ImageJ for the next generation of multidimensional image data, with a focus on scientific imaging. Its central goal is to broaden the paradigm of ImageJ beyond the limitations of ImageJ 1.x, to support the next generation of multidimensional scientific imaging.

To ensure backwards compatibility, ImageJ2 has been designed to fully integrate into the existing ImageJ user interface. This allows users to keep using ImageJ in familiar ways, while providing the ability to migrate toward more powerful new features as needed.

The Fiji distribution of ImageJ has shipped with beta versions of ImageJ2 for quite some time, so you may already be familiar with some of ImageJ2's features—some of which, such as the Updater and Launcher, were originally developed as part of Fiji.

Features of ImageJ2

ImageJ2 provides a wealth of new features and capabilities:

  • The ImageJ Updater makes it simple to keep your ImageJ up to date, and to add new plugins by enabling additional Update Sites.
  • New and enhanced file format support via the SCIFIO library (see below).
  • More powerful Script Editor with support for several scripting languages.
  • New commands:
    • Plugins  ▶ Debug  ▶ Dump Stack for debugging when things hang.
    • Plugins  ▶ Debug  ▶ System Information for reporting on versions of installed plugins and libraries.
  • Use ImageJ2's N-dimensional ImgLib2-based data structures (still in beta).
  • Write parameterized commands and scripts:
    • Typed inputs and outputs with no dependence on AWT user interface.
    • Mix and match ImageJ 1.x and ImageJ2 data structures.
    • Plugins appear in the menu automatically without plugins.config files.
    • Reusable in many contexts: KNIME, CellProfiler, OMERO, headless...

Improved image I/O with the SCIFIO library

ImageJ2 uses the SCIFIO library (SCientific Image Format Input and Output) by default for most image input tasks. You can change this behavior at any time by running Edit  ▶ Options  ▶ ImageJ2 and modifying the Use SCIFIO when opening files option.

For further details, see the SCIFIO page.

ImageJ2 is more than just an application

ImageJ2 is also a collection of reusable software libraries built on the SciJava software stack, using a powerful plugin framework to facilitate rapid development and painless user customization.

The following software component libraries form the core of ImageJ2:

  • ImageJ Common - The core image data model, using ImgLib2.
  • ImageJ Ops - An extensible framework for reusable image processing algorithms.
  • ImageJ Updater - A mechanism to update individual plugins and libraries within ImageJ.
  • ImageJ Legacy - Provides complete backwards compatibility with ImageJ 1.x.
  • SciJava Common - The core frameworks for plugins, modules and the application itself.

See the Architecture page for further details.


In recent years a segment of the ImageJ developer community has repeatedly inquired as to ImageJ's future. The program has been successful enough that it would greatly benefit from modern open source software best practices: a publicly accessible source code repository, a suite of unit tests with a continuous build integration system, a central repository of extensions, clear guidelines on how external developers can contribute to both those extensions and to the core program when warranted, and a development roadmap addressing feature requests and tasks from the community.

Listening to the ImageJ community, it is clear that:

  1. There is substantial demand from developers for a next-generation version of ImageJ with a cleaner, more modular API, so that ImageJ can be leveraged not just as a standalone analysis program, but as a robust, extensible library in a variety of contexts.
  2. The ImageJ user community has invested a lot of time and energy to develop complex workflows within ImageJ, and they oppose any change that would break them. Thus, any effort to improve the software must maintain compatibility with existing code.
  3. Further, any next-generation version of ImageJ must maintain community unity, and not fork the project. All components of this project will be developed as upgrades to core ImageJ.
  4. The ImageJ community as a whole would substantially benefit from a central effort to organize and serve program code (both the core application and its plugins), keep track of bugs and feature requests, and better leverage external developer contributions.

For more details, see the presentation from the 2010 ImageJ Conference.


ImageJ2 is funded from a variety of sources. See the Funding page for details.


See also

  • "The ImageJ2 platform, and the Fiji distribution of ImageJ" [ video, slides ]