What Is AAC Codec? Advanced Audio Coding Explained for Streaming and OTT

AAC, short for Advanced Audio Coding, is a lossy audio codec built to deliver good sound quality while using less data than older formats like MP3. That’s the one-sentence version, and it’s true, but it’s also not particularly useful if you’re the person actually building an OTT pipeline. AAC shows up everywhere in digital audio, video streaming, broadcasting, and OTT delivery, and the reason it shows up everywhere is that the AAC family isn’t one fixed thing. It’s a set of profiles, bitrates, and channel configurations built for different jobs.

Knowing that AAC compresses audio is the starting point, not the answer. The questions that actually matter for an OTT team are more specific: which AAC profile fits this workflow, what bitrate makes sense, how does AAC behave inside HLS, and how does the audio actually get from your encoder to a phone, a browser, or a TV app without breaking along the way.

This guide walks through those decisions in order.

AAC Codec at a Glance

AAC is a family, not a single setting you flip on. AAC-LC, HE-AAC, HE-AAC v2, and xHE-AAC each solve a different bandwidth or playback problem. Apple currently supports several of these AAC variants in HLS audio workflows, and Fraunhofer, the organization behind much of the AAC standard’s development, identifies the AAC family as widely used across broadcasting and streaming. Keep that framing in mind as you read the rest of this: “we use AAC” is the start of a sentence, not the end of one.

>>> Related articles:

• A Comprehensive Guide to M3U8 Files For Streaming Enthusiasts
• What Is EPG? – 101 Electronic Program Guide for Media Business Owners
• RTMP vs SRT for Live Streaming: When to Use Each in an OTT Workflow

What Is an Audio Codec?

An audio codec encodes and decodes digital audio. That’s it, that’s the definition. The reason it exists is more interesting.

Uncompressed audio is heavy. Sending it straight over the internet would need more bandwidth and storage than most streaming services are willing to spend, especially once you multiply one stream by millions of concurrent viewers. So a codec compresses the data before it ever gets sent:

Raw audio → Encoder → Compressed audio → Decoder → Playback

The encoder compresses the source audio. That compressed stream gets stored or transmitted. On the other end, a compatible decoder on the viewer’s device rebuilds the audio so it can actually play. AAC is one codec that does this job. A well-established one, but one option among several.

AAC codec vs. AAC file vs. M4A and MP4

People mix these terms up constantly, and it’s worth untangling them once so you stop having to think about it.

AAC is the codec. It describes how the audio is encoded: the math and the psychoacoustic decisions happening inside the encoder.

MP4 and M4A are containers, or file formats. Think of them as the box the audio travels in, not the audio itself. A container can carry AAC-encoded audio along with other media or metadata.

So an .aac file might contain AAC audio directly, while that same AAC audio could just as easily live inside an MP4-based container. Small distinction, but it matters in video streaming specifically, because a streaming service has to think about the audio codec and the packaging format separately. Get one right and the other wrong, and playback still breaks.

Is AAC lossy or lossless?

Standard AAC is lossy. It reduces file size in part by discarding information the human ear is unlikely to notice missing. It does not preserve every bit of the original uncompressed signal. That was never the design goal.

The goal is to use significantly less data while keeping the listening experience at an acceptable quality. Not identical to the source. Acceptable. That word choice matters more than it looks like it should, because it’s the whole logic behind every profile decision later in this guide.

What Is AAC (Advanced Audio Coding)?

Advanced Audio Coding is part of the MPEG audio codec family. It was developed to push audio coding efficiency past what MP3 could do, and it has since spread across consumer electronics, mobile devices, broadcasting, and streaming.

What actually makes AAC useful for video streaming, specifically, is its flexibility. A service can pick an AAC configuration based on:

• available bandwidth;
• expected audio quality;
• stereo or multichannel requirements;
• target devices;
• live or on-demand delivery;
• playback compatibility.

That flexibility cuts both ways, though. It’s also why “we use AAC” doesn’t actually describe your audio configuration. Which profile? What bitrate? Those are the real decisions.

