T

audio

What audio bitrate should you use?

What audio bitrate should you use for podcasts, music, and the web? A simple guide to kbps, quality, and file size with practical presets.

Updated 2026-06-15

Audio files can be surprisingly large. A single uncompressed WAV recording can eat dozens of megabytes, while a compressed version of the same audio might weigh just a few. Bitrate is the number that controls that tradeoff — and knowing how to pick the right one saves you storage space, bandwidth, and loading time without noticeably hurting quality.

What bitrate actually means

Bitrate is the number of bits of audio data stored (or streamed) per second. It is measured in kilobits per second, or kbps. A file encoded at 128 kbps stores 128,000 bits of information for every second of audio.

Think of it like image resolution: a higher number means more detail is preserved, but the file gets bigger. A lower number strips out some detail in exchange for a smaller file. The codec (MP3, AAC, OGG, etc.) decides which details to throw away, but bitrate controls how aggressively that trimming happens.

How bitrate affects file size

For constant bitrate (CBR) encoding, the math is straightforward:

File size (MB) ≈ bitrate (kbps) × duration (seconds) ÷ 8000

A 5-minute track at 128 kbps comes out to roughly 5.8 MB. The same track at 64 kbps is about 2.9 MB. The duration and the bitrate are the two levers — nothing else.

One common misconception: switching from stereo to mono does not automatically shrink a file encoded at the same bitrate. The encoder just spends the same number of bits on one channel instead of two. The actual way to reduce file size is to lower the bitrate. The advantage of mono is that it lets you lower the bitrate further — for voice especially — while keeping the speech perfectly clear, because you are not wasting any bits trying to reproduce a spatial soundstage that was never there.

The law of diminishing returns

Most people cannot tell the difference between 192 kbps and 320 kbps in a blind listening test. The jump from 64 kbps to 128 kbps is obvious. From 128 to 192 is noticeable on music with complex high frequencies. Beyond 192, the improvements are subtle enough that they are mostly relevant in professional mastering contexts.

For most practical use — web playback, podcasts, social media, app audio — anything above 192 kbps is overkill. You are making the file bigger without a meaningful improvement in what listeners actually hear.

Use caseSuggested bitrateChannels
Voice memo / quick note48–64 kbpsMono
Podcast / spoken word64–96 kbpsMono
Web music (background, ambient)128 kbpsStereo
High-quality music streaming192–256 kbpsStereo
Archival / source file320 kbps or losslessStereo

These ranges work well with MP3 and AAC. If you are using a more efficient modern codec like OGG Vorbis or Opus, you can often go 20–30% lower and get equivalent perceived quality.

If you want a quick way to apply these settings without touching a command line, the compress audio for the web tool lets you pick a target bitrate and export directly in the browser — no upload required, nothing leaves your device.

Mono vs. stereo: what actually changes

Stereo carries two channels — left and right — which gives music a sense of space and width. Mono collapses those into one channel. For music, going mono can make the audio feel flat. For voice, it makes almost no difference to the listener, because speech does not have meaningful left-right content.

The practical rule: use mono for anything that is primarily talking (podcasts, voice-overs, interviews, audiobooks). Use stereo for music or anything where the spatial feel matters. Then set the bitrate accordingly using the table above.


FAQ

Does a higher bitrate always sound better?

Up to a point. Most listeners reach a point of “good enough” somewhere between 128 kbps and 192 kbps depending on the content. Above that, differences are inaudible in normal listening conditions and the extra file size is rarely worth it.

Can I improve quality by re-encoding at a higher bitrate?

No. Re-encoding a compressed file at a higher bitrate does not recover lost detail — it just creates a bigger file with the same quality as the original. Always keep a high-quality or lossless source file and encode down from there.

What bitrate does Spotify use?

Spotify streams at 24 kbps (very low data), 96 kbps, 160 kbps, or 320 kbps depending on your quality setting. Their highest tier (320 kbps AAC or OGG Vorbis) is roughly equivalent to a good MP3 at 256 kbps.

How do I compress audio without installing software?

The audio optimizer runs entirely in your browser, so there is nothing to install and no files are sent to a server. You choose your bitrate, format, and channel settings, and the processed file downloads straight to your device.

The bottom line

For most everyday uses, 128 kbps stereo is a safe default for music and 64–96 kbps mono covers voice content well. Going higher rarely improves what people hear; going lower saves meaningful storage and load time. Keep your originals, encode to the appropriate preset for your use case, and use a browser-based tool to do the conversion without the friction of installing software.