Initializing... drag & drop files here
Supports: FLAC
FLAC keeps every bit of the original recording, which is exactly why one album can run into the hundreds of megabytes. AAC throws away the parts a perceptual model judges inaudible and gets you a library that fits on a phone. The decision is genuinely one-way: FLAC to AAC is a lossy step, and no later conversion recovers what it discards. So the short answer is to keep the FLAC files as your masters and treat the AAC as a listening copy — then the only remaining question is what bitrate to spend, which the rest of this page works through.
| Property | FLAC | AAC |
|---|---|---|
| Type | Lossless | Lossy (perceptual) |
| Standardised as | RFC 9639, published December 2024 on the IETF Standards Track | MPEG-2 Part 7 and MPEG-4 Part 3 |
| Reversible | Yes — decodes to the exact original PCM | No — discarded detail is gone permanently |
| Cost per minute of CD-quality stereo | Roughly half to two-thirds of PCM's ~10.6 MB, so around 5–7 MB depending on the material | 1.9 MB at 256 kbps; 0.96 MB at 128 kbps |
| Containers | Native FLAC, Ogg, MP4 | MP4, ADTS (a bare .aac file), 3GP |
| Browser support | MDN lists support in Chrome, Edge, Firefox, Opera and Safari | MDN calls it "patent-encumbered" and "somewhat less predictable" — Firefox relies on OS or external library support, Chrome supports it only in MP4 containers and only Main Profile, and it is absent from Chromium builds |
| Licensing | Open specification with open-source reference implementations | Patent-encumbered codec licensing for implementers |
| Best for | Archiving, mastering, editing, anything you will re-encode again later | Phones, cars, streaming, fitting a large library into limited storage |
.flac files onto the page, or click "+ Add Files" to browse. Multiple tracks queue and convert with the same settings..aac files individually or as a ZIP. No sign-up, no watermark.| Mode | What you set | Range offered | Use it when |
|---|---|---|---|
| Quality Preset | A rung on a seven-step scale, with nothing pre-selected for you | Highest down to Lowest | A hands-off encode — the least predictable mode here, so move off it whenever the rate matters |
| Constant Bitrate | One exact rate from a list | 8 kbps to 384 kbps | Music — this is the mode that reaches transparent rates |
| Custom Bitrate | Any rate you type, in bps, Kbps or Mbps | Unrestricted | The rate you want is not one of the listed steps |
| Variable Bitrate | A target range | 20k–32k, 32k–40k, 48k–56k, 64k–72k, 96k–112k | Speech, podcasts and audiobooks where small size wins |
| Specific file size | A size in bytes, KB or MB | Any | You have a hard limit to hit and will accept whatever quality fits |
Note the asymmetry: Variable Bitrate here tops out at the 96k–112k range, so it is a size-first mode rather than a quality-first one. If you want a genuinely near-transparent music encode, Constant Bitrate at 256 kbps is the setting to use.
Yes — that is the trade, and it is worth naming honestly. FLAC decodes to the exact original PCM samples, while AAC applies a perceptual model that removes detail it predicts you cannot hear. At 256 kbps that prediction is good enough that most listeners cannot reliably distinguish the result from the source in a controlled comparison, but the discarded information is gone for good. Our pipeline decodes and re-encodes rather than repackaging, so there is no lossless path through this page. Keep the FLAC files.
For music, use Constant Bitrate at 256 kbps; 320 kbps if you want headroom and do not care about the extra size. The Variable Bitrate dropdown deliberately offers only lower ranges — 20k–32k through 96k–112k — because those quality-targeted modes are aimed at speech and small-file use cases. It is not a ceiling on what AAC can do, just on what that particular mode exposes. If a VBR range looks tempting for music, take the equivalent constant rate instead; you will get a better result and a predictable file size.
.aac or .m4a?This page writes a bare .aac stream — AAC audio in an ADTS wrapper with no container around it. That is fine for many players and is the right answer when a system specifically wants raw AAC. For a music library it usually is not: .m4a puts the same AAC audio inside an MP4 container, which carries tags, artwork and chapter information and is what Apple software expects. Same codec, better packaging — use FLAC to M4A if the files are going into a library rather than into a pipeline.
.aac file play in a browser?Do not count on it. MDN describes AAC support as "somewhat less predictable" because the codec is patent-encumbered: Firefox only supports it when the operating system or an external library provides it, and Chrome supports AAC only in MP4 containers, and only AAC's Main Profile — a raw ADTS .aac file falls outside that. AAC is also absent from Chromium builds entirely. If the audio needs to play from a web page, either wrap it in MP4 via FLAC to M4A or use a format with broader documented support.
At the bitrates people actually use, generally yes — AAC was designed as MP3's successor and its coding tools let it hold more detail per bit, which shows most clearly below about 128 kbps. The gap narrows as bitrate rises; at 256 kbps and above both are close enough to transparent that codec choice matters less than the encoder settings. The real reason to prefer one over the other is usually compatibility, not fidelity: MP3 plays on essentially anything ever made, which is why FLAC to MP3 remains the safer pick for an old car stereo or a stubborn device.
Work it from the bitrate. CD-quality stereo PCM runs at 44,100 × 16 × 2 = 1,411 kbps, about 10.6 MB per minute. FLAC typically brings that down to roughly half or two-thirds depending on how busy the music is, so call it 5–7 MB per minute. AAC at 256 kbps is 256 × 60 ÷ 8 = 1,920 kB, about 1.9 MB per minute — so around three times smaller than the FLAC. At 128 kbps it is 0.96 MB per minute, closer to six times smaller. Multiply by track length for a realistic estimate before you commit.
Only in the trivial sense that you can wrap the AAC's decoded output in a FLAC file — and that is a bad idea. FLAC would losslessly preserve the already-damaged audio, giving you a large file with none of the original's detail restored. The information AAC removed is not recoverable by any tool. This is the whole reason to keep your FLAC originals: they are the master, and every lossy copy is derived from them rather than replacing them. If you need a smaller lossless file, compress the FLAC itself rather than converting it.
Your FLAC files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours. There is no sign-up, no watermark, and your files are never shared or made public. FLAC uploads are large by nature, so upload time is the slow part of any big batch — if you are only reshaping existing lossy audio rather than converting a lossless master, the Audio Compressor works on the format you already have and moves far less data.