Cookies for analytics and advertising
We use cookies for analytics and advertising, both sent to Google. Refusing changes nothing you can see.Read the privacy page
Converting MKV to OGG takes the sound out of a recording and puts it in the container open-format policies name by default. What goes inside is Opus rather than Vorbis, which is the one thing to check before delivering anywhere — and because the picture is discarded rather than converted, an enormous Matroska lecture capture becomes an audio file a fraction of its size.
Up to 100 files at once. Mixed formats are fine.
They convert one after another and download together as a ZIP.
MKV to OGG
Lecture and conference recording systems write Matroska more often than anything else. Opencast produces it, OBS records to it by default because an MKV survives a crash where an interrupted MP4 does not, and camera-plus-slides capture rigs use it because they need to keep two video streams and several microphones in one file without arguing with a container about it.
That is excellent for recording and unhelpful for publishing. The systems these recordings end up in — institutional repositories, teaching platforms, wikis, federated video hosts — have accepted-format lists written around what is free to implement, and Matroska sits awkwardly across that line while Ogg sits squarely on the right side of it.
Ogg is a container, not a codec, and that distinction is the source of most of the trouble on this pair. It has carried Vorbis since 2000, FLAC since not long after, and Opus since 2012. A file with a .ogg extension therefore tells you almost nothing about what a decoder will need.
What this conversion writes is Opus. It is the right default by a wide margin — better sound per byte than Vorbis at every bitrate that matters, and specifically designed for speech, which is what a lecture is. It is also the answer that will surprise somebody whose requirement was written a decade ago, because for most of Ogg’s life "Ogg" meant Vorbis and some software still assumes it.
The accepted-formats list on a repository is frequently older than the software serving it, in both directions: a page that says "Ogg Vorbis" is often backed by a player that handles Opus perfectly, and a page that says "Ogg" is occasionally backed by one that does not. Neither can be resolved by reading.
So convert one short recording, upload it, and play it back through the destination’s own player rather than your own. Ten minutes spent on that at the start of a term is the difference between a working archive and eighty files that all need doing again. If Opus turns out not to be accepted, the conversion you need is to Vorbis, and that has to come from a desktop tool — nothing here writes it.
MP3, AAC, WAV and FLAC each hold exactly one soundtrack, so converting a multi-track MKV to any of them throws the rest away. The Ogg container has no such limit, and this conversion writes every audio track the browser can decode into the file rather than choosing one.
Treat that as storage rather than as a feature you can rely on. Multiplexed Ogg is legal and not much exercised, so whether a particular player offers you the second stream is a question about that player and worth testing before it matters. A lecture capture with a lectern microphone and a room microphone will contain both either way; if switching between them is the point, the M4A target is the one designed for it.
A capture from OBS or a merged download frequently carries Opus already, which makes it tempting to assume the stream is lifted across. It is not: every track is decoded back to samples and compressed again, so Opus to Opus costs a second generation.
On speech recorded in a hall this is genuinely inaudible, and for the volume of material a teaching archive produces the convenience is worth more than the difference. Where it is not — a recorded concert, a music seminar with performance in it — ffmpeg or a desktop remuxer will copy the existing Opus stream into an Ogg container in seconds with nothing changed at all.
The size that matters is not the size of the MKV. The picture is discarded rather than converted, and in a lecture recording the picture is nearly all of the file — a fixed camera on a speaker for ninety minutes compresses badly and stores enormously. What remains is an audio file whose size follows the quality band and the duration and nothing else.
Three bands are offered, defaulting to balanced. For a single voice in a room the small band is defensible and roughly halves the result; for a panel, a discussion or anything where several people talk across each other, balanced is worth its size. Opus is efficient enough that the difference between the two on a term of recordings is measured in tens of megabytes rather than gigabytes.
If a file stops with a message saying nothing in it could be converted, the browser could not decode the soundtrack and, with the picture already discarded, there was nothing left to write. The codecs involved are AC-3, E-AC-3, DTS and Dolby TrueHD.
A lecture capture will essentially never hit this, because capture software writes AAC or Opus. It is the disc-sourced Matroska file that fails — which is worth knowing if the archive you are publishing includes anything that came from a DVD of an older event. Those need their audio converted to AAC once by a desktop tool before anything here will read them.
The extension is a convention rather than a property. Xiph suggests .oga for audio in an Ogg container and .opus for Opus specifically, and most of the world carried on using .ogg for everything. If the upload form names .ogg, use .ogg; renaming a file changes nothing inside it and nothing here depends on the name.
The conversion itself happens inside the browser tab, on your own processor, with no account and nothing sent to a server. That matters for teaching recordings more than it does for most material: a lecture capture contains students’ voices, questions and sometimes names, and uploading it to a converter to get an audio file out is a data transfer somebody would have had to think about. Here there is nothing to think about, and the free tier takes files up to 100 MB.
| MKV | OGG | |
|---|---|---|
| Full name | Matroska Video | Ogg Audio |
| File extension | .mkv | .ogg, .oga |
| Media type | video/x-matroska | audio/ogg |
| Compression | Lossy — file size is bought with quality | Lossy — file size is bought with quality |
| First published | 2002 | 2000 |
| Published by | — | Xiph.Org |
| Specification | Matroska | RFC 3533 |
| Licensing | Open standard | Open standard |
| Standing today | Current | Current |
| Opens in a browser | Some browsers | Current browsers |
| Considered instead | MP4, WebM | MP3, AAC, OPUS |
OGG opens in current browsers, though not in older ones. MKV has narrower browser support than that. If the file is going onto a web page or into a form, that is usually the whole reason for the conversion.
OGG is a container rather than a single format. What actually plays is the codec inside it — usually Vorbis, Opus and FLAC — which is why two files with the same extension can behave differently on the same device.
VLC reads both MKV and OGG, so there is a way to check the result against the original without a second tool.
MKV was published in 2002. The specification is Matroska, and it is worth reading if the file has to outlive the tool that wrote it.
OGG comes from Xiph.Org and dates from 2000, specified as RFC 3533. Audacity, VLC and foobar2000 all read it.
No. This conversion runs entirely inside your browser, so the file never leaves your device. You can confirm it yourself: open the network tab of your browser's developer tools and convert something. You will see the page load, plus the analytics and advertising the site is paid for with — and nothing carrying your file. The engine behind this particular pair is mediabunny, a wrapper around WebCodecs, which borrows your device's own hardware decoders; your browser fetches it once and caches it.
Opus. Ogg is a container and Opus is what goes into it here, which is worth checking against your requirement — a specification written before 2012 that says "Ogg" almost certainly means Vorbis, and a system that only decodes Vorbis will not read this file even though the extension matches.
Upload one file and see. Modern repositories, browsers and Wikimedia-family projects all read Opus in Ogg; older institutional software and some embedded players do not. Testing a single short recording costs a minute and is the only reliable answer, because the accepted-formats list on a site is usually older than the software behind it.
The Ogg container has no one-track limit, and every audio track the browser can decode is written into the file — which is not true of MP3, AAC, WAV or FLAC. Whether a given player will offer you anything past the first stream is a question about the player, so test it before relying on it. If the alternate tracks are the point, the M4A target is the one built for that.
No. It is decoded and encoded again, so an Opus track going into an Ogg file costs a second generation of lossy compression. For a recorded lecture that is inaudible; for anything musical it is not nothing. A desktop remuxer will move the same stream across untouched in seconds if that matters.
Far smaller than the recording it came out of. Opus is unusually efficient on speech, and the size follows the quality band rather than the length of the video — the picture, which is most of the MKV, is discarded rather than converted, so a multi-gigabyte capture yields an audio file measured in tens of megabytes.
Convention rather than content. Xiph suggests .oga for audio in Ogg and .opus for Opus specifically, while .ogg remains what most software and most upload forms expect. If a repository names .ogg, use .ogg — renaming the file changes nothing inside it.