Method / tool

MoBIE

Fiji plugin for interactive exploration and cloud-hosted sharing of multi-modal big image data — renders terabyte-scale OME-Zarr and N5 volumes alongside segmentations, annotations, and paired omics tables without requiring a web server.

The problem — Processed light-sheet, CLEM, and spatial-omics datasets routinely exceed single-machine RAM. Sharing them reproducibly across labs — or between acquisition and analysis teams — requires either a running web server or a file format that handles multi-scale pyramids and remote access natively. Neither condition is routinely met in biology labs.

What it is / how it works — MoBIE (Multimodal Big Image Explorer) is an open-source Fiji plugin built on BigDataViewer and ImgLib2. It reads chunked multiscale image data (OME-Zarr, N5, or HDF5) directly from local disk or cloud storage (S3, Google Cloud) and renders arbitrary pyramid levels interactively without loading the full volume. A JSON project specification encodes views — predefined combinations of image layers, segmentation overlays, table annotations, and display settings — that can be shared as a URL or file, making a complex data exploration fully reproducible. Paired tables (e.g. morphology measurements per segmented cell) are loaded alongside images, enabling click-to-select workflows where a cell in the image highlights its row in the table.

Where it fits — MoBIE is an exploration and QC tool at the boundary of the preprocess and segment stages in light-sheet and volumetric workflows. It is the inspection layer: after ingest and stitching produce a multiscale OME-Zarr store, MoBIE is how an analyst verifies alignment seams, reviews segmentation quality on representative z-planes, and communicates findings with collaborators — all without moving the data. It also serves developmental biology and CLEM datasets where correlated modalities must be overlaid precisely.

Where it breaks — MoBIE is a viewer; it does not run batch processing or export analysis. Very large segmentations or dense annotation tables can slow interactive rendering. Cloud access is only as fast as bucket permissions and network latency allow — poorly configured S3 ACLs are a common setup failure.

MoBIE shares a *view* of data, not a guarantee of its quality. Reproducible views do not substitute for rigorous QC of the upstream ingest and stitching steps that produced the volume being viewed.

References

Appears in these notes

  • Data Standards and Scalable StorageThe OME data model and OME-NGFF/OME-Zarr exist because a microscopy image without a shared data model and a chunked, cloud-native layout is neither interpretable nor analyzable at scale. Format is not plumbing — it decides whether a petabyte dataset can be opened at all.
  • Why Interoperability Matters in MicroscopyA microscopy pipeline is always several tools in sequence, so the seams between them — file formats, metadata, coordinate conventions — decide whether the pipeline composes or quietly corrupts. Open standards like OME-Zarr/NGFF turn hand-offs from lossy conversions into clean interfaces, and avoid lock-in to any one vendor or tool.

← Back to the constellation