Podcast Loudness Standards Explained: LUFS, Peaks, Sample Rate, Bit Depth, and Export Settings

Your podcast can sound excellent in your editing software and still play too quietly, distort after encoding, or force listeners to reach for the volume control.

The problem is rarely the microphone alone. It is usually a mismatch between loudness, peak level, sample rate, bit depth, bitrate, and the requirements of the platform receiving the final episode.

These settings describe different parts of an audio file. Changing one does not necessarily fix the others.

This guide explains what each measurement means, what settings work well for most podcasts, and how to build an export workflow that produces consistent results across podcast apps and video platforms.

Podcast loudness and export settings at a glance

For most professionally produced podcasts, these settings provide a reliable starting point:

• Stereo loudness: Approximately -16 LUFS integrated
• Mono loudness: Approximately -19 LUFS integrated is a common podcast convention
• True-peak ceiling: No higher than -1 dBTP
• Conservative true-peak ceiling: -2 dBTP when additional encoding headroom is desirable
• Production sample rate: 48 kHz
• Production bit depth: 24-bit
• Archival format: WAV
• Stereo RSS delivery: AAC or MP3 at approximately 128–256 kbps
• Mono RSS delivery: AAC or MP3 at approximately 64–128 kbps

These are production recommendations, not one universal rule enforced by every podcast app.

Apple recommends an overall loudness of approximately -16 dB LKFS, plus or minus 1 dB, with true peaks no higher than -1 dBFS. Other platforms accept several audio formats without publishing an equivalent podcast-specific loudness target.

Your hosting provider may also process or re-encode your file, so check its current requirements before uploading.

Why podcast loudness standards matter

Listeners move between podcasts, music, videos, audiobooks, phone calls, and social media throughout the day. They expect each piece of content to begin at a comfortable, predictable volume.

If one episode is much quieter than the content surrounding it, listeners must turn it up. If the next piece of content is louder, the sudden change can be unpleasant.

Excessively loud mastering creates a different set of problems:

• Peaks may clip or distort.
• Lossy encoding can create new peaks.
• Voices can sound crushed or fatiguing.
• Background noise and room reflections become more noticeable.
• Music can overpower dialogue.
• Platform-level normalization may turn the entire episode down.

The goal is not to make a podcast as loud as possible. It is to make it consistently audible while preserving natural speech.

What is LUFS?

LUFS stands for Loudness Units relative to Full Scale. It measures perceived loudness rather than merely measuring the highest instantaneous signal level.

The measurement accounts for how people perceive different frequencies. That makes it more useful for comparing the apparent volume of two podcast episodes than a conventional peak meter.

LUFS is closely related to the term LKFS. For practical podcast production, a reading of -16 LUFS and a reading of -16 LKFS refer to the same programme-loudness level under the underlying loudness-measurement standard.

The measurement method is defined by ITU-R BS.1770, which specifies how programme loudness and true-peak levels should be measured.

Integrated LUFS

Integrated LUFS measures average perceived loudness across the entire programme.

For a podcast, this normally means measuring the complete finished episode—from the beginning of the intro to the end of the outro.

Integrated loudness is the number most people mean when they say that a podcast should be mastered to -16 LUFS.

Short-term LUFS

Short-term LUFS measures loudness over a smaller window, usually several seconds.

It can help you identify sections where:

• One guest becomes noticeably quieter.
• An advertisement is louder than the conversation.
• The intro music overwhelms the opening narration.
• A remote participant’s level changes during the interview.

An episode can reach its integrated target while still containing distracting short-term changes. That is why a single overall number cannot replace listening.

Momentary LUFS

Momentary LUFS uses an even shorter measurement window. It responds quickly to changes in speech and is useful for observing individual phrases.

Because natural speech is dynamic, the momentary reading will move constantly. It should not be forced to remain at one exact number.

What is dBFS?

dBFS stands for decibels relative to full scale.

In digital audio, 0 dBFS is the maximum possible sample level. Anything attempting to exceed it may clip.

All normal working levels are therefore negative:

• -18 dBFS is lower than -12 dBFS.
• -6 dBFS is close to the digital ceiling.
• 0 dBFS leaves no additional sample headroom.

A dBFS peak meter tells you how close the signal comes to the digital limit. It does not tell you how loud the entire episode will feel.

A podcast can have peaks at -1 dBFS and still sound quiet if most of the programme is much lower. Conversely, a heavily compressed episode can sound loud even when its highest peak remains below 0 dBFS.

What is true peak?

A standard sample-peak meter measures the individual samples stored in a digital audio file. However, the reconstructed waveform played by a listener’s device can peak between those samples.

These inter-sample peaks may be higher than the values shown by a basic peak meter.

A true-peak meter estimates the reconstructed signal and normally displays its result in dBTP. The “TP” means true peak.

Leaving true-peak headroom reduces the risk of distortion when an episode is converted to AAC, MP3, or another lossy format.

For most podcasts:

• -1 dBTP is a practical maximum.
• -2 dBTP provides additional encoding safety.

Setting a limiter to -1 dB does not automatically guarantee that the encoded file will remain below -1 dBTP. The limiter and meter should both support true-peak processing if you need an accurate ceiling.

Peak level and loudness are not the same

This distinction is one of the most important concepts in podcast mastering.

Peak level measures the highest moment in a signal. Loudness measures how the programme is perceived over time.

Imagine two interviews:

• The first has natural conversation with occasional laughter reaching -1 dBTP.
• The second is aggressively compressed, with almost every sentence sitting close to -1 dBTP.

Both may have the same highest peak, but the second will sound substantially louder and denser.

Peak control protects the file from overload. Loudness normalization creates consistency. A finished podcast generally needs both.

What sample rate should a podcast use?

Sample rate describes how many times per second an analog sound is measured when converted into digital audio.

The most common rates in podcast production are:

• 44.1 kHz: Common in music and audio-only distribution
• 48 kHz: Common in video, film, broadcast, and modern podcast production

Both can reproduce the audible frequency range needed for speech. A higher sample rate does not automatically make spoken audio sound dramatically better.

For a new podcast workflow, 48 kHz is usually the most practical choice, especially if the show includes video. It keeps the audio aligned with standard video-production workflows and reduces unnecessary conversions when the same recording is used for YouTube or social clips.

Consistency matters more than switching between the two.

Record, edit, mix, and export at the same sample rate whenever possible. Incorrectly interpreted or inconsistently converted audio can contribute to timing problems. If speech gradually separates from the picture, see our guide to fixing podcast audio that is out of sync with video.

What bit depth should a podcast use?

Bit depth affects the resolution and available dynamic range of digital audio.

The two most common production settings are:

• 16-bit: Suitable for final consumer audio
• 24-bit: Preferred for recording, editing, mixing, and archiving

Recording at 24-bit gives you more working headroom. You can record voices at safer levels without trying to push the signal close to 0 dBFS.

That helps prevent clipping when a guest suddenly laughs, moves closer to the microphone, or becomes more animated.

For professional production, use 24-bit WAV files throughout recording and post-production. If a distributor or delivery specification requires 16-bit audio, create that version from the final 24-bit master.

To understand why uncompressed production files retain more information, read our guide to lossless audio and bitrate for podcasters.

Bit depth and bitrate are different

The similar names create confusion, but these settings describe different things.

Bit depth applies primarily to uncompressed digital audio such as WAV files. It affects the precision used to represent each sample.

Bitrate describes the amount of data used per second. It is commonly used when discussing compressed formats such as MP3 and AAC.

An MP3 file labeled 128 kbps has a bitrate of 128 kilobits per second. That is not the same as a 24-bit WAV recording.

In general, a higher bitrate allows a compressed file to retain more information. It also creates a larger file.

Speech can remain understandable at relatively low bitrates, but aggressive compression may introduce:

• Metallic or watery artifacts
• Smearing around consonants
• Reduced clarity in music
• Harshness in sibilant sounds
• Audible degradation when the file is encoded again

Keep a lossless master even when the delivery copy is compressed.

What is the best LUFS level for a podcast?

A reliable general target is:

