1.8k

Shares

Best Audio Format for Podcasts: Bitrate, Mono vs Stereo, File Size

For a talk podcast, MP3 at 64 to 96 kbps in mono is the best format. If the show is built around music, step up to 96-128 kbps stereo. Anything above that spends data and storage on detail a voice recording does not contain.

This matters more for podcasts than for music because podcasts are long. An album is around 40 minutes; a podcast backlog can run to hundreds of hours. The bitrate you pick is the difference between a full series that fits on your phone and one that does not, and between an episode that downloads on a small data bundle and one that has to wait for Wi-Fi.

Below: why speech compresses so well, when mono beats stereo, exact file sizes at each bitrate, and which format plays on any device you are likely to own.

What is the best format and bitrate for a podcast?

The safe default is 96 kbps mono MP3. It handles a single host, a two-person interview, and a voice with a quiet music bed underneath, all with room to spare. If the recording is clean — a decent mic, a quiet room, no music — 64 kbps mono sounds essentially the same and costs a third less data.

MP3 rather than anything newer because of one fact: it plays everywhere. Old Android phones, budget feature phones with MP3 support, car stereos, cheap MP3 players, every browser. A podcast is something you listen to for an hour at a time, often on whatever device is at hand. Compatibility beats the small quality gains of newer formats.

Quick reference:

  • Pure talk show: 64 kbps mono MP3
  • Talk with music under the voices: 96 kbps mono MP3
  • Music-driven show or audio drama with sound design: 128 kbps stereo MP3
  • Recording you are still editing: WAV, then export to MP3 once at the end

Why does speech need so much less data than music?

Music uses the whole hearing range at once: bass at the bottom, cymbals at the top, several instruments overlapping in the middle. An encoder has to describe all of it, all the time. A voice is different. Nearly everything that makes speech understandable sits in a narrow middle band — roughly 300 Hz to 4 kHz — with some consonant detail just above that. There is simply less sound to describe per second.

Speech is also full of gaps. The pauses between words and sentences encode to almost nothing, and an encoder that uses variable bitrate spends nearly zero data on them. And your brain is very good at understanding a voice through background noise — phone calls prove that every day — so the faint compression artifacts that would be glaring in a quiet music passage hide behind a voice without you noticing.

That is why 64 kbps speech can sound clean while 64 kbps music sounds like it is playing through a wall. The two jobs are not comparable, and settings that are correct for a music library are wasted on a podcast feed.

Should a podcast be mono or stereo?

Stereo only earns its keep when the left and right channels carry different information. A host talking into one microphone produces the same signal in both ears. Modern encoders use joint stereo to avoid storing identical channels twice, so a stereo talk file is not literally double the cost — but mono still wins, because at 64 kbps mono the entire bitrate serves one clean voice channel, while stereo at the same bitrate has to stretch across two.

There is also a listening-side reason. Plenty of people hear podcasts with one earbud in — commuting, working, cooking. With a mono file they hear everything. With a stereo file, anything panned hard to one side, like a second host placed on the right channel, gets quieter or disappears entirely into the earbud they are not wearing.

Choose stereo only when the show genuinely uses it: music performances, field recordings, audio drama with sound design that places effects around the listener. For everything else, mono is not a compromise. It is the correct setting. If you convert files yourself, pick mono in the encoder rather than letting it keep stereo by default — the voice gets the full bitrate to itself.

How much data and storage do episodes use at each bitrate?

File size is bitrate multiplied by time — nothing else. The formula: MB = kbps × minutes × 0.0075. So a 30-minute episode at 96 kbps is about 21.6 MB, and the same episode at 192 kbps is about 43.2 MB. The table shows what that looks like across a whole series.

The last column is where the choice really bites. A weekly one-hour show at 192 kbps costs about 86 MB per episode; at 64 kbps mono it costs about 29 MB. Across a year of episodes that difference adds up to roughly 3 GB — several episodes' worth of data saved, and on a 32 GB phone it can be the gap between keeping a full archive and constantly deleting old episodes to make room.

Bitrate30-minute episode1-hour episode100 episodes at 45 min each
64 kbps (mono)14.4 MB28.8 MBabout 2.2 GB
96 kbps (mono)21.6 MB43.2 MBabout 3.2 GB
128 kbps (stereo)28.8 MB57.6 MBabout 4.3 GB
192 kbps (stereo)43.2 MB86.4 MBabout 6.5 GB
320 kbps (stereo)72 MB144 MBabout 10.8 GB

