Compatibility reference

Microscopy File Compatibility in SlideScope

SlideScope has dedicated desktop readers for CZI, ND2, SVS, TIFF, and DICOM families. This page separates an accepted file extension from the dimensions, metadata, compression, and workflow details that determine whether a specific file is a good fit.

Want the measurements rather than the claims? We opened 792 real microscopy and whole slide files and published every result, including the failures.

Download App Subscribe Now
7 accepted extensions Windows and macOS Last reviewed July 12, 2026

Current compatibility matrix

The matrix is derived from current SlideScope application routing and reader behavior. Use it as a screening reference, then test representative files from the exact microscope, scanner, software version, and compression settings used by your team.

Format family Accepted extensions Reader behavior Important checks
ZEISS CZI .czi Normalizes time, Z, channel, Y, and X dimensions; reads acquisition metadata and spatial calibration when exposed. Scenes that share a pixel type and axes become separate steppable scenes, each at its own size, and XY Overview shows them together. Exports the scene on screen, or every scene, to OME-TIFF. Test scenes, mosaics, uncommon sub-block layouts, and very large acquisitions.
Nikon ND2 .nd2 Maps time, Z, channels, and image size. Multiple stage positions are a separate position axis with its own control, and XY Overview places them at their recorded stage coordinates. Confirm position/time interpretation, RGB layout, metadata, and the exact NIS-Elements generation.
Aperio SVS .svs Reads TIFF-based whole-slide pyramid levels and selects a manageable display level under memory constraints. Check JPEG/JPEG 2000 codecs, pyramid integrity, scanner metadata, and desired resolution level.
TIFF and OME-TIFF .tif, .tiff Uses named axes where available, including time, Z, channel, Y, and X. Recognizes OME-TIFF and ImageJ metadata and spatial scale when present. TIFF is a flexible container. Verify compression, BigTIFF size, pyramids, axes, and metadata preservation.
Vendor scanner slides .ndpi, .mrxs, .scn, .bif, .vms, .vmu, .svslide, .qptiff Reads the scanner's own image pyramid through the OpenSlide backend and loads the level matching the region on screen. Scale bar, measurements, and annotations use the scanner's micron calibration at every zoom level. MRXS, VMS, and VMU store pixel data in a companion folder beside the index file, so they open from local storage only and are rejected for remote links. Check pyramid integrity and vendor metadata on representative slides.
Standard DICOM .dcm, .dicom Handles standard single- and multi-frame datasets, mapping time, Z, channels, frames, and selected metadata. Tiled whole-slide DICOM is read through a separate pyramid path with native tile access. Confirm transfer syntax/codecs, SOP class, de-identification policy, and research-use requirements.

Format-specific detail and authoritative references

CZI: multidimensional review without implying ZEISS certification

CZI can contain multiple scenes, channels, Z planes, time points, acquisition metadata, and tiled sub-blocks. SlideScope reads common review dimensions and metadata, and steps through a file's scenes one at a time or shows them together in XY Overview. Scenes whose pixel type or axes differ from the first are not steppable: the first scene is shown with a notice saying why. Export writes an OME-TIFF with lossless compression, pixel size and channel names; exporting from XY Overview puts every scene into one file as a separate image, and a large tiled scan is exported at its overview resolution. Each exported scene keeps the pixel size it was acquired at (fixed in SlideScope 1.8.57; earlier versions could mis-calibrate non-tiled scenes of different sizes). The CZI family is broad enough that a real file test matters; the multi-scene CZI guide shows scenes and export step by step. ZEISS documents the format and its application ecosystem on the official CZI image file format page. That reference defines the source format; it does not represent an endorsement or certification of SlideScope.

ND2: time, Z, channels, and positions

SlideScope maps the primary ND2 axes into its viewer contract. Since version 1.8.41 a multi-position acquisition keeps its positions on an independent axis rather than folding them into time, and XY Overview places each position at its recorded stage coordinate. Stage orientation has been verified on a limited set of instruments, so check a representative multi-position experiment before a team standardizes on it. Nikon's official NIS-Elements software resources describe Nikon's free standalone viewer, multidimensional dataset viewing, and TIFF export in Nikon's own ecosystem.

