How to normalize audio volume to a LUFS target
Streaming platforms play every track at roughly the same loudness — about -14 LUFS on Spotify and YouTube, about -16 on Apple Music — and turn louder tracks down without asking. A podcast recorded at -26 LUFS plays quietly next to one recorded at -16, and a master at -8 LUFS gets turned down anyway. Normalizing before you publish means the platform plays your audio the way you made it, instead of deciding for you.
To use it:
- Drop your audio files — MP3, WAV, FLAC, M4A, AAC, OGG, Opus or AIFF, up to 5 at a time. Each file is measured automatically: integrated loudness in LUFS, true peak in dBTP and loudness range, shown on its card before anything changes.
- Pick a target. Streaming (-14 LUFS) for music and video, Podcast (-16 LUFS) for spoken word, Broadcast (-23 LUFS) for EBU R128 work, or a custom level from -30 to -6 LUFS with your own true-peak ceiling.
- Pick a batch mode. Per file normalizes every file to the target on its own. Album applies one gain to the whole batch, so an album or a set of takes keeps its relative balance — the loudest track lands on target and the rest follow.
- Press Normalize audio. The engine normalizes each file, then re-measures the finished file — the after numbers on the card are measured from the actual download, not from the normalize pass's own estimate. Download files one at a time, or all of them as a ZIP.
What makes this normalizer different
The pages that top the results for this search are good tools, and most of them do one part of the job well. Pi7's audio normalizer batches files and re-measures them, but only exports the format you put in. AudioUtils exports MP3 only and caps files at 20 MB. GrepCut and MixMasterAI export WAV only. KlipTools takes one file at a time. This page combines the parts the others split up: batch normalization with per-file before-and-after LUFS measured from the actual output, an album mode that keeps a batch's relative balance, both WAV (lossless 16-bit PCM) and MP3 (192 kbps) output, a built-in sample tone so you can try it without a file, and a live network-request counter so you can verify the privacy claim yourself. No file-size cap below 200 MB per file, no account, no daily limit.
When is this the right tool?
Whenever audio from different sources has to play at the same loudness: podcast episodes recorded on different days, music tracks for a playlist or a release, voiceovers cut in different sessions, video clips for one channel, or a batch of samples for a sound library. If the files belong together as a set, use album mode; if they are unrelated, use per-file mode.
Honest limitations
Single-pass accuracy is about ±1 LU
Per-file mode uses ffmpeg's loudnorm in one dynamic pass, which is accurate to roughly ±1 LU. The after number on each card is re-measured from the finished file, so it is the real result — and when the true-peak ceiling caps the gain, the file lands below target instead of clipping, and the card says so.
MP3 output is lossy
MP3 output is libmp3lame at 192 kbps — small and playable everywhere, but lossy. If the file is a master you will edit again, download WAV instead. WAV output is 16-bit PCM; a 24-bit source is dithered down to 16-bit by the encoder.
It is not a compressor or a limiter
Album mode applies one static gain and nothing else. Per-file mode's loudnorm pass can gently limit peaks to hold the ceiling, but it does not compress dynamics, remove noise, or fix clipping that is already in the recording. A file that clips at the source still clips after normalizing — it just clips quieter.
Long files take a while
In-browser processing runs at roughly real-time speed, and each file goes through three passes (measure, normalize, re-measure). A 2-hour file is the limit, and anything over 30 minutes warns you first. For a whole library, a desktop normalizer will be much faster.
Silence measures as nothing
A file that is mostly silence, or a file with a long quiet intro, measures by its gated loudness — near-silence is discarded by the measurement, so the number reflects the audible part. A fully silent file has no loudness to measure and is refused with an explanation instead of a made-up number.
Surround and odd formats
Stereo and mono are fully supported. Multichannel files keep their channels in WAV output; MP3 output is stereo. Video files are not accepted — strip the audio to MP3 or WAV first, or use a video converter.