MP3 Quality: 128 vs 192 vs 320 kbps

What each bitrate actually gives you

Those sizes are arithmetic, not estimates: bitrate times duration. A four-minute track at 192 kbps lands near 5.8 MB; the same track at 320 is close to 9.6 MB. Nearly double the storage for a difference most listeners cannot pick out in a blind test.

The rule everyone forgets: you cannot exceed the source

This is the part that makes most bitrate arguments pointless.

When you extract audio from a video, the sound has already been compressed once — by the platform, when the video was uploaded. YouTube typically serves audio in the region of 128 kbps for the standard track. That is the ceiling of what exists.

Converting that to a 320 kbps MP3 does not add anything back. The detail was discarded at upload and cannot be reconstructed. What you get is a bigger file containing the same audio, plus whatever tiny artefacts the second compression pass introduces.

It is like photocopying a photocopy on better paper. The paper is nicer. The copy is not.

So the honest question is never ‘what is the highest bitrate available’. It is ‘what did the source actually have’ — and for video audio, the answer is usually modest.

Where the differences really are audible

Bitrate matters most where the audio is complex and the listening is careful:

• Cymbals and hi-hats. Sharp transients are the first thing low bitrates smear. If something sounds like it is behind a curtain, this is why.
• Reverb tails. The long quiet decay after a note is expensive to encode and gets truncated first.
• Dense arrangements. Orchestral or heavily layered music needs more data to keep instruments separate.

Where it barely matters: speech, podcasts, lectures, most spoken-word content. A voice is narrow-band and predictable — 128 kbps handles it comfortably, and going higher mostly adds size.

And the factor that outweighs bitrate entirely: what you are listening on. Phone speakers and cheap earbuds cannot reproduce the differences under discussion. In a car, with road noise, neither can anything else.

Why we use 192 and not 320

Our audio downloads come out at 192 kbps. That is a deliberate setting, and the reasoning is the section above applied honestly.

The audio track we receive from a platform is already compressed. Re-encoding it at 320 would produce a file roughly 65 % larger with no additional information in it. We would be charging your storage and your data plan for a number on a label.

192 sits above the source in every case we have measured, so nothing is lost in the conversion, while the file stays reasonable — an hour-long podcast lands around 85 MB rather than 145.

If we ever handle sources that genuinely exceed this, raising it is one configuration change. Until then, offering 320 would be marketing rather than quality.

Formats beyond MP3, and when they matter

MP3 is not the only container for audio, and it is not the best one — it is the most compatible one. That distinction is worth understanding before you go hunting for a better setting.

Here is the practical consequence. Platforms often serve audio as Opus or AAC, because those are efficient. Converting that to MP3 is a step down in codec efficiency — you need a higher bitrate in MP3 to match what the original achieved with less.

So why convert at all? Compatibility. An M4A file that will not play in someone's car is worth less than an MP3 that plays everywhere, and most people asking for audio want it on a device they already own rather than a lecture about codecs.

If your player handles M4A, taking the audio in its original format avoids the conversion entirely and gives you the platform's file untouched. That is genuinely the highest-quality route available, and it is also faster, because nothing has to be re-encoded.

Choosing a bitrate for what you are actually doing

Rather than arguing about numbers in the abstract, match the setting to the job:

The last row is the one worth remembering. If a recording genuinely matters — your own upload, a talk you will never find again — the best thing you can do is not convert it at all. Take the audio in whatever format the platform serves and leave it alone. Every conversion is a one-way door.

For everything else, the difference between a good choice and a perfect one is smaller than the difference between listening on decent headphones and listening in a noisy car. Spend the attention where it changes what you hear.

Common bitrate myths worth dropping

• ‘320 is always better.’ Only if the source has 320 worth of information. Above the source, extra bitrate stores nothing.
• ‘Variable bitrate is worse than constant.’ The opposite, usually. VBR spends data where the music is complex and saves it where nothing is happening, which is a better use of the same average.
• ‘You can hear the difference on any headphones.’ Between 192 and 320, on typical equipment, most people cannot — and that includes people who are certain they can. Blind tests are humbling.
• ‘Converting twice is fine.’ Each compression pass discards detail permanently. Converting an MP3 to another MP3 always loses something, however high the second number is.

None of this means bitrate is unimportant. It means it is one factor among several, and it is the one most easily inflated for marketing because it is a single number that sounds like quality.

How to check what you actually got

You do not have to trust anyone's label. Every operating system will tell you:

• Windows. Right-click the file, Properties, Details tab — bitrate is listed.
• Mac. Select the file and press Command-I, or open it in Music and check Get Info.
• Android. Most file managers show it under file details.
• iPhone. Harder — the Files app does not display bitrate. Divide the file size by the duration for a close estimate.

That last trick works anywhere: a 5.8 MB file lasting four minutes is roughly 192 kbps. If a tool promised 320 and the arithmetic says 128, you have learned something useful about that tool.