How Does AAC Compression Work?

AAC uses perceptual audio coding. Instead of treating every part of an audio signal as equally important, the encoder studies the signal and spends its data budget where it will actually be noticed.

A simplified version of the workflow looks like this:

PCM audio → Frame analysis → Psychoacoustic analysis → Frequency transformation → Quantization → Coding → AAC bitstream → Decoder → Audio playback

Broken into steps:

1. The encoder receives the source audio. It starts with audio samples, typically represented as PCM before compression happens.

2. Audio gets divided into blocks or frames. Instead of processing an entire program in one pass, the encoder works through smaller sections of the signal at a time.

3. The encoder figures out what listeners are actually likely to perceive. Sounds can mask other sounds. Some frequencies contribute far less to perceived quality than others. This is the psychoacoustic step, and it’s where AAC decides which parts of the signal deserve coding precision and which don’t.

4. The signal is transformed and quantized. The encoder represents the audio more efficiently in the frequency domain, then reduces the precision of that information according to the available bitrate and whatever coding decisions were made upstream.

5. The compressed result becomes an AAC bitstream. Significantly smaller than the original PCM, and now ready to be stored, packaged, or transported.

6. A decoder reconstructs the audio during playback. The viewer’s device decodes the AAC stream and hands the resulting audio off to the playback system.

The real process has more moving parts than this, obviously. But even the simplified version explains why audio coding affects both bandwidth consumption and perceived quality at the same time. They’re not separate levers.

AAC Profiles Explained

Not every AAC stream behaves the same way. Different profiles exist because quality, bitrate, complexity, and latency pull against each other, and no single configuration satisfies all four at once. Treating AAC as one universal setting is the fastest way to make a bad encoding decision.

AAC-LC

AAC-LC, or AAC Low Complexity, is the general-purpose member of the family, and it’s the one you’ll run into most often. Fraunhofer describes it as supporting sampling rates from 8 to 96 kHz, along with mono, stereo, and multichannel configurations.

For OTT delivery, AAC-LC earns its place through a practical combination: solid audio quality, mature decoder support, straightforward playback, and stereo-plus-multichannel capability. Apple also lists AAC-LC among the supported stereo and multichannel codecs for HLS delivery, which tells you something about how established it is in the ecosystem you’re most likely deploying to.

HE-AAC

HE-AAC, High-Efficiency AAC, extends the format for more bandwidth-constrained situations. It’s built to hold onto useful audio quality at lower bitrates than a standard AAC-LC configuration would need.

Fraunhofer lists typical HE-AAC stereo use around 48 to 64 kbit/s and identifies it as widely used for broadcasting and streaming. So HE-AAC becomes relevant the moment reducing bitrate matters more to you than squeezing out maximum fidelity at a higher one.

HE-AAC v2

HE-AAC v2 pushes the high-efficiency approach further, aimed at very low-bitrate stereo delivery. Fraunhofer lists 24 to 32 kbit/s stereo as a typical range in its codec overview.

That range isn’t a suggestion that every OTT service should be encoding stereo audio down at 24–32 kbit/s. It’s a signal that HE-AAC v2 was designed for a different operating point than AAC-LC entirely. Target-device compatibility still needs to be part of the decision. A profile designed for low bitrates doesn’t help you if the devices you’re shipping to can’t decode it.

xHE-AAC

xHE-AAC is the newest generation in the AAC family, and it was built with adaptive audio and video streaming specifically in mind. Fraunhofer describes it as supporting a particularly wide operating range, with mandatory loudness and dynamic-range-control functionality baked in. It’s designed to move between lower and higher bitrates as network conditions shift.

That’s what makes xHE-AAC genuinely interesting for adaptive streaming. A viewer might start a session on strong Wi-Fi, move to a congested mobile network, then lose most of their bandwidth entirely, all in one sitting. xHE-AAC decoding is supported in modern Android, Fire OS, iOS, and Windows environments, according to Fraunhofer, and Apple’s HLS specification also lists xHE-AAC as a supported stereo codec.

