How to Convert AIFF to WAV

AIFF is Apple's uncompressed audio format, and WAV is Microsoft's. Under the surface they are remarkably alike: both wrap raw PCM samples with almost no compression, so both store audio at full quality and both produce large files. Converting AIFF to WAV is closer to relabeling a box than reshaping its contents, but the details of how each format lays out its bytes are what make a converter necessary at all, and understanding them tells you exactly why the swap is safe.

Two names for the same idea

AIFF and WAV were designed on different platforms in the same era to do the same job: keep audio uncompressed and pristine. AIFF was published by Apple in 1988 and is derived from the Electronic Arts Interchange File Format, while WAV was introduced by Microsoft and IBM around 1991 as a subset of the Resource Interchange File Format.^[1][3] Both descend from the same idea of a file built out of tagged chunks, so at the structural level they are close cousins. The samples inside are stored in a different byte order and a different header layout, which is why a swap is needed at all, but the underlying sound data is the same kind of raw PCM. This makes the conversion a container change rather than a re-encode.

Where AIFF and WAV came from

The reason two nearly identical formats exist at all is a story of parallel platforms. In the mid-1980s, Electronic Arts devised the Interchange File Format, a general scheme for building files out of self-describing chunks, so that different programs could read each other's data by simply skipping any chunk they did not recognize. Apple adopted that scheme for audio and published AIFF in 1988, giving the Macintosh a clean, extensible way to store uncompressed sound.^[1]

Microsoft and IBM, working on the PC side, took the same chunked idea and defined their own variant called the Resource Interchange File Format, then built the WAV audio format on top of it around 1991.^[3] The two camps solved an identical problem in an almost identical way, differing mainly in the small conventions each platform preferred, most notably the byte order inherited from their respective processor families. That shared ancestry is exactly why converting between them is so clean: you are moving audio between two dialects of the same underlying language rather than translating between genuinely foreign formats.

Inside the two files: chunks and byte order

Both formats organize their data as a series of labeled chunks. An AIFF file opens with a FORM header and then carries a Common chunk describing the sample rate, channel count, and bit depth, followed by a Sound Data chunk holding the actual audio.^[2] A WAV file opens with a RIFF header and carries a fmt chunk with the same essential parameters, followed by a data chunk of samples.^[4] The parallel is almost one to one, which is precisely why the conversion is trivial in engineering terms.

The one genuine technical difference is byte order, sometimes called endianness. AIFF, following its Motorola-based Apple heritage, stores multi-byte sample values big-endian, most significant byte first. WAV, following its Intel-based origins, stores them little-endian, least significant byte first. So a converter is not just changing headers: for each sample it reverses the order of the bytes. This is a mechanical, perfectly reversible operation that changes not a single value, only the sequence in which the value's bytes are written to disk.

How the conversion works under the hood

The converter runs a short, lossless pipeline. First it parses the AIFF chunks to learn the sample rate, bit depth, and channel count and to locate the Sound Data chunk. Then it reads the PCM samples and reorders each value's bytes from big-endian to little-endian. Finally it writes a new RIFF container, emitting a fmt chunk that restates the same parameters and a data chunk holding the reordered samples. No filtering, resampling, requantization, or perceptual modeling happens anywhere in that chain.

Because every sample keeps its exact numeric value, the output is a bit-for-bit faithful representation of the same waveform. That is the defining property of this conversion and the reason it can be repeated in either direction without any accumulating loss, unlike anything involving a lossy codec.

Why quality does not change

When the converter reads AIFF and writes WAV, it moves the same PCM samples into the new container. There is no lossy step, so the audio you hear afterward matches the original exactly. This is why AIFF to WAV is described as lossless: the only things that change are which program can open it comfortably, how the header is written, and the order of bytes within each sample, not the sound itself.

Convert AIFF to WAV step by step

1. Add your AIFF file

   Open the audio converter and drop in the AIFF file. It runs on your device, so nothing is uploaded.

2. Choose WAV

   Select WAV as the output. There is no bitrate to pick, since both formats are uncompressed.

3. Convert and download

   Run it and download the WAV. The file size will be close to the AIFF you started with.

Why both files are the same size

One question people often have is why converting to WAV does not make the file any smaller. The answer follows directly from the fact that both formats store raw PCM. The size of uncompressed audio is fixed by its parameters alone: sample rate multiplied by bit depth multiplied by channel count gives the data rate, and that rate multiplied by the duration gives the size. At CD quality, 44,100 samples per second at 16 bits across two channels, that works out to about 10 megabytes per minute, and the same figure holds whether the container around those samples calls itself AIFF or WAV.

Because the conversion only reorders bytes and rewrites headers, it cannot change that arithmetic. The two files differ by a few dozen bytes of header at most. This is exactly what distinguishes a container swap from a real compression step: converting AIFF to FLAC would run an actual lossless compressor over the samples and typically halve the size, while converting AIFF to WAV leaves the sample data untouched and therefore leaves the size unchanged. If a smaller file is the goal, WAV is simply the wrong destination.

Edge cases: AIFF-C, floats, and metadata

Most AIFF files are plain uncompressed PCM and convert to WAV with no complications. A few carry details worth knowing about. There is a compressed variant called AIFF-C, which can hold audio encoded with a codec rather than raw PCM.^[2] If your file is AIFF-C with a compressed payload, moving it into WAV means decoding that codec first, so the operation is no longer a pure byte-order swap, though the audio remains as faithful as the codec allows. A plain uncompressed AIFF has no such wrinkle.

High-resolution audio adds another consideration. Studio files at 24-bit depth, 32-bit floating point, or sample rates of 96 kHz and above transfer cleanly to WAV, since WAV supports all of those, but classic 32-bit WAV files are capped near four gigabytes by the format's size fields, so extremely long high-resolution recordings can exceed that limit and need a modern extension. Finally, metadata does not always survive: tags, markers, and loop points that AIFF stored in its own chunks may not have an exact WAV equivalent, so a converter can only carry across what both formats understand. The audio itself always transfers intact; auxiliary information is the part that can be lost.

Real-world scenarios and the right choice

Because the swap is lossless, the real question is simply whether WAV is the format your destination wants:

When to make the swap

Convert AIFF to WAV when a tool or platform prefers WAV, which is common outside the Apple ecosystem. Plenty of Windows software, game engines, hardware samplers, and web tools accept WAV as their default uncompressed format and may not read AIFF cleanly. Since the swap costs no quality, it is a safe way to make an Apple-recorded file portable.

If everything you use already opens AIFF, there is no need to convert. And when your real goal is a smaller file rather than a different container, choose a compressed format instead: FLAC for lossless size savings, or a lossy format for the smallest result.

When WAV is not what you want

WAV is the right target only when you need an uncompressed file that WAV-first software can open. It does nothing to solve the real weakness both AIFF and WAV share, which is size. If a file feels too big to store or send, swapping AIFF for WAV will not help, because the result is just as large.

For a smaller file with no quality cost, FLAC compresses the same PCM losslessly to roughly half the size and can be turned back into an exact WAV or AIFF whenever you need one. For the smallest possible file where perfect fidelity is not required, a lossy format such as MP3 or AAC will shrink the audio far more by discarding inaudible detail. Choose WAV for compatibility with uncompressed-audio tools, FLAC for a lossless archive that takes less room, and a lossy codec for portability. Reaching for WAV should be a decision about which programs need to open the file, not an attempt to make it smaller.