Initializing... drag & drop files here
Supports: M4A
An .m4a file is an MP4 container that usually holds an AAC audio stream, while a .aac file is that same audio stored as a raw ADTS stream with no container wrapped around it. Converting M4A to AAC unwraps the audio into a self-synchronizing bitstream that hardware decoders, embedded players, and streaming pipelines can read frame by frame — when the source is already AAC, this is a container change rather than a re-encode.
| Property | Value |
|---|---|
| Standard | MPEG-4 Part 14 (ISO/IEC 14496-14:2003), built on the ISO base media file format |
| Released | 2003 (derived from Apple's QuickTime container) |
| Type | Container, not a codec |
| Audio payload | Usually AAC-LC; can also hold ALAC, and less commonly ALS or others |
| Metadata | Rich — title, artist, album artwork, chapters, gapless info, purchase tags |
| Common source | iTunes / Apple Music downloads, Voice Memos, podcast files |
| Best for | Tagged libraries where artwork and track metadata matter |
| Property | Value |
|---|---|
| Standard | AAC codec: ISO/IEC 13818-7 (1997) and ISO/IEC 14496-3 (current 2019); .aac carries a raw ADTS stream |
| Type | Raw coded audio stream (no MP4 container) |
| Compression | Lossy; perceptual coding, more efficient than MP3 at the same bitrate |
| Sample rates | 8–96 kHz |
| Channels | Up to 48 full-bandwidth channels plus 16 LFE |
| Bit depth | Up to 24-bit internal precision |
| Metadata | None natively — ADTS frames carry audio only, so tags and artwork are dropped |
| Best for | Streaming, embedded/IoT players, broadcast feeds, AAC-only hardware |
Not quite — they describe different layers. AAC is the codec that compresses the audio; M4A is the MP4 container that wraps an AAC (or ALAC) stream along with metadata. A .aac file holds the coded audio on its own as a raw ADTS stream, with nothing wrapping it. So most M4A files already contain AAC audio; this conversion just removes the container around it.
If your M4A holds an AAC stream — which is the typical case for iTunes, Apple Music, and Voice Memos files — choosing AAC as the output lets the audio copy across without re-encoding, so there is no generational quality loss. Quality only drops if the source uses a different codec (ALAC) or if you deliberately lower the bitrate in Advanced Options.
A raw .aac (ADTS) stream has no field to store tags, so album artwork, title, artist, chapters, and purchase information are dropped during the conversion. If you need that metadata preserved, keep the file as M4A or convert it to a tag-friendly format like MP3. In our testing, a tagged 4-minute Apple Music M4A came out as a clean .aac stream that played everywhere but no longer showed its cover art or track title.
Yes, but it cannot be a straight copy. ADTS streams only carry AAC, so an ALAC payload has to be decoded and re-encoded to AAC first, which is a lossy step. Set a high Quality Preset or a bitrate of 256 kbps or higher to keep the result close to the lossless original. If you specifically want to stay lossless, ALAC belongs in an M4A or CAF container instead.
The output is AAC-LC (Low Complexity), the profile used by virtually all M4A music files and the most widely supported AAC variant across hardware and browsers. When the source already uses AAC-LC, the exact encoded frames are carried through unchanged inside the new ADTS stream.
Reach for a raw .aac file when a target expects a bare ADTS stream: some embedded and IoT audio players, certain broadcast and streaming ingest tools, and firmware that decodes AAC but does not parse MP4 containers. For everyday playback, syncing to phones, or keeping a tagged library, M4A is the more convenient wrapper — you can re-wrap a raw stream with the AAC to M4A converter, or switch to a tagged format with the M4A to MP3 converter.
Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — no sign-up, no watermark, and nothing is shared or made public. Because a same-codec M4A to AAC pass is a container change rather than a re-encode, the practical limit is upload time on your connection rather than processing.