Supported image formats

Image files

QuPath can be used with a wide range of image formats, including many whole slide formats, thanks to two essential open source libraries:

Both libraries have their own distinct advantages:

  • OpenSlide is typically fast, lightweight and programmer-friendly (especially through Python), but is restricted to only 2D, 8-bit, RGB images.

  • Bio-Formats can support a much wider range of image types, including multidimensional data (e.g. z-stacks, time series and multiplexed images).

Bio-Formats supports most images that can be read by OpenSlide, but not all - and therefore QuPath continues to include both libraries.

However, file formats are tricky and tend to have lots of variants. Just because a format is listed as being supported by Bio-Formats or OpenSlide doesn’t mean files in that format will always open (properly) in QuPath. The following sections contain some extra details and caveats, partly based on user feedback about what does and doesn’t work.

Important

If you’re using a QuPath build for Apple silicon (i.e. a recent Mac with M1/M2/M3 processor), then you might find that .ndpi and .czi images don’t work with Bio-Formats.

See here for more details and workarounds.

Reporting problems

Despite the fantastic work of the Bio-Formats and OpenSlide developers, the use of proprietary formats throughout the field means that images often turn up that can’t be opened within QuPath.

In some cases, this is simply because the format isn’t supported.

Library

Supported formats

Issues page

Bio-Formats

Link

GitHub

OpenSlide

Link

GitHub

You can also check the QuPath issues page for past discussions.

Note

OpenSlide has not been updated for several years, whereas Bio-Formats is actively maintained by the OME team.

However, before relying on Bio-Formats to continue supporting and adding proprietary formats forever, one should read the OME position regarding file formats.

Specific formats

BIF (Ventana)

Both OpenSlide and (more recently) Bio-Formats now support BIF images. If you have trouble with one library, you might try reading the images with the other.

There have previously been problems with misaligned tiles (see here).

CZI (Zeiss)

Since the release of Bio-Formats v5.3.0 QuPath has been able to work with .czi files.

To open CZI files that use JPEG-XR compression on Windows, you may also need to install the Visual Studio 2015 C++ Redistributable - see here for more information.

If you’re using the Apple silicon build, Bio-Formats can’t read .czi files that use JPEG-XR compression. You’ll either need to convert the images outside of QuPath, or switch to using the Intel build of QuPath for macOS.

DICOM

Bio-Formats 6.8.0 introduced support for DICOM whole slide images. This is available in QuPath from v0.4.0.

OpenSlide 4.0 also added support for DICOM whole slide images. This is available in QuPath from v0.5.0.

iSyntax (Philips)

iSyntax is a proprietary format, not compatible with QuPath. We are unaware of any open source library capable of reading iSyntax files.

Tip

See here for a blog post from Glencoe Software about converting iSyntax to OME-TIFF.

MRXS (3D HISTECH)

OpenSlide has some limited support for MRXS images, but many do not work. Specifically, 2D, 8-bit, RGB images that do not use JPEG-XR compression seem to be ok. Anything else (e.g. 16-bit fluorescence) is not.

QuPath may still be able to open a low-resolution thumbnail for an unsupported MRXS image, but unfortunately not the full data.

The reasons why Bio-Formats and OpenSlide do not offer better MRXS support may be gleaned from the following links:

Tip

See here for a blog post from Glencoe Software about converting .mrxs to OME-TIFF.

NDPI (Hamamatsu)

NDPI is generally quite well supported by both Bio-Formats and OpenSlide. Note that z-stacks are only supported by Bio-Formats; with OpenSlide, only one plane will be opened.

If you’re using the Apple silicon build, Bio-Formats can’t read most .ndpi (or .ndpis) files. Fortunately, OpenSlide can handle .ndpi so this usually isn’t a problem.

TIFF

TIFF is a file format commonly used for whole slide images, but it is important to recognize that not all TIFFs are the same. Internally, the data in a TIFF file can be represented quite differently in terms of layout and compression.

Consequently, although OpenSlide and Bio-Formats support many TIFF files, it is quite possible to encounter variants that cannot be opened with QuPath.

Perhaps the most common reason for this is that the file does not contain pyramidal layers, or these layers cannot be automatically recognized. This is one reason why well-supported, open formats should generally be preferred (e.g. OME-TIFF).

Open URI

QuPath is not limited to working with image files stored locally.

File ‣ Open URI… provides a way to access some images stored elsewhere, however extensions are needed to support different kinds of image server. A few such extensions exist already, hopefully more will be created in the future by QuPath users.

OMERO

QuPath includes a built-in extension to work with whole slide images hosted through OMERO.

To use it, simply find the image you want through the OMERO web viewer, copy the URI, and paste it into the File ‣ Open URI… dialog in QuPath.

There is some additional documentation from the OMERO team in the OMERO Guide.

Warning

OMERO support is via the web API. This results in several limitations:

  • Only RGB images are supported

  • Image tiles are JPEG compressed

Essentially, QuPath is requesting image tiles in the same way as the OMERO web viewer.

Tip

QuPath’s OMERO support will be improved in future releases. It is already possible to add URLs in a variety of formats that OMERO can provide.

This makes it possible to import multiple images – even including some annotations – to a QuPath project in one go.

Community extensions

Extensions have been developed to link QuPath with other image management systems, including:

Note that these are external extensions that have not been tested and cannot be supported by the QuPath developers – if you have any questions about their use, it is best to contact whoever maintains the relevant extension.