• Approximately -16 LUFS integrated for stereo
• Approximately -19 LUFS integrated for mono

However, the mono recommendation needs context.

Why mono podcasts are often mastered to -19 LUFS

Some loudness-measurement and playback systems treat a mono signal differently when it is reproduced through two speakers. The common -19 LUFS mono convention accounts for an approximately 3 dB difference relative to a stereo programme.

In practice, playback behavior is not perfectly consistent across every device and app. Some systems compensate for mono playback while others do not.

Apple’s published podcast guidance recommends approximately -16 dB LKFS, plus or minus 1 dB, without presenting a separate -19 target for mono RSS episodes.

Therefore:

• Use -19 LUFS if you follow the established mono podcast convention.
• Use approximately -16 LUFS when a specific distributor, client, or platform requests it.
• Document the standard your production team uses so every episode is treated consistently.

Do not convert a stereo production to mono purely to chase a loudness number. Choose mono or stereo based on the content.

Should a podcast be mono or stereo?

Mono works well when an episode consists almost entirely of spoken voices and does not depend on spatial effects.

Its advantages include:

• Smaller files at a comparable perceived quality
• More efficient use of lower bitrates
• Simple, centered playback
• Consistency across one-speaker devices

Stereo is useful when the production includes:

• Stereo music
• Ambience or sound design
• Narrative positioning
• Live performances
• Material that depends on left-to-right space

Even when the final episode is mono, record each participant to a separate source track whenever possible. Separate recordings give the editor control over levels, noise, interruptions, and processing before the final mono mix is created.

Our explanation of isolated tracks versus mixed tracks covers why this matters during post-production.

Apple Podcasts loudness and file requirements

Apple publishes one of the clearest sets of podcast-audio recommendations.

According to the company’s current audio requirements, Apple recommends:

• Overall loudness around -16 dB LKFS, plus or minus 1 dB
• True peaks no higher than -1 dBFS
• A sample rate of at least 44.1 kHz for WAV and FLAC files
• 16- or 24-bit resolution for WAV and FLAC
• MP3 or AAC for episodes delivered through an RSS feed

For RSS audio at 44.1 or 48 kHz, Apple’s recommended bitrate ranges are:

• Mono: 64–128 kbps
• Stereo: 128–256 kbps

Apple recommends AAC over MP3 at the same bitrate because AAC generally provides better quality for a given amount of data.

These recommendations do not mean every podcast must be distributed directly as a WAV file. Most RSS-based shows upload a compressed delivery file to their hosting provider while retaining a WAV master internally.

Spotify podcast loudness and file formats

Spotify for Creators accepts MP3, M4A, and WAV uploads in mono or stereo, according to its audio episode publishing guidance.

Spotify does not publish an equivalent podcast-upload rule on that page requiring every episode to be mastered to a particular LUFS value.

You may see -14 LUFS described online as “the Spotify standard.” That figure comes from Spotify’s music-normalization guidance for Spotify for Artists. It should not automatically be treated as a universal Spotify podcast-mastering requirement.

For podcasts, a better approach is to:

• Produce a consistent final master.
• Follow your hosting provider’s technical specifications.
• Avoid clipping and excessive limiting.
• Use a true-peak ceiling that leaves encoding headroom.
• Check the processed episode after publication.

A platform’s playback processing is not a substitute for properly leveling your show.

Loudness settings for YouTube and video podcasts

Video production typically uses a 48 kHz audio sample rate, making it the safest production choice for podcasts that will also appear on YouTube.

For a video podcast:

• Record at 48 kHz and 24-bit when available.
• Keep the project and source recordings at 48 kHz.
• Export a high-quality video master.
• Avoid embedding audio that is already heavily compressed.
• Keep dialogue consistent across the complete programme.
• Leave at least 1 dB of true-peak headroom, with 2 dB offering extra safety.

YouTube may apply playback processing and offers features such as stable volume in some listening situations. You should still upload a well-controlled master rather than relying on the platform to repair inconsistent dialogue.

If you release both audio and video editions, create them from the same approved mix whenever possible. Separate, independently adjusted masters can make the podcast sound noticeably different between apps.

