Subtitles and extra tracks dropped
MKV files can hold multiple audio tracks, subtitles, and chapters. The WebM output keeps only the primary video and audio track. Ship subtitles as a separate WebVTT file in your <video> element.
Take heavy MKV captures from OBS and turn them into lean VP9 WebM ready for the web.
Drop video files here or click to browse
Files queue into the current batch until you convert · MP4, MOV, MKV, WebM, M4V
OBS-to-CMS is the workflow this page exists for. OBS captures land as MKV (a flexible container that can carry several audio tracks, subtitle tracks, and chapter atoms), and most CMSes (or your own self-hosted <video> tag) want the opposite: one video track, one audio track, modern codec, lean container. WebM with VP9 fits that brief, with the caveat that the converter only carries the primary video and audio track through.
The video usually moves from H.264 inside MKV to VP9 inside WebM, which often produces a smaller file at matched perceived quality. The container itself also gets simpler, with no chapter atoms, no extra audio streams, and no embedded subtitles.
The conversion runs locally in your browser, so a stack of multi-hour OBS captures works the same as a few short clips. No upload, no server timeout.
MKV can carry many audio tracks, subtitles, and chapters. The WebM output keeps just the primary video and audio track, which is exactly what HTML <video> wants.
Re-encoding from H.264 or H.265 MKV to VP9 WebM often produces smaller files at matched perceived quality, with the largest gains on talking-head and screen content. Exact ratios vary with content.
VP9 WebM plays in Chrome, Edge, Firefox, and Safari 14.1+. Pair it with an MP4 fallback in your <video> tag for older Safari support.
MKV files can hold multiple audio tracks, subtitles, and chapters. The WebM output keeps only the primary video and audio track. Ship subtitles as a separate WebVTT file in your <video> element.
VP9 software encoding is slower than typical H.264 hardware encoding. Long OBS sessions take meaningful time to encode. Start the batch and let it run.
Convert a folder of MKV files to WebM in your browser without uploading anything.
Drag and drop one or many MKV files into the queue, or click to pick them.
Output is preset to WebM. For web embedding, drop the width to 1280 or 1920 and use the balanced quality preset.
Click Convert files. Each file is processed locally in your browser.
Download converted WebM files individually, or grab the whole batch as a ZIP.
No. The conversion runs in your browser via WebCodecs and your files stay on your device.
They are not carried into the WebM output. If you need subtitles for the web, ship them as a separate WebVTT track in your <video> element.
In most cases, yes. VP9 is more efficient than the H.264 typically found inside OBS-captured MKVs, and the WebM container has less overhead than MKV.
Browsers do not play MKV natively in <video> tags. WebM is the closest spiritual cousin that plays everywhere modern.
Conversion uses the WebCodecs API. Fully supported: desktop Chrome 94+, Edge 94+, Opera 80+, Firefox 130+, and Safari 26+. Safari 16.4 to 25 work for most files but some may fail because their WebCodecs implementation is partial. Browsers without WebCodecs (Chrome/Edge <94, Firefox <130, Safari ≤16.3, Internet Explorer) cannot run the converter at all. Mobile browser support is improving but inconsistent, so a desktop or laptop is recommended for batch work.
OBS recordings, screen captures, and rips. Turn folders of MKV into MP4 in one pass.
Turn MOV clips into VP9 WebM files for self-hosted web video.
The browser runs the encoder directly, so there is no upload to a server.
Shrink a folder of videos in one pass, typically several times smaller, with little visible quality loss.