A supported file extension such as .mp4 or .mov describes only the container wrapping your media, not the audio and video codecs stored inside it, and that gap between "the container looks right" and "the codecs match what the browser can decode" is the most common reason a video-to-audio conversion still fails. The extension is essentially a label; the bytes inside follow rules that have changed across devices, encoders, and software versions over more than two decades, so two files with the exact same .mp4 suffix can contain entirely different codec combinations. When you select a video in a browser-based converter, the tool does not inspect the suffix and trust it: it must hand the file to the browser, which checks whether the specific codecs inside are decodable. The same applies to audio: a video container might be fully readable but hold no audio track at all, or carry audio in a codec the current browser cannot interpret. Recognizing this difference between container and codec is the first step in turning a failed extraction into a successful one.
What a Supported Extension Actually Describes
A file extension is a hint to the operating system, not a contract about the bytes inside. MP4 (technically ISO BMFF), MOV (QuickTime File Format), WebM, M4V, and Ogg are all container formats. Each container can hold many different audio and video codec combinations, and the combination that ends up in a file depends on the program that produced it. An iPhone might record HEVC video with AAC audio inside an MP4 wrapper, while a screen recorder might store VP9 video and Opus audio inside a WebM file with the same suffix as something else entirely.
For a browser-based converter, the relevant question is not "does the file end in .mp4" but "can the user's browser decode the specific audio codec inside the file?" If the browser can play the audio, it has the codec built in. If it cannot, the conversion path stops before any extraction begins. This is the part that surprises most users: a file that opens fine in VLC at home might still fail in a browser tool, because the codec stacks shipped with browsers are smaller than the codec packs desktop players install.
The same rule covers audio codecs. AAC (used in many MP4 and MOV files from Apple devices), MP3, Opus (common in WebM), Vorbis (common in Ogg), and FLAC all have different browser support profiles. A MOV file with PCM audio inside it is a different extraction job from a MOV file with AAC inside it, even though the extension matches.
Other Reasons a Supported Extension Still Fails
Beyond the codec question, several other conditions can stop an extraction even when the extension is on the supported list:
The video has no audio track. A silent video, a screencast without microphone audio, or a file whose only stream is video will fail explicitly when the converter requires at least one audio track to capture. The browser can still decode the picture; it just has nothing to put into the audio recorder.
The browser does not expose the right recording primitives. The Video to Audio Converter relies on HTMLMediaElement.captureStream and a MediaRecorder that supports an Opus WebM MIME type. Safari and some other browsers may not expose captureStream, or may not include a MediaRecorder profile compatible with Opus WebM, which stops the run with a visible message before any output is generated.
The file crosses a documented limit. Even when the codec is fine, the browser enforces hard boundaries on file size, decoded duration, and dimensions. These protect memory, decode time, and tab stability. Files outside these limits produce an explicit error rather than a partial file.
The browser session itself is the processor. Because nothing is uploaded and no server does the work, the codec support available in the current browser is what governs the run, and that varies by browser rather than by file extension.
It is worth noting here that the output is always Opus in a WebM container, regardless of what went into the file. The conversion is not a copy of the original audio packets — it is a re-encode by the browser's MediaRecorder. This means the output is a single-audio WebM, and it is not MP3, WAV, AAC, or FLAC.
How to Convert Video to Audio When the Extension Matches
When the codec, dimensions, duration, and browser all line up, the path through the Video to Audio Converter is short:
- Choose one MP4, WebM, MOV, M4V, or Ogg file from your device that has an audio track you want to extract.
- Select "Extract audio" and keep the tab open. The browser plays the video in real time while MediaRecorder captures the exposed audio stream, so a roughly one-minute video takes about one minute to process. A progress label follows the playback head.
- Check the displayed duration and file size, then download the Opus WebM audio file. Cancel is available if you need to stop a run that is already underway.
The tool never uploads the source, never calls an API for the audio, and never retains the output. Everything happens in the current tab, and the download is exposed through a revocable object URL.
Limits That Trigger a Visible Error
The Video to Audio Converter enforces a small, documented set of boundaries. Exceeding any one of them stops the run with a visible message rather than producing a partial or silent file.
| Boundary | Value | What happens when exceeded |
|---|---|---|
| File size | Up to 500 MiB | Visible error before decoding; no job starts. |
| Decoded duration | No longer than 5 minutes | Visible error during validation. |
| Longest side | No larger than 4096 pixels | Visible error during dimension check. |
| Total area | No greater than 3840 × 2160 pixels | Visible error during dimension check. |
| Required media track | At least one audio track | Visible error when the container has no audio stream. |
These limits describe what the current browser can decode and record in one tab. They are not policy choices to be reconfigured; they reflect memory and playback constraints documented in the tool.
Check the Failure Before You Retry
A failed run usually points at one of three causes, and a quick check narrows the next step fast:
Is the audio track actually there? Open the file in a media player and confirm there is sound. ffprobe or VLC's Tools → Codec Information will list the streams. If there is no audio stream listed at all, no browser-based converter will produce an audio file from it.
Is the browser the limiting factor? Switch to a Chromium-based browser on the same machine and try the same file. If the extraction works there, Safari's captureStream support (or lack of it) is the cause, and a browser change is the fix rather than a file change.
Has the codec been checked? Use a media-info tool to see whether the audio inside the container is AAC, Opus, MP3, Vorbis, PCM, or something less common. If the audio codec is one your browser does not decode, the run fails before recording starts. For background on the captureStream primitive the tool depends on, the MDN captureStream reference is a useful starting point.
Two more things help in edge cases. First, the tool will not bypass DRM, platform access controls, protected streams, or remote URLs, so any file from a paid streaming download will fail by design and should not be reused. Second, the output is an Opus WebM audio file, so a download that plays back as silent in software expecting MP3 or WAV is not actually empty; the player is the limitation, not the converter.
For long recordings, lossless production work, multichannel preservation, or precise trimming, a dedicated desktop audio editor is the right tool. The Video to Audio Converter is built for the broadly useful local browser path on short clips, and that scope is what makes the limits and the warning messages predictable. For a deeper look at pre-conversion checks, the guide on how to make sure a video to audio conversion succeeds lays out the same conditions in checklist form.
Related reading: Why Converting Video to Audio Takes the Full Video Length.