Convert AIFF to AIFC — Free Online Tool
Convert AIFF files to AIFC format in your browser, re-encoding the uncompressed PCM audio stream using the pcm_s16be big-endian codec — the native signed 16-bit format that AIFC inherits directly from its AIFF parent. AIFC extends AIFF with optional compression support (including A-law and μ-law), making it a flexible target for Apple ecosystem workflows that need compatibility with legacy and professional tools.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your AIFF 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
AIFF and AIFC share the same IFF-based chunk structure, so this conversion is essentially a container-level repackaging rather than a destructive transcode. Your AIFF file already contains uncompressed PCM audio (most commonly pcm_s16be — signed 16-bit big-endian samples), and FFmpeg writes that stream into an AIFC container using the same pcm_s16be codec. AIFC adds a COMM chunk field that identifies the compression type — in this case, 'NONE', indicating uncompressed PCM — which is what distinguishes a valid AIFC file from a plain AIFF at the binary level. Because no lossy encoding is applied in the default command, there is no generation loss; the audio samples remain identical.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg binary. In the browser tool this runs via FFmpeg.wasm (WebAssembly), so no local FFmpeg installation is required; copying this command to your terminal runs the same logic natively on your desktop. |
-i input.aiff
|
Specifies the input AIFF file. FFmpeg detects the AIFF container and identifies the embedded PCM audio stream (most commonly pcm_s16be) to be re-encoded into the AIFC output. |
-c:a pcm_s16be
|
Sets the audio encoder to signed 16-bit big-endian PCM, which is the baseline uncompressed codec shared by both AIFF and AIFC. This ensures no lossy compression is applied and the audio data remains identical to the source. |
-b:a 128k
|
Specifies a target audio bitrate of 128 kbps. For uncompressed PCM codecs like pcm_s16be this value is effectively overridden by the codec's fixed bitrate (determined by sample rate and bit depth), but it becomes meaningful if you switch to a compressed AIFC codec such as pcm_alaw or pcm_mulaw. |
output.aifc
|
Defines the output filename with the .aifc extension. FFmpeg uses this extension to select the AIFC muxer, which writes the FORM/AIFC container structure including the extended COMM chunk that distinguishes AIFC files from plain AIFF. |
Common Use Cases
- Delivering audio assets to legacy macOS or ProTools workflows that specifically require the AIFC container format rather than plain AIFF
- Preparing audio files for embedding in older QuickTime-based multimedia projects that expect the AIFC COMM chunk structure
- Converting a studio recording stored as AIFF into AIFC so it can later be re-encoded to a compressed AIFC codec (such as pcm_alaw or pcm_mulaw) for telephony archival
- Archiving Apple IIgs or early Macintosh sound samples that were originally distributed in AIFC format, starting from a modern AIFF source
- Satisfying audio ingest requirements from certain broadcast or post-production systems that validate the AIFC container signature before accepting a file
- Generating AIFC files locally for testing audio playback pipelines that branch behavior based on AIFC versus AIFF container detection
Frequently Asked Questions
No. The default command uses pcm_s16be, which is the same uncompressed, big-endian 16-bit PCM codec that standard AIFF files use. Since no compression or lossy encoding is applied, the audio sample data is transferred byte-for-byte into the AIFC container. The only change is the addition of the AIFC-specific COMM chunk that identifies the encoding type.
Both formats use Apple's AIFF IFF-based chunk layout, but AIFC extends the COMM (common) chunk to include a four-character compression type code and a human-readable compression name string. A plain AIFF file lacks this field entirely. When the compression type is 'NONE', an AIFC file is functionally equivalent to AIFF in terms of audio data, but some strict parsers and legacy Apple applications require the AIFC container signature to accept the file.
Yes. AIFC natively supports pcm_alaw (G.711 A-law) and pcm_mulaw (G.711 μ-law), both of which are 8-bit logarithmically compressed formats used widely in telephony. To use A-law compression, change the codec flag in the FFmpeg command to '-c:a pcm_alaw'. These codecs are lossy and reduce file size significantly, but they were designed for voice-range audio and will degrade the quality of music or wideband content.
To preserve more precision from a 24-bit or 32-bit AIFF source, replace '-c:a pcm_s16be' with '-c:a pcm_s24be' or '-c:a pcm_s32be' in the command. The '-b:a 128k' flag is more relevant for compressed codecs; for uncompressed PCM codecs the bitrate is determined by the sample rate and bit depth rather than a target bitrate setting. For example, pcm_s24be at 48 kHz stereo will always encode at approximately 2,304 kbps regardless of the '-b:a' value.
Standard ID3-style metadata embedded in AIFF (stored in an ID3 chunk) is generally carried over by FFmpeg into the AIFC output. However, AIFC's native metadata storage uses an ANNO (annotation) chunk, and some fields may not map cleanly depending on how the original AIFF was tagged. If precise metadata preservation is critical — for example, for music library management — verify the output tags with a tool like MediaInfo or exiftool after conversion.
Yes. In a Unix shell (macOS or Linux), you can loop over all AIFF files in a directory with: for f in *.aiff; do ffmpeg -i "$f" -c:a pcm_s16be -b:a 128k "${f%.aiff}.aifc"; done. On Windows Command Prompt, use: for %f in (*.aiff) do ffmpeg -i "%f" -c:a pcm_s16be -b:a 128k "%~nf.aifc". This is especially useful for converting large libraries that exceed the browser tool's 1 GB per-file limit.
Technical Notes
AIFC was introduced by Apple in 1988 as an extension to the original AIFF specification to accommodate compressed audio codecs on early Macintosh hardware. The format stores audio in big-endian byte order, which is why all native AIFC PCM codecs (pcm_s16be, pcm_s24be, pcm_s32be, pcm_f32be, pcm_f64be) use the 'be' (big-endian) suffix — this matches the Motorola 68000 and early PowerPC architectures that AIFC was designed for. When FFmpeg writes an AIFC file, it sets the FORM chunk type to 'AIFC' rather than 'AIFF' and populates the extended COMM chunk accordingly. One known limitation is that AIFC's compressed codec support in FFmpeg is limited to pcm_alaw and pcm_mulaw; proprietary Apple MACE 3:1 and MACE 6:1 compression, which appeared in early AIFC files, is not supported for encoding. File sizes from AIFF to AIFC conversions using the default pcm_s16be codec will be nearly identical — the AIFC container overhead adds only a few bytes for the extended COMM chunk.