AAC-LD and AAC-ELD

AAC-LD and AAC-ELD sit on the lower-delay side of the family. They’re not optimized for conventional on-demand playback. Instead, they’re built for applications where the delay between encoding and playback has to stay much smaller than usual.

Fraunhofer ties AAC-ELD and AAC-ELDv2 to real-time communication use cases, things like audio/video communication and VoIP. For a standard VOD service, these profiles are probably unnecessary complexity. For an interactive or communication-heavy application, latency stops being a nice-to-have and becomes most of the codec decision.

Read: What is Low Latency? Tips to Improve Low Latency Streaming with CMAF

Which AAC Profile Should You Use?

There’s no single AAC profile that’s correct for every streaming service. Anyone telling you otherwise is skipping a step.

A useful starting framework:

Treat this as a selection framework, not a universal prescription. Before you lock in a profile, work through these questions:

1. Which devices must play the stream?
2. What bitrate range does the service need?
3. Is the content mostly speech, music, movies, or mixed programming?
4. Is the service VOD, linear live, or interactive?
5. Is stereo enough?
6. Is multichannel audio required?
7. Which streaming protocol and container will carry the audio?

AAC Bitrates and Settings for Streaming

The question shows up constantly: what AAC bitrate should I use for streaming? There isn’t one universal number, because bitrate only makes sense alongside profile, channel count, content type, and playback environment. Still, there are useful reference points to anchor around.

Apple’s current HLS authoring specification recommends 32 to 160 kbit/s for stereo AAC and 320 kbit/s for 5.1 AAC in Apple HLS workflows. Apple also advises against using HE-AAC above 64 kbit/s. Fraunhofer’s numbers, for its part, are profile-specific: HE-AAC stereo around 48–64 kbit/s, HE-AAC v2 stereo around 24–32 kbit/s.

Line those numbers up and the point becomes obvious: “AAC bitrate” isn’t a standalone variable. It only means something in the context of the profile you’ve already chosen.

A practical selection approach

Test the output against your actual content. A bitrate that sounds fine on a news broadcast can fall apart on a concert, a movie soundtrack, or a sports event with a roaring crowd underneath the commentary. Don’t assume one test clip tells you everything.

AAC vs. Other Audio Codecs

Codec comparisons get simplified into “which one is best” way too often. That’s the wrong question. The right one is which codec fits the delivery requirement in front of you.

AAC vs. MP3

MP3 is still one of the most recognizable audio formats around, but AAC was built afterward as a more modern coding approach, and it shows in compression efficiency and how deeply AAC is integrated into current media ecosystems.

MP3 still earns its place when compatibility with older, audio-only systems is the overriding requirement. There are still plenty of those in the wild. For contemporary video delivery, though, AAC is generally the more relevant comparison because of its role in MP4, HLS, mobile, and OTT environments specifically.

AAC vs. Opus

Opus is particularly strong in interactive, real-time internet communication, and it’s also capable of efficient media streaming more broadly. AAC’s advantage is different: a deeply established ecosystem across consumer video, broadcast, mobile, and HLS environments.

So the decision comes down to where the content actually has to play. Browser-based real-time communication as the priority? Opus deserves serious consideration. Need broad, consistent integration with established video streaming ecosystems? AAC is usually the easier one to deploy without surprises.

AAC vs. AC-3 and E-AC-3

AC-3 and E-AC-3 are strongly tied to multichannel television and premium entertainment experiences. AAC also supports multichannel configurations, but which one you use often comes down to the target device and ecosystem rather than a spec-sheet comparison. Apple’s HLS specification, for instance, supports AAC, AC-3, and E-AC-3 across different audio configurations and recommends keeping suitable fallback audio in place.

Which means the real question isn’t “which codec has better sound.” It’s “which audio formats can my target devices reliably decode.”

Quick codec decision table

Where Is AAC Used?

