This release is a pre-release and may not be stable for production use.
Next generation file format IO — a Python library for OME-Zarr bioimage analysis.
ngio is built for OME-Zarr, a cloud-optimised format that stores large, multi-dimensional microscopy images and their metadata in an efficient, scalable way. It provides an object-based API for opening, exploring and manipulating OME-Zarr images and high-content screening (HCS) plates, along with labels, tables and regions of interest (ROIs) for extracting and analysing specific regions of your data.
Installation
To install ngio, use whichever package manager you already work with — it is published on both PyPI and conda-forge.
pip install ngio # pip
uv add ngio # uv project (or: uv pip install ngio)
pixi add ngio # pixi, from conda-forge (--pypi for PyPI)
mamba install -c conda-forge ngio # mamba/conda
Then work through the quickstart.
Key features
- Object-based API — open, explore and manipulate OME-Zarr images and HCS plates; derive new images and labels with minimal boilerplate.
- Tables and ROIs — tight integration with tabular data, extensible table schemas, and measurements stored alongside the image.
- Scalable processing — five iterators (image processing, segmentation, masked segmentation, feature extraction, object detection) that scale a per-region function from one ROI to a full plate: serial, threaded, multi-process, batched for neural networks, or split across cluster jobs — with halos for seamless tiles and stitching for objects split across tile boundaries.
- Remote stores — stream from S3 and other fsspec-backed sources, with a configurable IO retry policy.
- Supported OME-Zarr versions — ngio supports OME-Zarr v0.4 and v0.5, backed by either Zarr v2 or v3 storage. Support for v0.6 and later is planned.
Versioning
ngio follows semantic versioning: from 1.0 onwards the public API
is stable, and breaking changes are reserved for major releases. The one carve-out is
the structural protocols — MapperProtocol, TransformProtocol, and MergePolicy:
implementing them pins you to the documented contract, which minor releases may extend
with optional members.
Documentation
Full documentation, including guides, tutorials and the API reference, is at biovisioncenter.github.io/ngio. The tutorials' worked examples are executed when the site is built, so the code and the output you read are what actually ran.
Citing ngio
If ngio contributes to work you publish, please cite it. See
CITATION.cff for the
current citation metadata.
Project
ngio is developed at the BioVisionCenter, University of Zurich, by @lorenzocerrone and @jluethi. It is released under the BSD-3-Clause licence, and developed in the open on GitHub — issues and contributions welcome.
Metadata
Release files for ngio 1.1.0a2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| ngio-1.1.0a2.tar.gz | 833.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ngio-1.1.0a2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.2 MB
Release files / ngio-1.1.0a2.tar.gz
| Download URL | ngio-1.1.0a2.tar.gz |
|---|---|
| Size | 833.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cf7fa24e72b493b4980edf8477f349be48edb2402e8fc8a99135ce511ebc3569
|
|
BLAKE2b-256 checksum How to use checksums |
6fd6adba6ba4a92173bb2171159e81916aa443d5a2a2990bbd673c32c9944008
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 21, 2026.
Transparency logRelease files / ngio-1.1.0a2-py3-none-any.whl
| Download URL | ngio-1.1.0a2-py3-none-any.whl |
|---|---|
| Size | 367.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
68d9a9ee0caad97f0a943ddfab84ace819dcf9134e3e4b049f59dc2de5fb51b4
|
|
BLAKE2b-256 checksum How to use checksums |
523f589ecf3bdc80262daff6adaa1b80bf305e3396fbada0f9f1ff2d7f648042
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 21, 2026.
Transparency log