Audio

What Is Audio Bitrate: Why 320 kbps Beats 128

"128 kbps," "320 kbps," "VBR V0" — everyone has seen these labels on audio files, but what do they actually mean? Why does the same song sound rich in one version and flat and muddy in another? Let's take bitrate apart to the studs: no formulas, but plenty of specifics, so you always know which number to set.

Close-up of a mixing console with rows of blue and red volume knobs in warm light
Bitrate is the "data budget" for each second of sound. The bigger it is, the less has to be sacrificed. Photo: Pexels

Bitrate in plain English

Bitrate is how much data a file spends on one second of audio. It's measured in kilobits per second, kbps. That "128" or "320" on an MP3 is the bitrate. The logic is direct: the more data allotted per second, the more of the original detail survives, and the richer and cleaner the sound.

A handy analogy is a budget. Imagine the encoder is given a fixed sum of "money" for each second and must fit all the sound into it. At 320 kbps the budget is generous — it can carry quiet overtones, ringing cymbals, and depth. At 128 kbps there's two and a half times less to spend, so the encoder has to economize somewhere. The only question is where.

Don't confuse it with sample rate and bit depth

Bitrate is about compressed formats (MP3, AAC). For uncompressed audio, quality is set differently: by sample rate (44.1 kHz on a CD) and bit depth (16-bit). A WAV's bitrate is always a huge ~1411 kbps, because it throws nothing away at all.

What gets lost at 128 vs 320

The encoder doesn't cut corners at random — it first trims what the ear notices least. Even so, at low bitrate the losses become audible. Here's what suffers first:

  • High frequencies. At 128 kbps cymbals and the "air" of a recording sound swishy and smeared, as if through a thin sheet. At 320 they're crisp and distinct again.
  • Dense, busy passages. Where many instruments play at once, low bitrate turns everything to mush: details clump together and the soundstage narrows.
  • Quiet overtones and reverb. Echo tails, a singer's breath, the atmosphere of a room — these get cut first, and the recording loses its "space."

An important caveat: whether you hear this depends on your gear. On penny earbuds or in a noisy car, 128 kbps can sound fine. But on decent headphones the gap between 128 and 320 is usually obvious even to a newcomer — just A/B the two versions of a familiar track.

Close-up of mixing console faders labeled MUTE, CLIP, SOLO and a decibel scale
The encoder, like an engineer at the desk, decides where to spend a limited resource and where to pull it back. Photo: Pexels

CBR vs VBR: constant vs smart

Bitrate can be spread across a track in two ways, and that's a separate, important setting.

CBR (constant bitrate) spends exactly the same amount of data on every second. Pick 192 kbps and both dead silence and a thundering chorus get 192 kilobits each. Simple and predictable, but wasteful: silence eats as much as the most complex moment.

VBR (variable bitrate) is smarter: it analyzes the music and hands out data on demand. Complex, dense sections get more; pauses and simple notes get less. The result: at the same quality the file is 10-20% lighter than CBR. That's why VBR is almost always the better choice for new files. In the popular LAME encoder, the VBR V0 mode reaches full transparency at an average bitrate lower than 320 kbps CBR — it sounds the same but weighs less.

ModeHow it spends dataSizeWhen to use
CBREqually per secondLargerStreaming, broadcast, steady-flow needs
VBRBy moment complexitySmaller at the same qualityPersonal library, MP3 archive

Bitrate by format and task

The same numbers mean different quality in different formats: a more modern codec sounds cleaner at the same bitrate. A guide for MP3 and its relatives:

96 kbps
Speech, podcasts; too little for music
128 kbps
Bearable on basic gear, audible artifacts
192 kbps
Sensible minimum for music
256 kbps
Practical quality/size sweet spot
320 kbps
MP3 maximum, "with headroom"
VBR V0
~220-260 kbps, transparent and lighter than 320

"Transparency": where it stops mattering

Transparency is the key word in the audio world. It's the point where a compressed file is indistinguishable from the original by ear: no matter how you switch, you can't catch a difference. For most people on ordinary gear, transparency arrives around 192-256 kbps.

Hence a practical takeaway: chasing numbers past a certain point is pointless. A 320 kbps file won't become "better than" the original — you can't jump higher than the source. And if you want perfect quality with no "almost" at all, that's not about bitrate anymore, but about lossless formats like FLAC, where there's no loss by definition.

Bitrate isn't "more is always better" without limit. Past the point of transparency, extra kilobits just bloat the file and add nothing to the ear.

Three bitrate myths

1

"Re-encode 128 to 320 and it gets better"

No. Lost detail doesn't return, only the size grows. A high bitrate only helps when encoding from a lossless source.

2

"320 kbps is always audibly better than 256"

Almost never — both are usually already past transparency. You likely won't catch the difference even on good headphones.

3

"Bitrate is the only thing that matters"

No. Encoder quality, VBR/CBR mode and the format itself matter just as much. AAC at 128 beats MP3 at 128.

Working with files every day?

FormatZ converts images, documents and other files online — fast, free and right in your browser, with nothing to install.

Open the FormatZ converter

Now that bitrate is no longer a mystery, look at the bigger picture: how lossless differs from lossy and whether extra bits are worth paying for. Choosing the format itself? The MP3 vs WAV vs FLAC breakdown helps. About to move tracks around? Don't miss how to convert music without loss.

Bitrate is how much data is spent on one second of audio, measured in kilobits per second (kbps). The higher the bitrate, the more of the original detail is kept and the cleaner the sound. A 320 kbps file spends about two and a half times more data per second than a 128 kbps file.
On cheap earbuds or in a car, 128 kbps can sound fine. But on good headphones you notice a lack of crispness up top: cymbals sound swishy and fuzzy, and busy passages feel cramped and muddy. At 320 kbps those problems are mostly gone — most listeners can't tell it from the original.
For new files VBR is almost always better. It spends more bits on complex moments and fewer on silence, so at the same quality it's 10-20% smaller than constant CBR. LAME's VBR V0 mode reaches transparency at a smaller size than 320 kbps CBR.
The practical sweet spot for music is 256 kbps: it's the level where many people in blind tests stop being able to tell MP3 from the original, while the file is still meaningfully smaller than 320. If you want headroom, use 320 kbps CBR or VBR V0. For music, try not to drop below 192 kbps.
No. If a file is already compressed at 128 kbps, converting it to 320 kbps won't restore quality — the lost detail doesn't come back, only the size grows. A high bitrate only helps when you encode from a lossless source: WAV, FLAC or a CD.