Zarr Python

Zarr-Python 3 gives you chunked, compressed N-dimensional arrays that live on disk, in memory, or in cloud object storage. If you're juggling multi-terabyte scientific datasets with NumPy, Dask, or Xarray, this is how you avoid loading everything into RAM at once. The chunking strategy matters more than you'd think: a (200, 200, 200) array can be 65× faster to read if you align chunks with your access pattern. Version 3.2+ defaults to the new Zarr format, drops Python 3.11 support, and plays nicely with S3 and GCS through fsspec. The skill covers compression codecs, sharding for when you've got millions of tiny chunks, and the difference between vindex and oindex that you'll inevitably need.

skills.sh installs: 2K
GitHub stars: 56.6K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add k-dense-ai/scientific-agent-skills --skill zarr-python --agent claude-code

Installs into .claude/skills of the current project.

Files

Zarr Python

When to use

Use for chunked scientific arrays, hierarchical stores, codecs, sharding, partial reads, cloud object storage, and NumPy/Dask/Xarray interoperability. This community guide targets Zarr-Python 3.4.0, released 2026-09-15, with Python 3.12+. The package version and on-disk format are separate: this release reads/writes formats 2 and 3; new arrays default to format 3. Keep downstream packages that require zarr<3 in their own environments.

Install

uv pip install "zarr==3.4.0" "numpy==2.5.3"
# Optional remote backends and migration CLI:
uv pip install "zarr[remote,cli]==3.4.0" "fsspec==2026.9.0" "s3fs==2026.9.0" "gcsfs==2026.8.1"

Commit the project's resolved lockfile. Optional integration versions exercised here: Dask 2026.8.0, Xarray 2026.9.0, h5py 3.16.0, NumCodecs 0.17.0, obstore 0.11.1. Local examples below and in the references use tiny synthetic arrays; remote snippets are illustrative and require a real authorized store. This does not establish cloud permissions, production throughput, or compatibility of every downstream reader.