PicaJet
Search Build shortlist

Reference Formats

AAC

AAC is a lossy audio codec standardized in MPEG-2 in 1997 and extended in MPEG-4 in 1999, designed as MP3's technical successor with better compression efficiency at the same bitrate.

Extension

.aac

Full name

Advanced Audio Coding

Introduced

1997

Vendor

MPEG (Fraunhofer IIS, Dolby, Sony, Nokia, AT&T and others)

What is inside the container

AAC is a codec, not a file format on its own — it's typically delivered either as a raw ADTS bitstream with a .aac extension and almost no metadata support, or wrapped in an MP4/M4A container, which is the far more common case in DAM libraries and adds full support for iTunes-style atoms (title, artist, cover art, ratings). Because both AAC and Apple's lossless ALAC codec commonly share the .m4a extension, a DAM cannot reliably tell them apart from the extension alone and must inspect the container's codec atom.

How to open it

macOS / iOS Music.app and QuickTime Player play AAC natively, including .m4a
Windows Windows Media Player (with the MPEG-4 extension) or VLC Media Player
Browser HTML5 plays AAC/M4A in Chrome, Safari and Edge; Firefox depends on OS codec support
Cross-platform VLC Media Player and FFmpeg for playback and batch conversion

For archives

AAC is a delivery/streaming format, well suited to a DAM's preview and low-bandwidth-download tier, not to permanent archival — like MP3 it discards audio data irreversibly. It generally sounds better than MP3 at equivalent bitrates, so DAMs building new streaming or mobile-delivery pipelines often standardize on AAC over MP3 for that tier while still keeping MP3 available for maximum legacy compatibility. Keep the lossless original (WAV/FLAC) as the true master whenever one exists.

AAC was designed from the outset as a clean break from MP3’s legacy constraints rather than an incremental patch — the MPEG committee, with major contributions from Fraunhofer IIS, Dolby, Sony, AT&T and Nokia, standardized it in 1997 as part of MPEG-2 (ISO/IEC 13818-7), then extended it under MPEG-4 (ISO/IEC 14496-3) in 1999 with additional profiles for lower bitrates and broader device support. The result compresses more efficiently than MP3 at a given bitrate, which is why Apple made it the default codec for the iTunes Store and why it underpins most modern streaming and mobile-video audio tracks.

  • AAC-LC (Low Complexity) — the baseline profile used for iTunes downloads and most general-purpose encoding
  • HE-AAC (High-Efficiency AAC) — adds spectral band replication for strong quality at low bitrates; common in internet radio and mobile streaming
  • HE-AACv2 — layers parametric stereo on top of HE-AAC for even lower bitrates
  • xHE-AAC (Extended HE-AAC) — newer profile tuned for variable-bitrate broadcast and podcast delivery

Unlike MP3, AAC never became patent-free. Shipping an AAC encoder or decoder, in hardware or software, requires a license from Via Licensing Alliance (folded into Via LA after its 2022 merger with MPEG LA), which collects a per-unit royalty from device and software makers. End users encoding or listening to AAC files don’t pay anything directly — the obligation sits with whoever built the encoder/decoder — but it’s a meaningfully different licensing posture than the now-free MP3 or the always-royalty-free FLAC and Opus.

For a DAM, the practical wrinkle is that AAC rarely travels as a bare .aac file — it’s almost always packaged inside an MP4 container with a .m4a extension, the same extension Apple’s lossless ALAC codec uses. That means an asset-management system importing a library of .m4a files can’t assume audio quality from the extension alone; it has to inspect the container’s codec metadata to tell a compressed AAC voice memo from a lossless ALAC master.

Frequently asked

Is AAC royalty-free like FLAC or Opus?

No. AAC encoder and decoder patents are pooled and licensed through Via Licensing Alliance (now part of Via LA), and any company shipping AAC encoding/decoding software or hardware pays a per-unit royalty. End users don't pay to listen to or create AAC files, but it is not an open, royalty-free codec the way FLAC and Opus are.

Why do M4A files in a DAM sometimes contain AAC and sometimes contain ALAC?

Apple uses .m4a for both its lossy AAC codec and its lossless ALAC codec because both live in the same MP4-based container. A DAM's ingest pipeline needs to read the actual codec identifier inside the file rather than trust the .m4a extension to know which one it's dealing with.

Is AAC better quality than MP3 at the same bitrate?

Generally yes — AAC's more modern compression techniques extract better perceptual quality per kilobit than MP3, which is one reason Apple, YouTube, and most modern streaming platforms default to AAC rather than MP3 for their delivery tiers.

Can a DAM safely use AAC as a long-term archival format?

No — AAC is lossy compression and permanently discards audio detail, the same limitation as MP3. It belongs in the delivery/preview tier of a DAM's storage strategy, with a lossless WAV or FLAC master kept as the true archival copy whenever one exists.

Does AAC support embedded cover art and descriptive metadata?

Yes, when wrapped in an MP4/M4A container — the format uses the same atom-based metadata scheme as other MP4 files, supporting title, artist, album art, and custom fields, similar in richness to ID3v2 for MP3. A bare ADTS-stream .aac file, by contrast, carries essentially no metadata.

Do all browsers play AAC audio without a plugin?

Chrome, Safari and Edge play AAC/M4A natively via HTML5, but Firefox's support depends on the operating system's own codec libraries being present, so playback isn't guaranteed on every Firefox install the way MP3 playback is.

What HE-AAC and xHE-AAC profiles should a DAM know about?

HE-AAC (High-Efficiency AAC) and xHE-AAC are extensions tuned for very low bitrates — HE-AAC is common in internet radio and mobile streaming, xHE-AAC in newer broadcast and podcast delivery. A DAM handling incoming media from varied sources may encounter these as distinct AAC profiles requiring the same licensing consideration as standard AAC-LC.

How should a DAM batch-convert legacy WMA or WAV libraries to AAC for mobile delivery?

FFmpeg with its built-in AAC encoder (or the licensed Fraunhofer FDK-AAC encoder for higher quality) handles scripted batch conversion, and most DAM platforms integrate this into an automatic transcoding step triggered on ingest rather than requiring manual per-file conversion.

Sources