Skip to main content
AI MUSIC
DETECTOR / LAB

Runs in your browser

Volume Normalizer

Bring a track to a chosen LUFS target under a safe true-peak ceiling, compare before and after, then export a WAV — all of it running in your browser.

Drop a track here to normalize it

or browse for a file on your device

MP3 · WAV · FLAC · AAC · M4A · MP4 · OGG · OPUS · 25 MB max

Want a full loudness breakdown first? visit the Loudness Analyzer.

Nothing leaves your device

Decoding, measurement and export all happen locally, using your browser's own audio engine. Your file never reaches our servers, and closing the tab clears it from memory.

  • No cost
  • No sign-up
  • Runs on-device

What normalizing actually changes

The tool measures your track's integrated loudness using the ITU-R BS.1770-4 algorithm, works out the gap between that reading and your target, and applies that gain uniformly across every sample. Because it's one constant gain change, the relationship between the quietest and loudest parts of the music is preserved exactly.

Headroom is the one complication. Raising a track by 4 dB raises its peaks by 4 dB too, and if those peaks were already near full scale, the result would clip. The two modes exist specifically to handle that, and the tool reports the gain it actually applied along with before-and-after measurements, so you can see exactly what happened instead of just trusting a progress bar.

Which LUFS target to pick

Go with -14 LUFS for Spotify, YouTube and most streaming platforms, -16 LUFS if you're targeting Apple Music's Sound Check, and -23 LUFS for European broadcast delivery under EBU R128. Podcasts typically land around -16 LUFS for stereo and -19 LUFS for mono.

For a batch of tracks that need to sit at a consistent level — a DJ folder, a playlist, a set of interview recordings — which target you pick matters less than applying the same one across the board. Consistency is what counts.

  • -14 LUFS: Spotify, YouTube, Amazon Music, Tidal
  • -16 LUFS: Apple Music Sound Check, stereo podcasts
  • -19 LUFS: mono spoken-word podcasts
  • -23 LUFS: EBU R128 broadcast delivery

Why a -1 dBTP ceiling is the safe default

A digital file can reconstruct into an analogue waveform that peaks higher than any individual stored sample suggests. Lossy encoding makes this worse: an MP3 or AAC made from a file already brushing 0 dBFS routinely overshoots, and that overshoot turns into audible distortion on playback.

Keeping a -1 dBTP ceiling costs nothing you can hear and removes the problem outright. The normalizer defaults to it, enforces it in both modes, and never lets a sample exceed it in the exported file.

Common questions

  • It measures your track's perceived loudness and applies a single gain adjustment so the whole file reaches your chosen target. It doesn't re-compress or remaster anything — the balance between loud and quiet sections stays as it was, unless you deliberately turn on the limiter mode.

You might also need