Initializing... drag & drop files here
Supports: OGV
.ogv is the video profile of Xiph.Org's Ogg container, the extension RFC 5334 assigns to the video/ogg media type, and the picture inside is almost always Theora with a Vorbis soundtrack. .mkv is Matroska, an open, EBML-based container specified in RFC 9559 as of October 2024. Converting between them is a container and codec migration: Matroska imposes no codec of its own, so the practical question on this page is not "MKV or not" but "which codecs go inside the MKV."
That matters more than it used to, because browsers have retired the Theora decoder. An .ogv from the open-web era is now a file most software will open only through VLC, MPV, or FFmpeg. Re-encoding it into Matroska with H.264 video and AAC audio gives you a copy that current players, media servers, and archival tooling handle without a special decoder.
| Property | Value |
|---|---|
| Container | Ogg (Xiph.Org) |
| Extension defined by | RFC 5334, .ogv = video/ogg |
| Usual video codec | Theora — bitstream frozen 2004, 1.0 released 3 November 2008 |
| Theora lineage | Derived directly from On2's VP3, under an irrevocable free licence from On2 |
| Usual audio codec | Vorbis (Opus, Speex and FLAC also occur in Ogg) |
| Compression | Lossy video, lossy audio |
| Licensing | Royalty-free, patent-unencumbered |
| Native browser support | Withdrawn — see the browser table below |
| Typically found in | Wikimedia Commons downloads, early HTML5 <video> pages, Linux screen recorders |
| Property | Value |
|---|---|
| Container | Matroska, built on EBML (RFC 8794) |
| Specification | RFC 9559, Standards Track, October 2024 |
| Codec policy | Codec-agnostic — the container carries whatever you put in it |
| Our default payload | H.264 video + AAC audio |
| Carries | Multiple video, audio and subtitle tracks, chapters, tags, attachments |
| Notable features | Fast seeking, error resilience, streamable, modularly expandable |
| Compression | None of its own; determined entirely by the codecs inside |
| Best for | Archiving a source with its metadata intact, multi-track and multi-subtitle files, media-server libraries |
.ogv onto the page or click "Add Files" to browse. You can queue several clips and convert them all on the same settings..mkv. No sign-up, no watermark.The Video Codec dropdown on this page lists 21 encoders and the Audio Codec dropdown lists 24. Matroska is genuinely permissive, but the dropdowns are wider than the set our pipeline treats as container-native, and an explicit codec choice is passed straight to the encoder rather than being re-checked against the output container. Practically: stay on the list below and the file will mux cleanly.
| Goal | Video Codec | Audio Codec | Why |
|---|---|---|---|
| Play anywhere, including hardware players | H.264 | AAC | The default. Decoded by essentially every player and TV shipped in the last decade. |
| Smallest file at the same quality | H.265 or VP9 | AAC or Opus | Both are far more efficient than the source Theora, so the MKV can be smaller than the .ogv. |
| Keep the soundtrack from a second lossy pass | H.264 | FLAC | Matroska carries FLAC natively, so the decoded audio is stored losslessly. The video re-encode still applies. |
| Stay in the open-codec family | VP9 or AV1 | Opus or Vorbis | Royalty-free end to end, the same rationale that produced the .ogv in the first place. |
| Preserve the original picture bit-for-bit | Not possible here | — | Our server always re-encodes; there is no stream-copy path, so every conversion costs one lossy generation on the video. |
On H.264 the Quality Preset resolves to a CRF value — Highest 17, Very High 18, High 20, Medium 23, Low 26, Very Low 28, Lowest 32 at a 1080p reference — then shifts by one step per doubling or halving of the pixel count, clamped to plus or minus two. That is why a 480p Theora clip at "Very High" is encoded a little more conservatively than a 1080p one at the same setting.
No, and nothing can. Theora is a lossy codec, so the .ogv has already discarded detail permanently, and our server re-encodes rather than stream-copying — that is a second lossy generation on top. A high preset keeps the result close to the source; it cannot rebuild what Theora threw away. The honest framing is that you are rescuing footage into a durable container, not restoring it.
.ogv?Because Matroska is the better archival envelope. RFC 9559 gives it a published, Standards Track specification, and one file can hold several audio tracks, subtitle tracks, chapters, tags and attachments alongside the video. MP4 is the better distribution envelope — OGV to MP4 is what you want for phones, browsers and social platforms. Pick MKV when the file is going into a library or a long-term archive.
It is genuinely specified. Matroska is built on EBML, itself standardised as RFC 8794, and the container format was published by the IETF as RFC 9559 on the Standards Track in October 2024. Before that it existed as a long-running community specification at matroska.org. Either way it has never been a vendor-controlled format, which is what makes it a sensible destination for open-format material like Ogg Theora.
.ogv has Vorbis audio — does that survive?Not as Vorbis, unless you ask for it. The default writes AAC, which means the Vorbis track is decoded and re-encoded — a second lossy pass on the audio. Two ways out: set Audio Codec to Vorbis to stay in the same codec family, or set it to FLAC so the decoded audio is stored losslessly from here on. FLAC will make the file larger; on speech and web-quality music the AAC default is usually inaudible.
Usually because a high-bitrate or lossless selection is in play — HuffYUV video or PCM audio will inflate a file dramatically — or because the source Theora was encoded at a very low bitrate that H.264 at a high preset simply exceeds. Drop the Quality Preset a notch, or switch to Specific file size and name the size you want.
Matroska does carry Theora, and it is in the Video Codec dropdown, but selecting it does not avoid a re-encode — our server decodes and re-encodes on every conversion, so choosing Theora means Theora-to-Theora, a lossy generation for no compatibility gain. If the goal is to stay on royalty-free codecs, VP9 or AV1 is the better choice: same open licensing, far better efficiency, and current players decode both.
.ogv files, and does that affect this conversion?Playback support has been withdrawn, but decoding is unaffected. caniuse records Chrome disabling Theora by default from version 120 and removing it in 123, Edge from 122, Opera from 106, and Firefox disabling it by default in version 126; Safari never supported it. Standalone decoders in FFmpeg and VLC still read Theora perfectly, which is how your source file is read here. The MKV you get back has no Theora dependency at all.
There is nothing to carry over from a typical .ogv. Ogg can technically transport timed text via Kate or CMML, but almost no real-world .ogv file uses it, so the practical answer is that you get a clean video and audio track. Matroska's subtitle and chapter support is why you would archive into MKV: you can add those tracks later with a Matroska tool without re-encoding the video again.
Your .ogv is uploaded over an encrypted connection, decoded and re-encoded on our servers, and both the upload and the finished .mkv are deleted automatically after a few hours. There is no sign-up, no watermark, and files are never shared or made public. For the reverse direction see MKV to OGV, and for other targets from the same source, the OGV converter hub lists them all.