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 .au 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 .au 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.
An .au file is the Sun audio format, one of the earliest structured audio files, created for Unix workstations. A minimal header followed by sample data, classically 8 kHz mu-law telephony audio, makes .au about as simple as an audio format can get. For this route the practical draw is so simple that nearly any audio tool can parse it and pCM variants preserve the recording exactly — balanced against essentially obsolete outside legacy systems, which is worth knowing before you commit a large batch.
The practical trigger for this conversion is usually a mismatch: with .aiff, as bulky as any uncompressed format. Switching to .au buys you so simple that nearly any audio tool can parse it, which is why it is the better fit for maintaining sound assets in vintage Unix and Java software. Because the conversion runs locally, trying it costs nothing but a few seconds of compute on your own machine.
| Aspect | Audio Interchange File (.aiff) | Sun audio (.au) |
|---|---|---|
| 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 24-byte header carries a '.snd' magic number, data offset, encoding type, sample rate, and channel count |
| Strongest at | delivering masters from macOS-based studios | maintaining sound assets in vintage Unix and Java software |
| Weak spot | as bulky as any uncompressed format | essentially obsolete outside legacy systems |
| 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 | an optional annotation field in the header can hold a short text string; no formal tag structure exists |
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 .au in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if AU 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 AU file. Outputs keep the original filename with the .au extension.
Both sides are re-encoded, so expect a small generation loss controlled by the quality setting: aiff is lossless-oriented and au 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.
Audio tools such as Audacity, sox, and ffmpeg open .au readily, and Java's sound APIs still accept it. Consumer players, phones, and browsers dropped meaningful support long ago, so conversion to WAV or MP3 is the practical route.
It depends on the content: a 24-byte header carries a '.snd' magic number, data offset, encoding type, sample rate, and channel count. 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 → .au → .aiff is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.