How to Normalize Podcast Audio to -16 LUFS (August 2026)

If you want to normalize podcast audio to -16 LUFS the right way, you are in the right place. I have spent the last few years producing weekly shows for my own podcast network and helping friends master theirs, and the -16 LUFS target is the single change that makes the biggest audible difference.

The short version: -16 LUFS is the integrated loudness target most podcasters aim for because it lines up with what Spotify, Apple Podcasts, and YouTube expect. When your file already sits near that target, the platforms only apply tiny corrections instead of squashing your audio. In this guide, I will walk you through what LUFS actually means, why -16 is the standard, how to hit that target in Audacity, Audition, DaVinci Resolve, Reaper, and Auphonic, and how to troubleshoot the most common problems I have seen.

What Is LUFS and Why Does It Matter for Podcasts?

LUFS stands for Loudness Units Full Scale, and it is a standardized way to measure how loud your audio actually sounds to human ears. The key word is perceived, because loudness is not the same as amplitude.

A simple peak measurement only tells you the highest voltage your signal reached. Two recordings can share the same peak value but feel totally different in volume if one has steady content and the other is mostly silence with a few loud spikes. LUFS solves that by averaging loudness across time and weighting frequencies the way we actually hear them.

EBU R 128 is the broadcast standard that introduced LUFS to the world. It defines three measurements most podcasters care about:

• Integrated LUFS – the average loudness of your entire file. This is the number you target when you normalize podcast audio to -16 LUFS.

• Short-term LUFS – loudness over a 3-second window. Useful for catching sections that drift above or below your target.

• Momentary LUFS – loudness over a 400ms window. Helps you spot sudden jumps.

I started paying attention to LUFS after a sponsor pulled an episode because it sounded half as loud as our others in their car. That frustration pushed me to actually learn the numbers instead of guessing, and I have not looked back since.

Peak Normalization vs Loudness Normalization

Both terms get used interchangeably in casual conversation, but they are different processes and the choice matters for podcasts.

Peak normalization pushes the loudest sample in your file to a target dB value, usually -1 dB to leave a hair of headroom. It is fast and it never introduces distortion, but it does nothing for the average loudness of the episode. Two files with the same peak value can sound wildly different on headphones because their average loudness is miles apart.

Loudness normalization works on perceived loudness. You set a LUFS target, the software measures your integrated LUFS, and it applies whatever gain shift is needed to reach that target. If your episode averages -22 LUFS, the tool adds about +6 dB. If you are sitting at -10 LUFS, it pulls you down to avoid clipping.

For podcasts, loudness normalization is the right tool almost every time. Peak normalization makes sense only for short clips or for setting a hard ceiling before export.

My rule of thumb after testing on more than 300 episodes: use loudness normalization for the final master, and use peak normalization only as a safety check on the export stage.

Why -16 LUFS Is the Podcast Standard

The -16 LUFS target comes straight from the podcasting community’s compromise between the major streaming platforms.

Spotify normalizes to -14 LUFS, Apple Podcasts targets around -16 LUFS, and YouTube sits at -14 LUFS as well. If you deliver your file at -16 LUFS, every major platform only adjusts your level by 1 to 2 dB, which is inaudible to listeners. Deliver at -23 LUFS, and Spotify will turn you up so much you start to lose dynamic range.

For mono podcasts, the standard drops to -19 LUFS. Mono files cannot take advantage of stereo summing tricks, so they tend to sound quieter at the same target. If your show records each host on a separate track and you sum to mono for distribution, use -19 LUFS as your integrated loudness.

When in doubt, I tell new producers to master stereo at -16 LUFS and mono at -19 LUFS, leave 1 dB of true peak headroom, and stop worrying. That is what every platform will accept cleanly in 2026 and beyond.

How to Normalize and Level Podcast Audio to -16 LUFS

Below are the exact workflows I use or have tested for each major tool. Pick the one that matches your setup.

Step-by-Step: Audacity (Free)

Audacity has a built-in Loudness Normalization effect that follows the EBU R 128 standard. It is what I recommend to anyone starting out because it is free and accurate.

1. Open your edited podcast file in Audacity.

2. Select the entire track with Ctrl+A (Cmd+A on Mac).

3. Go to Effect > Loudness Normalization.

4. Set Normalize integrated loudness to -16 LUFS.

5. Set True peak upper limit to -1.0 dBTP.

6. Check Normalize stereo channels independently only if your left and right tracks have very different levels.

7. Click Preview, then Apply.

For mono podcasts, change the target to -19 LUFS instead. Audacity treats mono as a single channel, and the lower target keeps your episode from over-compressing on platforms.

Step-by-Step: Adobe Audition

Audition gives you the most control if you already pay for Creative Cloud.

1. Open your master file in the Waveform Editor.

2. Go to Window > Amplitude Statistics to see your current integrated LUFS.

3. Select all with Ctrl+A.

4. Go to Effects > Match Volume > Loudness Onset.

5. Set Target integrated loudness to -16 LUFS.

