Convert AVI to WEBA — Free Online Tool
Convert AVI video files to WEBA audio by extracting and re-encoding the audio stream using the Opus codec — discarding the video entirely and producing a compact, web-optimized audio file. WEBA with Opus delivers excellent quality at low bitrates, making it ideal for web playback and streaming applications.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your AVI file here
or click to browse
Free — no uploads, no signups. Your files never leave your browser.
Settings
Note: Browser-based encoding uses approximate quality targets. For precise CRF compression, copy the FFmpeg command above and run it on your desktop.
Estimated output:
Conversion Complete!
DownloadHow It Works
When converting AVI to WEBA, FFmpeg strips the video stream completely and extracts only the audio from the AVI container. The audio — which in an AVI file is most commonly MP3 (libmp3lame) or AAC — is then decoded and re-encoded into the Opus codec, wrapped in a WebM-based WEBA container. This is a full transcode of the audio: the original audio data is decoded to raw PCM and then compressed again using Opus. Opus is a modern, highly efficient lossy codec developed by the IETF that outperforms older codecs like MP3 and AAC at equivalent bitrates, particularly below 128k. The resulting WEBA file contains no video data, only the Opus-encoded audio stream, making it significantly smaller than the original AVI.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg binary — the open-source multimedia processing engine that handles all decoding, filtering, and encoding operations in this conversion pipeline. |
-i input.avi
|
Specifies the input file, an AVI container. FFmpeg will probe this file to detect its internal audio and video streams, including the audio codec (commonly MP3 or AAC in AVI files) and the video codec, before processing begins. |
-c:a libopus
|
Sets the audio encoder to libopus, which encodes the extracted AVI audio into the Opus codec. Opus is the native and preferred codec for WEBA/WebM audio, offering better compression efficiency than the MP3 or AAC typically found inside AVI files. |
-b:a 128k
|
Sets the Opus audio bitrate to 128 kilobits per second. At this bitrate, Opus produces audio that is generally considered near-transparent for most content — comparable to or better than MP3 at 192k — making it a solid default for both music and speech extracted from AVI sources. |
-vn
|
Disables video output entirely, telling FFmpeg to ignore and discard the video stream from the AVI file. This flag is required because WEBA is an audio-only container and cannot hold video data. |
output.weba
|
Defines the output filename with the .weba extension, which signals to FFmpeg and to browsers that this is an audio-only WebM file encoded with Opus. FFmpeg uses this extension to automatically select the WebM container muxer for the output. |
Common Use Cases
- Extracting the audio commentary or narration from an old AVI screen recording to publish as a podcast or voice memo
- Pulling a music track or background score out of an AVI video file to use in a web-based media player that supports WEBA/Opus natively
- Converting a collection of AVI video lectures into audio-only WEBA files so students can listen on mobile without downloading large video files
- Stripping audio from AVI game capture footage to create Opus-encoded sound effect or ambient audio assets for a web game
- Reducing bandwidth consumption by serving audio-only content from AVI source files to users on slow connections, leveraging Opus's efficiency at lower bitrates
- Archiving the audio track from legacy AVI media files into a modern, web-compatible format before the AVI originals are retired
Frequently Asked Questions
Yes, this conversion is lossy. Even if your AVI contained high-quality audio, the re-encoding process decodes the original audio to raw PCM and then re-compresses it using Opus. However, Opus is one of the most efficient modern audio codecs available — at 128k (the default), it typically sounds transparent or near-transparent for most content, and it often outperforms MP3 or AAC at the same bitrate. If your AVI's audio was already encoded at a low bitrate, you should not set the WEBA output bitrate higher than the source, as this will not recover lost quality.
No, this is intentional. WEBA is an audio-only container format based on WebM, and it cannot store video streams. The -vn flag in the FFmpeg command explicitly discards the video track. If you need to keep both audio and video in a web-friendly format, you would want to convert the AVI to WebM or MP4 instead.
Yes. The -b:a flag controls the Opus audio bitrate. The default is 128k, but you can change it to values like 64k for smaller files, or 192k or 256k for higher fidelity. For speech content, Opus performs exceptionally well at 64k or 96k. For music, 128k is generally considered near-transparent, and anything above 192k offers diminishing returns. Replace '128k' in the command with your preferred bitrate: for example, ffmpeg -i input.avi -c:a libopus -b:a 192k -vn output.weba.
By default, FFmpeg selects only the best single audio stream from the AVI file and encodes it into the WEBA output. WEBA does not support multiple audio tracks, so only one stream will be preserved. If your AVI has multiple audio tracks and you want a specific one, you can add a stream selector flag such as -map 0:a:1 to pick the second audio track before the output filename in the command.
WEBA with Opus is natively supported in Chrome, Firefox, and Edge, but Safari has historically had limited or no support for WEBA, though modern Safari versions have improved Opus support. For maximum browser compatibility, MP3 or AAC in an MP4 container remains safer. That said, Opus in WEBA is technically superior to MP3 — it has lower latency, better quality at low bitrates, and is an open, royalty-free standard, making it the preferred format for WebRTC, streaming, and modern web audio APIs.
The single command shown is for one file at a time, but you can adapt it for batch processing in a shell script. On Linux or macOS, you can run: for f in *.avi; do ffmpeg -i "$f" -c:a libopus -b:a 128k -vn "${f%.avi}.weba"; done. On Windows Command Prompt, use: for %f in (*.avi) do ffmpeg -i "%f" -c:a libopus -b:a 128k -vn "%~nf.weba". This will process all AVI files in the current directory sequentially.
Technical Notes
AVI is a legacy Microsoft container that uses index-based interleaving of audio and video chunks (hence the name Audio Video Interleave). The audio codec inside an AVI is most commonly MP3 or, in older files, PCM WAV, with AAC appearing in some modern AVI variants. During conversion to WEBA, FFmpeg must fully decode whatever audio codec is present before re-encoding to Opus, meaning the process is always a generation loss regardless of source quality. WEBA is essentially a WebM container (based on Matroska) that is restricted to audio-only content — the file extension .weba is a convention to signal audio-only WebM to browsers and media players. The Opus codec selected by default (libopus) is defined by RFC 6716 and supports bitrates from 6k to 510k, making it unusually flexible. One limitation to note is that AVI does not support chapter markers or subtitle tracks, so no metadata of that kind will be present to migrate anyway. Standard metadata tags (title, artist, etc.) embedded in the AVI may not survive the conversion, as AVI uses the RIFF INFO chunk for metadata while WebM uses Vorbis comment-style tags — FFmpeg will attempt to map common fields but results can vary depending on the source file's tagging.