Tutorials Audio

What's Actually Happening When You 'Normalize' Audio

Intermediate · ~14 min

Overview

'Normalize' is used loosely to describe at least two genuinely different processes, peak normalization and loudness (LUFS) normalization, that can produce very different results on the same file, and understanding the actual mathematical difference explains why a 'normalized' file doesn't always sound as loud as expected.

What You Need

No special equipment required. This is a technical explainer, not a hands-on tutorial

Steps

The simple version: normalization adjusts overall volume to a target

At the simplest level, normalization looks at a specific measurement of an audio file's level and uniformly raises or lowers the entire file's volume so that measurement hits a specific target. The file's internal dynamics (louder and quieter parts relative to each other) stay the same, only the overall level shifts.

What's really happening: peak normalization measures the single loudest instant

Peak normalization looks only at the single loudest instantaneous sample in the entire file and adjusts overall gain so that peak hits a target level (often just below 0dBFS, the digital maximum). It says nothing about how loud the file sounds overall to a human listener, since a file with one brief loud spike and mostly quiet content will normalize to sound quieter overall than a consistently loud file with the same peak.

What's really happening: loudness (LUFS) normalization measures perceived average loudness

Loudness normalization uses a measurement (LUFS, loudness units relative to full scale) that approximates how loud a human actually perceives the file to be on average over time, accounting for the ear's varying sensitivity to different frequencies. This is what streaming and podcast platforms actually use for their normalization, which is why understanding LUFS matters more than peak level for most modern delivery.

Why the difference matters practically

A file that's been peak-normalized to just below 0dBFS can still sound quieter or louder than a different file peak-normalized to the same level, because peak normalization ignores how the perceived loudness accumulates over the whole file. This is exactly why this site's loudness cheat sheet and myth-busting tutorial on loudness both emphasize LUFS targets specifically, not peak levels, for anything being delivered to a modern streaming or podcast platform.

Pro Tips

Check whether your export or streaming target specifies a LUFS loudness target or a peak (dBFS) target. They're measuring genuinely different things and require different tools/settings to hit correctly.
Use a LUFS-capable loudness meter, not just a peak meter, if your delivery platform (most modern streaming and podcast platforms) specifies a loudness normalization target.
Don't assume two files peak-normalized to the same level will sound equally loud. Their average perceived loudness can differ significantly depending on their internal dynamics.

Knowledge Base

What You'll Learn

'Normalization' commonly refers to two different processes, peak normalization (matching the single loudest instant) and loudness normalization (matching average perceived loudness via LUFS), and modern streaming platforms use LUFS specifically, which is why understanding the distinction matters practically.

The Plain-English Version

Peak normalization asks 'what's the loudest single moment, and how do I adjust the whole file so that moment hits my target?' Loudness normalization asks 'how loud does this whole file sound on average to a human, and how do I adjust it so that average hits my target?', very different questions with very different answers on the same file.

The Misunderstanding This Clears Up

People sometimes assume 'normalizing' a file guarantees it will sound appropriately loud on a streaming platform, but if you only peak-normalized rather than loudness-normalized to the platform's actual LUFS target, the platform's own normalization may turn your file down (or up) further than you expected.

Where This Fits

This guide covers one specific part of mixing and mastering. The wider picture. The full mix workflow from gain staging and balance through panning, bus processing, and knowing when to stop, is in Mixing a Full Song: From Rough Levels to Final Bounce, which frames the discipline as a whole and links out to the detailed guides underneath it, including this one. If you are starting from scratch rather than solving a specific problem, read that first and come back here.

FAQ

Q: Why did my normalized podcast episode still get turned down by the platform?
A: You likely peak-normalized (matching the single loudest instant to a target) rather than loudness-normalized to LUFS (matching the average perceived loudness). Most platforms specifically normalize based on LUFS, so a peak-normalized file that exceeds the platform's LUFS target still gets turned down regardless of its peak level.

Q: Which type of normalization should I use for streaming or podcast delivery?
A: Loudness (LUFS) normalization, matched to your specific platform's target level, since that's what modern streaming and podcast platforms actually use to normalize incoming audio. This site's loudness cheat sheet covers the specific targets for different delivery contexts.