Audio Formats for Internet Radio: MP3, AAC & HLS
Why audio formats for internet radio matter for your station
Picking the right audio formats for internet radio is one of the first technical decisions you face when launching or upgrading a station. Each audio codec impacts sound quality, bandwidth usage, and compatibility with devices. Get it right and your listeners hear clean, stable audio whether they tune in from a browser, a phone, or a car stereo. Get it wrong and you risk buffering, tinny playback, or shutting out part of your audience entirely.
Your goals are straightforward: clear sound across music and talk, minimal buffering for listeners on mobile data or shared wi fi, and broad compatibility with web radio players, smart speakers, and other devices. Standing out partly depends on how polished your stream sounds and how reliably it reaches the end user.
This article unpacks three core concepts: MP3 and AAC as audio codecs, and HLS as a delivery protocol for live streaming. By the end, you will know which codec and which delivery mode to choose for your station.
Codecs vs delivery: how your audio actually reaches listeners
A codec (short for coder-decoder) compresses raw audio data into a smaller stream that can be transmitted over the internet and decoded on the listener’s device. MP3 and AAC are codecs. A delivery protocol is the route that compressed stream takes from your studio to phones, browsers, and smart speakers. HLS is a delivery protocol.
Think of it this way: the codec is the language your audio is “spoken” in, while the delivery protocol is the postal service that carries the message. Changing the postal route does not change the language.
You always choose a codec first, then decide how to deliver it. For example, you can serve an MP3 stream through a standard HTTP URL, or you can wrap the same encoded MP3 into HLS segments. Similarly, AAC audio can travel via a classic streaming link or through HLS. The underlying audio format stays the same either way.
A common misconception treats HLS as a third “format” alongside MP3 and AAC. It is not. HLS transports already-encoded audio. Comparing HLS to MP3 is a category error: they operate on entirely different layers of the stack.
Overview of the main audio formats for internet radio
Before diving into comparisons, here is a quick orientation on the options you will encounter in online radio today.
MP3 (MPEG-1 Audio Layer III) was finalized in 1993 and became the default lossy format for digital music and early internet radio. It uses lossy compression to shrink audio files by discarding digital information the human ear is less likely to notice. MP3 is the most widely supported streaming format across devices, from vintage receivers to modern browsers.
AAC (Advanced Audio Coding) was designed as a more efficient successor to MP3, and it is now the industry standard for wireless and internet radio. AAC files are smaller than MP3s at similar quality levels, which matters for both file size and bandwidth. The AAC family includes HE-AAC (AAC+) and HE-AAC v2, variants optimized for low-bitrate streaming with higher coding accuracy at modest data rates.
The most common audio formats for internet radio are MP3, AAC, and Ogg Vorbis. Ogg Vorbis is an open-source codec that generally offers better sound than MP3 at the same bitrate, though its device support is narrower. Other codecs worth knowing about include FLAC, a lossless format ideal for high-fidelity audio but not practical for large audiences due to its heavy bandwidth demands; Opus, known for excellent audio quality at low bitrates; and older formats like wma and wav, which see limited use in streaming today.
HLS (HTTP Live Streaming) is Apple’s protocol that packages encoded audio, usually AAC, into small HTTP-delivered chunks for adaptive playback. It is a delivery method, not a codec, and it gets its own section below.
MP3 format: strengths, limits, and best use cases
MP3 rose to dominance in the 1990s because it made digital audio small enough to share and stream over slow internet connections. That head start gave it decades of adoption. Today, most stations still offer at least one MP3 stream because of its near-universal hardware and software support.
The technical basics are simple: MP3 uses lossy compression, discarding some audio data to reduce file size. The MP3 format can range from 96 to 320 kbps, with common streaming bitrates for radio sitting at 128 or 192 kbps. MP3 supports up to 5.1 audio channels, though stereo is standard for broadcast use. The encoder splits audio into frames, applies psychoacoustic modeling, and outputs a stream your listener’s device can decode with minimal processing power.
Core advantages for broadcasters:
- Works on virtually every browser, operating system, car stereo, internet radio device, and embedded player
- Low decoding cost on older hardware
- Encoding software is mature and generally free or inexpensive
Sound quality at 128 kbps is acceptable for many listeners across genres from news to music. Push to 192 kbps and you get a fuller stereo image and crisper highs. Below 90 kbps, audio quality significantly drops: expect rolled-off treble, audible artifacts, and a thin sound that hurts the listening experience, especially for music.
Limitations become clear when you need to conserve bandwidth. MP3 requires more bits than AAC to achieve comparable fidelity, meaning larger data usage per listener and more strain on mobile connections. If your audience skews toward smartphones and data-conscious markets, MP3 at low bitrates is not your best option.
MP3 remains a smart choice when you target legacy devices, embed a player on a website that must support the widest possible audience, or simply want a format every receiver on Earth can handle.
AAC and AAC+: modern codecs for internet radio
AAC was designed after MP3 to deliver better sound quality at the same bitrate. It achieves this through improved transform coding, better quantization, and more refined psychoacoustic models. AAC provides better sound quality than MP3 at the same bitrate, which is why streaming services and mobile platforms adopted it as the default.
AAC+ (HE-AAC v2) extends AAC with two key tools. Spectral Band Replication reconstructs high frequencies from a compact set of parameters, while Parametric Stereo recreates a stereo image from a mono core plus side information. Together, these let HE-AAC v2 deliver surprisingly clear stereo audio at bitrates as low as 32 kbps, making it ideal for talk, news, and even background music on constrained connections.
AAC supports up to 48 audio channels for reproduction, far beyond what radio typically uses, but it shows the format’s flexibility. On the practical side, aac files are smaller than equivalent MP3s, which means lower data costs for your listeners and reduced bandwidth load on your server.
Compatibility is strong on modern smartphones, tablets, browsers, and connected speakers. Users on current iOS and Android devices will have no trouble with AAC streams. Some very old players or aftermarket car units may only handle MP3, so testing with your specific audience matters.
AAC shines when your listeners are mobile-heavy, when data plans are tight, or when you run multiple radio streams and need to keep server bandwidth under control. Web-only stations that focus on specific genres without ads often pick AAC because it lets them stream music at moderate bitrates with better sound quality than MP3 would deliver at the same rate.
Like MP3, AAC is still lossy. It discards some audio data to compress the signal. Choosing the right format depends on factors such as desired sound quality and listener compatibility, not on any claim that one codec is “lossless.”
MP3 vs AAC: quality at the same bitrate
This comparison is practical guidance for choosing your station’s codec, not a lab test. The table below describes what you can generally expect at common streaming bitrates.
| Bitrate | MP3 | AAC+ (HE-AAC v2) |
|---|---|---|
| 32 kbps | Very compressed; acceptable for talk-only, poor for music; highs heavily rolled off | Surprisingly listenable for speech and background music; stereo preserved via Parametric Stereo; still limited for full music detail |
| 64 kbps | Usable for talk and low-demand music; artifacts noticeable in cymbals and vocals | Good compromise: clear speech and decent music quality across most genres |
| 128 kbps | Solid quality for most music formats; suitable for general broadcasting | Very clean for talk and music; often comparable to higher-bitrate MP3 for many listeners |
| 192 kbps | High-quality for music; diminishing returns compared to 128 kbps for casual listening | Very transparent for radio use; gains over 128 kbps are subtle for typical listeners |
As bitrate increases, the audible difference between MP3 and AAC shrinks. At 192 kbps, most listeners would struggle to tell them apart. The real decision point lives at low and mid-range bitrates, where AAC’s efficiency advantage is most pronounced.
If you must operate at 32–64 kbps, for example to serve an audience in a country with expensive mobile data, AAC+ (HE-AAC v2) is usually the better option. If you can comfortably stream at 128 kbps or higher and need maximum compatibility with older hardware, MP3 remains viable. Many broadcasters today find that AAC at 96–128 kbps hits the sweet spot of quality and reach.
Bitrate, bandwidth, and listener experience
Bitrate is measured in bits per second (bps) and describes how much audio data is sent every second to the listener. For context, an audio CD bitrate is always 1,411 kilobits per second, uncompressed. Streaming bitrates for internet radio typically range from 32 kbps to 320 kbps, with lossy compression formats preferred for streaming to maintain sound quality while reducing bandwidth usage.
The trade-off is direct: higher bitrate generally means better audio quality. Higher bitrates capture a wider dynamic range and more detailed high frequencies, which matters for music-focused stations. But a high bitrate stream also consumes more of the listener’s data and demands a more stable internet connection. Internet radio requires an internet connection for streaming, and that connection quality varies wildly.
Practical guidance:
- 32–64 kbps: Suitable for talk, news, podcasts, or true crime programs where speech intelligibility is the priority
- 96–128 kbps: A balanced range for mixed programming, from music to talk
- 192+ kbps: Best quality for music-heavy stations where listeners expect rich sound, such as a song-focused format
Listener environments significantly impact playback stability. Home broadband is usually fine at any reasonable bitrate. Shared wi fi in a café, mobile data during a commute, or multiple users on the same network can all degrade the signal. A listener watching a youtube video while someone else video-calls can choke your stream if it runs at a high bitrate.
Test your stream on real devices and connections. Listen on a phone over cellular data, on a laptop through office wi fi, and through a car system. That hands-on check will tell you whether your chosen bit rate holds up for your audience.
HLS for internet radio: what it is and why it matters
HLS (HTTP Live Streaming) is a streaming protocol developed by Apple and standardized in RFC 8216. It works by breaking your live stream into small media segments, typically a few seconds each, and serving them over standard HTTP. A playlist file tells the player which segments to fetch and in what order.
HLS is not an audio codec. It does not determine how your audio is encoded. It is a delivery layer that transports audio already encoded in AAC (or occasionally MP3) more reliably across variable network conditions.
The standout feature is adaptive streaming. With HLS, you can offer multiple bitrate renditions of your stream. A compatible player monitors the listener’s current bandwidth and switches between renditions on the fly. If the signal weakens, the player drops to a lower bitrate instead of buffering. When bandwidth improves, it steps back up. This makes live streaming far more resilient for mobile listeners and anyone on an unstable connection.
Benefits for radio stations include smoother playback on mobile networks, better behavior behind corporate firewalls (since HLS uses standard HTTP ports), and improved support for in-stream metadata like song titles. HLS is particularly valuable for commuters moving between cell towers, listeners roaming around the house, and international audiences with varied internet quality.
If you want a deeper look at how this protocol changes the game for broadcasters, learn more about why broadcasters switch to HLS.
How Zeno.FM handles codecs, URLs, and HLS delivery
Zeno is a broadcasting platform built for internet radio stations and podcasters who need flexible format and delivery options without wrestling with server configuration.
Inside the station dashboard at tools.zeno.fm, you can choose the station output media format between AAC and MP3, and set the output bitrate, in the Stream configuration tab under Settings. This means you control the codec and quality level with a few clicks, whether you are running a news broadcast, a music program, or a mixed-format station.
Zeno automatically provides multiple stream URLs per station: MP3, M3U, PLS, and HLS, found under Stations in tools.zeno.fm. You can hand the right link to different players, apps, and directories without any extra configuration work. Need an MP3 URL for an older hardware player? It is there. Want HLS for a modern app? That is there too.
HLS is rolled out across the Zeno platform, so every station can take advantage of adaptive delivery while still choosing their preferred codec. Embed these URLs into your station website, share them with partner apps, or use them for record keeping and distribution. To explore Zeno’s streaming features in detail, visit the platform overview.
Choosing the right setup for your station
All the theory above boils down to a few practical decisions. The table below maps common station types to suggested codecs and bitrates.
| Station type | Suggested codec | Suggested bitrate | Notes |
|---|---|---|---|
| Talk / news | AAC+ (HE-AAC v2) | 32–64 kbps | Prioritize speech intelligibility and low data use; ideal for mobile and low-bandwidth listeners |
| Music-focused | AAC | 96–192 kbps | Aim for fuller sound; choose the higher end for genres where audio fidelity matters most |
| Mixed programming | AAC or MP3 | 64–128 kbps | Balance quality and compatibility; AAC at 96 kbps often works well for both talk and music |
| Low-bandwidth markets | AAC+ (HE-AAC v2) | 32–48 kbps | Keep streams accessible where connectivity and data costs are major constraints |
Consider a few scenarios. A global community station serving diaspora listeners in multiple countries with varied connectivity would benefit from AAC+ at 48 kbps delivered via HLS. Listeners on expensive mobile data get a clear stream; those on broadband still hear solid audio. A local music station targeting hi-fi enthusiasts with stable broadband might choose AAC at 192 kbps, or even MP3 at 192 kbps if compatibility with older fm-tuner-style receivers matters.
For most stations, combining the chosen codec with HLS delivery is the recommended approach. HLS smooths out playback across varied networks and devices without changing the audio format itself. Internet radio can be accessed via apps or web browsers, and HLS handles both environments well. You don’t sacrifice codec quality by choosing HLS; you gain stability.
Format choices for mobile apps, car systems, and other devices
Listening now happens across phones, cars, smart speakers, laptops, and connected TVs. Your format decisions affect how easily your station plays on each of these devices.
Mobile listeners make up a large share of most stations’ audiences. AAC streams at moderate bitrates are typically friendly to data plans and battery life, and they play well inside modern iOS and Android apps. If you want branded apps for your station, you can build mobile apps for your station through Zeno to give listeners a dedicated experience on their phone.
Connected car systems like CarPlay and Android Auto generally handle both MP3 and AAC without issues. Older aftermarket head units or legacy car stereos may be MP3-only, so keeping an MP3 stream URL available as a fallback is a practical safety net.
Smart speakers and home devices are optimized for modern streaming protocols and tend to work well with AAC-based HLS streams. Quick startup and stable playback are priorities for these devices, and HLS delivers on both.
The practical advice: test your stream URLs on a sample of real devices your audience uses. Keep at least one highly compatible option, such as an MP3 URL, alongside your preferred AAC and HLS setup. That way every listener, whether on a brand-new phone or an older receiver, finds a way in.
Putting it all together: your next steps with audio formats for internet radio
The right setup for your station comes down to three decisions. Pick a codec: AAC for efficiency and better sound quality at lower bitrates, or MP3 for legacy compatibility. Choose a bitrate that matches your audience’s typical connections and your content type. And favor HLS delivery when your players support it, because it reduces buffering without changing your underlying audio format.
Remember that HLS is your delivery layer, not a replacement for MP3 or AAC. Using it simply gives your encoded audio a more resilient path to the listener. The best audio formats for internet radio depend on your content (talk vs music vs mixed), your audience’s devices, and the bandwidth conditions in the regions you serve.
Your next step: log into tools.zeno.fm, open the Stream configuration tab under Settings, and set or revisit your station’s output media format and bitrate based on what you have learned here. If you need more capacity or features as your station grows, review Zeno’s plans to find the right fit. Your listeners may never see these settings, but they will hear the difference.
July 21, 2026
