Why Do This in Your Browser?
Loudness normalization is one of the genuinely useful audio tasks that almost every distribution platform now mandates. Spotify normalizes to -14 LUFS; Apple Music to -16 LUFS; YouTube to -14 LUFS; broadcast (EBU R128) to -23 LUFS. Submitting content above those targets gets it automatically reduced, often with subtle artifacts; submitting below leaves listeners reaching for the volume knob.
FFmpeg's `loudnorm` filter implements EBU R128 two-pass normalization — the broadcast standard. Pass one measures the input's integrated loudness, peak, and dynamic range; pass two applies the corrections to land precisely at the target LUFS. The browser version runs both passes locally, with the same math as desktop FFmpeg.
How It Works
Drop a file and pick a target. Built-in presets cover the common cases: Spotify (-14 LUFS), Apple Music (-16 LUFS), YouTube (-14 LUFS), EBU R128 Broadcast (-23 LUFS), AES Streaming (-18 LUFS), Voice/Podcast (-16 LUFS, more headroom). Custom mode exposes target LUFS, true peak (default -1 dBTP), and loudness range (default 11 LU).
Pass one runs an analysis. The tool displays measured integrated loudness, true peak, and loudness range — useful diagnostics on the source. Pass two applies the correction. Output sample format matches the input (you can override to PCM 16-bit WAV for archival, or compressed format with separate compression settings).
Tip: Normalize after final mixing — normalization on a partially-mixed file doesn't help if you're going to make more changes later. Combine with the Audio Compressor tool for final delivery — normalize first, compress second. For brickwall safety on the peaks the loudness boost can push past 0dB, follow up with the Audio Peak Limiter at -1dB ceiling.
Common Use Cases
How We Compare
Honest read on free, paid, and self-hosted options for this kind of job: