Podcast Loudness Explained: Hitting -16 LUFS Without a Mastering Engineer

Your podcast is quieter than everyone else's, and your listeners have noticed — they crank the volume for your show, then get blasted by the next one in the queue. Or the opposite: your levels look "fine" in the editor, meters bouncing near the top, but Apple Podcasts turns your episode down and suddenly your carefully mixed intro sounds thin. Both problems have the same root cause: podcast platforms measure loudness in LUFS, and most independent podcasters have never been told what that means. This guide fixes that — no mastering engineer required.

What LUFS actually measures

The meters most people watch measure peak level: the single loudest instant in the file. But human ears do not judge loudness by peaks — a single snare hit and a sustained voice can have identical peaks and feel completely different in volume. LUFS (Loudness Units relative to Full Scale) measures perceived loudness: it averages energy over time and weights frequencies the way hearing does, so a whisper with one loud cough measures quiet, as it should. Three related numbers matter:

• Integrated LUFS: average loudness of the whole episode. This is the number platforms normalize against.
• Loudness range (LRA): how much the loudness varies. Speech-heavy podcasts should keep this modest so listeners are not riding the volume knob in the car.
• True peak (dBTP): the actual maximum the waveform reaches after digital-to-analog conversion. Keep it at or below -1 dBTP so lossy encoding does not push peaks into distortion.

The targets, platform by platform

There is no single industry number, but the landscape is stable enough to plan around:

• Apple Podcasts: recommends about -16 LUFS for stereo content.
• Spotify: normalizes playback to roughly -14 LUFS.
• YouTube: normalizes to about -14 LUFS as well.
• Mono note: a mono file played over two speakers gains apparent loudness, so the common guidance for mono podcasts is about -19 LUFS to sound equivalent to a -16 LUFS stereo file.

So which do you pick? -16 LUFS integrated, -1 dBTP true peak remains the safest single answer for podcasts. Spotify will nudge a -16 file up slightly toward its target; Apple gets exactly what it asks for; and you avoid the crushed-dynamics sound of mastering hot to -14 just to beat a normalizer that would have leveled you anyway.

Why quiet episodes get skipped

Normalization can turn audio down cleanly, but turning it up has a cost. A -22 LUFS episode boosted toward target brings its noise floor up with it — room hiss, air conditioning, preamp noise all rise 6 dB. And not every playback path normalizes: direct MP3 downloads, embedded web players, and older apps play the file as-is, where your quiet episode sits next to properly mastered shows at a real disadvantage. Listeners rarely diagnose "this show is 6 LU under target"; they just feel that it sounds amateur, and skip.

Hitting the target with free tools

You do not need a mastering chain. You need one measurement and one adjustment, in the right order:

• Mix normally first. Balance voices against each other and against music beds by ear. Loudness normalization sets the level of the whole episode; it cannot fix a guest who is buried under the host.
• Apply gentle compression to the voices if levels wander. A smaller loudness range means the normalized episode sounds consistent, not just correct on average.
• Normalize the final mix to -16 LUFS. Many editors have a loudness meter buried somewhere; if yours does not, export the episode and run it through a loudness normalizer that measures integrated LUFS and adjusts the file to target in one pass. The normalization FAQ walks through the peak-vs-loudness distinction with examples.
• Check true peak last. If normalization pushed peaks above -1 dBTP, a limiter (or the normalizer's peak ceiling option) pulls them back without changing perceived loudness.

Common loudness mistakes

• Peak-normalizing to 0 dB and calling it done. Peak normalization makes the loudest instant loud; it says nothing about the other 59 minutes. Two files peak-normalized identically can differ by 10 LU of perceived loudness.
• Normalizing segments separately, then editing. Adding an intro after normalizing throws off the integrated measurement. Loudness is the last step before encoding.
• Chasing the number with volume automation alone. If your raw mix measures -26 LUFS, you have a gain-staging problem — fix recording levels rather than boosting 10 LU and amplifying the noise floor.
• Confusing loudness normalization with file compression. Normalizing changes volume, not file size. If the goal is a smaller file, that is a bitrate decision — the MP3 compressor handles it, and it is a separate step from loudness. The bitrate guide explains that side of the equation.

Measuring without buying anything

You cannot hit a target you cannot see, and ears adapt too quickly to be trusted for absolute loudness. Free meters are everywhere once you know to look: Audacity ships loudness normalization with an LUFS mode, most DAWs added integrated loudness meters years ago, and web-based normalizers report the measured value of an uploaded file before adjusting it. Measure a few of your published episodes first — the number is usually a surprise, and it tells you whether your problem is the mix or just the final gain. Then measure one big-name show for reference and note how consistent its episodes are with each other. That consistency, more than the specific number, is what listeners register as professional.

The two-minute episode routine

Once the concepts are clear, the practice is almost trivially short. Finish the mix. Normalize to -16 LUFS with a -1 dBTP ceiling. Encode the MP3 at your usual bitrate — the podcast bitrate FAQ if you have not settled on one. Spot-check the result against a big-name podcast at the same system volume; they should feel equally loud. That is the entire discipline. LUFS sounds like mastering-engineer territory, but it is really just a ruler — and once every episode is measured with the same ruler, your show stops being the quiet one in the queue, permanently.