Skip to content
Back to Articles
Article

WSI File Formats and DICOM: Why Interoperability Matters

28 October 2026 at 08:00
7 min read
WSI File Formats and DICOM: Why Interoperability Matters

Every whole slide image is stored in some file format, and that choice quietly decides which viewers, archives and analysis tools can use it for years to come. This article is for lab managers, pathologists and hospital IT teams who want to understand WSI file formats and DICOM well enough to avoid lock-in and plan for long-term access.

Why WSI file formats are different

A whole slide image is not an ordinary picture. It is a very large image stored as a pyramid of resolutions, cut into tiles so a viewer can load only what is on screen. A single file may also hold a label image, an overview image and metadata about the scan.

Standard photo formats were not designed for this. As a result, scanner manufacturers developed their own formats to hold pyramids, tiles and metadata efficiently. Many are based on TIFF with vendor-specific structures; others use entirely custom layouts or spread one slide across many files in a folder.

If the pyramid concept is new to you, our explainer on whole slide imaging from glass slide to gigapixel image walks through how these files are built.

The proprietary format problem

Proprietary formats work well inside the vendor's own ecosystem. The trouble starts when you need to step outside it.

Typical symptoms include:

  • A new viewer or image management system cannot open images from an older scanner.
  • A lab with scanners from two vendors runs two separate viewers and two archives.
  • An analysis tool supports some formats but not the one your scanner produces.
  • Metadata such as scan date, magnification or slide identifier is stored differently by each vendor, or is lost on conversion.
  • Moving the archive to a new platform requires a conversion project that nobody budgeted for.

Open-source libraries can read many common vendor formats, and they have been a lifeline for research groups. But relying on reverse-engineered support for clinical archives is a risk, especially as vendors update their formats.

The underlying issue is timescale. Scanners are replaced on an equipment cycle. Images, and the diagnostic record they support, may need to be retrievable for much longer.

What DICOM brings to digital pathology

DICOM (Digital Imaging and Communications in Medicine) is the standard that radiology has relied on for decades to store and exchange medical images. It includes an image definition for whole slide microscopy, designed to hold tiled, multi-resolution slide images with their associated metadata.

Structured, standard metadata

A DICOM whole slide image carries patient, study, specimen and acquisition information in defined fields. That means a slide identifier, stain or scan resolution is found in the same place regardless of which scanner produced the file. For laboratories, the ability to describe specimens and preparation steps in a standard way is particularly valuable.

Standard ways to store and retrieve

DICOM is not just a file format. It also defines how systems query, send and retrieve images, including web-based services. In principle, a viewer from one vendor can retrieve slides from an archive supplied by another, as already happens routinely in radiology.

A shared archive with radiology

Some hospitals see value in storing pathology images in an enterprise imaging archive alongside radiology. DICOM makes that possible, though pathology images are much larger than most radiology studies and the archive must be sized accordingly.

What interoperability means in practice

Interoperability is not a checkbox. It is the ability of each part of your digital pathology system to be replaced without breaking the others.

Think about the main connections:

  • Scanner to storage. Can the scanner write directly in an open format, or does it require conversion?
  • Storage to viewer. Can any compliant viewer open the images, or only the vendor's?
  • Images to case. Is the link between slide and case carried in standard metadata, or held only in a proprietary database?
  • Images to analysis tools. Can AI or image analysis software read the images without custom conversion?
  • Images to external partners. Can you share slides with a consultant or reference lab in a form they can open?

Each connection that depends on one vendor's software is a future cost. When you are choosing a whole slide scanner, format support deserves the same scrutiny as image quality.

Questions to ask vendors

Bring these questions to every scanner, viewer and image management vendor:

  1. Can your system produce or accept DICOM whole slide images natively, and has it been tested with other vendors' systems?
  2. If your native format is proprietary, is it publicly documented?
  3. Which metadata fields are preserved on export, and which are lost?
  4. Can we export our entire archive in an open format if we leave, and at what cost?
  5. Do you support standard query and retrieve services, including web-based access?
  6. How do format changes in software updates affect previously stored images?
  7. Which third-party viewers and analysis tools have you confirmed can read your images?

Ask for demonstrations, not assurances. A short test where a third-party viewer opens a file exported from the scanner tells you more than a brochure.

Planning for migration and long-term access

Even with good intentions, most labs will face at least one format migration. Plan for it from the start.

Keep a register of where images live, which format they are in and which scanner produced them. Prefer open formats for new acquisitions where your validated workflow allows. When converting, verify a sample of images visually and confirm that metadata, especially identifiers, survived intact. And remember that conversion of very large archives takes time and compute, so do not leave it until a contract is about to expire.

Common mistakes to avoid:

  • Assuming DICOM support on a spec sheet means full interoperability. Test it.
  • Converting images without checking that patient and slide identifiers carried over correctly.
  • Letting the image archive and the case record drift apart, so images can be found but not matched to reports.
  • Ignoring label images, which may contain patient identifiers and must be handled under your privacy rules.

Key takeaways

  • WSI file formats differ widely, and many are proprietary to the scanner vendor.
  • Proprietary formats create lock-in that becomes expensive when you change scanners, viewers or archives.
  • DICOM provides a standard structure for slide images, metadata and image exchange, borrowed from radiology's long experience.
  • Test interoperability in practice, and make archive export terms part of every contract.
  • Plan for migration early, and always verify identifiers after conversion.

If you are designing an image workflow that keeps slides tied to the right case, book a demo to see how PATHOLOGY+ connects whole slide image viewing with case records and reporting.

Found this useful? Share it with your team

HanumanIT Editorial
Clinical Communication Team