AIFF Format: Complete Technical Reference

Apple created AIFF in 1988, designed specifically for the Macintosh. The name stands for Audio Interchange File Format. The underlying file structure is based on Electronic Arts' IFF (Interchange File Format) specification — a chunk-based binary format. This makes AIFF technically distinct from WAV, which Microsoft and IBM built on their own RIFF (Resource Interchange File Format) structure despite both RIFF and IFF being chunk-based designs with similar principles. AIFF was the native audio format on classic Macintosh systems through the late 1980s and 1990s. When Apple built GarageBand (2004) and when Logic Pro matured on Mac OS X, AIFF remained the natural choice for Mac-native audio production. Apple introduced AIFF-C (AIFF Compressed) in 1989 — a variant that allowed compressed audio codecs inside the AIFF container — but it never achieved significant adoption; the uncompressed original remained the standard. Sound Designer, the precursor to today's audio editors, used AIFF as its file format. The Professional Audio industry on Mac worked almost exclusively with AIFF through the 1990s. Today AIFF sits alongside WAV in professional Mac workflows — some studios prefer it, some use WAV. In practice the choice is often arbitrary since they are technically equivalent in audio quality.

AIFF stores uncompressed PCM (Pulse Code Modulation) audio — the same raw sample data used in WAV and on audio CDs. Bit depths supported: 8-bit (rare), 16-bit (CD standard), 20-bit (uncommon), 24-bit (professional standard), and 32-bit integer. Sample rates: AIFF supports rates from 8 kHz up to 192 kHz and higher — the format uses an 80-bit extended precision floating-point field for the sample rate, theoretically allowing any rate. Mono and stereo are most common; AIFF supports multichannel audio up to 8 channels in practice, though the spec allows more. A 4-minute stereo recording at 16-bit/44.1 kHz (CD quality) is approximately 42 MB — identical to WAV at the same settings. At 24-bit/48 kHz (professional standard), a 4-minute file is about 83 MB. At 24-bit/96 kHz (high-resolution), it is approximately 166 MB. AIFF uses big-endian byte order (most significant byte first) — this is the historical Motorola 68000 byte order used in classic Macs. WAV uses little-endian (Intel/PC byte order). Modern software handles both transparently, but this technical difference occasionally surfaces in embedded systems or older hardware. AIFF files use the four-character code 'AIFF' in the file type field and use the .aiff or .aif extension.

AIFF and WAV are functionally equivalent in audio quality — both store uncompressed PCM audio with zero data loss. The differences are structural and ecosystem-based. Container structure: AIFF uses IFF-based chunks; WAV uses RIFF-based chunks. Both are chunk-based formats with similar capabilities but different implementations. Byte order: AIFF is big-endian (Motorola/Mac heritage); WAV is little-endian (Intel/PC heritage). Modern software handles both, but very old or embedded systems might struggle with one or the other. File size limit: standard WAV has a 4 GB limit due to a 32-bit RIFF chunk size field; AIFF shares a similar theoretical limit but in practice most software handles large AIFF files correctly, and the limit rarely matters for single recordings. Metadata: AIFF supports metadata through MARK (markers), INST (instrument/loop point data), MIDI (MIDI chunk), NAME, AUTH, COPYRIGHT, and ANNO chunks. WAV uses INFO and LIST chunks for metadata. For music production both are adequate; AIFF's MARK and INST chunks are significant for sampler users. Sampler loop points: AIFF has native support for defining loop start and end points used by sampler instruments — this is a meaningful advantage in certain sound design workflows. Compatibility: WAV is slightly more universal because of its PC/Windows origin; AIFF is natively preferred on Mac. Both play on all modern platforms.

One practical advantage AIFF has over WAV and most other formats is native support for sampler loop points through its MARK and INST chunks. A sampled instrument in a synthesizer or sampler plugin needs to know: where to start playing the sample, where the loop begins (so the note sustains when held), and where the loop ends. AIFF can embed these markers directly in the file. When you open an AIFF file in a sampler, it reads the embedded loop point markers and automatically configures the looping correctly — no manual setup needed. This feature made AIFF the default format for sample libraries through the 1990s and 2000s. Logic Pro's EXS24 sampler (now QuickSampler) and many third-party samplers read AIFF loop markers. Native Instruments Kontakt can import AIFF files with embedded loop points. Software instruments distributed as AIFF sample libraries maintain backward compatibility with this established ecosystem. WAV files can store loop point markers in their SMPL chunk, but AIFF's loop point support is older, more widely implemented, and better supported across Mac-native sampler instruments.

