MP4 → WebM, when the pipeline says so
Hardware VP9 or AV1 encoding for the toolchains and platforms that want open-format video.
Runs in your browser. Your file never leaves your computer.
- NeedsA hardware VP9/AV1 encoder
- OutputLeaner than H.264 at par
- Without oneGreyed chip, plain reason
- DestinationBrowsers and open pipelines
Some toolchains, wikis and platforms want WebM and will not negotiate. From MP4, this encodes VP9 or AV1 with your machine's hardware encoder; absent one, the option is shown disabled with the reason rather than pretending, because software encoding of these codecs runs at unusable speed. Where hardware exists, results come out smaller than the H.264 source at matching quality. Files that must play beyond browsers should generally stay MP4.
Questions
Why won't the page just encode VP9 in software?
Because it would take hours for minutes of video and users deserve honesty over a spinner. The greyed chip names a browser and hardware that can.
AV1 or VP9?
The page prefers AV1 hardware where present, VP9 otherwise; AV1 compresses better, both play in current browsers.
Where does encoding happen?
On your machine's media hardware, coordinated by the browser.
Related conversions
- WebM to MP4Screen recordings and downloads that only browsers open, moved to the container everything opens.
- MP4 to M4AMusic videos, lectures, recordings: the audio track lifts out cleanly, instantly when it is already AAC.
- MP4 to MP3Audio out of video, in the format the past two decades of hardware agree on. 320 kbps, trimmed as needed.
- MOV to WebMVP9 or AV1 in a WebM container, encoded with your machine's hardware where it has it.
- MKV to WebMContent bound for browser playback, re-encoded with hardware VP9 or AV1 where the machine offers it.
Part of convert video in your browser. Every other conversion is on the conversions index.