The first step to convert video to audio is choosing a local video file that your browser can actually decode, then opening a browser-based extractor that captures the audio track while the clip plays. In practical terms this means selecting a single MP4, WebM, MOV, M4V, or Ogg file from your device and confirming it contains an audio track, all before pressing any convert button. The reason this comes first is that the entire extraction pipeline depends on the browser being able to play the file: if the container format is supported but the inner codecs are not, the file is rejected at the decode step regardless of the file extension. Lizely's Video to Audio Converter follows this same first-step pattern, since the tool loads a chosen local file, validates it against size and dimension limits, and only then begins the real-time capture of the audio track into an Opus WebM file. Skipping straight to a convert button without first confirming the file type, audio track presence, and browser compatibility is the most common reason these tools fail with a confusing error message. So the very first action is the deliberate selection of a compatible local file inside a browser that supports the underlying media APIs.
What the first step actually involves
A "first step" question usually hides a second, more useful question: what does the tool actually need from me before it can do anything at all? For a local browser extractor like the Video to Audio Converter, three conditions have to be true before recording can start. The file must live on your device, not behind a remote URL or a streaming manifest. The browser must be able to decode the audio and video tracks inside the container. And the clip must contain at least one exposed audio track, because a video with no audio track fails explicitly rather than producing a silent file.
This is why the first step is file selection rather than tool selection. Choosing a tool before knowing whether your clip is browser-decodable just shifts the same compatibility problem downstream. The Video to Audio Converter handles the technical validation automatically, but it can only do so once you have pointed it at a specific local file. Think of the first step as identifying and confirming the input, not pressing the start button.
Before you start: file and browser requirements
The tool performs its checks at the moment a file is loaded, so it helps to know the requirements in advance and avoid the round trip of picking a file that immediately fails. The container must be one of MP4, WebM, MOV, M4V, or Ogg, and the file itself must be no larger than 500 MiB. The decoded video must be no longer than five minutes, no larger than 4096 pixels on either side, and no greater than 3840 × 2160 pixels in total area. These caps bound memory, playback time, and browser resource use so that the page stays responsive while recording.
A filename or MIME type only identifies a possible container; the browser still has to support the codecs inside it. A .mp4 wrapper around an unusual video codec, or a .mov with a protected audio track, can still fail even though the extension is on the supported list. If your clip uses a codec your browser cannot decode natively, no in-browser tool can rescue it. Safari and some other browsers do not expose captureStream or a compatible MediaRecorder format, and the tool stops with a visible message when the browser cannot run the extraction pipeline. The MDN reference for HTMLMediaElement captureStream lists which browsers expose that API at the time of writing.
How to extract audio from a local video
- Open the Video to Audio Converter in a current Chromium-based or Firefox browser, then choose a single MP4, WebM, MOV, M4V, or Ogg file up to 500 MiB from your device. The file stays in the current tab and is never uploaded.
- Wait for the browser to decode the file and confirm that at least one audio track is exposed. If the clip has no audio track, or the codecs inside the container are not supported, the tool stops with a visible message before any recording starts.
- Select Extract audio and keep the tab open and the page focused. The browser plays the video from time zero while MediaRecorder captures only the exposed audio track. The preview is muted during this step, but the captured stream still contains the video's audio when the browser supports media-element capture.
- Watch the progress label, which follows playback time. A one-minute video normally takes about one minute to process because extraction is real time. Cancel stops the current job if you need to abort.
- Check the duration and file size shown by the tool, then download the resulting Opus WebM audio file through the revocable Object URL the page exposes.
Limits that decide whether extraction succeeds
These limits interact, so a clip can pass one check and fail another. A 4K file under five minutes and under 500 MiB can still be rejected if either side exceeds 4096 pixels or the total decoded area is greater than 3840 × 2160. A short clip over 500 MiB is rejected on file size alone, regardless of resolution. The table below lists the exact bounds the tool enforces.
| Constraint | Value | What it controls |
|---|---|---|
| Container formats | MP4, WebM, MOV, M4V, Ogg | What the browser will try to load |
| File size | Up to 500 MiB | Memory and upload-free handling |
| Decoded duration | Up to 5 minutes | Playback and recording time |
| Longest side | Up to 4096 pixels | Decoded frame dimensions |
| Total pixel area | Up to 3840 × 2160 | Resource budget per frame |
| Audio track | At least one required | Whether extraction can produce output |
| Recorder bitrate | 128 kbps Opus | Output audio size and quality |
Why the output is WebM audio and not MP3
The tool uses the browser's built-in MediaRecorder, which means the output format is whatever Opus WebM MIME type the browser advertises first. MP3 encoding would require shipping a separate codec dependency, which goes against the goal of a small, browser-only tool. The output is therefore WebM audio with an Opus track at 128 kbps, not MP3, WAV, AAC, or FLAC. The exact file size for a clip of length L seconds is roughly 128 × L ÷ 8 kilobytes, so a sixty-second extraction lands near 960 KB before any container overhead, while a five-minute extraction lands near 4.8 MB. Re-encoding may change quality and file size compared with the original compressed audio packets inside the source video, so treat the result as a fresh Opus file rather than a bit-for-bit copy of the source track.
The generated WebM container is patched with the known media duration so downloaded files report a finite timeline in compatible players. If you open the downloaded file in a player that does not recognize the patched Segment Info, the clip may still appear to have an unknown length even though playback works. The MDN MediaRecorder reference describes how browser support for Opus WebM recording varies across versions.
When the browser path is not the right choice
The local browser extractor is built for quick, single-clip jobs where Opus WebM is a suitable delivery format. There are several situations where a different workflow is the better call, and it helps to recognise them before you start so you do not waste a session on a tool that was not designed for the task. The table below compares the browser path against the cases where a dedicated desktop audio editor makes more sense. For a deeper list of missteps to avoid when planning this kind of conversion, see Avoid These Mistakes When Converting Video to Audio.
| Scenario | Browser extractor fits | Use a desktop audio editor instead |
|---|---|---|
| Clip length | Up to about five minutes | Longer recordings, full episodes, multi-hour talks |
| Output format | Opus WebM is fine | A specific delivery codec like WAV, FLAC, or AAC |
| Editing needs | Pure extraction, no trimming | Precise trimming, fades, level changes, multichannel preservation |
| Quality goal | Convenient speech or reference audio | Lossless production work or archival copy of the source track |
| Source | A local file you own or have permission to process | DRM-protected streams, remote URLs, or platform access controls |
The tool does not bypass DRM, platform access controls, protected streams, remote URLs, or copyright restrictions, and Lizely does not upload the source video, send its contents to an API, or retain the output. Use the resulting audio only when you own the content or have permission to extract and reuse it. For everything outside the "short local clip, Opus WebM is fine" sweet spot, a dedicated desktop audio editor with the right export settings will give you a more predictable result.
Related reading: What Result to Expect When You Convert Video to Audio.