Convert AIFC to AAC — Free Online Tool

Convert AIFC audio files to AAC format, transcoding from Apple's extended AIFF container (which may contain lossless PCM or compressed audio streams) into the widely compatible AAC codec at 128kbps by default. This is ideal for making professional or archival Apple audio files playable on modern devices and streaming platforms without the overhead of uncompressed PCM data.

FFmpeg Command

Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg

Free — no uploads, no signups. Your files never leave your browser.

Estimated output:

Conversion Complete!

Download

How It Works

AIFC files store audio in Apple's extended AIFF container, which can hold either uncompressed PCM data (in big-endian formats like pcm_s16be, pcm_s24be, or pcm_s32be) or compressed audio. During this conversion, FFmpeg reads the AIFC container, decodes the internal audio stream — whatever its original codec — and re-encodes it using the AAC codec (via FFmpeg's built-in aac encoder) at 128kbps. This is a full transcode, not a remux: the audio is decoded to raw PCM internally, then lossy-compressed into AAC. The big-endian PCM data native to AIFC is handled automatically during decoding. The result is a standalone .aac file with no container wrapper overhead, ready for streaming, web playback, or use in Apple ecosystem apps.

What Each Flag Does

Flag What it does
ffmpeg Invokes the FFmpeg program, the open-source multimedia processing engine that powers this conversion both in the browser (via FFmpeg.wasm) and on the desktop command line.
-i input.aifc Specifies the input file — an AIFC audio file, which FFmpeg will demux and decode, automatically detecting the internal PCM or compressed audio codec stored in the big-endian AIFF-C container.
-c:a aac Tells FFmpeg to encode the audio stream using the built-in AAC encoder, transcoding from whatever codec was inside the AIFC (e.g., pcm_s16be or pcm_s24be) into lossy AAC compression suitable for streaming and device playback.
-b:a 128k Sets the AAC audio bitrate to 128 kilobits per second, a common default that balances file size and perceived audio quality for stereo content — increase to 192k or 256k for higher-fidelity output from lossless AIFC sources.
output.aac Defines the output filename with a .aac extension, producing a raw AAC bitstream file without an MP4 container wrapper; change this to output.m4a if you need iTunes or iOS-compatible container formatting.

Common Use Cases

  • Preparing professional studio recordings originally captured in AIFC/AIFF format for distribution on streaming platforms like Spotify or Apple Music, which require compressed formats
  • Reducing the file size of large lossless AIFC archives (e.g., 24-bit/96kHz recordings) to AAC for everyday listening without keeping multiple copies in different formats
  • Making legacy AIFC files from older Mac audio software or Pro Tools sessions compatible with modern mobile devices and media players that don't support AIFC
  • Converting AIFC audio assets from game development pipelines or post-production workflows into AAC for use in web-based or mobile applications
  • Creating AAC versions of AIFC field recordings or podcast raw files for web embedding, where AIFC is not supported by browser audio elements
  • Archiving a playback-friendly AAC copy of AIFC files received from Apple-ecosystem collaborators before editing, to use in non-Apple software that lacks AIFC support

Frequently Asked Questions

Yes — if your AIFC file contains uncompressed PCM audio (such as pcm_s16be or pcm_s24be), converting to AAC introduces lossy compression for the first time, which is an irreversible quality reduction. The default 128kbps AAC output is transparent enough for casual listening but will discard subtle high-frequency detail present in the original. If your AIFC already contains a compressed audio stream, you are decoding and re-encoding lossy audio, which compounds quality loss. Always keep your original AIFC as your archival master.
No — AAC is a perceptual lossy codec and does not preserve bit depth in the way lossless formats do. AIFC can natively store 24-bit (pcm_s24be) or even 32-bit float (pcm_f32be) audio, but AAC encodes audio based on psychoacoustic modeling and bitrate, not sample precision. The high dynamic range of a 24-bit AIFC source is effectively downsampled during AAC encoding, making this conversion most appropriate for consumer distribution rather than archival or professional post-production purposes.
Replace the value after -b:a in the command to set a different bitrate. For example, use -b:a 256k for higher quality suitable for music distribution, or -b:a 96k for smaller file sizes like voice podcasts. For AIFC sources containing high-resolution audio (24-bit or higher), a bitrate of 192k or 256k is recommended to better capture the dynamic range of the source before AAC's perceptual encoding takes over. The full adjusted command would look like: ffmpeg -i input.aifc -c:a aac -b:a 256k output.aac
AIFC files store metadata in AIFF-style chunks (such as NAME, AUTH, and ANNO markers), which are not directly compatible with the ID3 or iTunes-style atom metadata used by AAC files. FFmpeg will attempt to map common tags during conversion, but specialized or non-standard AIFC metadata chunks may be dropped. If accurate metadata preservation is critical, verify the output .aac file's tags after conversion and use a tool like mp4tags or Kid3 to re-apply any missing information.
A raw .aac file contains the AAC audio stream with no container wrapper, whereas .m4a wraps AAC audio inside an MPEG-4 container (MP4). The FFmpeg command here produces a raw AAC bitstream, which is broadly compatible but lacks features like chapter markers or rich metadata atoms. If you need .m4a output for better compatibility with iTunes, Apple Music, or iOS — or if you want to add album art — change the output filename to output.m4a in the command; FFmpeg will automatically mux the AAC stream into an MP4 container.
Yes — on macOS or Linux, you can batch process with a shell loop: for f in *.aifc; do ffmpeg -i "$f" -c:a aac -b:a 128k "${f%.aifc}.aac"; done. On Windows Command Prompt, use: for %f in (*.aifc) do ffmpeg -i "%f" -c:a aac -b:a 128k "%~nf.aac". This is particularly useful when you have an entire AIFC library — common in legacy Mac or Pro Tools projects — that you want to convert for use in a modern streaming or mobile context.

Technical Notes

AIFC (Audio Interchange File Format Compressed) is a big-endian format native to the Apple/Macintosh ecosystem, and FFmpeg handles its various internal codecs — including pcm_s16be, pcm_s24be, pcm_s32be, pcm_f32be, pcm_f64be, pcm_alaw, and pcm_mulaw — transparently during decoding. The AAC encoder used here is FFmpeg's native aac encoder, which produces good quality at 128kbps but is generally considered slightly inferior to the optional libfdk_aac encoder (which requires a separately compiled FFmpeg build). If audio fidelity is a priority — especially when converting 24-bit or 32-bit AIFC masters — consider using libfdk_aac by replacing -c:a aac with -c:a libfdk_aac in the command, if your FFmpeg installation supports it. Sample rate is preserved during conversion unless explicitly changed with -ar. AIFC's big-endian byte order is handled entirely at the decode stage and has no bearing on the AAC output. The .aac output container supports only a single audio track, so if your AIFC workflow involved multi-track or multi-channel configurations, be aware that channel mapping should be verified in the output.

Related Tools