AIFF to AAC
Convert AIFF to AAC in your browser. Nothing's uploaded.
Runs in this tab. The file stays here.
This runs in your browser. Nothing is uploaded. Longer clips take longer here than they would on a fast server. That's the trade-off for not sending the file.
Format hubs: AIFF · AAC · Convert
About AIFF to AAC
Converts AIFF to AAC in your browser. Audio IFF, common in Apple and pro-audio workflows. Output is AAC. Nothing is uploaded.
AIFF is audio IFF, common in Apple and pro-audio workflows. AAC is raw or ADTS AAC audio. This page is only that pair. It isn't a generic dump box that guesses the destination after an upload. If you have a different container, use that format's hub instead of forcing the file through the wrong decoder.
The recording is read into memory and converted with FFmpeg compiled to WebAssembly, loaded from this origin once (~30 MB) and then cached. You can open the network tab first: you should see this origin load, and on the first video or audio visit a local ffmpeg-core.wasm, not a POST of the file. After the page (and encoder, if this is media) has loaded, wifi can go off. That's the whole product, not a badge.
AAC is a lossless or uncompressed target. It won't restore detail a lossy AIFF file already threw away. It stores the current samples or pixels more honestly, usually in a larger file. That's useful when the next tool in a chain insists on AAC, not when you're trying to “improve” a compressed original.
Related conversions sit on this same origin. AIFF to another destination, or another source into AAC, are separate pages so the titles stay specific. The AIFF hub and the AAC hub list every pair I actually ship. Missing pairs are missing because the encoder or decoder isn't here, not because they are paid.
Start from the AIFF hub if you're leaving this format, or the AAC hub if you need to arrive in it. Those pages are indexes, not upload forms. A generic dropdown still exists under Video convert and Audio convert when you would rather pick the destination after you drop the file. Stills use jSquash or canvas; clips and recordings share the same FFmpeg core as the rest of the media tools. You can disconnect after that core has loaded.
How to use AIFF to AAC
- 1Drop a AIFF file. The in-browser encoder loads from this site the first time you open a video or audio tool.
- 2Click Convert. Encoding a long recording can take a while on a phone; that wait is local CPU, not an upload bar.
- 3Download the AAC result. It was never on my disk.
What it won't do
- Input is AIFF (audio/aiff,audio/x-aiff,.aiff,.aif). A different container belongs on its own pair.
- The encoder is GPL FFmpeg in WebAssembly, single-thread, from this origin. Exotic codecs inside a familiar extension can still fail.
Common questions
Does converting AIFF to AAC upload the file?
No. This is a static page. The recording stays in the tab. The network panel should show this origin, not a POST of your AIFF file.
Will AIFF to AAC look or sound the same?
Pixels or samples that are already in the AIFF file are kept. Anything AIFF already discarded is gone. AAC won't invent it back.
Why is there a separate AIFF to AAC page instead of one converter?
Searchers type this pair. A generic convert tool with a dropdown is easy to build and easy to bury. Each pair is its own URL, its own title, and a file picker that expects AIFF. The generic pickers still live at video convert and audio convert if you want a dropdown.
Can I convert AAC back to AIFF on this site?
Yes: that's /convert/aac-to-aiff. Going back and forth through a lossy codec twice is how you make mud. Do it once if you must.
Related tools
Why this one doesn't upload your file
There is no server to upload to. This page is a static file, and the work happens in your browser using the same graphics and WebAssembly code that renders every other site you visit. Your file is read from disk into memory, processed, and handed back as a download. Once the page has loaded you can disconnect from the network entirely and it keeps working. The longer explanation