After converting video to audio with a browser-based tool, you check the result by reading the duration and file size the page displays next to the output, then downloading the Opus WebM file and playing it in any compatible media player to confirm the audio matches the source video. The Video to Audio Converter exposes those values on the page so you can compare them against the original clip before you save anything. If duration or size is missing, the extraction has not finished; if they look reasonable, the next check is audio fidelity through playback. Because the source file never leaves your browser tab, you can repeat this verification pass as many times as you like without re-uploading anything. The whole check fits inside the same browser tab that ran the extraction, which keeps the workflow simple for short reference clips, voice memos captured on a phone, or a music snippet you need to identify.
What the page shows you is not just a download button. The tool reports the measured duration in seconds and the accumulated file size of the MediaRecorder buffer as the video plays, and that on-page report is your first verification surface. It does not perform an automatic waveform compare or a fingerprint match against the source, because those would require uploading the source. Instead, it gives you the two numbers that change most often when something is wrong, plus the file itself, so you can finish the check yourself in a few seconds.
What the page shows during and after extraction
The Video to Audio Converter runs in three phases and each phase exposes something different. During file selection, the page accepts one MP4, WebM, MOV, M4V, or Ogg file up to 500 MiB and rejects anything outside that bound with a visible message. As soon as the browser has decoded the video's metadata, the tool checks the decoded duration against the five-minute limit, the per-side pixel limit of 4096, and the 3840 × 2160 total-area limit. If the decoded video is within those bounds and exposes an audio track, the extraction proceeds; if not, it stops with a message you can act on rather than producing a silent file.
During playback, the page shows a progress label that follows the current playback time of the video element. That label is also your live check that audio is being captured. The preview is muted during processing so you do not get an echo, but the captured stream still contains the video's audio as long as the browser supports media-element capture. The file size readout climbs as new MediaRecorder chunks arrive, so a steadily increasing size is a positive signal that the recording is working. If the size sits at zero for several seconds, something has gone wrong and the run will fail with a visible message rather than save an empty file.
When playback ends and the recorder produces its last chunk, the page patches the generated WebM container with the measured duration so the file reports a finite timeline in compatible players, then exposes the result through a revocable Object URL. At that point the duration field should match what your source video actually was, and the size field should reflect an Opus WebM file at roughly 128 kbps over that duration. A Cancel control is available during the run if you need to stop the current job and start over.
Inspecting duration and file size before downloading
Duration and file size are the two numbers that catch most problems, and the tool surfaces both before the download starts. A rough sanity check is enough: if you started with a 60-second clip, the output duration should read roughly 60 seconds, and the file size should be close to 1 MB because Opus at 128 kbps compresses to about 1 MB per minute of audio. If the duration is shorter than expected, the playback ended early or a decoder error stopped the recorder. If the duration is much longer, the browser is counting time the video was not actually playing.
The file size check is useful even when the duration looks right. An Opus WebM file for one minute of audio typically weighs around 0.9 to 1.1 MB at 128 kbps, while a five-minute clip lands near 4.5 to 5 MB. Numbers far outside that range usually mean the stream did not contain audio or the recorder produced an empty buffer. The exact numbers depend on your specific input, so treat them as a sanity check rather than a fixed target.
| Check | Where to look | What a healthy result looks like |
|---|---|---|
| Duration | Output label after extraction ends | Within a second of the source video's actual length |
| File size | Output label after extraction ends | About 1 MB per minute of audio for Opus at 128 kbps |
| Container format | Downloaded file extension and MIME type | .webm with an Opus audio track, not MP3, WAV, or AAC |
| Audio track present | Player info or media inspector | One audio stream with a non-zero bitrate |
| Finite timeline | Player scrubber | Scrubber reaches the recorded duration, not infinity |
Play back the Opus WebM file to verify audio
The on-page numbers tell you the recording completed, but only playback tells you the captured stream actually contains the audio you wanted. Open the downloaded file in any browser tab, in VLC, or in a simple HTML5 player such as the one bundled with your operating system. If your browser supports the Opus WebM format, the audio will start immediately. If the player refuses to open the file, the codec inside the container is the problem rather than the recording itself.
Listen for the things that matter for the source you care about: speech should be intelligible, music should be free of harsh artifacts, ambient sound should preserve direction if it had any. Because Opus is a perceptual codec, very quiet passages may sound slightly different from the original compressed packets in the source video, and re-encoding can change the file size and quality relative to the original audio. That is a property of the chosen codec, not a sign that the recording failed.
For a different framing of the same end-to-end browser workflow, see a walkthrough that tests audio extraction online in the browser, which covers the same verification steps from a testing perspective.
Run the extraction and check the result
- Choose one supported local video with an audio track, an MP4, WebM, MOV, M4V, or Ogg file up to 500 MiB whose decoded length is at most five minutes and whose dimensions fit the 4096-pixel and 3840 × 2160 area bounds.
- Select Extract audio and keep the tab open while the video is processed in real time; the browser plays the media stream while MediaRecorder captures only the exposed audio track, so a one-minute clip normally takes about one minute to process.
- Watch the progress label follow playback time and the file size readout grow with each chunk; this is your live signal that the recording is still working.
- Check the duration and file size the page reports once playback ends, and confirm the duration is close to the source and the size lands in the expected Opus WebM range.
- Download the Opus WebM audio file, open it in a compatible player, and confirm the captured audio matches the audio in the original clip.
- If any number looks wrong, select a fresh file and run the steps again; the output is generated fresh each time and nothing is cached on the page.
What to do if the result looks wrong
A duration of zero or a size that never grows means the recorder produced an empty buffer. This happens when the browser cannot expose captureStream for the loaded media element, or when the MediaRecorder does not support the Opus WebM MIME type the tool selects first. Safari and some other browsers fall into this category, and the run stops with a visible message rather than saving a silent file. Switching to a Chromium-based browser is the standard remedy.
A duration close to the source but a file size much smaller than expected usually means the audio track was extremely quiet, because Opus compresses silence aggressively. Open the file and listen; if the audio is there at low volume, the recording worked and your downstream volume control is what needs adjusting. A duration close to the source but a file size much larger than expected usually means the page kept capturing after playback ended; cancel and rerun without leaving the tab in the background.
If the output plays but sounds wrong, remember that the recording path goes through re-encoding. The output is an Opus WebM audio track, not MP3, WAV, AAC, FLAC, or a lossless copy of the original compressed packets. For long recordings, lossless production work, multichannel preservation, precise trimming, or a specific delivery codec, use a dedicated desktop audio editor and verify its export settings. The underlying mechanics are documented in the MDN captureStream reference and the MDN MediaRecorder reference, which describe the same browser APIs the tool relies on.
Limits that affect what you can verify
The numbers on the page are bounded by the same limits the tool applies to the source. Files above 500 MiB are rejected before extraction starts. Decoded videos longer than five minutes, wider than 4096 pixels on either side, or larger than 3840 × 2160 in total area are rejected with a visible message. Videos without an audio track fail explicitly instead of producing a silent file. Decode errors, unsupported recorders, empty output, invalid duration, excessive dimensions, and canceled work all stop with a visible message rather than producing a corrupted file.
A supported file extension is a hint, not a guarantee. A filename or MIME type only identifies a possible container; the browser must still support the codecs inside it. If the extension matches but the browser cannot decode the inner codec, the tool stops with a decode error and the duration and size fields stay empty. This is the same check the page performs up front, so you find out before any playback runs and your verification pass is not wasted on an input that cannot be processed.
Use the result only when you own the source or have permission to extract and reuse its audio. The tool does not bypass DRM, platform access controls, protected streams, remote URLs, or copyright restrictions. It works on the file you have locally, which is what makes the on-page verification meaningful: the audio you hear in the player is the audio that came from your file, captured in your browser, with nothing else mixed in.
If you're weighing options, Compare Two Ways to Convert Video to Audio covers this in detail.