Extracting audio from a video means isolating the sound track inside a video file and saving it as a standalone audio file, leaving the pictures behind. The Video to Audio Converter does this entirely inside your browser tab: it decodes the video you select, captures its audio track while the clip plays, and rewrites that captured stream as an Opus WebM audio file you can download. No upload happens, no server sees the file, and the original video is never modified. The result is a single audio file that contains whatever the video's track carried — speech, narration, music, background sound, or a reference recording — packaged in a broadly compatible WebM container. Because the tool uses the browser's built-in media APIs rather than a third-party encoder, the output format is fixed to what the browser can record natively, and processing speed is tied to the playback speed of the source clip.
What "Extract Audio from Video" Actually Means
Inside a video file, the picture and the sound usually live as separate tracks inside one container. Extracting audio means peeling off the sound track and writing it out as its own file, the same way you might save a song from a CD rather than the whole music video. The video frames are discarded; the audio is preserved as a continuous recording that begins at the video's first frame and ends at its last.
This is different from muting a video, which only turns the sound off in a video player. Extraction produces a brand-new audio file with no video at all, so you can drop it into a podcast editor, a slide deck, a music library, or a voice memo app. The catch is that the output is a fresh recording of the original audio, not a lossless copy of the source packets. Re-encoding can change both file size and quality, and the container format of the output is determined by the tool you use, not by the container of the input.
How the Browser Captures the Audio Track
The Video to Audio Converter relies on three web APIs working together. First, the browser loads the selected file and decodes it as a normal media element. Once the metadata is available, the tool calls HTMLMediaElement.captureStream to obtain a live MediaStream from the playing video. That stream is filtered to keep only the audio tracks, and the picture tracks are dropped. Finally, a MediaRecorder is attached to the audio-only stream and writes the captured data into a WebM container with an Opus audio track.
Because the recording is tied to playback, the browser plays the video from time zero to the end while the recorder listens. The preview is muted during processing so the user does not hear the clip twice, but the captured stream still contains the video's audio when the browser supports media-element capture. Progress is shown as a label that follows playback time, and Cancel stops the current job. A one-minute video therefore takes roughly one minute to process, and there is no faster-than-real-time path because the recorder samples the live stream rather than the original compressed packets.
Supported Inputs and the Hard Limits You Need to Know
Before opening a file, it helps to know what the tool will accept and what it will refuse. The limits exist because the browser has to decode the entire video into memory and play it back while recording, so very large or very long files would exhaust the tab. The table below summarises the boundaries that the tool enforces.
| Item | Limit |
|---|---|
| Container formats | MP4, WebM, MOV, M4V, Ogg |
| Maximum file size | 500 MiB |
| Maximum decoded length | 5 minutes |
| Maximum longer side | 4096 pixels |
| Maximum total area | 3840 × 2160 pixels |
| Output container | WebM with Opus audio, 128 kbps |
A filename or MIME type only tells the tool what the container might be. The actual codecs inside that container are what matter: if your browser cannot decode the video's video codec, or cannot expose its audio track, the job stops with a visible message. Decode errors, unsupported recorders, empty output, invalid duration, excessive dimensions, and cancelled work all fail in the same explicit way rather than producing a silent or partial file. For a deeper look at how container, codec, and dimension limits interact, see the guide on extract audio from video accuracy, codec, and limits.
Extract Audio from Video in Three Steps
- Choose one supported local video with an audio track. The file must be an MP4, WebM, MOV, M4V, or Ogg container up to 500 MiB, and the decoded clip must be no longer than five minutes with no side larger than 4096 pixels.
- Select Extract audio and keep the tab open while the video is processed in real time. The browser plays the clip from start to end while the recorder captures the audio track; the preview is muted so you do not hear the audio twice.
- Check the duration and file size, then download the Opus WebM audio file. The downloaded container is patched with the known media duration so compatible players can report a finite timeline.
There is no account, no upload step, and no option to choose a different output format. The job runs in the current tab from start to finish, and the resulting audio file is exposed through a revocable object URL that the browser releases once the download is complete.
Why the Output Is Opus WebM and Not MP3
The audio format is determined by the browser's MediaRecorder, not by user choice. Modern browsers can typically record Opus inside a WebM container natively, so the tool picks the first supported Opus WebM MIME type and writes at 128 kbps. Producing MP3, WAV, AAC, or FLAC would require bundling a separate encoder library, which would add a large dependency and break the no-upload, no-install promise of a thin browser tool.
Opus is a versatile, broadly supported codec that handles speech and music well at modest bitrates, and WebM is a lightweight container that most modern players can open directly. If you specifically need MP3, WAV, or a lossless copy of the original compressed packets, you will need a dedicated desktop audio editor. As a rough size guide for the Opus output: 128 kbps × 60 seconds = 7,680 kilobits, which is roughly 0.92 MB per minute of audio. Scaling that to a five-minute clip: 0.92 MB per minute × 5 minutes = 4.6 MB, though the exact figure will vary with the silence and complexity of the source.
When to Use a Dedicated Audio Editor Instead
The browser tool is deliberately narrow. It exists for the common case of pulling a short clip's audio out quickly, locally, and without uploading anything. It is not a replacement for a full audio editor. Reach for a dedicated software tool when you need lossless preservation of the original audio, multichannel or surround sound, precise trimming to a millisecond, batch processing of many files, or a specific delivery codec that the browser cannot emit natively. For long recordings, professional production work, or downstream formats such as WAV or FLAC, install a desktop editor and verify its export settings before delivering the file.
You should also stop and reconsider the source itself. The tool does not bypass DRM, platform access controls, protected streams, remote URLs, or copyright restrictions, and it does not work on content you do not own or have permission to extract and reuse. Extract audio only when you have the right to do so, and reach for the dedicated editor when the job outgrows the browser's recording path.