Upload a AIFF file and get a WAV back. No signup, no watermark, no limit on how many.
AIFF is Apple's uncompressed PCM format — WAV's opposite number, same audio, different byte order and a container that handles tags rather better.
Where you run into it: Logic and Pro Tools sessions, Mac recordings, older Apple software that wrote it by default.
What it costs you: As big as WAV, and outside the Mac world rather less widely accepted.
WAV is raw, uncompressed PCM in a Microsoft container: the audio exactly as it was sampled, with nothing clever done to it.
Where you run into it: Recording sessions, sample libraries, video editors, anything that has to be edited rather than merely listened to.
What it costs you: It is enormous — roughly 10 MB a minute in CD-quality stereo — and it carries almost no tagging, so a folder of WAVs is a folder of filenames.
These two are the same idea from opposite sides of the industry: uncompressed PCM in a chunked container, Apple's answer and Microsoft's. The samples are identical and the conversion is largely a byte swap — an AIFF stores them big-endian, a WAV little-endian. Worth knowing: most “AIFF” files written by Apple software are technically AIFF-C, the variant with a compression field, usually set to sowt, which means uncompressed and already byte-swapped. All of those are read here, so a file some older software rejects will still convert.
The reason is nearly always Windows. AIFF is read perfectly well on a Mac and by most serious audio software anywhere, but plenty of Windows applications, cheap hardware players, car stereos and embedded devices read WAV and stop there. Two things go missing in the move: the cover art, since an attached image is dropped, and — if the file came out of Logic or Pro Tools at 24 bits — a third of its depth. The written tags do come across, into the WAV's INFO chunk. For archiving a Mac session rather than feeding a device, FLAC is the better destination on both counts.
Yes, entirely, and there is no cap on how many files you convert. No account, no watermark, no trial.
Not for a 16-bit AIFF — the WAV holds exactly the same samples. A 24-bit AIFF is a different matter: WAV is written here at 16 bits, so a 24-bit Logic or Pro Tools export gives up depth on the way through. One more case to be aware of, since AIFF-C allows real compression: a file holding an IMA4 or µ-law payload, which old Mac software wrote, is already lossy, and the WAV will carry that faithfully rather than repair it.
Essentially unchanged for a 16-bit file — same samples, same rate, same channels, a few dozen bytes of difference in the headers. A 24-bit AIFF shrinks by a third on the way to a 16-bit WAV, which is the only circumstance in which this conversion changes the size at all, and it is not a saving anyone should want.
Not here. AIFF can be read but not written by this converter — ffmpeg decodes it happily, and encoding back to it would mean a format almost nothing plays. If you need the original AIFF, keep it rather than recreating it.
The file is uploaded to do the conversion — nothing here runs in your browser — and both your upload and the converted result are deleted the moment the file is sent back. Nothing is stored and nothing is logged beyond the request itself.