Convert AIFC to M4A — Free Online Tool
Convert AIFC audio files to M4A by transcoding the source PCM or compressed audio stream into AAC, Apple's preferred lossy codec for iTunes and iOS. This is the go-to conversion for shrinking large professional or archival AIFC recordings into a streaming-friendly format without sacrificing meaningful perceptual quality.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your AIFC file here
or click to browse
Free — no uploads, no signups. Your files never leave your browser.
Settings
Note: Browser-based encoding uses approximate quality targets. For precise CRF compression, copy the FFmpeg command above and run it on your desktop.
Estimated output:
Conversion Complete!
DownloadHow It Works
AIFC files store audio using big-endian PCM variants (such as pcm_s16be, pcm_s24be, or pcm_s32be) or legacy compressed codecs like A-law and μ-law. None of these codecs are compatible with the M4A container, so this conversion is a full transcode: the raw or compressed audio is decoded to an intermediate PCM representation and then re-encoded using the AAC codec at 128 kbps by default. The resulting audio stream is wrapped in an MPEG-4 container with the .m4a extension, which supports iTunes metadata fields and gapless playback markers that AIFC does not expose in modern workflows. The -vn flag is included as a safeguard to suppress any non-audio data, ensuring a clean audio-only output.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg binary, the open-source multimedia processing engine that handles decoding the AIFC input (including its big-endian PCM or legacy compressed audio) and encoding the AAC output into an M4A container. |
-i input.aifc
|
Specifies the AIFC source file as the input. FFmpeg reads the AIFF-C container, identifies the audio codec (commonly pcm_s16be or pcm_s24be for professional recordings, or pcm_alaw/pcm_mulaw for telephony sources), and decodes it to raw PCM for the encoder. |
-c:a aac
|
Selects AAC (Advanced Audio Coding) as the output audio codec, which is the standard codec for M4A files and the format natively supported by iTunes, Apple Music, iOS, and most modern browsers. This triggers a full transcode from the AIFC source audio into lossy AAC. |
-b:a 128k
|
Sets the AAC encoder's target bitrate to 128 kilobits per second. This is the default balance point between file size and perceptual quality for M4A — suitable for general music listening. Increase to 192k or 256k for higher fidelity, or reduce to 96k for voice-only content where smaller file size is a priority. |
-vn
|
Disables any video stream in the output. This flag is a required safeguard for M4A output because the MPEG-4 container can technically hold video; -vn ensures the output is strictly audio-only, which is the definition of a valid .m4a file and prevents playback issues in iTunes or iOS. |
output.m4a
|
Defines the output filename and signals to FFmpeg that the file should be wrapped in an MPEG-4 audio container. The .m4a extension tells both FFmpeg and downstream applications — including iTunes and Apple devices — that this is an audio-only MPEG-4 file encoded with AAC. |
Common Use Cases
- Preparing archival studio recordings stored as 24-bit or 32-bit AIFC files for distribution on iTunes, Apple Music, or Podcasts, where M4A/AAC is the native preferred format.
- Shrinking large uncompressed AIFC masters captured by professional audio workstations (Pro Tools, Logic Pro) into smaller M4A files for sharing with clients or collaborators over email or cloud storage.
- Converting A-law or μ-law encoded AIFC files produced by telephony or broadcast equipment into the universally playable AAC/M4A format for web or mobile playback.
- Importing legacy Mac-native AIFC audio into modern iOS or Android apps that expect M4A containers rather than the older AIFF-family formats.
- Batch-converting a library of AIFC samples or sound effects into M4A so they can be embedded in HTML5 web audio projects that rely on AAC for broad browser compatibility.
- Producing podcast episode files from AIFC field recordings captured on professional recorders, outputting M4A with AAC to meet Apple Podcasts' recommended audio specifications.
Frequently Asked Questions
Yes, this conversion introduces lossy compression because the M4A file is encoded with AAC, whereas AIFC typically stores audio as lossless PCM (pcm_s16be, pcm_s24be, etc.). At the default 128 kbps bitrate the quality loss is imperceptible for most listeners, but the original PCM fidelity cannot be fully recovered from the M4A output. If you need a lossless M4A you can encode to FLAC inside the M4A container instead, though iTunes and iOS do not support FLAC in M4A the way they support AAC.
FFmpeg handles A-law (pcm_alaw) and μ-law (pcm_mulaw) AIFC files transparently — it decodes the compressed audio to PCM internally before passing it to the AAC encoder. You do not need to change the command. The output M4A will sound identical in character to the original A-law or μ-law audio, just re-encoded into AAC at the specified bitrate.
Change the value after -b:a to your desired bitrate. For example, use -b:a 256k for higher quality suitable for music distribution, or -b:a 96k to produce a smaller file for voice-only podcasts. AAC generally achieves transparent quality for most listeners at 192 kbps and above, while 96 kbps is typically acceptable for speech content. Avoid going below 64 kbps as AAC audio can become noticeably degraded at very low bitrates.
FFmpeg will attempt to map common metadata fields (such as artist, title, and album) from the AIFC file to the equivalent iTunes atom tags in the M4A container. However, AIFC uses an older AIFF-style chunk metadata structure that does not map perfectly to iTunes metadata atoms, so some fields may be lost or require manual verification after conversion. You can inspect the output with a tag editor like MusicBrainz Picard or Apple Music to confirm the metadata transferred correctly.
Yes. On macOS or Linux you can loop over all AIFC files in a directory with: for f in *.aifc; do ffmpeg -i "$f" -c:a aac -b:a 128k -vn "${f%.aifc}.m4a"; done. On Windows PowerShell use: Get-ChildItem *.aifc | ForEach-Object { ffmpeg -i $_.FullName -c:a aac -b:a 128k -vn ($_.BaseName + '.m4a') }. Each file is processed sequentially and the output M4A files are placed in the same directory.
M4A and MP4 share the same underlying MPEG-4 container format, but .m4a is the extension Apple introduced specifically for audio-only MPEG-4 files to help iTunes and iOS distinguish them from video files. Using .m4a ensures the file is recognized as an audio track by Apple devices, iTunes, and most modern media players without needing to inspect the container contents. The -vn flag in the FFmpeg command reinforces this by stripping any non-audio streams, guaranteeing the output is audio-only.
Technical Notes
AIFC operates natively in big-endian byte order, which is a legacy of the Motorola 68k architecture used in early Apple hardware. All of the PCM variants it supports (pcm_s16be, pcm_s24be, pcm_s32be, pcm_f32be, pcm_f64be) are big-endian, meaning FFmpeg must byte-swap the samples during decoding before handing them to the AAC encoder. This is handled automatically and has no impact on the output. The M4A container uses the MPEG-4 Part 14 structure and supports iTunSMPB and iTunNORM atoms for gapless playback metadata, which is particularly relevant if the AIFC source is part of an album or a continuous recording. AAC encoding in FFmpeg uses the native aac encoder by default; for higher quality at equivalent bitrates you may substitute -c:a libfdk_aac if you have a version of FFmpeg compiled with the Fraunhofer FDK AAC library, though this requires a separately licensed build. FLAC is technically supported inside the M4A container (-c:a flac) for a lossless output, but compatibility with Apple devices and iTunes is not guaranteed for FLAC-in-M4A. File sizes will decrease substantially compared to 24-bit or 32-bit AIFC sources: a 24-bit stereo AIFC at 96 kHz might be 50–100 MB per minute, whereas the 128 kbps AAC M4A equivalent is roughly 1 MB per minute.