Recommended export settings for an audio-only stereo podcast

A strong stereo workflow uses two files: a high-quality master and a distribution copy.

Production and archival master

• Format: WAV
• Sample rate: 48 kHz
• Bit depth: 24-bit
• Channels: Stereo
• Loudness: Approximately -16 LUFS integrated
• True peak: No higher than -1 dBTP
• Processing: Final approved mix with no lossy encoding

RSS delivery file

• Format: AAC or MP3, depending on the host
• Sample rate: 44.1 or 48 kHz
• Channels: Stereo
• Bitrate: Approximately 128–256 kbps
• Loudness: Approximately -16 LUFS integrated
• True peak: -1 dBTP or lower

If your host accepts WAV and generates its own delivery formats, upload the high-quality file it recommends. Do not assume that every host processes source audio in the same way.

Recommended export settings for an audio-only mono podcast

Production and archival master

• Format: WAV
• Sample rate: 48 kHz
• Bit depth: 24-bit
• Channels: Mono
• Loudness: Approximately -19 LUFS integrated under the common mono convention, or the level required by your distributor
• True peak: No higher than -1 dBTP

RSS delivery file

• Format: AAC or MP3
• Sample rate: 44.1 or 48 kHz
• Channels: Mono
• Bitrate: Approximately 64–128 kbps
• True peak: -1 dBTP or lower

If the episode contains substantial music or layered sound design, listen carefully before choosing the lower end of the bitrate range.

Recommended settings for a video podcast

Production audio

• Format: WAV
• Sample rate: 48 kHz
• Bit depth: 24-bit
• Loudness: Approximately -16 LUFS integrated as a practical spoken-content target
• True peak: -1 to -2 dBTP

Audio embedded in the video

• Codec: High-quality AAC or the format required by the publishing workflow
• Sample rate: 48 kHz
• Channels: Stereo unless mono is intentionally required
• Processing: One final encode whenever possible

Preserve the original WAV mix separately. The audio embedded in a compressed video should not become your archival master.

A practical podcast loudness workflow

Loudness should be handled near the end of post-production, not used as a shortcut for skipping the mix.

1. Record clean source audio

Begin with healthy levels that leave room for sudden changes in speech. Avoid recording so close to 0 dBFS that one laugh can clip the microphone input.

Whenever possible, record each participant locally and on an isolated track.

Boomcaster records locally in the browser and provides separate high-quality participant tracks, giving editors more control than they would have with only a compressed conference-call recording.

2. Complete the editorial cut

Remove unwanted sections, reorder the conversation, repair interruptions, and confirm the final running order before measuring integrated loudness.

If you normalize an unfinished timeline, later edits can change the programme’s overall measurement.

Our professional podcast workflow explains how recording, editing, and publishing fit together.

3. Balance individual voices

Before processing the complete mix, make the speakers feel consistent relative to one another.

This may involve:

• Clip-gain adjustments
• Volume automation
• Corrective equalization
• Gentle compression
• Noise reduction
• De-essing
• Removal or muting of inactive microphones

Do not normalize every isolated speaker track to -16 LUFS. The loudness target applies to the finished programme, not to every raw source independently.

For more detail, see our guide to mixing podcast audio.

4. Mix music, advertisements, and sound effects

Intro music should support the voice rather than forcing listeners to adjust the volume before the conversation begins.

Check every inserted element, including:

• Prerecorded advertisements
• Guest introductions
• Listener messages
• Music beds
• Stingers
• Archived recordings
• Remote inserts

These assets often come from different sources and may have dramatically different loudness levels.

5. Measure the complete episode

Measure integrated LUFS from the beginning to the end of the final programme.

Also inspect:

• Short-term loudness changes
• True-peak level
• Audible compression
• Transitions between sections
• The relationship between speech and music

Measure the actual finished mix, not only a representative excerpt.

6. Adjust loudness and control peaks

Use level adjustments, compression, automation, or loudness normalization to bring the episode toward its target.

Then use a true-peak limiter to control any remaining peaks.

