ome-zarr-io
Read, write, and validate OME-Zarr 0.5 images and high-content-screening plates: from a NumPy array to a spec-compliant OME-Zarr image in a few lines of Python.
Microscopy datasets are growing faster than desktop tools can handle. OME-Zarr
is the community format for storing them in a chunked, cloud-friendly way that viewers such as napari and Vizarr
can open. Getting the metadata exactly right is fiddly. ome-zarr-io handles it for you, so you can spend your
time on the analysis instead of the file format.
ome-zarr-io writes NumPy or Dask arrays as OME-Zarr 0.5 images with axes, units, pixel sizes, multiscale pyramids, channels and segmentation labels, and arranges such images into high-content-screening plates. It also reads images back and validates images and plates against the OME-Zarr 0.5 schemas, from Python or the command line.
Installation
pip install ome-zarr-io
Quick start
import numpy as np
from ome_zarr_io import Writer, Reader, validate
image = np.random.randint(0, 255, size=(2, 16, 256, 256), dtype=np.uint8)
Writer(
path="example.ome.zarr", image=image, dims=["c", "z", "y", "x"],
axis_units={"z": "micrometer", "y": "micrometer", "x": "micrometer"},
scale_transformations={"z": 0.5, "y": 0.2, "x": 0.2},
channels={"DAPI": {"color": "0000FF"}, "GFP": {"color": "00FF00"}},
downscale_levels=2, overwrite=True,
).write()
print(validate("example.ome.zarr")) # spec check
print(Reader("example.ome.zarr").get_voxel_size()) # physical pixel size
The same validation is available on the command line:
ome-zarr-io validate example.ome.zarr
Documentation
The full documentation is at https://turku-bioimaging.github.io/ome-zarr-io/:
- Getting started: installation, including remote (URL) support, and the terminology used throughout.
- Guides for reading and writing images, channels, labels, high-content-screening plates, validation and the command line.
- The API reference.
Metadata
Release files for ome-zarr-io 0.11.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ome_zarr_io-0.11.0.tar.gz | 97.9 kB | With provenance | Details for ome_zarr_io-0.11.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ome_zarr_io-0.11.0-py3-none-any.whl | Python 3 | none | any | Details for ome_zarr_io-0.11.0-py3-none-any.whl |
Total release size: 152.1 kB
Release files / ome_zarr_io-0.11.0.tar.gz
| Download URL | ome_zarr_io-0.11.0.tar.gz |
|---|---|
| Size | 97.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c4cf1d7ca8eea8992df4b5981453148d3028ca30f9505ff41ee7ce0ad86fa7f6
|
|
BLAKE2b-256 checksum How to use checksums |
573b6a52a9cd665dbaa30fbf89dcd5044ba8c88339eaaa6154a03de1088839da
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 2, 2026.
Transparency logRelease files / ome_zarr_io-0.11.0-py3-none-any.whl
| Download URL | ome_zarr_io-0.11.0-py3-none-any.whl |
|---|---|
| Size | 54.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c3fbda7d683a6eb2e55437a7c7735a76de70ba79050707e0e93173ee7b439bbe
|
|
BLAKE2b-256 checksum How to use checksums |
c44842e64a5171ff4445e3039b5ee88ce752415c100b17a07d13510e68bdf606
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 2, 2026.
Transparency logSecurity for ome-zarr-io 0.11.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for ome_zarr_io-0.11.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 2, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.