Universal workbench

mzML to mzML metadata JSON

Create mzML metadata JSON from mzML locally, with no upload or account.

Device-onlyNo uploads. Ever.
Pipelines, branches, presets, naming, and detailed controls
Display
Help me choose the best output Suggested: mzML metadata JSON

Recommendations use the registered target format and tested fidelity classification. They never inspect or upload your content.

01Input
Drop files or a folder hereChoose mzML files or a folder — batch input is welcome
or paste content
276 chars · 1 lines · 276 B
02Configure & run
mzMLmzML metadata JSON
structural conversion · single or batch
Conversion preflightSize, memory, engine, execution, and fidelity before you start
Input
276 B
Estimated peak memory
16 MiB
On-demand download
No large engine download
Execution
Responsive local worker
Fidelity
No lossy step declared
What to providePaste mzML content or drop a matching file.What you’ll getProduces previewable mzML metadata JSON text and a correctly named download.
Output naming & batch behavior
Exampleoutput.mzml.json
Pipeline 1 linear · 0 branches
Why use A → B → C?

A pipeline feeds each result directly into the next compatible converter. Use one when the destination needs an intermediate representation or when you want to inspect and normalize that middle format.

  • JSON → CSV → XLSX turns records into rows before building a workbook.
  • Markdown → HTML → DOCX resolves markup before creating a document.
  • SVG → PNG → PDF intentionally flattens vector artwork before placing it on a page.
Only type-compatible next steps are offered. Lossy steps are marked before you run them.
1mzML to mzML metadata JSONstructural
Processing happens locally. Your file bytes are never sent anywhere.
About this conversion

How to convert mzML to mzML metadata JSON

Before you start

Paste mzML content or drop a matching file.

Accepted: .mzml · application/mzml+xml
  1. Paste valid mzML content, choose files, or drag them onto the drop zone.
  2. Confirm the detected format. Mixed-format batches are flagged before conversion.
  3. Select “Convert on this device.” Produces previewable mzML metadata JSON text and a correctly named download.

How this converter behaves

Biological, molecular, genomic, matrix, and binary scientific metadata are parsed into bounded typed records and serialized locally without executing content.

What happens to your data?

The conversion engine runs in this browser tab. OmniCastConverter has no upload API and never sends your content, file name, or converted result to a server.

Fidelity and limitations

This route is classified as structural. The converter preserves meaning and structure supported by both formats.

  • Scientific records are validated and normalized, but domain-specific annotations and application conventions may require expert review.
  • This route inspects bounded metadata only. Scientific arrays, pixels, point records, spectra, and other bulk payloads are not decoded or rewritten.

Try a valid example

The “Use example” action in the workbench loads this exact input. Produces previewable mzML metadata JSON text and a correctly named download.

<?xml version="1.0"?><mzML xmlns="http://psi.hupo.org/ms/mzml" version="1.1.0"><run id="local-run"><spectrumList count="1"><spectrum id="scan=1" index="0" defaultArrayLength="0"><cvParam accession="MS:1000511" name="ms level" value="1"/></spectrum></spectrumList></run></mzML>