Podcast Loudness Standards: LUFS Explained Simply

-16 LUFS isn't arbitrary — the loudness targets every directory expects and how to hit them.

The landscape

When it comes to loudness as distribution compliance, not audiophile detail, the details matter. Here's what the evidence and practitioner experience point to:

• -16 LUFS integrated loudness is the de facto podcast standard — Apple, Spotify and most platforms expect it; off-target audio gets normalized or sounds wrong.
• True peak should stay under -1.0 dBTP to prevent clipping on lossy transcodes — the ceiling directories check.

What actually works

When it comes to loudness as distribution compliance, not audiophile detail, the details matter. Here's what the evidence and practitioner experience point to:

• Loudness range matters more than the number: compressed-to-death audio sounds flat; reasonable dynamics with consistent level is the goal.
• Inconsistent loudness between segments is the most common amateur tell — listeners notice the 'jump', not the absolute level.

Putting it into practice

When it comes to loudness as distribution compliance, not audiophile detail, the details matter. Here's what the evidence and practitioner experience point to:

• AI-rendered audio sidesteps this: provider output is consistent by construction; PodKrafter renders target the -16 LUFS standard.
• Check your rendered file with a loudness meter (free tools exist) once — if it consistently passes, the pipeline is sound.

Key takeaways

• -16 LUFS integrated loudness is the de facto podcast standard — Apple, Spotify and most platforms expect it; off-target audio gets normalized or sounds wrong.
• Inconsistent loudness between segments is the most common amateur tell — listeners notice the 'jump', not the absolute level.
• Check your rendered file with a loudness meter (free tools exist) once — if it consistently passes, the pipeline is sound.

Ready to put this into practice? PodKrafter turns research into broadcast-ready podcast episodes — start free.