What -16 LUFS Actually Means for Your Podcast

A listener switches from someone else’s show to yours and reaches for the volume knob.
That is not a content problem, it is a loudness problem, and it has a precise fix that takes
about a minute.

Loudness is not volume

Peak level tells you how close the loudest instant comes to distortion. It says nothing
about how loud something sounds. A recording can peak near the ceiling and still feel
quiet, if the loud moments are rare and everything between them sits low.

LUFS measures perceived loudness across the whole programme, weighted roughly the way
human hearing works. That is why platforms specify LUFS and not peak: it is the number that
predicts whether a listener will reach for the knob.

The numbers worth knowing

• −16 LUFS — the usual target for stereo podcast delivery.
• −14 LUFS — where YouTube and the music streaming services
  normalise to.
• True peak — a separate ceiling, typically −1.5 dBTP for
  podcast and −1.0 dBTP elsewhere, that the audio must not exceed after conversion.

Publish louder than the target and the platform turns you down anyway. Publish quieter and
some platforms leave you quiet. Hitting the number is the whole job.

Why true peak sometimes wins

This is the part most guides skip, and it is the reason a masterer sometimes tells you
“that is as loud as it goes”.

Loudness only rises by adding gain, and gain raises the peaks by exactly the same amount.
If your recording is quiet and spiky — a big dynamic range between the loudest
consonants and the average level — reaching −14 LUFS can require more gain than
the peak ceiling allows. Something has to give: either the ceiling breaks and the audio
distorts, or you stop short of the target.

Stopping short is the correct answer. A file at −15 LUFS that respects the ceiling
sounds fine. A file at −14 with clipped peaks sounds broken, and no platform will fix
it for you.

Two-pass normalisation, and why one pass is not enough

A single-pass loudness filter guesses as it goes. On uneven material it drifts, and the
finished file lands somewhere near the target rather than on it.

Two-pass measures the whole file first, then applies a correction calculated from those
measurements. The difference is not academic: on quiet or uneven recordings a single pass can
miss by several decibels, which is exactly the error you were trying to remove.

Better still is to measure the result afterwards and correct once more if it
landed outside tolerance. That is the difference between “we applied a loudness filter” and
“the file measures −16.1 LUFS”, which is a claim you can check.

The rest of the mastering chain

Loudness is one step of four, and the order matters.

1. High-pass first. Cutting below about 80 Hz removes desk thumps, chair
   creaks and mains hum. Do it before measuring, or that rumble eats headroom you needed.
2. Trim the silence. Recorders run before you speak and after you stop.
   Cut the dead air at the ends, and leave the pauses inside the conversation alone —
   they are the rhythm of the thing.
3. Normalise. Measure, then apply.
4. Fades last. A fade applied before normalisation gets partly undone by
   it. Half a second in and a second out is a sensible default.

What mastering cannot fix

It sets the level, tidies the ends and protects the peaks. It does not remove room echo,
repair clipping already baked into the recording, balance two hosts recorded on separate
tracks, or make a bad microphone sound good. Mastering is the last step, not a rescue —
and if the recording has steady background noise, clean that before you normalise,
not after.

A workflow that holds up

Record with headroom, aiming for peaks around −6 dB rather than as loud as possible.
Edit. Remove steady noise if there is any. Then master: high-pass, trim, normalise to
−16 LUFS for the podcast feed, fade. If the same audio also goes to YouTube, run it
again at −14 rather than uploading the podcast master and hoping.

Check the output number. If a tool cannot tell you what the finished file measures, it is
asking you to take its word for it.