Notice it yet? One episode sounds louder, the next sounds thinner, and the music seems to sit differently every time. If your podcast sounds different from week to week, you’re not imagining it.
Since 2014, we’ve launched 3,000+ podcasts and produced 50,000+ episodes as a full-service podcast production agency. This article is for marketing, comms, and L&D teams who work with a production partner and want their show to have a consistent sound.
We’ll look at what causes those inconsistencies, what should be included in a written audio spec, and how you can compare three episodes in about 30 minutes. I’ll also share some of the things we look at during our own production process.
Why one show can sound like three
A lot of inconsistencies start during the editing process. The hosts and recording environment might stay the same, but small differences in how each episode is mixed can add up.
One episode has music that sits nicely underneath the conversation. The next has music that’s competing with the host. You can hear that something is different, even if you can’t quite put your finger on what it is.
Here’s the goal we set for every show:
The goal isn’t to make every episode sound identical. Content and recording conditions are naturally going to vary. What we want is a consistent listening experience where those differences don’t distract from the conversation or make it feel like a completely different team produced each episode.
It’s really about creating a consistent feel. Your listeners should be able to move from one episode to the next without noticing a change in the production team behind the scenes.
What your listeners notice first
Your audience will often notice a difference before you do. They probably aren’t going to describe it as a change in vocal processing or compression. They’re just going to reach for the volume knob.
From our production sessions:
Listeners usually notice the experience before they can identify the technical problem. They might find themselves turning the volume up for one episode and down for the next. The host’s voice might feel noticeably different, background music might become distracting, or transitions might feel abrupt. Even if they can’t explain why something sounds off, those changes can make the show feel less polished.
Ever found yourself turning a podcast up one week and down the next? That’s one of the more noticeable signs of inconsistent podcast volume levels.
And it can have a bigger impact than you might think. Even when the conversation and content are great, a show that sounds inconsistent can leave listeners with the impression that it isn’t as polished as it could be.
The tricky part? Your own team may not notice these differences as easily. When you’re listening to the same show every week, you become familiar with it. Small changes can start to feel normal, even when they’re noticeable to someone listening for the first time.
What causes inconsistent podcast audio
It’s easy to point to the editor when something sounds different, but the editor isn’t necessarily the problem. More often, the issue is whether everyone involved in production is working from the same expectations and standards.
Here’s how I would look at it:
I would point to a combination of factors rather than one single cause. Having a rotating pool of editors can contribute to inconsistencies, but the bigger question is whether everyone is following the same standards and processes. Without those, even experienced editors may make different decisions about how an episode should sound.
Here are some of the most common causes of inconsistent podcast audio:
- Spec: There’s no written audio standard, so each editor is making their own decisions about how the show should sound.
- People: Multiple editors are working on the show, each with their own preferences and approaches.
- Source: Recordings come in at different levels or with varying amounts of background noise.
- Processing: Voice settings, compression, or noise reduction are applied differently from one episode to the next.
- Tools: Templates or plugins change, but those changes aren’t communicated or documented.
- Quality control: The review process looks for technical errors but doesn’t necessarily compare the episode against the show’s established sound.
That last one is worth paying attention to. An episode can pass every technical check and still sound noticeably different from the rest of the show.
Curious what a producer does all day? For the full picture, read what a podcast producer does day to day.
What a written audio spec should hold
A good audio spec needs to cover two things: the technical standards and the overall sound you’re trying to achieve.
The technical side gives your editors measurable targets to work toward. The other side helps everyone understand how the show should actually sound, so those decisions aren’t being made from scratch every time an episode is assigned.
Here’s how I look at that second piece:
The objective isn’t to take away an editor’s judgment or creativity. It’s to give them a consistent framework to work within. That way, regardless of who is assigned to an episode, everyone is working toward the same end result.
| Part of the spec | What it sets | Question it answers |
|---|---|---|
| Loudness target | The average level of a finished episode | How loud should the whole episode play? |
| Peak ceiling | The highest point the signal may reach | How close to the digital limit can it go? |
| Host sound | Tone and processing for the main voice | Should the host sound warm, bright or plain? |
| Music | Where beds sit under speech and how they fade | Does the music ever fight the voice? |
| Transitions | Timing for intros, outros and breaks | How long is the gap between segments? |
| Reusable assets | Intro, outro and bed files used every time | Which files may an editor swap? |
Now let’s talk about the numbers. How loud should a podcast be? That depends on which measurement you’re using.
Apple’s audio requirements recommend approximately -16 LKFS, give or take 1 dB, with a true peak at or below -1 dBFS.
Podnews says LUFS and LKFS name the same measure. It also notes that many podcasters aim for -16 LUFS, while Spotify normalizes audio to -14 LUFS.
What about dBFS? According to NUGEN Audio, dBFS measures digital signal level, while LUFS measures perceived loudness. They’re related, but they aren’t interchangeable.
Here’s the target we use:
At Resonate, our loudness target is -16 dBFS. Having a defined target gives our editors a consistent baseline to work from rather than leaving everyone to make their own judgment about how loud an episode should be.
If you’re working with a production partner, ask what LUFS target they use for your show and, just as importantly, which measurement they’re referencing. Get the target and peak ceiling documented so everyone is working from the same standard. That’s an important part of establishing consistent podcast audio.
But the numbers alone aren’t going to solve everything:
The loudness target is only one part of the equation. Two episodes can hit the exact same technical target and still sound noticeably different. Vocal processing, background noise, compression, and the balance between dialogue and music all play a role.
The same goes for templates. They help establish consistency, but they can’t compensate for poor source audio or replace an editor’s judgment.
That’s why templates are still important. Having saved intros, outros, and music beds helps keep timing and presentation consistent, regardless of who is assigned to the episode.
Want to learn more about what goes into a polished episode? Our guide to how to edit a podcast walks through the process.
Check it yourself in 30 minutes
You don’t need specialized equipment or software to start identifying inconsistencies. A simple listening exercise can tell you quite a bit.
We recommend starting with three recent episodes.
- Minutes 1 to 5: Pick three episodes. Load them on the same device and use the same headphones for all three.
- Minutes 6 to 20: Listen to the opening, a representative section of conversation, and any music changes or transitions in each episode.
- Minutes 21 to 30: Make notes about what you heard and when you found yourself reaching for the volume control.
Once you’ve listened to all three, there are five areas I’d focus on:
1. Dialogue loudness: Does the host sound consistently present and comfortable to listen to, or are you finding yourself adjusting the volume between episodes?
2. Music bed and intro treatment: Is the music balanced appropriately underneath the conversation? Are the intro levels, fades, timing, and transitions consistent?
3. Vocal tone and processing: Does the host’s voice have a similar sound from one episode to the next? Or are differences in EQ, compression, noise reduction, or other processing making the voice noticeably different?
4. Technical measurements: I’d compare integrated LUFS, true peak, and loudness variation throughout each episode. Depending on the recording conditions, I’d also take a look at background noise and the noise floor.
5. Editing and overall polish: Are pauses, cuts, and transitions handled consistently? Are changes in recording quality addressed appropriately? Most importantly, is anything distracting from the content or interrupting the listening experience?
For the fourth check, you’ll need a loudness meter. Apple’s requirements above give you a good reference point for comparison.
One important thing: Don’t jump straight into fixing everything you notice. Start by documenting what you’re hearing and identifying which of these five areas has the biggest difference between episodes. That gives you somewhere concrete to start.
Need some help with the recording side of things? Our guide to how to record a podcast covers the setup and recording process.
What finished episodes can and can’t tell you
Listening to finished episodes is a great place to start, but it won’t necessarily tell you why something sounds different. Sometimes you need to go back to the original recordings to figure that out.
Here’s what you can identify at each stage:
- From finished episodes: Differences in loudness, music balance, vocal tone, and transitions.
- From raw files: Source noise, microphone level issues, and changes in recording quality from one session to the next.
- From the production workflow: Which editor, template, or plugin was used and where different production decisions were made.
Remote guests can introduce another layer of inconsistency, especially when recording environments, microphones, and internet connections vary. Our guide to remote podcast recording covers some of the ways to help keep guest audio consistent.
If you need to get to the bottom of a recurring issue, ask your production partner for the raw recordings. Without those files, there are some things you simply won’t be able to diagnose with certainty.
What to ask your producer about consistency
If consistent audio is important to your show (and it should be!), there are a few questions I’d recommend asking your production partner.
A good producer should be able to walk you through these without making things overly technical:
- Spec: Do you have a written audio spec for our show, and can we see it?
- Targets: What loudness measurement and peak ceiling do you use?
- Templates: Which intros, outros, and music beds are saved and reused?
- People: When an editor changes, how do you make sure the show’s established sound carries over?
- Quality control: Are episodes compared against previous episodes before delivery, or is QC focused primarily on individual technical checks?
- Raw files: Can we access the original recordings if we need to investigate an audio issue?
For more guidance, take a look at our questions to ask a podcast agency. You can also review what a full-service package includes to better understand where editing and mixing fit into the overall process.
Our guide to working with a podcast production company covers what that partnership should look like. And our lessons from 100 business shows highlight some of the practices that help keep a show running consistently.
If you’re looking for a production partner to manage the process and maintain your show’s sound week after week, learn more about our podcast management service.
What we can’t tell you
There are a few things worth keeping in mind when evaluating your show’s audio:
- We can’t tell you exactly why your show sounds different without hearing it. The causes we’ve covered are common possibilities, not a diagnosis of your specific show.
- We can’t identify every source noise or microphone issue from a finished episode alone. That requires access to the original recordings.
- We can’t promise that hitting a specific loudness target will automatically fix inconsistent audio. Two episodes can meet the same target and still sound different.
- We can’t make every episode sound identical. Recording conditions, conversations, and content will naturally vary. The goal is a consistent listening experience, not identical recordings.
- We can say that having a written spec, consistent templates, and a process for comparing episodes makes it much easier to identify and address inconsistencies.
Conclusion
Consistency doesn’t happen by accident. It comes from having clear, documented standards that everyone involved in production understands and follows.
If you’re not sure where to start, try the three-episode listening exercise. Then ask your producer to walk you through the audio spec they’re using for your show. Those two steps can tell you a lot about where inconsistencies are coming from and what needs attention.
Want a second set of ears on your show? Book a call and we’ll listen to a few episodes with you.