How to Normalize a Podcast to -16 LUFS (and Why That Is the Target)

Your episodes sound like they were recorded in different rooms at different volumes, even when they were not. The fix is one number: -16 LUFS, the loudness Apple Podcasts asks for. This guide shows how to get every episode there, and why that target exists.

If you want the short road, drop your file into the loudness normalizer and pick the Podcast preset. The long road below explains what happens under the hood, so you can trust the result — or reproduce it in any tool.

Why -16 LUFS?

Apple Podcasts is the reference directory most podcast apps mirror, and its guidance for stereo episodes is about -16 LUFS integrated loudness, with true peak at or below -1 dBTP. Hit that number and your show sits at the same loudness as the big networks in a listener's queue. Miss it by a lot and the apps adjust you on their own terms. Mono shows are the exception: they need -19 LUFS, for the reason explained in the mono vs stereo guide.

Why -16 and not louder? Podcast listening happens close to the ear, often on the move, and speech needs less loudness to feel full than dense music does. The -16 figure also leaves real headroom: an episode at -16 with natural dynamics has peaks that stay clear of clipping through the MP3 or AAC encode every platform applies. It is a target chosen for speech, on earbuds, in the real world — not an arbitrary line.

It also helps to know what happens at the extremes:

How to Normalize, Step by Step

1. Export your finished mix. Loudness is the last step, after editing, EQ and compression. Export the same format you plan to publish.
2. Measure first. A loudness meter reads the whole file and reports integrated LUFS, true peak and loudness range. Never skip the measurement — you cannot fix a number you have not seen. The LUFS explainer defines each term.
3. Apply the correction. The gap between the measured value and -16 is the gain to apply: a file at -21 LUFS needs +5 dB. A two-pass normalizer does this math itself and uses the measurement to apply one exact, linear gain.
4. Hold the true peak. If gain would push peaks past -1 dBTP, a limiter holds them. Files recorded hot may land slightly off target; a good report says so instead of hiding it. See the true peak guide for why the ceiling matters.
5. Measure again and publish. Verify the finished file reads -16 LUFS (±1) with true peak under -1 dBTP, then upload.

That is the whole method. Everything below is about the cases where the simple path needs judgment.

A Worked Example, Start to Finish

Take a typical episode: a 42-minute interview exported as a stereo WAV. The first measurement reads:

• Integrated loudness: -20.4 LUFS
• True peak: -4.6 dBTP
• Loudness range: 7 LU

The gap to the target is -16 minus -20.4, so the file needs +4.4 dB of gain. Adding 4.4 dB also lifts the true peak from -4.6 to about -0.2 dBTP — too close to the ceiling. The normalizer's limiter therefore holds the very highest moments at -1 dBTP while the gain goes on. The second measurement reads -16.2 LUFS, true peak -1.0 dBTP. Slightly under target because the limiter traded a little loudness for peak safety, and well inside the ±1 tolerance. That file is done. Total hands-on time: about a minute.

Contrast a second episode recorded too hot: it measures -15.1 LUFS but its true peak is already +0.3 dBTP — over full scale between samples, quietly clipping on some devices. Here the problem is not loudness but peaks. Turning it down 1.5 dB lands it at -16.6 LUFS with peaks at -1.2 dBTP: on target, and the crackle on the loudest laugh is gone. Normalization fixes both directions, which is why the measure step always comes first — you cannot know which problem you have until you read the numbers.

One Master or Several?

Most podcasts publish to every app at once, and the apps do not all aim at the same number. The practical choices:

Notice what is not on this list: a different file for every app. The differences between -14 and -16 are small, and a sane master near either target behaves well everywhere. The expensive mistake is not choosing between them — it is publishing at -22 or -10 and letting each platform improvise.

Why Not Just Turn It Up in the Editor?

A volume slider changes peaks, not loudness, and it cannot tell you where you landed. Normalization to a measured LUFS target is repeatable: episode 1 and episode 100 end up at the same loudness even if they were recorded months apart, on different microphones, in different rooms. That consistency is what listeners hear as "this show sounds professional." If an episode is far too quiet to fix with gain alone, the quiet recording guide covers the repair order.

There is also a subtle trap in editor meters. Many editors show a loudness readout, but the default may be a momentary or short-term view, or an unweighted RMS approximation. Producers chase the live needle to -16 while they mix, then discover the finished file integrates to -19 because the quiet half of the interview dragged the average down. Integrated loudness is a property of the whole file. It can only be certified after the file exists.