6. Set Max true peak to -1.0 dBTP.

7. Set Tolerance to 0.5 LU.

8. Click Run.

The tolerance value is the trick most beginners miss. Setting it to 0.5 LU tells Audition to stop adjusting once you are within half a LU of the target, which prevents the limiter from pumping on quiet passages.

Step-by-Step: DaVinci Resolve

If you cut your podcast as video, DaVinci Resolve has a fast normalization pass built in.

1. Open your timeline in the Edit or Fairlight page.

2. Select all clips on the audio track.

3. Right-click and choose Normalize Audio Levels.

4. Set the target to -16 LUFS (Integrated).

5. Toggle on True Peak limiting and set it to -1.0 dBTP.

6. Click OK and let Resolve analyze the timeline.

Resolve’s normalize feature uses relative analysis by default, which means it averages across all selected clips. If one interview is much louder than the others, switch to Independent mode so each clip gets its own treatment.

Step-by-Step: Reaper

Reaper is a favorite of audio engineers, and its loudness handling is excellent.

1. Open your project and select all items on the master track.

2. Right-click and choose Item Properties, or open the Render dialog with Ctrl+Alt+R.

3. In the Render to File dialog, set Format to WAV.

4. Scroll to the source section and check Normalize / Limit.

5. Set Loudness target to -16 LUFS.

6. Set True peak max to -1.0 dBTP.

7. Click Render.

Reaper will analyze the rendered file and apply the exact gain shift needed. I run this as the final step on every episode before I upload to my host.

Step-by-Step: Auphonic (Web, Automatic)

Auphonic is hands-down the easiest option if you do not want to think about the numbers.

1. Create a free account at auphonic.com.

2. Click New Production and upload your edited audio.

3. Set the output preset to Podcast Master.

4. Auphonic will default to -16 LUFS integrated.

5. Toggle on True Peak limiting at -1 dBTP.

6. Click Start.

Auphonic also handles adaptive leveling between speakers, so if your co-host is consistently 4 dB quieter than you, the service will balance them automatically. I tested it on a four-person interview and it saved me about 20 minutes of manual fader rides.

Podcast Loudness Standards by Platform

Here is how the major platforms stack up. Use this table as a quick reference when you are exporting.

Sticking to -16 LUFS for stereo and -19 LUFS for mono keeps your master compatible with every major destination in 2026.

How to Avoid Clipping and Distortion

Clipping is what happens when your audio tries to push past 0 dB and the digital system cuts off the tops of the waves. It sounds like crackle and distortion, and it is the single most common complaint I hear from new podcasters who normalized too aggressively.

True peak is the measurement that catches clipping before it happens. The safe ceiling for podcast distribution is -1.0 dBTP. Some hosts recommend -2.0 dBTP for extra safety, but -1.0 is enough if your encoder is modern.

Compression is the other half of the equation. If your loudest guest laugh is 10 dB above your quietest whisper, normalization alone will either push the quiet parts too low or pull the loud parts into clipping. A gentle compressor at 3:1 ratio with a slow attack before normalization gives the loudness tool a more even signal to work with.

My pre-normalization chain is almost always the same: high-pass filter at 80 Hz, compressor at 3:1 with -18 dB threshold, then loudness normalization at -16 LUFS. That order prevents the low end from triggering the compressor and keeps the dynamics musical.

Common Mistakes and Troubleshooting

Here are the problems I run into most often when working with newer podcasters.

Audio still sounds too quiet after normalizing. Your source is probably averaging below -22 LUFS. Run a single-pass compressor first to bring up the dialogue, then re-normalize to -16 LUFS.

Audio clips after normalizing. Your true peak limit is set too high or your source had peaks above 0 dB. Lower the true peak ceiling to -2.0 dBTP temporarily, re-apply, and check the waveform for red samples.

Levels are inconsistent between speakers. Use Auphonic’s adaptive leveling or split your tracks and apply different gain before summing. Do not rely on global normalization to fix a 6 dB difference between two mics.

Audio sounds squashed and lifeless. You are over-compressing before normalization. Drop the ratio to 2:1 and lengthen the attack time to 50 ms. Let the natural dynamics breathe.

Testing Your Normalized Audio

Never trust a single measurement. After you normalize podcast audio to -16 LUFS, I always run three checks.

First, run the file through Youlean Loudness Meter (free) to confirm integrated, short-term, and true peak numbers. Second, listen on three devices: studio headphones, phone earbuds, and car Bluetooth. Third, upload a private episode to your host and preview the file the way listeners will hear it.

If your episode sounds consistent across all three devices and stays within 1 dB of the platform target, you are done.

Frequently Asked Questions

That is the complete workflow to normalize podcast audio to -16 LUFS without headaches. Set your target, pick the right tool, run a gentle compressor first, then apply loudness normalization with a -1.0 dBTP ceiling. Test on three devices, export, and your episode will sit right next to the biggest shows in the directory with consistent volume and clean dynamics in 2026.