Add your AIFF file
Drop one or more .aiff files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
Re-encoding .aiff audio as .wav changes how the sound is compressed and which players will accept it. Free, private, and validated — the file never leaves your browser.
Batch files can each use a different output. Nothing uploads for local conversions.
Working inputs include camera RAW, browser-local audio/video, PDF, CBZ/CBR comics, office documents, ebooks, markup, 3D models, structured text, images, and archives.Re-encoding .aiff audio as .wav changes how the sound is compressed and which players will accept it. An .aiff file is Apple's Audio Interchange File Format, storing uncompressed PCM audio much as WAV does on Windows. Mac-based studios have exchanged .aiff masters for decades, and Logic Pro sessions and sample libraries remain full of them.
A .wav file is Microsoft's Waveform Audio format, which in practice almost always stores uncompressed PCM samples. Because every bit of the original signal is preserved and no decoding is required, .wav remains the default working format in recording studios and audio editors. For this route the practical draw is bit-perfect with zero generation loss and negligible CPU cost to read or write — balanced against enormous compared with FLAC, which halves the size losslessly, which is worth knowing before you commit a large batch.
The mirror of the WAV-to-AIFF trip, and the more common direction now that most DAWs, game engines, and upload forms default to WAV. An AIFF master coming off a Mac session carries identical samples; rewriting it as WAV just puts them in the byte order and chunk layout the rest of the world reads first. Nothing is re-encoded, so there is no generation loss to worry about — this is a container change, not a transcode.
| Aspect | Audio Interchange File (.aiff) | WAV audio (.wav) |
|---|---|---|
| Format type | Lossless — every pixel or sample is preserved exactly | Lossless — every pixel or sample is preserved exactly |
| How it stores data | classic AIFF stores big-endian PCM, the opposite byte order from WAV, in COMM and SSND chunks | a RIFF chunk container whose fmt chunk usually declares linear PCM, though compressed codecs are technically permitted |
| Strongest at | delivering masters from macOS-based studios | capturing and mixing sessions in a DAW |
| Weak spot | as bulky as any uncompressed format | enormous compared with FLAC, which halves the size losslessly |
| Metadata | nAME, AUTH, and ANNO chunks provide basic text, marker and instrument chunks store loop data, and an ID3 chunk is a common unofficial extension used by iTunes | rIFF INFO chunks hold basic tags, while the Broadcast Wave bext chunk and iXML add description, originator, and timecode for production workflows; some tools also embed ID3 chunks |
Drop one or more .aiff files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
Select .wav in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if WAV is selectable, the route is real and validated.
Press Convert. The transcode runs on an FFmpeg engine compiled to WebAssembly, so the audio never leaves your device.
Each result is signature-checked before the download unlocks, so a failed encode can never masquerade as a valid WAV file. Outputs keep the original filename with the .wav extension.
Both sides are re-encoded, so expect a small generation loss controlled by the quality setting: aiff is lossless-oriented and wav is lossless-oriented. For visually or audibly transparent results keep quality high; for smaller files lower it and compare.
Yes — the .aiff file is processed inside your browser tab and never uploaded. The transcode runs on an FFmpeg engine compiled to WebAssembly, so the audio never leaves your device. Close the tab and the file is gone from memory.
Windows, macOS, Linux, iOS, Android, and all major browsers play .wav natively. Recordings that exceed 4 GB require the RF64 variant, which some consumer software fails to recognize.
It depends on the content: a RIFF chunk container whose fmt chunk usually declares linear PCM, though compressed codecs are technically permitted. Convert one representative file first and compare before batch-processing a large set.
This converter strips container metadata deliberately (the FFmpeg command runs with metadata mapping disabled) so exported files do not leak recording details. In the source, nAME, AUTH, and ANNO chunks provide basic text, marker and instrument chunks store loop data, and an ID3 chunk is a common unofficial extension used by iTunes; none of it is transmitted anywhere because the file never leaves your browser.
Yes — the reverse route exists as a separate tool. Bear in mind that round-tripping .aiff → .wav → .aiff is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.