If you’ve ever exported an episode that sounded fine on your headphones but came out much quieter than other shows, loudness normalization is the missing step. Here’s the shortest useful explanation of the three numbers involved.
LUFS: perceived loudness
LUFS measures loudness the way human hearing perceives it — averaged over the whole program, weighted toward the frequencies we’re sensitive to. It’s a better yardstick than peak level, because two files can have identical peaks and wildly different perceived loudness.
For spoken-word content, a target around −16 LUFS is the widely used convention — it’s the level podcast apps are generally mixed around, so an episode normalized there sits comfortably next to other shows in a listener’s queue. Broadcast television uses a different standard, EBU R128, which targets −23 LUFS; you’ll sometimes see the two conflated online. For podcasts, around −16 is the practical target.
True peak: the safety ceiling
Normalizing raises your audio toward the target, and the loudest instants need somewhere to go. True peak measures the actual maximum the waveform reaches — including the “inter-sample” peaks that appear when digital audio is converted back to an analog signal. Keeping true peak safely below 0 prevents clipping and distortion on playback devices and after lossy encoding to MP3 or AAC.
How far below 0 depends on where the audio is going. Our Podcast Audio Studio pairs each loudness target with the ceiling normally used alongside it: the Podcast preset is −16 LUFS with a −1.5 dBTP ceiling, while the YouTube and Spotify presets are −14 LUFS with −1.0 dBTP.
One honest limitation of any loudness target
Loudness and peak ceiling can pull against each other. Making a file louder means applying gain, and gain raises the peaks by the same amount. On a very quiet or very peaky recording, a −14 LUFS target and a −1 dBTP ceiling cannot both be satisfied — something has to give. Our tool keeps the ceiling, gets as close to the loudness target as the ceiling allows, and tells you when it had to stop short, rather than quietly crushing the audio to hit a number.
Order matters: clean first, normalize second
Loudness normalization raises quiet content. If your recording still has background noise, normalization raises the noise right along with the voice.
We have a measurement for this. On our test file, performing the loudness step inside the noise-removal pass instead of separately afterwards cut the signal-to-noise improvement from +11.1 dB to +2.2 dB, and the residual noise floor ended up at −37.4 dBFS rather than −52.0 dBFS. Run noise removal first, then normalize the cleaned file as a separate step.
What the Podcast Audio Studio does with all this
It applies two-pass loudness normalization to the target you pick with true-peak protection, trims silence from the start and end of the file, and adds a fade at each end. You upload a file, it returns a normalized MP3 or WAV — the numbers above are the whole story of what happens in between.
Do I need to think about this every episode?
No — that’s the point of automating it. What’s worth internalizing is just the order (clean, then normalize) and the reason your episodes should all pass through the same normalization step: consistency across episodes is what listeners experience as “professional”. The full three-step workflow is here.