WebM is what your browser records. The MediaRecorder API in Chrome, Firefox, and Edge defaults to WebM containers when capturing microphone audio in the browser. Google Meet exports use WebM. Any web app that records audio (lots of newer voice-note tools, in-browser meeting recorders) ends up with .webm files. MDisBetter accepts them directly without a transcode step.
Where WebM audio comes from
WebM was originally designed as a video format (VP8/VP9 video + Vorbis/Opus audio) but the audio-only variant has become the de facto output of in-browser recording. The reason is technical: the MediaRecorder Web API defaults to WebM-with-Opus-audio in Chrome, the most common recording browser, because Opus is royalty-free and high quality. Any web tool that says "record from your microphone" without installing a plugin is producing a WebM file under the hood.
Common WebM audio sources
Google Meet recordings can be exported with the audio track as WebM. In-browser voice notes from web-based meeting tools, online recorders (vocaroo, online-voice-recorder), and any custom web app using MediaRecorder. Browser-based screen recorders use WebM internally for browser-side capture. Discord browser recordings save as WebM in some configurations. The breadth of sources means if you're working with web-captured audio at all, you'll see WebM eventually.
Why direct WebM support matters
Most online transcription tools refuse WebM and require you to convert to MP3 first using a separate tool (online converters, ffmpeg, Audacity). That's a re-encoding step that loses audio quality (the WebM is already lossy; MP3 conversion makes it lossier still) and takes a few minutes you'd rather not spend. Direct WebM support removes the friction: the file goes from your browser's download folder straight into Markdown.
Before / After
Before (PDF):
[WebM audio file]
Opus audio in WebM container, 2.8 MB, 14 minutes mono
Metadata: browser-recorded (Chrome MediaRecorder)
(no extractable text — browser-captured waveform)
After (Markdown):
# Web Meeting — Product Review
## Demo Walkthrough
[00:00:02] OK sharing my screen now. So this is the new onboarding flow we've been talking about. Looks clean. What's the conversion data so far?
## Conversion Numbers
[00:00:18] We rolled it out to 10% of new signups two weeks ago. Activation is up 14% relative to the control group…
Frequently asked questions
Will my Google Meet WebM exports be labelled by participant?
No. We transcribe the audio but do not identify speakers, so a Meet recording comes back as one continuous transcript rather than participant-by-participant turns. You still get punctuation, ## H2 sections at topic shifts and inline timestamps, which is what makes the recording searchable. For per-participant attribution, Google's own Meet transcript has the attendee list, or run a dedicated diarisation tool over the same file.
What's the difference between WebM and MP4 for audio?
WebM is the open-source, royalty-free container (Vorbis/Opus audio inside). MP4 is the older, more universal container (AAC audio inside). Both work for audio; WebM is what browsers produce, MP4 is what most other recording tools produce. Both are accepted directly without conversion.
Can I record audio in my browser and immediately transcribe?
Yes — the workflow is: browser records to WebM, downloads file, drop into MDisBetter, get Markdown. For a custom application embedding this flow, the OSS path is short: capture with MediaRecorder API, send the resulting Blob to a backend that calls a transcription model (faster-whisper for self-hosted, or any commercial API). MDisBetter is the no-code path for the same outcome.
Does this work with WebM files that have video tracks too?
Yes — when a WebM contains both video and audio, we extract just the audio track for transcription. The video itself isn't analysed (MDisBetter is a converter, not a video understander), but the spoken audio comes through cleanly. For full video-to-text workflows including visual context, see YouTube to Markdown for an alternative pipeline.
Are WebM files from screen recorders supported?
Yes — screen recorders that produce WebM (browser-based screen recorders, some OBS configurations) export with audio in the standard WebM-with-Opus structure. The transcription extracts the audio track and processes it like any other WebM. Useful for transcribing demo videos, tutorial recordings, and async screen-recorded walkthroughs.