SVS: whole-slide pyramids and compression

SVS files are TIFF-based whole-slide images with pyramid levels and Aperio metadata. SlideScope chooses a level that balances display detail and available memory. The open-source OpenSlide project documents the Aperio format structure, including tiled images, pyramid levels, associated images, and metadata properties.

TIFF and OME-TIFF: a container, not one uniform layout

A file ending in .tif can be a plain 2D image, RGB image, ImageJ stack, OME-TIFF dataset, BigTIFF, or a pyramidal image with different compression. SlideScope's reader recognizes OME and ImageJ metadata when present, but every variant should not be treated as identical. The OME-TIFF specification explains how TIFF planes and OME-XML metadata encode dimensions and pyramids.

DICOM: standard frames and tiled whole-slide pyramids

Current public Windows and macOS installers support ordinary single- and multi-frame DICOM for research review, including fluorescence Z-stacks and time-lapse captures. Files carrying the VL Whole Slide Microscopy Image Storage SOP class are read through a separate whole-slide path that uses the DICOM pyramid and tile structure directly, so tiled WSI DICOM opens without conversion. Compressed transfer syntaxes are decoded through the bundled GDCM, openjpeg, and imagecodecs plugins. SlideScope is not a PACS and is not presented as a validated diagnostic workstation. The DICOM Standards Committee's Supplement 145 defines whole-slide microscopic image objects and helps explain why WSI is a separate compatibility class.

Why a supported extension can still fail

Incomplete or renamed file

A partial download, interrupted copy, or file renamed to a supported extension may not contain a valid format header or complete pixel data.

Codec or compression variant

Whole-slide TIFF, SVS, and DICOM files can depend on JPEG, JPEG 2000, or other codecs. An unusual transfer syntax or missing packaged codec can prevent decoding.

Unusual dimensional layout

Vendor files can encode scenes, positions, illuminations, views, tiles, or axes differently. A reader may open the file but map a specialized layout differently than expected.

Memory and pyramid limits

Very large images need valid lower-resolution levels or enough memory for the selected plane. Test the largest routine files, not only a small sample.

A practical pre-adoption test

  1. Choose files from every microscope or scanner model your team actually uses.
  2. Include a small file, a typical file, the largest routine file, and one older archived file.
  3. Verify channel colors, time points, Z planes, positions, pyramid detail, and spatial calibration.
  4. Compare key metadata against the acquisition software or another trusted reader.
  5. Test TIFF export and confirm what dimensions and metadata the downstream workflow expects.
  6. Record the application version, operating system, hardware, source software, and outcome.

This creates evidence a lab can review later and is more reliable than assuming every file with the same extension is identical.

Formats not currently advertised as supported

NDPI, MRXS, SCN, BIF, VMS, VMU, SVSLIDE, and QPTIFF scanner slides are supported through the OpenSlide backend and appear in the compatibility matrix above. Current extension routing does not advertise LIF, LSM, VSI, OME-Zarr, NIfTI, or general video formats. Do not rename one of those files to a supported extension. If one of these formats is important to your workflow, contact support with the format name and acquisition software before purchasing.

For supported files that still fail, the in-app support flow can include non-sensitive slide context. Do not send patient-identifying data or proprietary files unless your organization has approved that sharing.

Compatibility questions

Which microscopy file extensions does SlideScope open?

Current releases route .czi, .nd2, .svs, .tif, .tiff, .dcm, and .dicom files to dedicated readers.

Does SlideScope open OME-TIFF files?

The TIFF reader recognizes OME-TIFF metadata and maps named time, Z, channel, Y, and X axes when exposed. Test representative compression, BigTIFF, and pyramid variants.

Does extension support guarantee every file will open?

No. Damage, incomplete transfers, uncommon codecs, vendor variants, and unusual dimensional layouts can still affect compatibility.

Is SlideScope a diagnostic DICOM viewer?

No diagnostic claim is made. SlideScope is intended for research, education, and review workflows; clinical use requires the institution's own validation and regulatory assessment.

Test the files your team actually uses

Install the correct Windows or Mac build, then verify representative CZI, ND2, SVS, TIFF, and DICOM datasets.

Download App