Reference Formats
AIFF
AIFF is Apple's uncompressed PCM audio container, introduced in January 1988 and built on Electronic Arts' IFF chunk structure, functioning as the Mac-native counterpart to WAV.
Extension
.aiff
Full name
Audio Interchange File Format
Introduced
1988
Vendor
Apple
What is inside the container
Like WAV, AIFF wraps raw, typically uncompressed PCM samples in a chunked container — in AIFF's case, based on Electronic Arts' EA IFF 85 format rather than Microsoft/IBM's RIFF, which is why the two formats are structurally similar but not interchangeable byte-for-byte. AIFF supports NAME, AUTH, ANNO and COMT chunks for basic descriptive metadata, and a compressed variant, AIFF-C (AIFC), can hold various lossy or lossless codecs inside the same container shape, though in practice almost all AIFF files found in production are uncompressed PCM.
How to open it
For archives
AIFF is a legitimate lossless archival format, functionally equivalent to WAV in fidelity, and is still the native master format many Apple-based audio and video production pipelines (Logic Pro, Final Cut) output by default. A DAM serving mixed Windows/Apple production teams should treat AIFF the same way it treats WAV — as an archival master to be transcoded, not distributed directly — since Windows tooling generally handles AIFF less gracefully than native WAV.
Apple developed AIFF between 1987 and 1988, releasing the initial 1.1 specification in January 1988, building it on the EA IFF 85 chunk-based container that Electronic Arts had designed a few years earlier for the Amiga. That shared ancestry with WAV — both formats descend from the same general “interchange format” idea, just implemented independently on the Mac and Windows sides — explains why the two look structurally similar to a parser but aren’t directly compatible without conversion.
| AIFF | WAV | |
|---|---|---|
| Base container | EA IFF 85 (Electronic Arts) | RIFF (Microsoft/IBM) |
| Native platform | macOS / Apple | Windows |
| Introduced | 1988 | 1991 |
| Basic metadata chunks | NAME, AUTH, ANNO, COMT | LIST/INFO |
AIFF became the standard way Mac applications, and later professional Apple audio tools like Logic Pro and Sound Designer, stored uncompressed audio, occupying the same niche on Apple platforms that WAV occupies on Windows. A compressed sibling, AIFF-C (or AIFC), was defined for cases needing smaller files, but it never displaced uncompressed AIFF as the default in professional workflows the way MP3 displaced uncompressed audio for consumer distribution.
For a DAM ingesting assets from Apple-centric production teams — video post houses, podcast studios, music production — AIFF files show up regularly as source masters alongside or instead of WAV. The practical handling is identical to WAV: preserve the lossless original, and generate a compressed proxy for preview and delivery, since AIFF support in cross-platform web and mobile playback is inconsistent compared to the now-universal MP3 or AAC.
Frequently asked
Is AIFF the same quality as WAV for archival purposes?
Yes — both are uncompressed PCM containers and preserve identical audio fidelity. The choice between them for a DAM's archival tier usually comes down to which platform produced the file (Apple tools default to AIFF, Windows tools to WAV) rather than any quality difference.
Can a DAM convert AIFF to WAV without any quality loss?
Yes, converting between AIFF and WAV is lossless as long as both are uncompressed PCM — it's purely a container repackaging, not a re-encode, so there's no generational quality loss the way there would be converting between two lossy codecs.
Does AIFF support embedded metadata the way MP3 uses ID3?
AIFF has its own native chunks — NAME, AUTH, ANNO, COMT — for basic descriptive fields like title, author, and comments, though support for reading and writing these varies more across tools than the now-ubiquitous ID3v2 does for MP3.
Why do video and podcast production teams still deliver AIFF masters?
Because Apple's professional audio and video tools (Logic Pro, Final Cut, GarageBand) default to AIFF for exported audio, so studios working primarily on Mac hardware naturally produce AIFF files without deliberately choosing the format.
Does AIFF play natively in web browsers the way WAV does?
Support is inconsistent — Safari plays AIFF natively, but Chrome and Firefox have unreliable or absent native AIFF support. A DAM serving AIFF assets to a browser-based preview player should transcode to WAV, MP3, or AAC rather than relying on the browser to handle AIFF directly.
What is AIFF-C (AIFC) and does a DAM need to handle it differently?
AIFF-C is a compressed variant of AIFF that can hold lossy or lossless codecs inside the same chunk structure. It's uncommon in modern production, but a DAM's ingest pipeline should check the actual compression type field rather than assume every .aiff/.aifc file is uncompressed PCM.
Is AIFF an open format or does it require licensing to support in DAM software?
AIFF's specification has been publicly documented since Apple released it in 1988, and there are no patent licensing obligations for building AIFF encoders or decoders, making it straightforward for any DAM or media tool to support without royalty concerns.
How large is a typical AIFF file compared to FLAC for the same recording?
Roughly double the size, since AIFF is uncompressed and FLAC applies lossless compression that typically shrinks files by 40–60%. A DAM optimizing storage costs for a large Apple-originated audio library may choose to transcode incoming AIFF masters to FLAC without losing any fidelity.
Sources
- Apple released the initial AIFF specification (version 1.1) on January 21, 1988, based on Electronic Arts' EA IFF 85 chunk-based container format. checked 2026-08-07 — Wikipedia — Audio Interchange File Format