Initializing... drag & drop files here
Supports: WAV
WAV (Microsoft / IBM, 1991) and AIFF (Apple / Electronic Arts, 1988) are the two dominant uncompressed PCM audio containers. Both are lossless. Both store the same audio samples. The difference is structural: WAV is a RIFF container with little-endian byte order (intended for x86); AIFF is an IFF container with big-endian byte order (intended for Motorola 68000 / early Macintosh). For practical purposes the audio is bit-identical — converting WAV to AIF is a container change, not a quality change. The .aif extension is just the 3-character variant of .aiff used historically on Windows; macOS and pro audio tools treat .aif and .aiff as the same format.
| Property | WAV | AIFF (.aif / .aiff) |
|---|---|---|
| Year / origin | 1991, Microsoft + IBM | 1988, Apple + Electronic Arts |
| Container family | RIFF | IFF |
| Byte order | Little-endian | Big-endian (standard); little-endian variant is AIFF-C "sowt" |
| Compression | Uncompressed PCM (LPCM) by default | Uncompressed PCM by default |
| Compressed variant | Rare; usually LPCM only | AIFF-C / .aifc supports μ-law, A-law, ADPCM, etc. |
| Default codec on this page | — | PCM_S16BE (16-bit signed big-endian) |
| Typical 1-min stereo size at 16-bit/44.1 kHz | ~10 MB | ~10 MB |
| Native OS | Windows | macOS |
| Pro audio default | Pro Tools, most Windows DAWs | Logic Pro, GarageBand |
| Metadata chunks | RIFF INFO + optional BWF / iXML | Name, Author, Copyright, Annotation, Comment, MIDI, Application, ID3 |
| BWF timecode | Supported (Broadcast WAV) | Not supported |
| File extensions | .wav | .aif, .aiff (same format); .aifc (compressed variant) |
| Setting | When to use | Notes |
|---|---|---|
| Original sample rate | Default — pure container change | No resampling, bit-identical audio |
| 44100 Hz | CD audio, music release, streaming masters | Standard for music delivery |
| 48000 Hz | Video post, broadcast, film audio | Standard for FCP, Logic-to-video workflows |
| 24000 / 16000 Hz | Speech, podcasts where size matters | Resamples — alters audio data |
| 8000 / 12000 Hz | Telephony, narrowband voice | Heavy quality loss; only for voice tools |
| Mono channel | Single-source voice, mono mics, podcasts | Cuts file size ~50% |
| Stereo channel | Music, ambient, anything spatial | Doubles size vs mono |
| Original channel | Default — keep what the source has | Recommended unless you need to force layout |
No. Both formats store uncompressed PCM samples; only the container header and byte order change. If you leave sample rate and channels on Original, the output is a bit-identical representation of the same audio. Run a phase-inversion null test against the source and you will get silence. The only way the audio changes is if you deliberately resample (e.g., 48000 to 44100 Hz) or downmix (Stereo to Mono).
Yes. AIF is just the 3-character version of AIFF, kept historically for compatibility with Windows file-extension conventions. The bytes inside are identical. macOS, Logic Pro, GarageBand, Final Cut Pro, QuickTime, VLC, ffmpeg, and Audacity all treat .aif and .aiff as the same format. AIFF-C (.aifc) is the different one — it adds optional compression codecs (μ-law, A-law, ADPCM) and uses a different chunk signature.
Standard AIFF stores audio as big-endian PCM. AIFF-C ("AIFF-Compressed") is a 1991 extension that adds compression codecs and a "sowt" (literally "twos" reversed) profile that holds little-endian PCM. Modern macOS and Logic Pro often write AIFF-C/sowt internally but label the file as AIFF. This page outputs standard big-endian PCM (PCM_S16BE) — the most universally compatible AIFF profile.
No. Broadcast WAV adds a bext chunk for timecode that AIFF does not have an equivalent for. Converting BWF to AIFF strips the timecode. If you need timecode to survive, keep the file as BWF/WAV or use a format like CAF that preserves it. If you don't care about timecode (e.g., music masters, sample-pack delivery), conversion to AIFF is fine.
Three reasons: (1) Logic Pro and GarageBand record AIFF by default, so the project graph already speaks AIFF natively. (2) AIFF metadata chunks are richer and more cleanly handled by macOS Finder and Apple pro apps than WAV's RIFF INFO. (3) Historically, sample libraries and instrument packs in the Apple ecosystem ship as AIFF, so studios standardise on it. Sonically there is no advantage — it's a workflow and pipeline preference.
Yes. Drop in every track at once. Each file converts independently in your browser session and downloads as separate AIFs or one combined ZIP. Settings (channel, sample rate, trim) can apply uniformly across the batch — the typical case when prepping an album for delivery to a Mac mastering engineer.
Only if the source is genuinely mono content (single-mic voice recording, podcast, audiobook chapter). Downmixing real stereo music to mono collapses the stereo image and is destructive. For music masters always keep Stereo. For voice-only recordings, Mono cuts file size by half with no quality loss for speech.
Yes. Windows Media Player has supported AIFF since Windows 7, and any modern audio app on Windows (VLC, foobar2000, Audacity, Reaper, Audition) reads AIFF natively. The "Windows native" bias of WAV is historical — the formats are interchangeable on every modern OS.
This page outputs PCM 16-bit big-endian (PCM_S16BE) — 16 bits per sample, the universal AIFF profile that every player understands. AIFF as a format supports up to 32-bit and arbitrary sample rates, but for a clean WAV→AIF container swap, 16-bit is the safe default. If you need 24-bit or 32-bit float for mastering, render that bit depth from your DAW directly. For other directions, see AIFF to WAV, WAV to MP3, or WAV to FLAC.