Initializing... drag & drop files here
Supports: AIF, AIFF
AIF and AIFF refer to the same Audio Interchange File Format — Apple's uncompressed PCM container from 1988. The .aif extension is the original 3-character form (a holdover from classic Mac OS file-type conventions); .aiff is the longer modern spelling. The bytes inside are identical, and most tools accept either extension. WAV is Microsoft's RIFF-based PCM container from 1991. Both store bit-perfect PCM audio; the difference is which platform treats the file as native. Common reasons to convert AIF → WAV:
.aif outright or stumble on the big-endian byte order..aif — Some upload forms, web players, and older consumer apps accept .wav but flag .aif as "unknown." A lossless WAV copy sidesteps the issue without re-encoding.Need the reverse direction? See WAV to AIFF. Going to a smaller distribution format? Try AIFF to MP3 or AIFF to FLAC.
| Property | AIF | WAV |
|---|---|---|
| Origin | Apple (1988) | Microsoft / IBM (1991) |
| Container family | IFF (big-endian chunks) | RIFF (little-endian chunks) |
| Native PCM byte order | Big-endian (PCM_S16BE) | Little-endian (PCM_S16LE) |
| Compression | Uncompressed PCM (AIFF-C variant adds compression) | Uncompressed PCM |
| Bit depth options | 8 / 16 / 24 / 32-bit | 8 / 16 / 24 / 32-bit (int and float) |
| Loop / cue metadata | Native marker / instrument chunks | Cue chunks (inconsistent tooling) |
| Default home | macOS, Logic Pro, GarageBand, Pro Tools on Mac | Windows, broadcast, generic interchange |
| Audio quality | Bit-perfect | Bit-perfect (identical to AIF) |
| File size | ~10 MB / minute (16-bit / 44.1 kHz stereo) | ~10 MB / minute (same) |
| PCM encoding | What it is | Use case |
|---|---|---|
| 16-bit little-endian (default) | Classic WAV, CD-quality | General music, Windows DAWs, audio CD masters |
| 24-bit little-endian | Studio-resolution PCM | DAW masters, mixing headroom, high-resolution archives |
| 32-bit little-endian | Highest-resolution integer PCM | Mastering chains, intermediate DAW renders |
| 16-bit big-endian | Mac byte order inside a WAV header | Niche cross-tool handoff where a consumer wants BE samples |
| A-law (PCM A-law) | 8-bit logarithmic compander | Telephony archives, legacy voice systems (Europe) |
| μ-law (PCM mu-law) | 8-bit logarithmic compander | Telephony archives, legacy voice systems (US/Japan) |
.aif different from .aiff?No — they're the same Audio Interchange File Format. .aif is the older 3-character extension from classic Mac OS file-type conventions; .aiff is the longer modern spelling. The file contents are byte-for-byte identical, and XConvert accepts either as input. Some Windows tools auto-rename .aiff to .aif during transfer; that rename does not change the audio inside.
No. Both AIF and WAV store uncompressed PCM. When you keep the same bit depth, sample rate, and channel layout, the conversion is bit-perfect — the audio samples are identical, only the container header and PCM byte order change. Quality only changes if you deliberately pick a lower bit depth (e.g., 24-bit AIF down to 16-bit WAV) or a lower sample rate, in which case dithering / resampling applies.
Match the source. If your AIF is 16-bit / 44.1 kHz CD-quality (typical for older Mac sessions and CD rips), output 16-bit WAV — going to 24-bit doesn't add information that wasn't there. If your AIF is a 24-bit Logic Pro studio recording, keep 24-bit WAV to preserve the extra dynamic range. Drop to 16-bit only when the destination requires it (audio CD authoring, certain hardware samplers).
Standard AIFF (sometimes called "AIFF-PCM") stores raw uncompressed big-endian PCM. AIFF-C (Compressed) extends the same container to allow compression types like A-law, μ-law, ADPCM, and even MP3-style codecs. The "sowt" AIFF-C variant carries little-endian PCM specifically so Mac tools can write WAV-style PCM data without byte-swapping. XConvert reads all of these on input; the WAV output codec dropdown lets you choose how the PCM is laid out in the resulting WAV.
Because the audio data is identical. AIF and WAV are both uncompressed PCM at the same bit depth, sample rate, and channel count, so the payload size is the same. Only the small header differs (a few hundred bytes). A 5-minute 16-bit / 44.1 kHz stereo file is roughly 50 MB in either format.
Yes — drop in the entire stems folder and the files convert in parallel within your browser session. Settings can apply uniformly across the whole batch (typical for stems where you want consistent encoding) or be tuned per file. Downloads come individually or as a single ZIP.
The audio data transfers bit-perfectly. AIF stores loop points and musical-key metadata in dedicated chunks (MARK, INST); WAV's equivalents (cue, smpl) exist but tooling support is inconsistent. Loop and instrument metadata may not survive the round-trip cleanly. If you rely on loop points (e.g., Apple Loops, sampler instruments), keep an AIF copy alongside the WAV deliverable.
Yes. Use the trim section to enter a start time and duration. Both fields accept seconds (12.5) or HH:MM:SS.sss format (00:01:30.500). Useful for pulling a single song out of a long live-show AIF or extracting a clean take from a Logic Pro tracking session before delivering as WAV.
By default, yes — the converter reads the input AIF's sample rate, bit depth, and channel layout and produces a WAV that matches. You only need to touch the dropdowns when you deliberately want to change one of those values (e.g., downsample 96 kHz to 48 kHz for video work, or fold stereo to mono for a podcast).