Compress AAC

How to Compress AAC Audio Online

1. Upload Your AAC File: Drag and drop your .aac file or click "Choose Files." Batch compression is supported — drop a folder of episodes, lectures, or song stems and process them in one pass.
2. Pick a Compression Method: The "File Compression" dropdown defaults to File Size Percentage (drag the slider to a target like 50%; a 10 MB file becomes 5 MB). Switch to Specific file size to hit an exact MB target, Custom Bitrate to type any value in kbps, Constant Bitrate to pick a CBR preset (16, 32, 64, 128, 192, 256, 320 kbps), or Variable Bitrate to pick a VBR range (e.g. 96k–112k for near-transparent music, 20k–32k for spoken word).
3. Audio Channel and Sample Rate (Optional): "Audio Channel" keeps the original layout, downmixes to Mono (cuts size roughly in half), or forces Stereo. "Audio Sample Rate" leaves the source rate untouched or resamples to 8000, 12000, 16000, 24000, 44100, or 48000 Hz — drop to 24 kHz or below only for voice content.
4. Trim and Compress: Use the optional "Trim" controls to set a start time and duration in seconds or HH:MM:SS.sss, then click Compress. Files process in your browser session — no sign-up, no watermark, no email required.

Why Compress AAC Files?

AAC (Advanced Audio Coding) is already a modern lossy codec — defined in ISO/IEC 14496-3 (MPEG-4 Part 3) and standardized by MPEG in 1997. It is the default audio in YouTube, Apple Music downloads, the iTunes Store (iTunes Plus uses 256 kbps AAC), DVB and ISDB digital broadcast, and most MP4/M4A containers. Even so, an AAC file ripped at 256 or 320 kbps is much larger than it needs to be for podcasts, audiobooks, voice memos, or messaging — so re-encoding to a lower bitrate, narrower channel layout, or smaller sample rate is often the fastest way to fit upload, attachment, or storage limits.

• Email and chat attachments — Gmail and Outlook cap attachments at 25 MB; iMessage allows roughly 100 MB; Slack free workspaces cap individual file uploads at 1 GB but throttle storage. A 60-minute stereo AAC at 256 kbps is about 115 MB; recompressed to 64 kbps mono it drops to roughly 28 MB.
• Podcast and audiobook delivery — Apple Podcasts recommends 64 kbps mono or 128 kbps stereo AAC for spoken-word; Google Podcasts and Spotify accept the same range. Re-encoding voice content at 64 kbps is usually transparent to listeners and cuts size 4× compared to a 256 kbps master.
• Mobile data and offline storage — A 1 GB iPhone music cache holds about 8 hours at 256 kbps but ~17 hours at 128 kbps. Halving the bitrate on a long flight or commute playlist roughly doubles offline runtime.
• Replacing legacy MP3s — At 128 kbps, AAC-LC meets ITU "transparent quality" standards for stereo music — MP3 typically needs 160–192 kbps to sound similar. Re-encoding old MP3 rips to AAC at the same perceptual quality saves 20–30% storage.
• Broadcast and streaming uploads — DVB and ATSC 3.0 broadcast feeds, plus most live-streaming platforms (Twitch, YouTube Live, Restream), accept AAC at 96–192 kbps stereo. Anything higher is wasted bandwidth on the encoder.
• Voice memo and lecture archives — Voice-only content captured on iPhone Voice Memos defaults to AAC at 64 kbps. Older recordings or interview captures at 256 kbps can drop to 32–48 kbps mono with no intelligibility loss, shrinking a year of lectures from gigabytes to hundreds of megabytes.

AAC vs MP3 — Format Comparison

Sources: ISO/IEC 14496-3 standard; caniuse.com codec data; ITU-R BS.1116 transparent-quality testing referenced in the AAC Wikipedia entry.

AAC Bitrate Quick Guide

Frequently Asked Questions

What bitrate should I pick to keep AAC sounding transparent?

For stereo music, 128 kbps AAC-LC has been verified as "transparent" by ITU-R listening tests — most listeners cannot reliably distinguish it from the uncompressed source. For absolute safety on dense or critical material (orchestral, dense electronic, audiophile listening), use 192–256 kbps. For spoken word, 64 kbps mono is transparent; you can drop to 32–48 kbps mono before voice quality starts degrading noticeably.

Why is my AAC still huge after compressing?

The two biggest size drivers after bitrate are channels and sample rate. A stereo file recompressed to mono is roughly half the size at the same bitrate. A file resampled from 48 kHz to 24 kHz cuts size proportionally if you also lower the bitrate — there is no point keeping 48 kHz when you've capped bandwidth at 32 kbps mono. Trim silence and intro music too: even 30 seconds at the head of a long file adds up across a batch.

Will compression hurt audio quality?

AAC is lossy, so each encode discards some data. Re-encoding an existing AAC at a lower bitrate (transcoding) compounds losses, but for everyday voice or music delivery the difference between a 256 kbps source and a 128 kbps re-encode is rarely audible on consumer headphones or phone speakers. Stay above 96 kbps stereo for music, and above 32 kbps mono for voice, to avoid obvious artifacts like swirling cymbals or muffled consonants.

Should I convert AAC to MP3 instead of compressing?

Only if your target device or platform cannot play AAC. AAC at the same bitrate sounds better than MP3 — converting to MP3 loses quality and usually grows the file (MP3 needs 160–192 kbps to match AAC at 128 kbps). If you need MP3 specifically, use AAC to MP3; otherwise compress AAC directly to keep the format efficiency advantage.

Can I batch-compress many AAC files at once?

Yes. Upload multiple files together and the same compression method, channel, sample rate, and trim settings apply to all of them. Output is provided as individual downloads or a single ZIP archive. This is useful for an entire podcast season, a lecture series, or a years-long voice-memo backlog.

Why does my podcast app reject the compressed AAC?

Most podcast hosts (Buzzsprout, Libsyn, Apple Podcasts Connect) require AAC-LC inside an .m4a container with valid ID3 or iTunes metadata. A bare .aac ADTS stream may upload but skip metadata fields. If you need the M4A wrapper, run AAC to M4A after compression, then re-tag.

Does AAC compression preserve metadata and chapter markers?

ID3-style tags (title, artist, album, artwork) are usually preserved when the encoder writes a new container. Apple-style chapter markers (used in M4A audiobooks) are container-level features and may be dropped during a re-encode — back up the originals before batch processing if chapters matter.

Do all browsers and devices play AAC?

AAC playback works natively in Chrome, Edge, Safari, Opera, and Samsung Internet, plus iOS, Android, Windows, macOS, and Linux. Firefox plays AAC on Windows and macOS via OS codecs (partial support according to caniuse.com). Specialized players like older car stereos, e-ink readers, and budget MP3 players may not handle AAC — those need AAC to MP3 or AAC to WAV instead.

Is the compression done on my device or your server?

Files are uploaded over an encrypted connection, processed in your authenticated session, and removed automatically after the session ends. There is no permanent storage, no account requirement, and no watermark added to the output. If you need to chop a long file before compression, Trim AAC skips the re-encode step entirely.