Choosing the bitrate for your internet radio stream

For an internet radio station that plays music, 128 kbps MP3 in stereo is the bitrate to start from: every major browser plays MP3, and 128 kbps is the minimum Mozilla's codec guide recommends for stereo MP3. A talk-only station can go far lower, down to 32 kbps. HE-AAC holds up at lower rates still, if your listeners' players handle it. The best bitrate for internet radio is the lowest one that sounds right for your programme, plays on your audience's devices and fits your upload and your plan.

Steps
8
Reviewed
Runs on
Radio
Written by
Get Stream Hosting

By the Get Stream Hosting team

Every step was checked against the software's official documentation by independent reviewers before publishing. Last reviewed .

Pre-flight check

Settings to start from, by programme

Pick the row that matches what goes on air most of the day. The figures come from the codec makers' and browser documentation listed under sources; where a range is given, start at its top and step down only if listeners report buffering.

ProgrammeCodecBitrateChannelsWhy
Talk, sermons, newsMP332 kbpsMonoSuits talk radio; in mono one channel gets the whole budget
Music, widest reachMP3128 kbpsStereoMozilla's recommended minimum for stereo MP3; plays in every major browser
Music, lighter dataHE-AAC48 to 64 kbpsStereoFraunhofer's typical stereo range for HE-AAC
Music, lightest dataHE-AAC v224 to 32 kbpsStereo (parametric)Fraunhofer's range for good quality with parametric stereo
Music, plain AACAAC-LC96 kbps and upStereoMozilla's recommended minimum for stereo AAC
Music, OpusOpus96 kbps and upStereoMozilla's recommended minimum for stereo Opus
Highest MP3 qualityMP3320 kbpsStereoThe top bitrate MPEG-1 Layer III defines

A mixed station, music with long talk segments, should be set for the music. A music bitrate costs speech nothing but data; a speech bitrate takes detail out of the music.

MP3 or AAC: what decides it

Compatibility decides it before sound quality does. Mozilla's codec guide lists MP3 as supported by all major browsers, which is why it stays the safe default for a station heard mostly through a website player. AAC is more efficient: Fraunhofer IIS puts HE-AAC at 48 to 64 kbps for stereo and notes that most web radios are built on it.

  • MP3 plays in Chrome, Edge, Firefox, Opera and Safari. Choose it when you cannot test every player your listeners use.
  • AAC and HE-AAC need the browser or the operating system to decode them; Firefox, for example, relies on the platform's own AAC support. Test your listen link in each browser before you switch.
  • Ogg Vorbis and Opus are efficient, but Safari does not play Vorbis and Ogg files are not supported everywhere. Keep them for audiences on desktop players you know.
  • In BUTT, AAC needs the libfdk-aac library; some Linux packages ship without it, and the manual says to build from source in that case.

Mono, stereo and sample rate

Mono is the right call for a speech stream. Mozilla's guide notes that the number of channels changes only the sense of direction, not the quality, while each added channel can enlarge the encoded audio considerably. At 32 kbps, a mono stream spends every bit on the one voice your listeners hear; a stereo stream splits the same budget in two for no audible gain.

  • Music: keep stereo. At 96 kbps and above, AAC-LC or Opus will do (MP3 wants 128 kbps); at 48 to 64 kbps use HE-AAC, and below that HE-AAC v2 (24 to 32 kbps) keeps a stereo image by using parametric stereo.
  • Sample rate: Mozilla's recommended minimums for MP3, AAC and Opus are stated at 48 kHz. Use what your sound card and music library already run at, and keep it the same end to end.
  • Opus: BUTT always resamples Opus to 48 kHz. Set the audio device to 48 kHz so it does not have to.

What each listener downloads

A listener's data use is the bitrate times the time they listen. The sum is kbps × 3600 ÷ 8 ÷ 1000 for megabytes per hour, before a small allowance for network overhead. This is the number a commuter on a capped phone plan cares about.

BitratePer listener, one hourPer listener, 8-hour working day
32 kbps14.4 MB115 MB
48 kbps21.6 MB173 MB
64 kbps28.8 MB230 MB
96 kbps43.2 MB346 MB
128 kbps57.6 MB461 MB
192 kbps86.4 MB691 MB
320 kbps144 MB1,152 MB

Two features on the station side ease this. Every plan's player includes a data saver for listeners on phones, and on Platinum the station runs 3 streams, so phones can take a lighter bitrate while desktops get the full one.

