Convert AIFF Files Online for Free

AIFF Is a Chunked Audio Container, Not Just a Large Mac Sound File

AIFF, the Audio Interchange File Format, stores sampled audio in an IFF-style container. It is often encountered as .aif or .aiff and is frequently used for uncompressed PCM audio. That makes it suitable for interchange, editing, and a high-quality source copy, but the extension alone does not describe every detail a program needs. A reader must find and interpret the file’s chunks before it can decode samples correctly.

AIFF’s size is normally a direct consequence of audio parameters: duration multiplied by sample rate, channels, and stored bit depth, plus file overhead. There is no perceptual codec reducing ordinary PCM to a target bitrate. A 24-bit stereo source consequently needs more storage than a 16-bit mono source of the same duration. Converting it to a lossy MP3 or AAC creates a compact delivery copy but cannot preserve every original sample; converting to FLAC can reduce storage without changing decoded PCM.

Do not rename AIFF to another extension. A player expecting WAV, MP3, or M4A looks for a different container or codec structure. Proper conversion decodes the AIFF source, then writes the requested destination’s headers, audio representation, and metadata. Keep the original when the exact source waveform or its production metadata has value.

FORM AIFF, COMM, and SSND Are the Minimum Audio Evidence

An AIFF file begins with a FORM identifier and a form length, followed by the AIFF form type. It then consists of chunks, each with a four-character identifier, a big-endian 32-bit chunk size, and data. For audio with a nonzero length, the core evidence is the COMM common chunk and the SSND sound-data chunk. Unknown optional chunks can normally be skipped by their declared size, which is one reason the structure can carry application-specific information.

COMM declares channel count, number of sample frames, sample size, and sample rate. The rate uses an 80-bit extended floating-point representation, not a simple 32-bit integer. SSND begins with an offset and block-size field before the audio bytes. Most files put SSND near the end, but software should locate chunks rather than assume a fixed order. Validate that the COMM frame count is plausible for the usable SSND data after the offset; a mismatch can signal truncation or a damaged header.

A basic parser should also respect even-byte chunk alignment. An odd-sized chunk can have a pad byte before the next chunk. Ignoring it shifts every following identifier and may make a healthy file look corrupt. This is a useful diagnostic when an AIFF opens in one tool but a simple converter reports that COMM or SSND is missing.

Classic AIFF PCM Uses Big-Endian Sample Words

Classic uncompressed AIFF PCM is conventionally big-endian: in a multi-byte sample, the most significant byte comes first. This differs from the little-endian PCM commonly encountered in WAV. The distinction is not cosmetic. If a decoder reverses the wrong byte order, a quiet waveform can become loud noise and familiar speech can be unintelligible while duration and file size still look reasonable.

The sample-size field describes meaningful bits per sample frame, but storage containers are byte-oriented. Bit depth, channel count, and sample rate all affect the expected payload. Verify the decoded channel layout too: a stereo frame contains corresponding left and right samples, while an accidental mono interpretation can alter duration or drop information. Listen to the first and final seconds after import instead of trusting a display-only inspector.

AIFF-C/AIFC is related but not identical. It adds a format version and a compression declaration in COMM, allowing variants such as sowt little-endian PCM or floating-point forms. An .aif filename can be misleading in the wild. If a standard AIFF decoder fails, inspect the internal FORM type before forcing byte-order changes or assuming the recording itself is damaged.

MARK, INST, APPL, and Text Chunks Can Matter More Than Playback

The audio bytes are not necessarily the whole asset. A MARK chunk stores named sample-frame positions that other chunks can reference as cues. An INST instrument chunk can point to marker-based sustain or release loops. These details can be important to samplers and production sessions even though an everyday music player simply plays the waveform from start to finish.

AIFF also permits textual name, author, copyright, and annotation chunks, plus application-specific APPL data. A workflow may contain software-specific settings in APPL that another application ignores. Conversion to a generic delivery format often keeps a few descriptive tags but does not guarantee a one-to-one migration of loops, cue positions, or application data. Export those values separately if reconstruction matters.

For an archive, retain the original AIFF, calculate a checksum of the file, and record the decoder’s technical readout: duration, rate, channel count, bit depth, and any unusual chunks. For a delivery copy, verify only the tags and artwork that the receiving player actually displays. These are different goals and should not be confused.

Pick an AIFF Conversion Target by What Must Survive

Choose WAV when a recipient requests a broadly supported uncompressed PCM editing file. It can preserve decoded audio quality, but its RIFF/WAV chunk conventions and metadata behavior differ from AIFF. Choose FLAC for lossless storage where the target software supports it: decoded samples can be recovered exactly, but AIFF markers and application chunks still require their own migration plan.

Choose AAC/M4A or MP3 for compact listening and sharing. Both involve lossy encoding; select the codec, profile, bitrate, rate, and channels from the intended playback conditions. Start each lossy trial from the AIFF, not from a previously encoded MP3 or AAC. Repeated lossy transcoding accumulates artifacts that an original PCM source avoids.

Before a batch conversion, identify whether files are classic AIFF or AIFC and group sources by sample rate and channel layout. Validate one representative file from each group in the final player. This catches a hidden format variant, an unsupported rate, or a tag mapping problem before it affects an entire collection.

AIFF Compared With Common Destination Formats

AIFF File Questions Before You Convert or Preserve Audio

Is AIFF always lossless?
Classic AIFF normally stores PCM and therefore does not use a perceptual audio codec. However, the AIFF-C/AIFC family can declare other representations. Inspect the internal FORM type and COMM data instead of relying on the extension alone.

Why does an AIFF sound like static after import?
The usual cause is an incorrect byte-order or source-variant interpretation. Classic AIFF PCM is big-endian, while WAV-style PCM is commonly little-endian; AIFC can also declare byte-swapped or floating-point source data.

Can AIFF markers and loops survive conversion?
Not automatically. MARK and INST data has no universal equivalent in playback formats. Preserve the AIFF and export cue times or sampler settings separately when those instructions matter.

What is the best format to convert AIFF to for archiving?
Use FLAC when you need lossless recovery and target software supports it, while retaining the AIFF if its chunks matter. Keep WAV for uncompressed interchange. Choose AAC or MP3 only for compact delivery copies.

Why is an AIFF duration wrong in one program?
Check the COMM rate and frame count, SSND offset, and chunk alignment. A damaged chunk length or a parser that fails to skip an odd-size pad byte can mislocate later chunks and calculate duration incorrectly.