Audio Normalizer for recordings that drift
One interview is quiet, the next is loud, and the third clips. Normalization gives every file a predictable level without you touching a fader. Pick how the level is measured, choose a target, export.
The Audio Normalizer raises or lowers a track to a target level, either by its peak or by its average loudness, and protects against clipping. It measures the file first and shows both the measurement and the gain before you export.
Every platform has a target
Loudness is not the same as peak level. A file can peak at −1 dBFS and still feel quiet, because most of its energy sits low. Streaming services measure the average and turn louder files down, so pushing past the target buys nothing.
Normalize a file in three steps
Drop the audio
The tool reads the peak and the average level before it changes anything.
Pick a mode and target
Peak for a single file, average for a set that should feel equally loud.
Export
MP3 for delivery, WAV if the normalized file will be edited further.
Which target where
| Destination | Target | Notes |
|---|---|---|
| Spotify / YouTube | −14 LUFS | The platform turns louder files down |
| Apple Music | −16 LUFS | Slightly more dynamic |
| Podcast apps | −16 LUFS | Speech stays comfortable |
| Voice assistant | −16 to −20 LUFS | Playback happens close to the ear |
| Broadcast (EBU) | −23 LUFS | Legally defined in many countries |
| Single file, no platform | Peak −1 dBFS | Simple and safe |
Volume questions, answered
Does normalization change the sound?expand_more
Peak or average?expand_more
Why did the tool boost by only a few dB?expand_more
Is this compression?expand_more
Does it work on video?expand_more
Normalizing Volume Without Squashing the Life Out of It
Normalization is the least glamorous audio process and one of the most useful. It answers a simple question: how loud should this file be? Without an answer, every export becomes a guess, and every playlist becomes a volume-knob workout.
Peak is not loudness
The peak is the single highest sample in the file. It tells you whether the file will clip, not whether it will feel loud. A sparse recording with one loud door slam can peak at −1 dBFS and still be too quiet for a podcast. That is why peak normalization is safe but sometimes unsatisfying.
Average loudness looks at the whole file. Two files normalized to the same average feel equally loud to a listener, even if their peaks differ. This is the measurement streaming platforms use when they decide whether to turn a track down.
LUFS in one paragraph
LUFS is a loudness unit that approximates how the ear weighs frequencies. Spotify, YouTube and TikTok normalise to around −14 LUFS; Apple Music and most podcast hosts sit near −16. Broadcast in Europe often targets −23. If you deliver above the platform target, the platform simply reduces the level — you spent headroom for nothing.
Headroom and the no-clip option
Two rules keep normalization clean. First, leave at least 1 dB below 0 dBFS; true-peak meters can read higher than sample peaks. Second, when raising an average level, watch the loudest moment: it may reach the ceiling long before the average reaches the target. The no-clip option chooses the smaller of the two gains, which is why a file with a single loud transient may end up quieter than expected.
Normalization is not compression
Normalization multiplies every sample by the same number. Compression changes the level over time, making quiet parts louder relative to loud ones. If a recording has a wide dynamic range and the quiet parts are lost, normalization alone will not fix it; you need compression or a limiter. The loudness booster is the tool for that.
Where it fits in a workflow
Normalize after editing, not before. Cuts, fades and EQ all change the peak level, so a file normalized first will not stay at the target. Finish the edit, then normalize, then export. If the file goes to a platform, normalize to the platform target and stop.
Keep the original. A normalized file is a delivery copy, not a master.
More free audio tools
fact_checkQuick facts
- Peak normalisation moves the loudest sample to the target and leaves the dynamics alone, while loudness normalisation moves the average level and can change the relation between quiet and loud parts.
- Broadcast works at −23 LUFS under EBU R128, while the big streaming services normalise near −14 LUFS.
- EBU R128 normalises broadcast audio to −23 LUFS, which is why a commercial CD at −9 LUFS sounds loud until a platform turns it down.menu_bookEuropean Broadcasting Union
- LUFS is a weighted average over time, unlike a peak meter: a single loud drum hit does not raise the integrated loudness much.menu_bookITU
- 44.1 kHz, 16 bit, stereo means 44,100 samples × 2 channels × 2 bytes each second: 1411 kbit/s, or about 10 MB per minute.menu_bookMicrosoft Learn
helpQuestions people ask
What is the difference between peak and loudness normalisation?expand_more
What loudness level should I normalise to?expand_more
Can normalisation damage audio?expand_more
hubWhat this page is about
- Loudness (LUFS)open_in_new
The perceived level of a track measured in LUFS, defined by ITU-R BS.1770 and used by EBU R128 for broadcast normalisation.
- WAV (RIFF)open_in_new
An uncompressed container from Microsoft and IBM built on RIFF; CD-quality stereo at 44.1 kHz and 16 bit needs 1411 kbit/s.
- MP3open_in_new
A lossy audio format from MPEG-1 Audio Layer III, developed at Fraunhofer IIS, that removes sounds the ear is unlikely to notice.
- Web Audio APIopen_in_new
The W3C API that builds an audio graph in the browser and can render it faster than real time with an OfflineAudioContext.
library_booksOfficial sources cited on this page
- R 128: Loudness normalisation and permitted maximum level of audio signalsEuropean Broadcasting Union
- Recommendation ITU-R BS.1770: Algorithms to measure audio programme loudnessITU
- Resource Interchange File Format (RIFF)Microsoft Learn
- MP3 — the audio coding format developed at Fraunhofer IISFraunhofer IIS
- Web Audio APIW3C
Continue with the same file
Each of these opens what the tool above produces. Use “Use in another tool” under the result to carry the file over — it moves from tab to tab inside your browser, never to a server.
Switched-off tools are not listed here: only what works right now.