How to true-peak limit your podcast for streaming
- Step 1Finish editing and level the episode first — Peak limiting is the last step. Edit, denoise, and level loudness first — run loudness-normalizer (Apple Podcasts -16 LUFS or Spotify -14 LUFS) so the episode hits the right loudness, then bring it here for the ceiling. For dialogue evenness, speech-leveler helps before normalization.
- Step 2Check your tier against episode length — The limiter is Pro-gated. Pro allows 200 MB and 120 minutes per file — fine for most episodes, but a long, high-bitrate WAV interview can exceed either limit. Pro + Media and Developer remove the duration cap (100 GB).
- Step 3Drop the finished episode onto the tool — FFmpeg WebAssembly processes it locally; the episode stays in your browser tab. Accepted input is any audio FFmpeg can decode — your edited WAV master or an exported MP3.
- Step 4Leave the ceiling at -1.0 dBTP — The default -1.0 dBTP · standard is the podcast ceiling — Apple and Spotify both expect it. There's no reason to change it for spoken word unless your host re-encodes at very low bitrate, in which case -1.5 dBTP adds margin.
- Step 5Choose MP3 for upload or WAV for a lossless master — Most podcast hosts accept MP3; the 192 kbps output here is well above the spoken-word floor. If your host re-encodes from a lossless source, output WAV or FLAC so only one lossy generation happens.
- Step 6Verify the peak and upload — Confirm the reported peak sits at or near -1.0 dBFS, then upload to your host. The episode now has the headroom Apple Podcasts and Spotify's encoders need to play it back clean.
Podcast platform loudness + true-peak targets
What the major podcast destinations expect. Hit the LUFS with loudness-normalizer; hit the true-peak with this tool. Figures reflect the LUFS presets the loudness-normalizer uses.
| Platform | Loudness target | True-peak ceiling | This tool's option |
|---|---|---|---|
| Apple Podcasts | -16 LUFS | -1 dBTP | -1.0 dBTP · standard |
| Spotify (podcasts) | -14 LUFS | -1 dBTP | -1.0 dBTP · standard |
| YouTube (video pods) | -14 LUFS | -1 dBTP | -1.0 dBTP · standard |
| Generic host (Buzzsprout etc.) | -16 LUFS recommended | -1 dBTP | -1.0 dBTP · standard |
Recommended podcast mastering order
Where peak limiting sits in a typical spoken-word chain. Each step is a separate JAD tool; the one-click chain runs them together.
| Step | Tool | Purpose |
|---|---|---|
| 1 | ai-noise-reducer | Remove background hiss/hum (RNNoise speech model) |
| 2 | silence-stripper | Trim dead air and long gaps |
| 3 | speech-leveler | Even out quiet and loud passages |
| 4 | loudness-normalizer | Hit -16 / -14 LUFS (EBU R128, two-pass) |
| 5 | true-peak-limiter (this tool) | Final -1.0 dBTP ceiling before upload |
Cookbook
Podcast-specific limiting jobs. Peak figures reflect the dBFS ebur128 reports after processing.
Leveled episode, final -1 dBTP ceiling for Apple Podcasts
After loudness-normalizing to -16 LUFS for Apple Podcasts, a stray loud transient still peaks near full scale. The default ceiling pulls it to -1 dBTP so Apple's encode stays clean.
Input: episode-leveled.wav (-16 LUFS, peak -0.4 dBFS) Ceiling: -1.0 dBTP · standard Format: MP3 (192 kbps) Output: episode-final.mp3 ebur128 peak: -1.0 dBFS Apple Podcasts re-encode won't clip the loud transient.
Catch a desk bump that survived editing
A single loud thump near the end peaks at 0 dBFS while the rest of the episode is well below. The limiter pulls just that transient down without touching the dialogue.
Input: episode.wav (dialogue ~-6 dBFS, one bump at 0 dBFS) Ceiling: -1.0 dBTP Output: dialogue unchanged, bump pulled to -1.0 dBFS. Look-ahead limiter only acted on the transient.
Low-bitrate host — tighten to -1.5 dBTP
A host that re-encodes to 64 kbps mono can overshoot more. The safer ceiling keeps margin without audibly affecting speech level.
Input: episode-leveled.wav Ceiling: -1.5 dBTP · safer Format: MP3 (192 kbps) Output: episode-final.mp3, peak ~-1.5 dBFS Survives the host's 64 kbps mono re-encode cleanly.
Deliver a lossless master to a re-encoding host
Some hosts re-encode from a WAV master. Limit to -1.0 dBTP and output WAV so the host's single lossy encode starts from a clean, peak-safe source.
Input: episode-leveled.wav Ceiling: -1.0 dBTP Format: WAV (16-bit PCM) Output: episode-master.wav, peak -1.0 dBFS Host re-encodes once from a clean -1 dBTP source.
Or just run the whole chain at once
If you'd rather not run five tools by hand, the one-click master runs denoise → strip → normalize → true-peak limit together. This per-tool limiter is for when you want the ceiling step alone.
Alternative: podcast-master (one-click chain)
→ RNNoise denoise → silence strip → EBU R128 normalize
→ true-peak limit → publish-ready file
This tool: just the final -1.0 dBTP ceiling, on demand.Edge cases and what actually happens
Full-length episode exceeds Pro's 120-minute cap
Limit exceededPro caps each file at 120 minutes (and 200 MB). A long interview or panel episode can exceed the duration limit even if the file size is modest. Split it with audio-splitter and limit each part, or upgrade to Pro + Media / Developer for unlimited duration (100 GB).
Free account tries to limit an episode
Requires ProThe limiter is Pro-only. A Free account gets a 'requires a Pro subscription' message before processing. Free's audio limits (50 MB / 30 min) are for other tools; the true-peak limiter needs Pro (200 MB / 120 min).
Episode is quiet — limiter does nothing
PreservedWell-leveled spoken word often peaks below -1 dBTP already, so the limiter never engages and the audio is unchanged apart from the format re-encode. That's correct — the limiter is a ceiling, not a loudness boost. If the episode is too quiet, normalize loudness with loudness-normalizer rather than expecting the limiter to raise it.
Expecting the limiter to set podcast loudness
Wrong toolThis tool only sets the peak ceiling; it doesn't target LUFS. Apple/Spotify loudness (-16/-14 LUFS) comes from loudness-normalizer (two-pass EBU R128, which also applies -1 dBTP). Use this limiter as the final guarantee after normalization, or use podcast-master for the whole chain.
MP3 output bitrate can't be lowered for a small file
By designLossy output is fixed at 192 kbps here — more than enough for speech but not adjustable. If your host needs a specific smaller bitrate (e.g. 64 kbps mono), output WAV from this tool then set the bitrate with bitrate-changer.
Reported peak slightly above -1.0 dBFS
By designalimiter is sample-peak based and ebur128 reads true-peak-style, so after a -1.0 dBTP limit the verification may read around -0.9 dBFS. That's normal and still host-safe — the margin is intentional. Pick -1.5 dBTP for a larger guaranteed gap on aggressive hosts.
Stereo music-bed podcast stays stereo
PreservedThe limiter doesn't downmix to mono or change the sample rate — a stereo episode with a music bed stays stereo. If you want a smaller mono file for a speech-only show, use mono-to-stereo or a channel tool separately; the limiter leaves the channel layout alone.
Video podcast file dropped in
Audio-only toolFor a video podcast, extract the audio first with video-to-wav or video-to-mp3, limit it, then re-mux in your editor. This tool processes audio, not video containers.
Already-published MP3 re-limited and re-encoded
Quality noteLimiting an existing MP3 and outputting MP3 again stacks a second lossy generation, softening speech slightly. If you still have the WAV master, limit that instead and output WAV/MP3 from a clean source. For a one-off fix it's acceptable, but the lossless master is always the better input.
Episode still distorts after limiting
Source issueIf distortion remains, it was recorded into the take (mic/preamp clipping) — limiting can't undo capture-stage clipping. Re-record the affected segment, or accept the distortion is in the source. The limiter only prevents new overshoot on encode.
Frequently asked questions
What ceiling should I use for a podcast?
-1.0 dBTP — the default. Apple Podcasts and Spotify both pair their loudness targets (-16 and -14 LUFS) with a -1 dBTP ceiling. Only tighten to -1.5 dBTP if your host re-encodes at very low bitrate; there's rarely a reason to go to -2.0 dBTP for speech.
Is peak limiting enough, or do I also need loudness normalization?
You need both, in order. Normalize loudness first (loudness-normalizer at -16 LUFS for Apple or -14 for Spotify), then run this limiter as the final -1 dBTP ceiling. Limiting alone handles peaks but not how loud your show plays relative to others.
Where does peak limiting fit in my podcast workflow?
Last. The order is denoise → strip silence → level dialogue → normalize loudness → true-peak limit. The limiter is the final safety step before upload. If you'd rather not run each tool by hand, podcast-master runs the whole chain in one click.
Can a long episode hit a length limit?
Yes. Pro caps each file at 120 minutes and 200 MB. A long interview can exceed the duration limit. Split it with audio-splitter, or upgrade to Pro + Media / Developer, which remove the duration cap (100 GB files).
What does the tool actually do to the episode?
It runs FFmpeg's alimiter look-ahead brickwall limiter at your ceiling (converted from dB to linear), then verifies with ebur128=peak=true and reports the achieved peak in dBFS. Everything runs as WebAssembly in your browser — the episode never uploads.
Is the podcast limiter free?
No — it requires Pro. Free accounts can't run it. Pro processes episodes up to 200 MB / 120 minutes; Pro + Media and Developer go to 100 GB with no duration cap, useful for long shows.
Does my episode upload to a server?
No. FFmpeg runs locally in your browser via WebAssembly; the episode stays in the tab. Only an anonymous usage counter is recorded — never the audio. Unaired or sensitive content stays on your machine.
Should I upload MP3 or WAV to my host?
Depends on the host. Most accept MP3 — the 192 kbps output here is well above the spoken-word floor. If your host re-encodes from a lossless source, output WAV or FLAC so only one lossy generation occurs.
Will limiting make my voice sound squashed?
Not if applied as a final ceiling on a properly leveled episode — it only touches the few peaks above -1 dBTP. It squashes only if the episode is overall too hot, which means it needed loudness normalization first, not heavier limiting.
Can the limiter fix audio that was recorded too loud and distorted?
No. Capture-stage clipping (mic/preamp overload) is baked into the recording and can't be removed by limiting. Re-record the segment if possible. The limiter prevents new clipping on encode; it doesn't repair distortion already in the take.
Why isn't the reported peak exactly -1.0 dBFS?
alimiter is a sample-peak limiter while ebur128 measures true-peak-style, so the verification can read a hair above the linear ceiling — around -0.9 dBFS after a -1.0 dBTP limit. That small margin is intentional and is why -1 dBTP, not 0, is the podcast standard.
Can I limit a whole season in one go?
The limiter processes one file at a time on Pro, so you'd run each episode through the same default ceiling. The consistent -1.0 dBTP across episodes gives your season uniform headroom for the host's encoder. For full multi-step processing, podcast-master also runs per-episode.
Privacy first
Every JAD Audio tool runs entirely in your browser via FFmpeg (WebAssembly) and RNNoise. Your audio files never leave your device — verified by zero outbound network requests during processing.