Extract Audio from MOV to WEBA — Free Online Tool
Extract audio from MOV files and convert it to WEBA format, encoding the audio stream as Opus inside a WebM container — ideal for web delivery where Opus's superior compression efficiency at low bitrates outperforms older codecs like AAC. The video stream is discarded entirely, leaving a lightweight, streaming-ready audio file.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your MOV 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
MOV files commonly carry AAC or PCM audio alongside a video stream. During this conversion, FFmpeg discards the video stream entirely and re-encodes the audio — whether it was AAC, FLAC, MP3, or another codec inside the MOV — into Opus using the libopus encoder, then wraps the result in a WebM-based WEBA container. Re-encoding is necessary because WEBA only supports Opus or Vorbis audio, so any MOV audio codec must be transcoded rather than simply copied. The Opus codec is particularly efficient at bitrates like 64k–128k, making the resulting WEBA file noticeably smaller than the original MOV while retaining strong perceptual audio quality.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg binary. This is the same underlying engine running in your browser via WebAssembly (FFmpeg.wasm), so the command shown is directly portable to a local FFmpeg installation. |
-i input.mov
|
Specifies the input file — a MOV container that may contain video, one or more audio tracks, and potentially chapter or subtitle data. FFmpeg reads all streams from this file before applying the output options. |
-vn
|
Disables video output, ensuring no video stream is included in the WEBA file. This is essential here both because WEBA is an audio-only format and because retaining a video stream would produce an invalid or unplayable output. |
-c:a libopus
|
Selects the libopus encoder for the audio stream. Opus is one of only two codecs (alongside Vorbis) supported inside a WEBA container, and libopus is the standard high-quality open-source implementation used by FFmpeg to transcode the MOV's audio (typically AAC) into Opus. |
-b:a 128k
|
Sets the Opus audio bitrate to 128 kilobits per second. At this bitrate, Opus typically delivers transparent or near-transparent quality for most audio content, and it is noticeably more efficient than AAC or MP3 at the same bitrate — meaning the resulting WEBA file can sound as good or better than the original MOV's AAC track at a similar or smaller file size. |
-vn
|
A second instance of the video-disable flag applied just before the output filename, reinforcing that no video data should be written. This redundancy is harmless and acts as a safeguard to ensure the output WEBA file contains only the Opus audio stream. |
output.weba
|
The output filename with the .weba extension, which signals to FFmpeg to use the WebM muxer in audio-only mode. The .weba extension is the conventional designation for audio-only WebM files containing Opus or Vorbis, distinguishing them from full video .webm files. |
Common Use Cases
- Extracting narration or voiceover audio from a MOV screen recording to embed as a lightweight audio element on a webpage using the HTML5 <audio> tag, where WEBA/Opus is natively supported in Chrome and Firefox.
- Pulling music or a soundtrack from a Final Cut Pro or DaVinci Resolve MOV export to create a web-optimized audio preview for a portfolio or demo reel site.
- Converting MOV interview footage from a camera like a GoPro or mirrorless camera into a compact WEBA file for a podcast or transcription service that accepts web audio formats.
- Stripping the audio from a MOV video file recorded on an iPhone or Mac to produce a small Opus-encoded file for use in a Progressive Web App (PWA) or web game audio asset.
- Reducing bandwidth usage by converting a large MOV video's audio track to a WEBA file for streaming in a browser-based media player, taking advantage of Opus's low-latency streaming capabilities.
- Archiving the audio commentary track from a MOV editing project file in a compact, open-format WEBA file before deleting the video-heavy original.
Frequently Asked Questions
Yes — WEBA with Opus is a lossy format, so some audio information is discarded during encoding. However, Opus is widely regarded as one of the most efficient lossy codecs available: at 128k (the default), it typically sounds indistinguishable from the source to most listeners, and it often outperforms AAC or MP3 at equivalent bitrates. If your MOV source contains lossless audio like FLAC or PCM, you'll lose some fidelity, but the Opus output at 128k or higher will still be very high quality for web use.
The WEBA container is restricted to Opus and Vorbis audio codecs. MOV files most commonly contain AAC audio (the Apple default), which is incompatible with the WEBA/WebM format. Even if the MOV happened to contain Opus audio, FFmpeg would still need to rewrap it, and in practice re-encoding is the reliable path. This means every MOV-to-WEBA conversion involves a full audio transcode, not a stream copy.
Most standard metadata tags (title, artist, album, etc.) are not reliably carried over during this conversion. MOV files store metadata in Apple's proprietary atom structure, while WEBA uses WebM's Matroska-based metadata format. FFmpeg may transfer some basic tags, but chapter markers, multiple audio track labels, and QuickTime-specific metadata will not be preserved, as WEBA does not support those features.
Replace the '-b:a 128k' value in the command with your desired bitrate. For example, use '-b:a 64k' for a very small file suitable for speech or voice content, or '-b:a 192k' for higher fidelity music. Opus is exceptionally efficient at low bitrates — 64k is often sufficient for voice — so you can frequently go lower than you would with AAC or MP3 without noticeable quality loss. The full modified command would look like: ffmpeg -i input.mov -vn -c:a libopus -b:a 64k -vn output.weba
Safari has historically had limited support for WebM-based formats, including WEBA, because Apple has preferred AAC and MP4 containers. As of recent macOS and iOS versions, Safari has added partial WebM/Opus support, but it remains inconsistent. If your primary audience uses Safari or Apple devices, consider using an M4A or MP3 output instead. WEBA is best suited for Chrome, Firefox, and Edge environments.
Yes. On Linux or macOS, you can run a shell loop: for f in *.mov; do ffmpeg -i "$f" -vn -c:a libopus -b:a 128k -vn "${f%.mov}.weba"; done. On Windows Command Prompt, use: for %f in (*.mov) do ffmpeg -i "%f" -vn -c:a libopus -b:a 128k -vn "%~nf.weba". This is especially practical for large MOV files over 1GB, which exceed the browser tool's file size limit.
Technical Notes
WEBA is essentially a WebM container restricted to audio-only content, and it mandates either Opus (libopus) or Vorbis (libvorbis) as the audio codec. Opus, used here by default, is defined in RFC 6716 and is optimized for both speech and music across a wide bitrate range (6k–510k). MOV is a container with broad codec support including AAC, PCM, FLAC, MP3, and Opus, but because none of the video or non-Opus audio codecs overlap with WEBA's requirements, this conversion always involves full audio re-encoding — there is no stream-copy shortcut. The -vn flag appears twice in the generated command (once before the codec flags as intent, once as a safeguard before the output), which is harmless redundancy. One notable limitation is that if the source MOV contains multiple audio tracks — common in professional editing workflows — only the first (default) audio track is extracted and encoded; to extract a specific track, you would need to add '-map 0:a:1' (or the appropriate index) to the command. File sizes will vary significantly: a 100MB MOV with AAC audio might yield a 5–15MB WEBA file at 128k, depending on the duration and original audio complexity.