Mono vs Stereo Podcast Loudness: Why Mono Targets -19 LUFS
If your show is a single voice, mono files are smaller and simpler. But the loudness target changes with the channel count: -16 LUFS for stereo, -19 LUFS for mono. Publish a mono episode at -16 and it will sound louder than every stereo show in the queue. This guide explains the 3 LU rule and how to apply it without thinking about it again.
LoudNorm detects mono files automatically and applies the -19 target when you pick the Podcast preset.
Why Mono Plays Louder
A mono file is played through both earbuds or both speakers at once — the same signal, doubled. Two copies of the same sound sum to a louder perceived level than one copy, by about 3 LU. The loudness meter, measuring the single channel, does not know the file will be doubled at playback. So the convention compensates in advance: measure the mono file to -19 LUFS and it will be heard at the same loudness as a stereo file at -16.
| File type | Target | Heard as |
|---|---|---|
| Stereo episode | -16 LUFS | -16 LUFS in the queue |
| Mono episode at -19 LUFS | -19 LUFS | Matches the stereo shows |
| Mono episode at -16 LUFS | -16 LUFS | About 3 LU hotter than everything else |
The doubling is not a metaphor. When the same signal arrives at both ears, the brain sums it and judges it louder than a signal at one ear — acousticians call it binaural summation, and the size of the effect for correlated signals at both ears is roughly 3 dB at typical levels. Stereo content escapes the effect because its two channels carry different signals (music spread, room, panned voices) that do not sum the same way. A centred voice in a stereo file does sum — which is one reason a voice-heavy stereo mix can measure differently from how it feels, but the convention keeps life simple: it grades the file by its channel count, not by its content.
Which Shows Should Be Mono?
Solo narration, single-host commentary and voice-only interviews with no music beds are natural mono candidates: half the file size, identical clarity for speech. Shows with music, stereo ambience or panned voices should stay stereo. The choice is made at export; loudness comes after, as in the -16 LUFS workflow.
Some more cases, decided:
| Show format | Verdict | Why |
|---|---|---|
| Solo host, voice only | Mono | Nothing stereo exists in the content; halve the file |
| Two hosts, one call, voices centred | Mono works | Both voices are centre content anyway |
| Interview with stereo music intro and beds | Stereo | The music was produced in stereo; mono folds it down and thins it |
| Field reporting with ambience | Stereo | The place is part of the story, and place is stereo |
| Fiction and audio drama | Stereo | Panning and space are the craft |
| Video-first show's audio feed | Match the video | Listeners switching between versions hear one consistent show |
Whatever you choose, choose once and stay with it. A feed that alternates mono and stereo episodes at random sounds unsettled even when every episode is individually on target, because the character of the sound keeps changing under the listener from one week to the next.
How to Normalize Mono Correctly
- Export the episode in mono if that is your format.
- Measure it — the meter reports the single-channel loudness (see what LUFS means).
- Normalize to -19 LUFS with a -1 dBTP true-peak ceiling (why the ceiling matters).
- Confirm the report shows -19 ±1 LUFS, then publish.
With the Podcast preset on the home page, steps 2–4 happen automatically and the mono target is chosen for you; the report states which target was applied.
Notice step 3 says -19, not "the same as stereo." This is the whole guide in one line: the target follows the channel count. Everything else — the measurement method, the ceiling, the tolerance — is identical to stereo work.
A Worked Example: The Solo Show That Shouted
A solo narrator exports her episodes in mono — sensibly — but her editing template normalizes everything to -16, because the template was built for a stereo show. Her episodes measure a correct-looking -16.0 LUFS. In subscribers' queues, each episode then plays roughly 3 LU louder than the programmes around it. Reviews begin to say "great show, weirdly loud," and one listener asks if she changed microphones.
Nothing is broken. One line in the checklist — "mono = -19" — fixes it permanently. Her next episode measures -19.1 LUFS, true peak -1.1 dBTP, and the queue goes quiet about her loudness forever. Meanwhile her file sizes halved when she went mono and her voice never lost a thing. Mono done right is all upside; mono done at the stereo target is the single most common loudness error in podcasting.
The Reverse Mistake: Stereo Files at -19
The rule cuts both ways. A stereo show normalized to -19 "because the host read somewhere that podcasts should be -19" plays 3 LU under the queue, and the host concludes that listeners find the show "a bit quiet and flat." If you have inherited a template or a preset from another producer, check which channel count it assumes. Presets that do not ask about channels are stereo presets by default — except when they are not. The report is your friend: it states the target that was applied, and one glance settles which convention you actually shipped.
What About Dual-Mono and Fake Stereo?
Two edge cases confuse meters and producers alike:
Dual-mono files. A stereo file whose two channels carry the identical signal is mono wearing a stereo costume. It will sum at playback exactly like a mono file. If your "stereo" episodes are really one voice duplicated to both channels, grade them by the mono rule — or better, export true mono and take the file-size saving too.
Joint stereo MP3s. Encoders often store speech-heavy stereo efficiently by coding the shared centre once. This changes file size, not loudness behaviour: a genuinely stereo programme still grades to -16.
One voice panned slightly off-centre. Still essentially centre content; some producers do this to "sound stereo." It buys nothing and complicates the target question. Keep voices centred and let the channel count carry the decision.
When a file's channels are ambiguous, the honest test is playback: does it sound like one centred voice? Then the mono convention describes how listeners will hear its loudness, whatever the container claims.
Switching Formats Without Scaring Your Listeners
Shows change formats: the solo host adds a co-host, the music podcast drops its beds, the video show spins off an audio feed. If you switch channel count, handle the loudness transition deliberately:
- Pick the episode where the format changes and keep everything else about the sound the same — same voices, same processing — so only one variable moves.
- Grade the first new-format episodes by the new rule (-19 for mono, -16 for stereo) and verify by the queue test: play the last old episode and the first new one back to back at one volume setting. Your ears should report "same show," even though the meters reported different numbers.
- Say nothing about it publicly. Listeners do not need a loudness announcement; they need the absence of surprises.
If the queue test fails — the new episode still sounds louder or quieter — trust your ears over the convention once, check the file for the edge cases above (especially dual-mono), and fix the file rather than the rule. The convention describes typical playback honestly; a genuinely unusual file can bend it.
Troubleshooting
My mono episode still sounds louder than other shows at -19. Check for the dual-mono and template traps first, then listen for range: a tightly compressed mono episode at -19 can feel louder than a gentle stereo show at -16, because its average moment-to-moment level sits high even at the correct integrated number. That is a loudness-range question, answered in the LRA guide, not a target error.
My editor shows two channels for my mono file. Some editors wrap mono in a stereo timeline. What matters is the export: if the exported file has one channel, it is mono. Check the file's properties, or read the normalizer's report, which states the channel count it found.
A guest episode came back as a stereo file from my producer. Grade it as stereo (-16) for consistency with its own container, or ask for the mono export. Do not apply -19 to a true stereo file just because the show is "usually mono" — the rule follows the file, not the show's habits.
The Common Mistake
The usual error is a DAW template: a mono show exported through a stereo preset at -16, or a loudness tool that never asked about channels. The episode then shouts over the listener's other podcasts, and the platform's own normalization may or may not forgive it. One line in your publish checklist — "mono = -19" — prevents it forever.
Templates deserve the blame, honestly assigned. Loudness errors are rarely knowledge errors; the producer often knows the rule. They are workflow errors — a preset chosen once, in a hurry, in season one, silently applied to two hundred episodes. The cure is to put the channel check in the one place it cannot be skipped: the pre-publish measurement. If the report says the file is mono and the target says -16, stop. That mismatch is the mistake, caught at the last possible moment, every time it tries to happen.
Frequently Asked Questions
Does the -19 rule apply on Spotify and YouTube too? The doubling at playback is physics, not policy, so it applies everywhere a mono file plays through two ears. Streaming references differ (-14), so a mono streaming master sits 3 LU under that: measure mono to the platform target minus 3 and it will be heard at the platform loudness. Tools that detect channels — LoudNorm among them — apply the offset for you when you pick the preset.
Should I convert my stereo back catalogue to mono? No. The catalogue's loudness is already graded as stereo and sounds consistent. Converting changes file character for no loudness benefit. Decide mono versus stereo at the format level, going forward, and leave history alone.
My host records two people on one microphone. Mono? Yes — one microphone produces one channel of content regardless of how many voices it hears. Export mono, target -19.
Does mono hurt discoverability or quality scores? No platform grades channel count. Speech clarity is identical; file size halves; download and streaming costs drop; listener data usage drops with them. For voice-only shows, mono is simply the technically honest format, and the -19 target is its only special rule.
What if my show has a stereo intro but a mono body? Then the file is stereo, and it grades to -16. If the intro is a short brand sting, consider rendering the whole episode in mono with the sting folded down — but audition the fold-down first, because some stereo stings thin out badly in mono. Consistency of the body matters more than the five seconds of branding.
Do smart speakers change the rule? A single smart speaker sums channels to one driver, so a stereo show's centred voice and a mono file arrive similarly; the -19 convention still governs, because the same feed must also behave on earbuds, where the doubling is full. Grade for the two-ear case and the one-speaker case follows along acceptably — it has no better option, and neither do you.
References
- https://www.apple.com/apple-podcasts/ — Apple Podcasts, whose guidance carries the -16 stereo / -19 mono convention.
- https://www.itu.int/rec/R-REC-BS.1770 — ITU-R BS.1770, the measurement method.
- https://tech.ebu.ch/publications/r128 — EBU R128, the loudness framework behind the convention.