AAC shows up in far more than standalone audio files. The codec family covers video streaming, OTT services, mobile playback, digital television, radio broadcasting, music delivery, live streaming, and adaptive streaming systems generally. Fraunhofer identifies AAC-family technologies across broadcast systems, mobile platforms, consumer devices, and streaming environments, which is a fairly rare level of reach for any single codec family. That reach is part of why AAC has stayed relevant even as newer codecs keep entering the conversation.

Why AAC Is Widely Used for OTT Streaming

OTT platforms juggle several requirements at once, and none of them get to lose. Audio has to sound good, but it can’t eat unlimited bandwidth. It also has to play reliably across a device landscape that’s genuinely fragmented: phones, browsers, smart TVs, streaming boxes, each with their own quirks.

AAC addresses that through three practical characteristics.

Efficient audio delivery. Compression cuts down how much audio data has to move through the pipeline. That leaves more of the bandwidth budget for video, or lets the whole stream run at a lower total bitrate without the audience noticing.

Multiple profiles for different network conditions. AAC-LC handles conventional delivery. HE-AAC and xHE-AAC give the system options at lower or more variable bitrates. xHE-AAC in particular was built around adaptive delivery across a wide bitrate range, which matters more every year as viewing shifts toward mobile networks.

Strong integration with established streaming ecosystems. AAC is directly supported in Apple’s HLS authoring guidance: AAC-LC, HE-AAC v1, HE-AAC v2, and xHE-AAC are all in there. That matters because an OTT service almost never delivers to just one device. It delivers to all of them, at once, and has to keep them all happy.

How AAC Fits Into an OTT Streaming Pipeline

AAC is one part of a much bigger delivery workflow, not the whole thing. A simplified version of that architecture:

Source / Ingest → Video and audio encoding → Video + AAC audio renditions → Packaging → HLS / MPEG-DASH → CDN → OTT application/player → Device decoder → Viewer

Ingest. The platform receives a live contribution feed or a source media file. The incoming audio might already be encoded, or it might still be uncompressed.

Encoding. The audio gets encoded into one or more delivery formats. This is where the real decisions happen: audio codec, AAC profile, bitrate, sample rate, channel count. What’s correct here depends entirely on the intended playback environment, not on a default template.

Packaging. The encoded audio and video get prepared for streaming. Depending on the delivery architecture, audio might travel bundled with video or get exposed as its own separate rendition.

Manifest creation. Adaptive streaming systems describe available media through manifests. Different audio renditions can represent different languages, dubbing, audio description, different codecs, or different channel layouts, all living side by side.

CDN delivery. The packaged media segments and manifests get distributed through a content delivery network.

Player selection. The OTT player reads the streaming information and requests a rendition it can actually handle. The device decodes the AAC audio and plays it.

This is why codec selection isn’t an isolated encoding decision you can make in a vacuum. It ripples through packaging, player compatibility, device support, and ultimately what the viewer experiences.

AAC with HLS

AAC and HLS have a particularly close relationship. Apple’s HLS authoring specification lists AAC-LC, HE-AAC v1, HE-AAC v2, and xHE-AAC among the stereo audio codecs supported in HLS workflows, and Apple advises HLS authors to provide stereo AAC-family audio, describing it as an important compatibility option across Apple devices.

Multiple audio tracks in HLS

A program doesn’t have to be limited to one audio track. An HLS workflow can organize different audio renditions into audio groups. A single program could offer English audio, Japanese audio, dubbed audio, accessibility audio, and stereo alongside supported multichannel alternatives, all as separate selectable tracks. The player then exposes the appropriate options to the viewer.

Apple recommends organizing audio groups around codec/channel combinations and making sure each group covers the required language options. That’s especially relevant for global OTT services, where audio isn’t just a technical soundtrack decision. It’s part of localization strategy.

What About AAC and MPEG-DASH?

AAC-family codecs show up in MPEG-DASH environments too. Fraunhofer identifies HE-AAC as a codec used with MPEG-DASH and describes xHE-AAC as designed for adaptive streaming across both DASH and HLS.

