How to Edit and Export a Podcast Episode to MP3: The Complete 2026 Workflow

June 05, 2026 · MP3.now Editorial · Podcasting Workflows

Every podcast episode ends its life the same way: as a single MP3 file sitting on a hosting server. Everything before that moment — the multitrack session, the edits, the processing — exists only to make that one file sound good and load fast. Yet most editing tutorials stop at "export when you're done," skipping the settings that decide whether your episode sounds professional on AirPods and cheap earbuds alike, and whether a one-hour show weighs 40 MB or 400 MB. This is the complete workflow, from raw session to upload-ready MP3.

Work in the right order: edit first, process second, export last

The single biggest time-waster in podcast production is processing audio you are about to delete. If you apply noise reduction and EQ to a 70-minute session and then cut it down to 45 minutes, you processed 25 minutes of audio for nothing — and if you re-record a segment, you have to process again. Professionals lock the order: content edit, then cleanup, then loudness, then export.

Pass 1: the content edit

Go through the episode once at slightly elevated playback speed and make only structural decisions: cut the pre-show chatter, tighten tangents, remove failed takes, drop in your intro and outro placeholders. Do not touch a fader or an EQ. The goal is a locked runtime.

Pass 2: cleanup

Now handle the audio quality problems on the locked edit: remove mouth clicks and harsh breaths where they distract, apply gentle noise reduction to hissy tracks, and use a high-pass filter around 80–100 Hz on every voice track to remove rumble that eats headroom without adding anything audible to speech.

The processing chain that makes voices sit right

A minimal, reliable chain for each voice track runs in this order:

  • High-pass filter at 80–100 Hz to clear low-frequency rumble.
  • Subtractive EQ to tame boxiness (usually a small cut around 250–400 Hz) and harshness (2–4 kHz) if present.
  • Compression with a ratio around 3:1 and 3–6 dB of gain reduction on peaks, which evens out the distance-to-mic drift every untrained speaker produces.
  • Loudness normalization on the final mix, targeting -16 LUFS for a stereo file (or about -19 LUFS for mono), with true peaks kept at or below -1 dBTP.

That last step matters more than any other. Podcast apps normalize playback loudness, and episodes delivered far from the target get either turned down (harmless) or turned up in ways that expose noise floors. If your editor does not measure LUFS, export your mix and run it through a dedicated MP3 normalizer as a final step. The loudness normalization guide explains what LUFS measures and why peak normalization alone is not enough.

Export twice: a WAV master, then the MP3

Never make the MP3 your only export. Bounce the finished episode as a WAV first — 16-bit, 44.1 kHz is plenty for a spoken-word master — and archive it. This is the file you will return to when you need a clip for social media, when a hosting platform changes its requirements, or when you remaster the back catalogue. Re-editing from an MP3 means re-encoding an already lossy file, and each generation loses a little more quality.

Then encode the delivery MP3 from that WAV using a WAV to MP3 converter. Keep the sample rate at 44.1 kHz; resampling to 48 kHz buys nothing for speech, and 44.1 kHz is the safest common denominator across players. The sample rate FAQ covers when 48 kHz actually matters (video work) and when it does not (podcasts).

The bitrate decision, with real numbers

MP3 file size is pure arithmetic: bitrate in kilobits per second, divided by eight, times duration in seconds. That gives you these figures for a 60-minute episode:

  • 320 kbps stereo: about 144 MB — wasted on speech; nobody can hear the difference from 128 kbps on a voice recording.
  • 128 kbps stereo: about 58 MB — the de facto standard for stereo podcasts with music beds, and it keeps a one-hour episode under 60 MB.
  • 96 kbps mono: about 43 MB — excellent for voice-only shows.
  • 64 kbps mono: about 29 MB — still perfectly intelligible speech; the classic choice for long interview archives.

If your show is conversation with no stereo music, mono at 96 kbps is the sweet spot: transparent for voices and roughly half the download of stereo at equivalent quality. The podcast bitrate FAQ walks through the reasoning in more depth. Use constant bitrate (CBR) rather than variable: some players and hosting pipelines still misreport duration or scrub badly on VBR files, and the size savings on speech are minor — the CBR vs VBR explainer covers the trade-off. If an already-exported episode came out too heavy, an MP3 compressor can re-encode it down to target without touching your session.

Metadata and the final file

Before upload, fill in the ID3 tags: episode title, show name as artist, season and episode numbers, and cover art. Some podcast apps read these directly, and a file that escapes your RSS feed — shared in a group chat, copied to a USB stick — carries its identity with it. Name the file predictably (show-name-ep042.mp3) so your future self can find episode 42 in a folder of two hundred files.

The pre-upload checklist

  • Runtime locked, intro and outro in place, no editing artifacts at cut points.
  • Loudness at -16 LUFS stereo (or -19 mono), true peak at or below -1 dBTP.
  • WAV master archived to at least two locations.
  • MP3 encoded at CBR 128 kbps stereo or 96 kbps mono, 44.1 kHz.
  • ID3 tags and artwork embedded, filename follows your convention.
  • Spot-check the actual MP3 — first minute, a middle segment, the outro — on the worst headphones you own.

That last item catches more published mistakes than everything else combined. The encoder is rarely where problems hide, but a two-minute listen to the real deliverable is the cheapest insurance in podcasting. Once the checklist passes, upload — and next week the workflow runs faster, because every step is a decision you have already made once and never need to make again.