What About the Tolerance?

Apple's guidance is a target, not a cliff edge, and every serious meter and platform works with about ±1 LU of slack. A file at -15.4 or -16.6 is fine. A file at -18 is a small but real step down that regular listeners will feel against other shows. Practical rule: correct anything more than 1 LU off; never re-run a file just to move it 0.3 LU. Your time is worth more than a difference nobody can hear.

Common Mistakes

Normalizing the project instead of the export. Plugins, fades rendered at export, and the encoder itself can shift the final number slightly. Always verify the file you actually upload.

Normalizing twice. Running an already-normalized file through again with the wrong preset (say, a -14 streaming preset on a -16 podcast file) stacks decisions. Keep one master per destination and label them.

Letting the limiter do all the work. If an episode needs +9 dB, a limiter-heavy pass will squash its dynamics flat. That much distance means a mix problem — go back to the repair workflow instead of forcing it at the loudness step.

Ignoring the intro and ads. A booming intro over a -16 episode still startles. Integrated loudness is a whole-file average, so wild internal swings survive it; check that segments sit at similar short-term levels, and keep loudness range in a healthy band.

Forgetting mono. A mono episode normalized to -16 plays about 3 LU hot. The -19 rule exists for a reason, and it is the most-missed line in podcast loudness.

Doing a Whole Season

Normalizing one file is a chore; normalizing forty is a workflow. Paid plans on LoudNorm take batches of files to the same preset in one upload and return one report for all of them — see the batch guide. The free plan covers 60 minutes a month with the same measurement and the same report; paid plans raise the minutes and unlock batch, and no plan adds a watermark or a jingle to your audio.

Troubleshooting

My file lands at -17.5 even after normalizing. Almost always the true-peak ceiling is the cause: the source was peaky, the limiter held the peaks, and the trade landed you under target. Options: soften the loudest moments in the mix and re-run, or accept it — -17.5 is 1.5 LU under, audible only in direct comparison.

My meter and the report disagree. Check that both are BS.1770 integrated measurements of the same file. A common mismatch is a phone recording app re-encoding the file on export, which changes the audio after you measured it.

One guest is quiet but the file measures on target. Integrated loudness is an average; it cannot see balance. Fix the balance in the mix first — levelling is a mix job, normalization is a finishing job.

The platform still turned my episode down. Some services normalize playback to their own reference (Spotify and YouTube use -14) regardless of your file. At -16 they will raise you slightly or leave you; nothing is wrong. What you control is that every platform starts from the same, sane master.

After You Upload: Trust, but Verify

Once an episode is live, play the first minute in the app your listeners use most, at your normal volume, right after a big-network show. If you do not reach for the volume control in either direction, the chain worked. Do this for the first few episodes after you adopt the -16 routine; after that, the per-episode report is verification enough. If a platform's player offers a stats or loudness readout, even better — but your ears in the real app are the test that matters, because they are the same test every listener runs, on the same bus, train or kitchen radio, with the same distractions competing for their attention.

Keep the habit boring: export, measure, normalize, verify, upload, file the report. Shows that sound professional for years are rarely doing anything fancier than that, every single episode.

Frequently Asked Questions

WAV or MP3 — which should I normalize? Normalize the file you publish. If you publish an MP3, either normalize the WAV master and then encode, or normalize the MP3 directly and verify the MP3. Encoding shifts peaks a little, which the -1 dBTP ceiling is designed to absorb.

Does normalization change my audio quality? A two-pass normalization applies one clean gain change plus, when needed, limiting on the highest peaks only. Done at the end of production, it is the gentlest processing in the whole chain — far gentler than the platform's own encode.

What if my show has music and speech? The -16 target still applies to the whole file. Mix so speech and music sit at similar short-term loudness; the integrated number will follow.

How often should I check? Every episode, without exception. Loudness drift is slow and silent — a new mic position, a new room, a new co-host, a borrowed interface with its gain knob in a new place — and the only early warning you will ever get is the measurement you take before you publish.

References

• https://www.apple.com/apple-podcasts/ — Apple Podcasts publisher guidance, the source of the -16 LUFS / -19 LUFS convention.
• https://tech.ebu.ch/publications/r128 — EBU R128, the loudness framework podcasts borrowed from broadcast.
• https://www.itu.int/rec/R-REC-BS.1770 — ITU-R BS.1770, the measurement method behind every LUFS number.