At a high level, the same OTT principle carries through: encode audio, create compatible renditions, package for adaptive delivery, describe them in the manifest, and let the player pick a supported track. The exact packaging and signaling rules differ between HLS and DASH, but the codec’s job stays roughly the same either way.

How to Encode AAC with FFmpeg

For testing or smaller workflows, FFmpeg gets you AAC output quickly. A simple example:

ffmpeg -i input.mp4 -c:v copy -c:a aac -b:a 128k output.mp4

Walking through it: -i input.mp4 identifies the source file. -c:v copy copies the original video stream without re-encoding it. -c:a aac selects AAC as the audio codec. -b:a 128k sets the target audio bitrate. output.mp4 is where the resulting streams land, wrapped in an MP4 container.

That command is intentionally simple, and it should stay that way for testing. A production OTT pipeline needs more decisions layered on top: channel layout, loudness, sample rate, language metadata, adaptive renditions, streaming packaging, device compatibility. Don’t copy one FFmpeg command into production and call it a day. Design the configuration around the full delivery workflow instead.

Common AAC Streaming Problems

AAC is broadly supported, but audio problems still show up whenever different parts of the pipeline stop agreeing with each other.

The video plays but there’s no audio. Possible causes: an unsupported audio profile, incorrect packaging, missing audio rendition information, or a player/device compatibility gap. Check both the encoded media and the streaming manifest. Don’t assume the player is automatically at fault.

Audio works on one device but not another. Codec support isn’t just about the word “AAC” appearing somewhere in the spec sheet. Different devices support different AAC profiles, channel layouts, containers, and operating-system versions. Test against your real target-device matrix, not an assumption about what “should” work.

The wrong language or dubbing track appears. In multi-audio streaming, the actual problem often lives in the relationship between audio tracks, language metadata, manifest configuration, and player UI. Treat alternate audio as one complete workflow, from media preparation all the way to playback, not a series of disconnected steps.

Audio and video drift out of sync. Sync problems can involve timestamps, encoding, segment boundaries, or packaging. Apple’s HLS guidance emphasizes continuous media timing and aligned segment boundaries specifically for interoperability reasons.

Audio consumes more bandwidth than expected. Review the codec profile, the bitrate, the channel count, and the number of audio renditions you’re actually shipping. A small inefficiency here doesn’t feel like much in isolation. It becomes significant fast once you multiply it across millions of streaming sessions.

Advantages and Limitations of AAC

AAC stays popular because it balances several competing requirements reasonably well, not because it’s perfect at any one of them.

Advantages of AAC

Good compression efficiency. AAC-family codecs deliver useful audio quality without demanding uncompressed-audio bandwidth.

Strong streaming ecosystem support. AAC is integrated into major broadcast and streaming technologies, HLS and MPEG-DASH environments included.

Multiple operating profiles. AAC-LC, HE-AAC, HE-AAC v2, xHE-AAC, and the low-delay variants let the family address different requirements instead of forcing every application into the same box.

Stereo and multichannel support. Depending on the profile and the playback ecosystem, AAC handles mono, stereo, and multichannel audio.

Limitations of AAC

Profile compatibility still matters. A device supporting one AAC configuration doesn’t mean every possible AAC configuration is fair game. This is the mistake that catches people most often.

Licensing has to be considered. AAC is an MPEG standard, and patent licensing may apply depending on the implementation and distribution model. Fraunhofer points to the Via Licensing Alliance AAC licensing program for details here.

Newer or alternative codecs may fit some requirements better. Opus, E-AC-3, and others can be preferable for particular real-time, multichannel, or ecosystem-specific workflows. AAC should get chosen because it fits the delivery requirement, not simply because it’s the codec everyone reaches for by default.

AAC in OTT and Streaming