A limiter should catch occasional excess peaks. If it is constantly reducing the signal by a large amount, return to the mix and solve the underlying level imbalance.

7. Export a lossless master

Create a 24-bit WAV master before producing compressed copies.

The master should be the approved source for:

• RSS delivery
• Video exports
• Promotional clips
• Future remastering
• Syndication
• Archiving

Repeatedly converting an MP3 into another MP3 can compound compression artifacts.

8. Create the delivery copy

Encode the master according to your podcast host’s current requirements.

After encoding, measure and listen to the compressed file again. Lossy encoding can slightly change true-peak behavior and expose artifacts that were not obvious in the WAV master.

9. Perform real-world quality control

Listen on more than studio headphones.

Useful checks include:

• Phone speaker
• Laptop speakers
• Earbuds
• Car audio
• Television
• Smart speaker

These tests reveal different problems. A mix that sounds spacious on headphones may have weak dialogue on a phone. Bass-heavy music may mask voices in a car. Noise reduction may sound distracting through earbuds.

A repeatable podcast post-production routine makes this quality-control step easier to maintain.

Common podcast loudness mistakes

Normalizing every raw track to the final target

If five participant tracks are each normalized to -16 LUFS and then combined, the completed mix will not remain at -16 LUFS.

Balance the source tracks first. Measure the final programme afterward.

Using peak normalization instead of loudness normalization

Peak normalization makes the highest sample reach a selected level. It does not guarantee consistent perceived volume.

Two episodes peak-normalized to the same value may still sound dramatically different.

Pushing everything into a limiter

A limiter is not a replacement for dialogue editing, volume automation, compression, or a balanced mix.

Excessive limiting can make speech sound flat, harsh, and tiring.

Making a noisy recording louder

Loudness normalization raises everything, including:

• Room noise
• Computer fans
• Electrical hum
• Reverberation
• Headphone bleed
• Compression artifacts

Fix or reduce these problems before final loudness processing.

Processing a compressed file repeatedly

Every additional lossy encoding pass can remove information and introduce artifacts.

Edit from the original WAV recordings and create compressed files only at the delivery stage.

Making the intro much louder than the conversation

Listeners form an immediate impression from the opening seconds. If the music is loud and the first speaker is quiet, the episode feels inconsistent even if its overall integrated measurement is correct.

Ignoring advertisements and inserted segments

An episode may be well mastered while an externally supplied advertisement is several decibels louder.

Measure and audition the assembled programme, including every insertion.

Relying completely on platform normalization

Platforms may process different content types in different ways. Playback behavior can also change by device, app, or listener setting.

Start with a consistent master you control.

Changing sample rates unnecessarily

Converting repeatedly between 44.1 and 48 kHz adds complexity without improving the content.

For video podcasts, keep the workflow at 48 kHz from recording through delivery. If a sample-rate or timestamp problem has already affected the edit, follow our guide to diagnosing audio and video drift.

How to improve loudness without making voices sound unnatural

The cleanest loudness improvements usually happen in several small stages.

Start with clip gain or volume automation to reduce large differences between sentences and speakers. Then apply gentle compression to control normal speech dynamics. Use a limiter only for the remaining transient peaks.

A natural spoken-word chain might include:

1. Corrective equalization
2. Noise or resonance control where needed
3. De-essing
4. Gentle compression
5. Volume automation
6. Final loudness adjustment
7. True-peak limiting

The exact order can change depending on the recording. A heavily reverberant room requires a different approach from a clean studio microphone.

Do not assume that buying a more expensive microphone will solve inconsistent production. Many of the most meaningful improvements come from recording technique, room control, source-track quality, and a reliable workflow. We cover those factors in the hidden upgrades that make a podcast sound better.

Should every episode have exactly the same LUFS reading?

Consistency is important, but a podcast is not improved by forcing every episode to match an exact decimal value.

A solo narration, an energetic panel discussion, and an immersive documentary can have different dynamics even when their integrated readings are similar.

Treat the target as a controlled range, then listen for:

• Comfortable dialogue
• Consistent speaker relationships
• Natural emphasis
• Music that supports the story
• Transitions that do not surprise the listener
• Adequate peak headroom

