Free, and it never uploads

A LUFS meter that runs in your browser.

A LUFS meter and loudness meter for integrated loudness, true peak and loudness range, measured in your browser. No account, no queue, and the file never leaves this page.

Your file never leaves this browser. There is no upload, no server call and no copy kept. Close the tab and it is gone. Open the network panel and drop a file in — nothing goes out.

Questions

Questions about the checker

Does my file get uploaded?

No. The measurement runs in your browser and the file never leaves your computer. Close the tab and nothing is kept.

Which numbers does this LUFS meter report?

Integrated loudness in LUFS, true peak in dBTP, and loudness range in LU — the same three the master pages report.

Is this the same measurement the mastering uses?

For loudness and range, yes — the same BS.1770-4 and EBU 3342 methods, and the numbers are directly comparable. True peak is oversampled four times here, as the standard defines it, using a windowed-sinc filter rather than the standard’s own filter table — close enough to read as a headroom check, not as a compliance certificate.

What number should I be aiming for?

There is no single right answer, which is why the site publishes what each platform actually states rather than an industry rule of thumb. Most of them publish nothing at all.

Why is my true peak above zero?

A sample peak under full scale can still overshoot between samples, and a lossy encoder adds more of that on decode. A peak meter does not show it.

Before you upload anywhere

Where your mix sits before you upload it.

LUFS · dBTP · LU

What LUFS, true peak and LRA mean

Integrated loudness (LUFS)
how loud the whole track is
True peak (dBTP)
the highest level, including between samples
Loudness range (LU)
the distance between the quiet parts and the loud parts

Integrated loudness

One number for the whole track, weighted the way hearing works rather than the way a meter does, with the silence between sections gated out. It is what streaming services use to decide how far to turn your track up or down, which is why it is the number worth aiming at.

True peak

A digital file only stores levels at each sample. Reconstructing the waveform for playback — or encoding it to MP3 or AAC — produces peaks between those samples, and those are what actually clip. A track can read 0.0 dBFS at every sample and still distort on a phone. Leaving a decibel of true-peak headroom is what prevents that.

Loudness range

How much distance is left between the quiet parts and the loud parts across the whole track. Very low numbers usually mean heavy limiting. Very high numbers can mean the arrangement has not been controlled yet. There is no correct value.

How this tool measures

Integrated loudness follows ITU-R BS.1770-4: K-weighting, 400 ms blocks at 75% overlap, an absolute gate at −70 LUFS and a relative gate 10 LU below the ungated mean. Loudness range follows EBU Tech 3342 — 3-second windows, a 20 LU relative gate, and the spread between the 10th and 95th percentiles.

True peak is oversampled four times, which is how BS.1770-4 defines it, through a 32-tap windowed-sinc filter per phase rather than the standard’s own filter table — so treat it as a headroom check rather than a compliance certificate. Checked against ffmpeg’s ebur128 meter on the same audio, including hard-clipped noise that peaks 7.1 dB between samples, this page reads within 0.25 LU on integrated loudness and to the reported decimal on true peak.

Files are decoded by your browser at 48 kHz, so a 44.1 kHz file is resampled before measurement. Which formats decode at all is your browser’s decision: WAV and MP3 work everywhere, FLAC, AIFF and M4A do not.