For OTT platforms, audio quality is just as important as video quality. AAC coded audio plays a crucial role in ensuring a positive user experience. High compression efficiency enables users to stream content without experiencing long buffering times, even on moderate internet connections. At the same time, multi-channel support enables immersive sound in movies, series, and live events.

OTT platforms and FAST channels rely heavily on AAC because it allows them to deliver high-quality audio efficiently. Users enjoy clear sound without interruptions, and providers benefit from lower bandwidth costs and higher user satisfaction.

By integrating AAC coded audio, streaming platforms like OTTclouds can maintain professional sound standards while keeping delivery fast and reliable.

>>> Explore more: 

• How White-Label OTT Platforms Revolutionize Content Delivery in 2025?
• How to Create a Custom OTT Platform: Step-by-Step White-Label OTT Platform Guide
• White Label OTT Platforms – The Best Solution for Media Businesses

How OTTclouds Supports the Streaming Experience Around Audio

At OTTclouds, we know that delivering a top-notch streaming experience is about clear, smooth, and immersive audio. That’s why our platform fully supports AAC-coded audio, ensuring your audience hears every word, note, and sound effect exactly as intended.

Clear Sound with Less Data

Our use of AAC (Advanced Audio Coding) means your content sounds fantastic without consuming excessive bandwidth. This efficiency allows viewers to enjoy high-quality audio even when internet speeds are limited, keeping your streams smooth and uninterrupted.

Works Seamlessly on Any Device

Whether your audience watches on a phone, tablet, computer, or smart TV, OTTclouds ensures perfect audio playback. No matter the device, your content’s sound is clear, balanced, and reliable.

Perfect for Movies, Shows, and Live Streams

From VOD content to live events and FAST channels, OTTclouds maintains consistent audio quality across all types of programming. Every movie, show, or broadcast sounds just as great as it was intended.

Smart Streaming for Every Connection

OTTclouds automatically adjusts audio quality based on the user’s internet connection. Even viewers on slower networks experience smooth, uninterrupted sound, keeping them engaged and immersed in your content.

Immersive Stereo and Surround Sound

Support for stereo and surround sound provides a rich, cinematic experience that makes audiences feel like they are part of the action. Whether it’s a dialogue-heavy series or a high-energy live event, OTTclouds delivers sound that captivates.

Easy and Reliable

With OTTclouds handling the technical side of audio delivery, you can focus on creating amazing content without worrying about whether your audience will hear it properly. Our platform guarantees reliable, high-quality sound for every viewer.

OTTclouds helps you reach more viewers with high-quality, immersive audio, ensuring that every show, movie, or live event plays clearly and smoothly. Deliver the best streaming experience possible and let your audience enjoy your content the way it was meant to be heard.

When Should an OTT Platform Use AAC?

AAC is a strong candidate when a streaming service needs established support across modern streaming ecosystems, efficient stereo audio delivery, HLS compatibility, multiple bitrate options, support for mobile and TV playback environments, and access to higher-efficiency profiles once streaming bandwidth gets tighter.

But codec selection should always start with the target playback matrix, not with the codec. Ask where the content actually needs to play. Then figure out which codec, profile, bitrate, channel layout, packaging format, and fallback strategy support those devices. That order, devices first and codec second, is more reliable than picking a codec because it sounds better in isolation.

Conclusion

AAC remains an important audio codec family for video streaming because it combines compression efficiency, broad ecosystem support, and multiple profiles for different delivery conditions. For a basic OTT workflow, AAC-LC is still the right reference point to start from. HE-AAC pushes bitrate down further when you need it to. xHE-AAC extends the family toward wider adaptive streaming ranges. The right choice still depends on target devices, network conditions, content type, channel requirements, and streaming protocol. None of that gets answered by a single codec name.

For OTT teams, the real question was never “should we use AAC?” It’s this: which AAC configuration gives your audience reliable audio across the devices and streaming conditions you actually need to support?

OTTclouds provides the application and playback layer for VOD, live, linear, mobile, web, and TV viewing experiences, including features such as subtitles and dubbing across supported plans and devices.

Frequently Asked Questions