A reading of -16.1 LUFS is not automatically better than -16.8 LUFS. The numbers help you make decisions; they do not replace editorial judgment.

How Boomcaster supports a loudness-ready workflow

Final loudness is created during mixing and mastering, but the quality of that result depends on the source recordings.

Boomcaster captures participant audio locally rather than relying only on the sound transmitted through a live internet connection. It also provides isolated participant tracks for detailed post-production.

That gives an editor the ability to:

• Balance each speaker independently
• Reduce noise only where it occurs
• Repair interruptions without affecting every participant
• Apply different processing to different microphones
• Build a clean mix before loudness normalization
• Preserve high-quality source audio for future versions

Boomcaster’s online recording studio is designed for remotely recording high-quality podcast audio and video. After recording, Boomcaster’s AI post-production tools can help streamline the path from raw session to publishable content.

Whether you mix inside one application or move the isolated files into dedicated podcast editing software, begin with the cleanest sources available and keep a lossless master.

Podcast loudness FAQ

What LUFS level should a podcast be?

Approximately -16 LUFS integrated is a widely used target for stereo podcasts. Approximately -19 LUFS is a common convention for mono podcasts. Follow any specific requirement supplied by your host, distributor, network, or client.

Should Spotify podcasts be mastered to -14 LUFS?

Not necessarily. Spotify publishes -14 LUFS in its music-normalization guidance, but its Spotify for Creators audio-upload documentation does not state that every podcast must be mastered to -14 LUFS. Do not apply a music-mastering figure automatically to podcast production.

Is -16 LUFS too loud for a mono podcast?

It depends on the distribution specification. -19 LUFS is a common mono podcast convention, while Apple recommends approximately -16 dB LKFS for podcast audio without publishing a separate mono target in its requirements. Choose one documented standard and apply it consistently.

What is a good true-peak level for podcasts?

Keep true peaks at or below -1 dBTP. A ceiling of -2 dBTP provides additional room for changes introduced by lossy encoding.

Should podcasts use 44.1 or 48 kHz?

Both can work for audio-only distribution. Use 48 kHz when the podcast includes video or when you want one consistent production format across audio and video.

Should podcasts be recorded at 16-bit or 24-bit?

Record and edit at 24-bit whenever possible. It provides more working headroom and is better suited to production. Create a 16-bit version only when required for delivery.

What bitrate should a podcast use?

Apple recommends 64–128 kbps for mono RSS audio and 128–256 kbps for stereo RSS audio at 44.1 or 48 kHz. Check your hosting provider before exporting.

Is AAC better than MP3 for podcasts?

AAC generally provides better quality than MP3 at the same bitrate, and Apple recommends it for RSS delivery. MP3 remains widely supported and may still be the preferred format for a particular hosting workflow.

Can loudness normalization fix a bad recording?

It can correct overall level, but it cannot restore clipped speech, remove room echo, separate voices from a mixed track, or recover detail lost through heavy compression.

When should loudness be measured?

Measure the complete episode after editing and mixing. Check the compressed delivery file again after encoding.

Do podcast platforms normalize loudness?

Some services may adjust playback or process uploaded files, but behavior varies by platform and content type. Do not depend on platform processing to create a consistent podcast.

Final podcast export checklist

Before publishing an episode, confirm that:

• The final programme has been measured from beginning to end.
• Dialogue remains consistent between speakers.
• Music, advertisements, and inserted clips match the surrounding programme.
• Stereo loudness is approximately -16 LUFS, or the required target.
• Mono loudness follows your chosen documented standard.
• True peaks remain at or below -1 dBTP.
• The project uses a consistent sample rate.
• A 24-bit WAV master has been archived.
• The delivery copy matches the host’s accepted format and bitrate.
• The encoded file has been auditioned after export.
• The episode has been checked on more than one type of playback device.

Loudness standards are not about flattening every creative decision. They give your listeners a predictable starting point.

When clean isolated recordings, a balanced mix, controlled peaks, and sensible export settings work together, the podcast sounds consistent without losing the natural character of the conversation.