Build with mzPeak
Everything around mzPeak is open source — a specification, reference libraries in seven languages (read across all; Rust and C# also write), converters, a conformance validator, an in-browser viewer, and third-party readers. Pick a starting point — or see Why mzPeak for the mzML comparison, a quickstart, and the full read/write support matrix.
The canonical format — JSON Schemas, controlled-vocabulary rules, and prose.
Libraries across seven languages — Rust (reference, mzpeak_prototyping), Python, R, C#, JavaScript/TypeScript, C++, and Java — all on Apache Arrow / Parquet. All read; Rust and C# also write (Java write is a proof-of-concept).
Open any .mzpeak directly in your browser, streamed over HTTP — no upload, no backend. Inspect spectra and chromatograms for LC-/GC-MS runs, or render ion images and click pixels for MS-imaging (MSI) datasets.
A language-independent, profile-driven conformance validator. Check a file in the browser — paste an HTTPS or s3:// URL, or upload a .mzpeak (up to 1 GB) — or from the CLI: mzpeak-validate file.mzpeak.
Readers
Tools that read mzPeak archives straight into other ecosystems.
Reads mzPeak imaging archives — chunked and point layout, position columns, position_offset, Bruker regions, embedded images — and writes SpatialData for spatial-omics analysis. Thyra marks its mzPeak input as experimental. By M4i, Maastricht University.
On the roadmap: a direct vendor RAW → mzPeak path (e.g. inside ProteoWizard
msconvert) so every vendor format converts in one step, embedding the original acquisition method as provenance.
See the viewer in action on the Try it page.
Building a tool that reads or writes mzPeak? The format is language-independent — start from the specification and validate against the mzPeak Validator. Contributions and feedback are welcome via the HUPO-PSI repositories.