Variable-bitrate (VBR) files land near these numbers but wander a little from episode to episode.

MP3, AAC or Opus: which format plays everywhere?

Bitrate is only half the decision. The format decides where the file will actually play, and that is where the newer options trade blows.

The pattern: each newer format buys you a little quality at low bitrates and costs you device support. Opus is excellent inside apps that already use it, but an Opus file sent to a friend may simply refuse to open. AAC is fine if the file will never leave your own phone. For anything you share, archive, or play on unknown hardware, MP3 remains the answer — which is why most podcasts still publish in it.

FormatPlays onSpeech at low bitratesBest use
MP3Practically every phone, car and playerGood at 64-96 kbpsDefault for sharing and archiving
AAC (M4A)iPhone and most Android phones; risky on old devicesSlightly better than MP3 at the same bitrateFiles that stay on your own phone
OpusModern browsers and apps; many players refuse itBest of the three below 64 kbpsIn-app streaming, not files you pass around
WAVEverything, but far larger filesPerfect (uncompressed)Recording and editing only

How do you shrink a podcast file that is too big?

You cannot change what a show publishes, but you can shrink files you control: your own recordings, and episodes you have saved for personal listening. The rules are simple.

  1. Start from the highest-quality copy you have. Every lossy-to-lossy conversion throws away a little more, so convert once, not repeatedly.
  2. Pick your target: 64 kbps mono for pure talk, 96 kbps mono if there is music under the voices. For audio you find through the Music FM search tool, choose the lowest quality that still sounds clean to you.
  3. If you only need part of an episode — one segment without the long intro or the ad break — open it in the MP3 cutter and save just that part. A trimmed file is smaller at any bitrate.
  4. Play the new file all the way through before you delete the original.

Do not re-encode a file that is already at 64 kbps or lower — there is nothing left to save and the sound only gets worse.

Does bitrate matter on Bluetooth or phone speakers?

Less than you think. Phone speakers and basic earbuds roll off the deep bass and the top end long before 128 kbps becomes the limiting factor, so the extra detail in a high-bitrate file never reaches your ears in the first place.

Bluetooth adds another step: the phone re-encodes the audio before sending it to your headphones, so a 320 kbps file loses its advantage in transit regardless. Over either of these paths, 64-96 kbps speech is effectively indistinguishable from higher bitrates. Save the high settings for music played on decent gear in a quiet room.

Frequently asked questions

Why can't I choose a bitrate in my podcast app?

Most podcasts publish exactly one audio file through their RSS feed, and the app downloads that file as-is. There is nothing to choose because the publisher already made the decision when they exported the episode. Bitrate options only exist when a show offers separate high- and low-quality feeds, or when you convert the file yourself after downloading.

Does a lower podcast bitrate save battery?

Barely, once the file is on your phone. Decoding MP3 costs the processor very little at any bitrate, so playback drain is almost identical. Where a small file does help is the download itself: the radio is the power-hungry part, and a 15 MB episode keeps it active far less time than a 90 MB one.

Why is my downloaded episode bigger than the bitrate math says it should be?

The extra weight is metadata inside the MP3. Embedded cover art is the usual culprit — one high-resolution image can add several megabytes to every episode of a show. Chapter markers, shownotes written into the tags, and file padding add a little more. A tag editor that strips the artwork usually recovers most of the difference.

Is it legal to download and keep podcast episodes?

In the normal case, yes. Creators publish podcasts through feeds precisely so listeners can download episodes and play them later, so saving those files for your own offline listening is the intended use. What you cannot do is re-upload episodes, sell them, or build them into your own app without the creator's permission. Paywalled or subscription shows carry their own terms, so check those.

What bitrate should I use when exporting my own podcast?

Record and edit in WAV so your cuts and level changes stay clean, then export once to MP3: 96 kbps mono for a talk show, 128 kbps stereo if music is central to the episode. Keep the WAV or project file as your master. If you ever need a different format later, you want to export from the master, not from an MP3.

Does the sample rate matter — 44.1 kHz or 48 kHz?

Either works. 44.1 kHz is the long-standing MP3 standard and plays on everything; 48 kHz comes from the video world and is fine on modern devices. At speech bitrates the encoder may downsample automatically to spend its bits better — let it. A higher sample rate does nothing audible for a voice recording.

Read next