Add your AVI file
Drop one or more .avi 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.
Pulling the soundtrack out of a .avi video into .au audio keeps what you can hear and drops the picture entirely. 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.Pulling the soundtrack out of a .avi video into .au audio keeps what you can hear and drops the picture entirely. An .avi file is Microsoft's Audio Video Interleave container, one of the oldest video wrappers still in circulation. It stores video and audio in alternating chunks inside a RIFF structure, and the extension remains common on older camcorder captures and DivX-era rips.
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 usual reason to take .au audio out of a .avi file is that only the sound matters — a talk, interview, song, or podcast segment. Keeping the video stream would waste storage, and a dedicated audio file is easier to trim, tag, and play. On the source side, no streaming support of any kind; on the target side, the payoff is so simple that nearly any audio tool can parse it, which is exactly what you want for maintaining sound assets in vintage Unix and Java software.
| Aspect | AVI video (.avi) | Sun audio (.au) |
|---|---|---|
| Format type | Container — quality depends on the codecs and settings inside | Lossless — every pixel or sample is preserved exactly |
| How it stores data | interleaves audio and video chunks inside a RIFF file, with the codec identified by a four-character FourCC code | a 24-byte header carries a '.snd' magic number, data offset, encoding type, sample rate, and channel count |
| Strongest at | playing back footage digitized from DV and Hi8 tapes | maintaining sound assets in vintage Unix and Java software |
| Weak spot | no streaming support of any kind | essentially obsolete outside legacy systems |
| Metadata | rIFF INFO chunks store basic fields such as title, artist, and encoding software, but nothing comparable to ID3 or MP4 atoms exists | an optional annotation field in the header can hold a short text string; no formal tag structure exists |
Drop one or more .avi 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. A WebAssembly FFmpeg build demuxes the audio track and re-encodes it locally; the video stream is simply discarded.
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.
Since avi is container-oriented and au is lossless-oriented, the conversion preserves the source content exactly as stored; no additional compression pass is applied beyond what .au itself requires.
Yes — the .avi file is processed inside your browser tab and never uploaded. A WebAssembly FFmpeg build demuxes the audio track and re-encodes it locally; the video stream is simply discarded. 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.
Much smaller — the video stream is usually 80–95% of a .avi file's weight, and it is discarded entirely. The remaining audio is re-encoded at the bitrate implied by your quality setting.
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, rIFF INFO chunks store basic fields such as title, artist, and encoding software, but nothing comparable to ID3 or MP4 atoms exists; none of it is transmitted anywhere because the file never leaves your browser.