Apple introduced AIFF-C in 1989 as a compressed variant of AIFF. The design intent was sound: AIFF-C used a four-character compression type field in the COMM chunk to indicate what codec was used for the audio data. Supported compression types included 'NONE' (identical to standard AIFF), 'MAC3' and 'MAC6' (MACE compression, Apple's proprietary speech compression), 'ulaw' (G.711 µ-law, telephone quality), 'alaw' (G.711 A-law, European telephone standard), and in theory any other codec that could be defined. In practice AIFF-C never achieved meaningful adoption. The MACE codecs were low quality by music production standards. The format arrived before broad internet distribution made compression critical. And when Apple needed a good compressed format, they chose AAC inside M4A rather than extending AIFF-C. Today AIFF-C files are essentially a historical curiosity. If you encounter a .aiff or .aif file that does not play correctly, it might be an AIFF-C file with a codec your software does not support — this is rare but possible with very old Mac software archives. VLC usually handles AIFF-C correctly even when other players fail.

AIFF is the native uncompressed format of choice for Mac-centric music production. Logic Pro records sessions in AIFF by default on macOS — though it can be configured to use WAV. GarageBand exports finished projects as AIFF (and also M4A and MP3). Final Cut Pro uses AIFF for audio in its production pipeline. Pro Tools on Mac supports AIFF alongside WAV; many Mac-based Pro Tools studios use AIFF because it integrates cleanly with the rest of the Apple audio ecosystem. Avid Sibelius and Finale can export AIFF. Reason, Ableton Live, and most other DAWs import and export AIFF without issues. In the sample library world, older EXS24 instruments, Kontakt libraries built for Mac, and many third-party sound packs distributed through the Apple ecosystem use AIFF. For stems and file interchange between Mac studios, AIFF works as reliably as WAV. The practical difference between AIFF and WAV in a modern professional workflow is minimal — they decode identically. Choice of format often comes down to convention: a studio that standardized on Logic Pro a decade ago likely uses AIFF; one that standardized on Ableton or Pro Tools on Windows likely uses WAV.

AIFF's limitations are worth knowing before you commit to it. AIFF is not compressed — files are large, identical in size to WAV at the same settings. A 1-hour stereo recording at 24-bit/48 kHz is over 1 GB. For archival where storage matters, FLAC achieves 40–60% compression with zero quality loss and is usually the better choice. AIFF is not universally supported outside Apple and professional audio software. Windows Media Player requires QuickTime or a codec pack. Many Android devices cannot play AIFF natively. Car stereos essentially never support AIFF. Browser support for AIFF HTML5 audio is inconsistent — some browsers handle it, others do not. AIFF is not suitable for web delivery, email attachments (too large), or distribution to general audiences. AIFF does not have a compressed lossless mode — for that, use FLAC or ALAC. AIFF's metadata fields (NAME, AUTH, ANNO) are more limited than modern tagging systems like Vorbis Comments or iTunes atoms — fine for production, less capable for music library management. And AIFF's big-endian byte order can occasionally cause compatibility issues with embedded systems, hardware recorders, or unusual software that only handles WAV's little-endian byte order.

Pros: Perfect uncompressed audio quality — every sample of the original preserved with zero data loss. Native format for Logic Pro, GarageBand, and the Mac professional audio ecosystem. Native sampler loop point support via MARK and INST chunks — important for sound designers and sample library developers. Identical audio quality to WAV. Supported by every professional DAW on macOS. Clean metadata support adequate for professional production. Cons: Large file sizes — identical to WAV, roughly 10 MB per minute at CD quality. Not universally supported outside Mac and professional audio software. Car stereos almost never support AIFF. Android does not play AIFF natively on most devices. Web browser support for AIFF is inconsistent. Less common than WAV in cross-platform professional audio interchange — most cross-platform studios default to WAV. No compression option for archival — use FLAC or ALAC if file size matters. Big-endian byte order occasionally causes compatibility issues with non-standard equipment.

macOS plays AIFF natively — built into Core Audio since Mac OS X. iOS plays AIFF in the Music app and via the AVFoundation framework in third-party apps. Logic Pro, GarageBand, and Final Cut Pro import and export AIFF natively. Pro Tools on Mac handles AIFF. Ableton Live, Reason, FL Studio on Mac, and most other professional DAWs import AIFF without issue. VLC plays AIFF on macOS, Windows, Linux, and iOS. QuickTime Player on macOS opens AIFF. Windows Media Player requires QuickTime for Windows (discontinued) or a codec pack for AIFF — Windows 10 and 11 can play AIFF with the right codec but do not include one by default, unlike WAV. Chrome and Firefox have inconsistent AIFF support in HTML5 audio — do not rely on it for web delivery. Safari on macOS and iOS plays AIFF reliably. Android does not play AIFF natively; VLC for Android is the common workaround. Car stereos essentially never support AIFF — convert to MP3 or WAV for car audio use. Serato DJ Pro and rekordbox support AIFF on Mac. Ableton Live handles AIFF on both Mac and Windows. Native Instruments Kontakt reads AIFF sample libraries. Most professional audio hardware recorders (Zoom, Tascam) record in WAV not AIFF, even when used with Mac.

File size calculations for AIFF (identical to WAV at the same settings). Formula: file size in MB = (sample rate × bit depth × channels × duration in seconds) ÷ (8 × 1024 × 1024). CD quality stereo (16-bit, 44.1 kHz): 1 minute is approximately 10.1 MB; 4 minutes (one song) is 40.4 MB; 1 hour is 605 MB. Professional standard stereo (24-bit, 48 kHz): 1 minute is approximately 16.6 MB; 4 minutes is 66.2 MB; 1 hour is 996 MB. High-resolution stereo (24-bit, 96 kHz): 1 minute is approximately 33.2 MB; 4 minutes is 132.5 MB; 1 hour is 1.95 GB. High-resolution stereo (32-bit, 192 kHz): 1 minute is approximately 88.5 MB; 4 minutes is 354 MB; 1 hour is 5.3 GB. For comparison: FLAC at 16-bit/44.1 kHz stereo achieves 50–65% compression, bringing a 4-minute song to roughly 18–22 MB versus 40 MB for AIFF/WAV. For archival where storage efficiency matters, FLAC is the better choice; for production workflow where CPU efficiency and direct editing matter, AIFF or WAV is preferred.

Use AIFF in Mac-centric music production environments where it is the expected or native format. Logic Pro sessions that export stems to other Mac-based collaborators. Sample library development for Mac-native samplers where loop point markers matter. Archiving recordings in a professional Mac studio where AIFF is the established standard. If your collaborators or studio are Windows-based, use WAV instead — it is universally supported and technically equivalent. For distribution to general audiences, convert AIFF to MP3 (for maximum compatibility) or AAC M4A (for Apple ecosystem distribution) or FLAC (for audiophile distribution). Never use AIFF for web audio, streaming, or email delivery — file sizes are too large and browser support is inconsistent. For lossless archival where storage matters, FLAC compresses AIFF content at 40–60% smaller with zero quality loss; ALAC M4A is an alternative for Apple-ecosystem archival. The decision between AIFF and WAV for production is usually convention — pick what your DAW defaults to and stay consistent across a project.

Common AIFF conversion workflows: AIFF to MP3 — the most common conversion, for sharing or car stereo use. AIFF is lossless so you are encoding from the best possible source; use 192 kbps or 256 kbps for music. AIFF to WAV — a lossless conversion with no quality change. Useful when sharing with Windows collaborators or software that prefers WAV. The audio data is identical; only the container header changes. AIFF to FLAC — lossless conversion. FLAC will be 40–60% smaller than AIFF with no quality loss. The right choice for archival where storage matters. AIFF to AAC (M4A) — lossy conversion for Apple ecosystem distribution. Use 256 kbps for music quality. AIFF to OGG — lossy conversion for web or open-source projects. AudioUtils converts all of these directly in your browser. No upload required — FFmpeg WebAssembly processes your files locally. Large AIFF files (several GB) may be slow to process in-browser depending on your hardware; for batch conversion of large libraries, desktop software like fre:ac or XLD (Mac) may be faster.