Publish a store

A store is a directory of static objects. Upload it to an HTTPS host, keep its relative paths intact, then share the root URL. No application server is required.

Choose the prefix and cache policy

For an immutable release, use a new versioned prefix and long-lived caching. Upload chunks first, child metadata second, and the root zarr.json last. The root then marks a complete store. Avoid requesting the final URL before the upload finishes.

If you plan to append, use short cache lifetimes for metadata and objects that can change. A CDN rule must respect those origin headers. The append guide and hosting recipes explain the object classes and upload order.

Check the live URL

chronozarr doctor https://your-host/my_store

Browser access needs CORS. Sharded stores also need correct byte-range responses; missing objects must return 404, rather than an HTML fallback. Doctor checks the layout, HTTP behavior, and decoding and reports failures separately from advice.

Open the viewer

Use your URL as the store parameter:

https://chronozarr.org/demo/?store=https://your-host/my_store

The reader and renderer run in the browser. The host serves data objects.

Follow the detailed recipes for R2, S3 with CloudFront, GCS, or Source Cooperative.