Your upload carries one copy

Your encoder sends one stream to the server; the server sends a copy to each listener. So the studio line carries just the bitrate you pick, whatever the size of your audience. Mozilla's guide makes the point that a stream should stay below the bandwidth available, with room to spare for fluctuations and for other traffic on the same line.

  • Measure the studio's upload speed at the hour you broadcast, not at quiet times.
  • Leave generous headroom: a video call or a cloud backup on the same line can take it away mid-show.
  • If you record the show locally, BUTT can record at a higher bitrate than it streams, for example 192 kbps to disk and 96 kbps on air.
  • The serving side is ours: listeners at 128 kbps add up quickly (2,500 of them is 320 Mbps), and the station's server carries that, not your connection.

Matching the stream to your plan

Each radio plan has a highest bitrate, and your encoder should never exceed it. The plans are described in full on the SSL radio streaming page; the bitrate side of them is below.

PlanHighest bitrateListeners at onceFits
Free32 kbps1,000Talk, speech, a first test of your chain
Premium128 kbps2,500Music in MP3 for every device, AutoDJ, live DJs
PlatinumUp to 320 kbps5,000Full-quality music plus lighter streams for phones, nearest-server delivery from five cities

Every stream is served over HTTPS, so the player embeds on a secure website without mixed-content warnings. Premium and Platinum also come with a browser-based studio encoder offering automatic or fixed quality, which means a guest presenter never has to learn any of these settings.

Setting the bitrate in BUTT

  1. Open Settings and go to the Audio tab. Pick your audio device and its sample rate.
  2. Under the Streaming section, choose the codec: MP3 unless you have tested AAC on your listeners' players.
  3. Set the bitrate from the table above, no higher than the ceiling of your plan.
  4. Set the channel mode: mono for speech, stereo for music.
  5. Enter the server address, port and source password exactly as your control panel shows them.
  6. Press play to go live.

Confirm it worked: open your listen link in a player that shows stream details and check the reported bitrate matches what you set. Then check in your control panel that the source shows as connected and the listener count moves when you tune in.

When it sounds wrong

  • Listeners buffer or drop: check your upload at broadcast time, then step the bitrate down one rung.
  • Music sounds harsh or smeared: the codec is running at too low a bitrate. Raise it one rung, or test HE-AAC in the 48 to 64 kbps range.
  • The encoder will not stay connected: check the bitrate is within your plan's ceiling and the server details are exact. Running video as well? Live video streaming takes its own RTMP encoder and settings.
  • The player stays silent in Safari: check the format; Safari does not play Ogg Vorbis. Move to MP3.
  • Still stuck: open a ticket or a live chat; chat runs around the clock, with a person taking over when you ask.

Questions people ask

Is 128 kbps good enough for a music station?

Yes, for most stations. It is the minimum Mozilla's codec guide recommends for stereo MP3, and MP3 plays in every major browser. If your listeners' players handle AAC, Fraunhofer puts the typical stereo range for HE-AAC at 48 to 64 kbps, which saves data.

Does a lower bitrate let more people tune in?

Not on its own. Your plan sets the number of simultaneous listeners; the bitrate does not. A lower bitrate cuts the data each listener uses and lowers the chance of buffering on weak mobile connections.

How much mobile data does an hour of listening use?

About 14.4 MB at 32 kbps, 28.8 MB at 64 kbps and 57.6 MB at 128 kbps, plus a little network overhead. Multiply the bitrate by 3,600 seconds and divide by 8 to get the figure in kilobytes.

Should a church service or talk show stream in stereo?

Usually not. Speech gains nothing from stereo, and in mono the whole bitrate goes to one channel. Switch to stereo for services with a choir or a band, and raise the bitrate to a music setting when you do.

Can I send a higher bitrate than my plan allows?

Keep the encoder within the highest bitrate of your plan: 32 kbps on Free, 128 kbps on Premium and up to 320 kbps on Platinum. If your programme needs more, move the station to a higher plan rather than pushing past the ceiling.

Is 320 kbps worth it for internet radio?

It is the highest rate an MP3 stream can carry, and it costs each listener about 144 MB an hour. It suits a music-first station whose audience listens on good connections. Pair it with a lighter stream for phones, which Platinum's 3 streams allow.

Radio

Put your stream on air

Try your encoder settings on the free plan first, then move up when the music needs more bitrate.