The short answer
Podlove Publisher is the most detailed podcast publishing system WordPress has: episodes, multiple media formats per episode, chapters, contributors, transcripts, feeds. It is precise about everything except the one thing it never claimed — how the audio actually sounds. Nothing in Podlove reports that an episode sits 6 LU below the last one.
What Podlove does and does not cover
Podlove validates that your media files exist, are reachable and have the expected size and type. That is a delivery check. A file can pass it and still be far too quiet — validation says the file arrived, not that it is publishable.
| Step | Handled by Podlove |
|---|
| Episodes, media formats, chapters, contributors | Yes |
| Feeds and subscribe button | Yes |
| Asset validation (file exists, size, type) | Yes |
| Is the episode loud enough? | No |
| Will it clip on playback? | No |
| Is there dead air in it? | No |
Several formats, several files
Podlove’s multi-format model is a strength and a trap. One episode can carry MP3, M4A and Opus versions, and each is a separate render from your production chain. If one of them came out of a different export preset, listeners on that format hear a different episode from everyone else — and nothing in the publishing flow will say so.
Measuring the file you actually ship, rather than the session you exported it from, is the only way to catch that.
Adding the check to a Podlove workflow
- Render your episode and register the media formats as usual.
- In the WordPress editor, run an AudioLinter analysis on the file: integrated loudness, true peak, loudness range and any dead air.
- If it is off target, repair it and re-register the corrected file.
- Publish, and let Podlove do the part it is good at.
What to look at
- Integrated loudness against your target. −16 LUFS for Apple Podcasts, about −14 for Spotify and YouTube, −23 LUFS if you also deliver to broadcast. See the platform targets.
- −1 dBTP true peak or lower, so a lossy encode does not clip on playback.
- Loudness range. A wide range usually means one voice is much louder than the rest — common in panel shows, and invisible until someone listens in a car.
Frequently asked questions
Does Podlove Publisher check audio loudness?
No. Podlove Publisher handles episodes, media formats, chapters, contributors and feeds — publishing infrastructure, in more detail than most plugins offer. Its wordpress.org listing does not mention loudness, LUFS, true peak or normalisation. The files you register as media formats are shipped exactly as they are.
Podlove validates my media files already — is that not enough?
Podlove's asset validation checks that a file exists, is reachable and has the expected size and type. That is a delivery check, not an audio check: a file can validate perfectly and still be 8 LU too quiet.
Where does a loudness check fit into a Podlove workflow?
After the file is rendered and before the episode is published. Podlove's strength is that one episode can carry several media formats; each is a separate file, and each ships at whatever level it was rendered.
Does AudioLinter replace Podlove Publisher?
No. Podlove owns episodes, formats, chapters and feeds — considerably more than AudioLinter would ever attempt. AudioLinter measures and repairs the audio file. They work side by side in the same WordPress install.
What should I check before publishing?
Integrated loudness against your target (−16 LUFS for Apple Podcasts, about −14 for Spotify and YouTube, −23 LUFS for broadcast), true peak at or below −1 dBTP, and no long silent stretches.