ngff-zarrΒΆ
A lean and kind Open Microscopy Environment (OME) Next Generation File Format (NGFF) Zarr implementation, OME-Zarr.
β¨ FeaturesΒΆ
Minimal dependencies
Work with arbitrary Zarr store types
Lazy, parallel, and web ready β no local filesystem required
Process extremely large datasets
Conversion of most bioimaging file formats
Multiple downscaling methods
Supports Python>=3.11
Reads OME-Zarr v0.1 to v0.6 into simple Python data classes with Dask arrays
Optional OME-Zarr data model validation during reading
Writes OME-Zarr v0.4 to v0.6
v0.6 adds RFC-5 coordinate systems and transformations
Sharded Zarr stores
Zarr I/O backed by zarrista / Rust zarrs (Python) or zarrita (TypeScript) β no zarr-python dependency; OME-Zarr 0.4 (Zarr v2) outputs stay readable by zarr-python 2 and 3, and 0.5+ (Zarr v3) by zarr-python 3
Anatomical orientation metadata (RFC-4)
OME-Zarr Zip (.ozx) file support for single-file OME-Zarr datasets (RFC-9)
High Content Screening (HCS) support for plate and well data
TIFF/OME-TIFF support with automatic metadata extraction and multi-series conversion
Leica Image Format (LIF) support for Leica microscopy data
Model Context Protocol (MCP) server for AI agent integration
- β‘ Quick start
- πΎ Installation
- π Python Interface
- π¦ TypeScript / JavaScript Interface
- π¨βπ» Command Line Interface
- π€ MCP Server
- π§ RFC-4: Anatomical Orientation Support
- π§ RFC-5: Coordinate Systems and Transformations
- 𧬠High Content Screening (HCS) Support
- β¨ Specification Features
- βοΈ Insight Toolkit (ITK)
- π Methods
- π€ Frequently Asked Questions (FAQ)
- π¨ Development
π Migration Guides
- π v0.43 to v0.44
- Purpose
- What is compatible
- What is not compatible
- Python 3.11 or newer is required
- zarr-python is no longer installed
- zarr-python store objects are no longer accepted
- Remote writes are not supported
- The remote extra no longer pulls in fsspec
- The tensorstore extra is removed
- The chunk store argument is removed
- Only the bytes codec plus gzip, zstd, or blosc is written
- Zarr metadata is validated more strictly on read
- In-memory mapping reads cover fewer stores
- MCP server changes
- Migration checklist
- Further reading
π Reference