What Does LUFS Mean for Podcast? Mastering Integrated Loudness, Explained

What LUFS Measures

Forget about the meters on your DAW, because podcast measurements are very different. LUFS stands for Loudness Units relative to Full Scale – but the scale here isn't tied to levels you might set a limiter to. It's a way to calculate average playback level, measured over the whole podcast duration.

[TO VERIFY: A primary-source definition of short-term LUFS and momentary LUFS from the standards body itself; the available material here did not provide a clean primary citation for those meter modes.]

This means even if only a tiny part of the podcast is loud, it might still end up normalised when uploaded. So creators fall into the trap of turning everything up, just getting tall peaks, but still delivering a quiet file. That’s why the crucial figures for podcast delivery are integrated loudness and true peaks.

The Podcast Target

Podcast guidance defines an integrated target, usually around -16 LUFS for a stereo file and -19 if it’s mono/mono. These average levels are promoted across the whole podcast.

Each podcast platform may also send back a true-peak ceiling. Any ingest MP3 or AAC needs to stay under -1.0 dBTP, never clip. This provides a safety net for high peaks after normalization by a server.

In summaries across secondary guides, Spotify is cited at -14 LUFS as a different target level to -16 on Apple. The rules for tolerance show that podcasters need all the rounded down, tight controls they can keep.

Why Peak Loudness Is Not Enough

Many audio engineers learned to mix based on loudness peaks – but this is the wrong approach for podcast delivery. Podcast loudness doesn't just get judged by that one peak, it is gauged by an average level over the episode. That's why cross-fading between an overly-loud podcast and another one, peaking just as loud, sounds like the playing-field has tilted.

Avoid that problem by remembering that servers query a file's integrated average on upload, not the overall peak. They then rework that baseline, for consistent loudness, platform-wide.

What Creators Do In Practice

There is a predictable workflow of podcast normalization. Firstly, process the audio, making sure the phase coherence stays intact. Then, use compression on the signal to meld together the loudest and quietest areas.

Next, set a limiter at the output, adjusting so the peak dots hit the zero mark. After that, normalize the file to -16 LUFS, then aim for an integrated readout matching the reference guide. The full file needs to be rendered, checked for output levels, then measured: happening last, after the final rendering.

Where The Numbers Come From

The EBU's integrating loudness standard R128, released in 2010, sets a prescriptive baseline for this format of podcast controls. It has been picked up by Apple for the Podcasts server, netting a recommended podcast server loudness target of -16 LUFS with a ±1 LU tolerance.

That EBU approach is a direct adaptation of the much older proposals in ITU R 1770, from 2006 – refining the method used to query average volume. All these standards and guidance can lead to very different real-world targets across platforms.

Edge Cases And Caution

This podcast world of 'perfect loudness' lingo can trip podcasters up. To avoid over-normalization, creators need to recognize that files encoded in mono see a different target to stereo files. The reason why? Those mono files can have louder averages, long-term, on replay, so podcasters need to aim much lower to equate to the expected server result.

To illustrate, the Apple recommended setting of -16 LUFS integrated stereo is often paired with -19 LUFS as an integrated mono target. That's why podcasters go through the motions, here where the mono setting reads appropriately lower.

It's also not perfect. Spotify is given a -14 LUFS as their common reference point, in the secondary summaries of their platform guidance. Make sure to check for that, because, per these summaries, Apple's recommended headroom is a whole 2 LU louder.

Normalizing For Sound Consistency

There is no single universal podcast integration target, but matching the server rules is how you unlock reliable listener volume. Podcasters may get caught out, normalizing a file too high, then delivering listeners a quiet file. It's the integrated loudness, not the tall peaks, which podcast servers judge. Even matching the delivery limits to audio heads is not enough: deliver the right average.

This is how podcasting normalizes the story.

—-