← All apps

mzML Centroider

Turn profile-mode mzML into centroided mzML. Drop as many files as you like; they are processed in parallel and come back as standard, indexed mzML. Everything runs in your browser — your files never leave your machine.

Starting workers…

Settings

Others are copied unchanged.
Auto: apex height for Orbitrap/FT/TOF, summed signal for ion trap scans.
Drop peaks at or below this. 0 keeps all.
Noise = median positive intensity of the scan. 0 = off.
Array precision is kept as in the input.
Drop profile mzML files here
or click to choose · try an example

Batch

Files
0
Done
0
Failed
0
Spectra centroided
0
Size
—

Files

Output fileStatusSpectraCentroided Points → peaksInOutTime

How peaks are picked. Each profile scan is reduced to its local maxima. On high-resolution scans (Orbitrap, FT-ICR, Astral, TOF) the apex is refined with a 3-point Gaussian fit. Checked against Thermo's own centroiding (msconvert vendor peak picking) on 27 runs from 15 Orbitrap models, including Astral, this reproduces Thermo's peak lists to within 0.04% in peak count, with a median m/z difference under 0.02 ppm and intensities within 0.6%. Ion trap and quadrupole scans, recognized from the mzML's analyzer information, are smoothed before picking and report the summed peak signal; they approximate Thermo's ion-trap centroids (about 97% of peaks agree).

What changes in the file. Selected profile spectra are rewritten as centroid spectra (MS:1000127) with new m/z and intensity arrays and updated base peak and m/z range. Spectra that are already centroided, chromatograms, and all metadata are copied unchanged. A peak picking step is recorded in the file's data processing list, and indexed mzML gets a rebuilt index and checksum. Extra binary arrays on a centroided spectrum (other than m/z and intensity) are dropped, since they no longer line up with the peaks. MS-Numpress encoded spectra are left as they are.