MyMediaTools

Convert AIF to AIFC — Free Online Tool

Convert AIF audio files to AIFC format using the PCM 16-bit big-endian codec, preserving Apple's professional audio container structure while gaining access to AIFC's extended codec support. This tool runs entirely in your browser — no uploads required — and displays the exact FFmpeg command for processing larger files locally.

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

AIF and AIFC are closely related formats — AIFC is literally an extension of the AIFF specification, so this conversion is more of a container repackaging than a full re-encode. The audio stream from your AIF file, which uses PCM big-endian encoding (the native byte order for AIFF-family formats), is decoded and written into the AIFC container using the pcm_s16be codec (16-bit signed big-endian PCM). If your source AIF file was recorded at a higher bit depth (such as 24-bit or 32-bit), this conversion will reduce it to 16-bit, which is standard CD-quality audio. The AIFC container is then stamped with the 'NONE' or 'sowt' compression marker to indicate the codec in use, which is how AIFC distinguishes itself from plain AIFF even when carrying uncompressed PCM data. No video, subtitle, or chapter streams are involved — both formats are audio-only.

What Each Flag Does

Flag What it does
ffmpeg Invokes the FFmpeg tool, which handles reading the AIFF container, decoding the PCM audio stream, and writing the output AIFC file in your browser via WebAssembly.
-i input.aif Specifies the input AIF file. FFmpeg reads the AIFF container header to identify the audio codec (typically pcm_s16be, pcm_s24be, or another big-endian PCM variant) and stream parameters like sample rate and channel count.
-c:a pcm_s16be Sets the output audio codec to 16-bit signed big-endian PCM, which is the standard uncompressed codec for the AIFC container and matches the byte order Apple defined for the AIFF format family. If your source AIF uses 24-bit or 32-bit PCM, this will reduce the bit depth to 16-bit.
-b:a 128k Specifies a target audio bitrate of 128 kbps. For uncompressed PCM codecs like pcm_s16be, the actual bitrate is fixed by sample rate and bit depth rather than this parameter, so it has minimal practical effect here — it is included as a default for consistency with compressed codec workflows.
output.aifc Defines the output filename with the .aifc extension, which tells FFmpeg to write an AIFF-C container. FFmpeg uses this extension to select the aiff muxer in AIFC mode and correctly populates the COMM chunk's compression-type field in the file header.

Common Use Cases

  • Preparing AIF recordings for use in legacy Mac Pro Tools or Logic Pro sessions that specifically require AIFC container format for compatibility with older plugin chains
  • Archiving AIF field recordings into AIFC to take advantage of the format's extended codec metadata markers, which help audio asset management systems correctly identify compression type
  • Converting studio-recorded AIF files to AIFC before handing them off to post-production houses whose ingest systems only accept AIFC-tagged audio files
  • Standardizing a batch of mixed AIF and AIFC audio assets into a single AIFC format for consistent metadata handling in Final Cut Pro or Avid Media Composer timelines
  • Repackaging AIF audio samples from a sample library into AIFC containers to use with software that reads the compression-type chunk in the AIFC header for routing to specific audio engines
  • Reducing bit depth from a 24-bit or 32-bit AIF master to a 16-bit AIFC deliverable when the target platform or client specification requires 16-bit PCM

Frequently Asked Questions

If your source AIF file is already 16-bit PCM, the conversion is entirely lossless — the audio data is repackaged into the AIFC container without any modification to the samples themselves. However, if your AIF was recorded at 24-bit or 32-bit precision, this conversion will downsample it to 16-bit pcm_s16be, which does reduce dynamic range from roughly 144dB to 96dB. If preserving the original bit depth matters, you should change the codec flag in the FFmpeg command to pcm_s24be or pcm_s32be before converting.
AIFC (also written AIFF-C) is a formal extension of Apple's original AIFF specification, introduced to add support for compressed audio codecs like A-law and mu-law in addition to raw PCM. The container structure is nearly identical, but AIFC files include a mandatory 'COMM' chunk field that names the compression type (such as 'NONE' for uncompressed, 'alaw' for A-law, or 'ulaw' for mu-law). Plain AIF files are always uncompressed PCM, whereas AIFC files may contain either compressed or uncompressed audio. Most modern audio software reads both formats transparently.
AIFC inherits the same metadata chunk structure as AIFF, so basic markers and sample rate information are preserved during the conversion. However, neither AIF nor AIFC supports rich ID3-style tags (artist, album, track title) natively the way MP3 or AAC files do — any such metadata embedded in the original AIF via non-standard chunks may not survive the repackaging. The sample rate and channel count from the source file are always preserved by FFmpeg unless you explicitly override them with -ar or -ac flags.
Replace pcm_s16be in the command with pcm_s24be for 24-bit audio, pcm_s32be for 32-bit integer audio, pcm_f32be for 32-bit floating point, or pcm_f64be for 64-bit floating point — all of which are valid codecs in the AIFC container. For example: ffmpeg -i input.aif -c:a pcm_s24be output.aifc. You can also add A-law or mu-law compression by specifying -c:a pcm_alaw or -c:a pcm_mulaw, which are AIFC-specific codecs not available in plain AIF files.
Yes, the single-file command shown can be adapted for batch processing in a shell script. On Linux or macOS, use: for f in *.aif; do ffmpeg -i "$f" -c:a pcm_s16be "${f%.aif}.aifc"; done. On Windows PowerShell, use: Get-ChildItem *.aif | ForEach-Object { ffmpeg -i $_.FullName -c:a pcm_s16be ($_.BaseName + '.aifc') }. This is especially useful for files over 1GB, which exceed the browser tool's limit.
When the source AIF and the output AIFC both use uncompressed 16-bit PCM, the file sizes should be nearly identical. Any small size increase is due to AIFC requiring additional header chunks — specifically the mandatory compression-type field in the COMM chunk and, in some implementations, an annotation chunk — which add a negligible amount of overhead (typically a few hundred bytes). If the output file is significantly larger, check whether FFmpeg is resampling or up-converting the audio, which can be verified by inspecting the command output in the terminal.

Technical Notes

Both AIF and AIFC use big-endian byte ordering for their PCM samples, which is native to the PowerPC and 68k architectures Apple originally designed the format for. This means FFmpeg uses the pcm_s16be (signed 16-bit big-endian) codec rather than the little-endian pcm_s16le used in most Windows-centric formats. The AIFC specification (Apple AIFF-C version 1.2, 1991) introduced the required 'compressionType' OSType field in the COMM chunk — FFmpeg correctly populates this as 'NONE' for uncompressed PCM when writing AIFC output. One known limitation is that AIFC's compressed codecs (pcm_alaw, pcm_mulaw) are lossy and are primarily legacy telephone-quality formats (8-bit, 8kHz); they should not be used for music or high-fidelity audio. The -b:a 128k flag in the command is inherited from FFmpeg's generic audio pipeline but has limited effect on PCM codecs, which are inherently uncompressed and whose bitrate is determined entirely by sample rate, bit depth, and channel count. Neither format supports subtitles, video, chapters, or multiple audio tracks.

Related Tools

Convert AIF to AAC Convert AIF to CAF Convert AIF to ALAC Convert WAV to AIFC Convert DVR to AIFC Convert J2B to AIFC Compress AIF Trim Video or Audio AIF