OGV to M2TS Converter

OGV to M2TS — Which Transport Stream Do You Actually Need?

M2TS is the BDAV MPEG-2 transport stream: the container Blu-ray Disc, Ultra HD Blu-ray and imported AVCHD footage are stored in. OGV is Xiph.Org's Ogg container carrying video, usually Theora or VP8 with a Vorbis track — the format Wikimedia Commons, old HTML5 fallback paths and Linux screen recorders left behind in large numbers.

Converting between them re-encodes everything, which is straightforward. What is not straightforward is choosing between the three transport-stream spellings this site offers, because they are not interchangeable and the extension decides the packet layout. Start with the comparison below, then read the audio question, which is where this conversion usually goes wrong.

TS, MTS and M2TS Compared

We wrote the same encode out under each extension and read the first bytes back: only the .m2ts file carries the BDAV header. That is not cosmetic and it is not something a rename can fix — the framing is chosen when the file is written, so pick the page whose output matches what the receiving tool checks for.

How to Convert OGV to M2TS

1. Upload Your OGV File: Drag the .ogv onto the page or click "+ Add Files" to browse. Several files can be queued and each is converted with the same settings.
2. Set the Video Codec: H.264 is what the list opens on and is the codec Blu-ray and AVCHD hardware expects. H.265, MPEG-1, MPEG-2, MPEG-4, DivX and Xvid are also selectable, but of those only MPEG-2 belongs to the classic Blu-ray video set and only H.265 belongs to the Ultra HD one.
3. Choose the Audio Codec and a Compression Mode: Audio Codec opens on AAC, which software players read but disc-oriented hardware does not expect — switch it to AC3 if hardware is involved. DTS (DCA), EAC3, MP2 and MP3 are the other entries. Under File Compression, Quality Preset opens at "Very High (Recommended)", with Specific file size, Constant Bitrate, Variable Bitrate, Constant Quality and Constraint Quality alongside it. Video resolution opens on "Keep original" and Trim takes a Start time and Duration.
4. Convert and Download: Click Convert and save the .m2ts. Files upload over an encrypted connection, are converted on our servers and are deleted automatically after a few hours — no sign-up, no watermark, never shared or made public.

Matching Your Settings to the Target

The rule of thumb is H.264 plus AC3 whenever hardware is in the chain. AAC is smaller and every software player decodes it, which is why it is the value the page opens on, but it sits outside the audio set BDAV and AVCHD players are required to handle — and that is the single most common reason a converted file plays with picture and no sound on a television.

A Stream Is Not a Disc

The .m2ts you download is genuinely BDAV-framed, which is what most people checking this conversion want to confirm. What it is not is a disc. An authored Blu-ray or AVCHD volume is a folder structure — BDMV containing a STREAM directory for the media, alongside clip-information and playlist files, plus index and menu data a set-top player navigates. Nothing inside a single file can supply any of that.

The practical result is that a player which happily reads a USB stick full of video may still ignore an .m2ts dropped onto it, and a Blu-ray deck almost certainly will. Feed the file to authoring software when you want a disc; use it directly when the target is a PC, a media player, or an editor that ingests transport streams. If you only wanted something that plays, OGV to MP4 is a smaller file with far wider support.

Frequently Asked Questions

Is this a real BDAV M2TS, or just a renamed transport stream?

It is really BDAV-framed. The file is written with 192-byte packets — a standard 188-byte MPEG-2 transport packet behind a 4-byte header carrying a copy-permission indicator and a 27 MHz arrival timestamp — so the sync byte sits at offset 4 rather than offset 0. We compared the first bytes of this page's output against the plain-TS pages and only the .m2ts file carries the prefix. Open it in a stream analyser and it will report the BDAV packet size rather than the broadcast one.

Can I just rename a .ts or .mts file to .m2ts instead?

No — that gets you a file whose name claims BDAV framing and whose bytes do not have it. The packet layout is decided when the file is written, not by the extension it is later given, so renaming relabels the file without re-framing it. Anything that validates packet size will reject it. If your tool wants BDAV, convert on this page; if it wants the plain broadcast layout, use OGV to TS or OGV to MTS and keep that extension.

Why does my TV show picture but no sound?

Because the hardware cannot decode AAC inside a transport stream. The BDAV and AVCHD specifications treat Dolby Digital (AC-3), DTS and linear PCM as the audio formats players must handle; AAC is not in that set. It is the value this page opens on because it is compact and every software player reads it, which is the right default for a computer-bound file and the wrong one for a television. Re-convert with Audio Codec set to AC3 and the sound comes back.

Why won't my Blu-ray player or games console play the file?

Because a stream is not a disc. Authored Blu-ray and AVCHD playback depends on a BDMV folder structure with a STREAM directory, clip-information files and playlists that tell the player what titles exist and how to play them; a single loose file carries none of it. Some devices read standalone .m2ts from USB and many flatly refuse. If you need real disc playback, run this file through authoring software that builds the folder structure around it.

What happens to the Vorbis or Opus audio from my OGV?

It is decoded and re-encoded into whatever you selected — a transport stream has no place for a Vorbis or Opus track, and nothing here copies streams through untouched. That means a second generation of lossy encoding on a soundtrack that was already lossy, so if the audio matters, keep the original .ogv. It also means an .ogv with no audio track at all, which is common with screen recordings and some Wikimedia material, produces a silent .m2ts; there is nothing on this page that can add sound the source never had.

Will converting from Theora or VP8 to H.264 hurt the picture?

There is always some loss, because this is a full decode and re-encode rather than a rewrap. The direction of travel helps, though: H.264 is a more efficient codec than either Theora or VP8, so it can hold the same picture in fewer bits. Keeping Quality Preset at "Very High (Recommended)" and leaving the resolution on "Keep original" limits the damage to a single generation. Dropping to a low preset or a tight Specific file size target is where softening becomes visible, particularly on grain and fast motion.

Does M2TS handle 1080p and 4K?

The container was built for high definition and 1080p is comfortably within scope. 4K is real too — Ultra HD Blu-ray stores 3840x2160 HEVC video in the same BDAV container at data rates well above standard Blu-ray — but that depends on your target decoding HEVC at that resolution, and H.264 at 4K is not part of the classic Blu-ray video set. In practice, whether a standalone 4K .m2ts plays is entirely a question of what the receiving hardware supports. Most .ogv sources are well below either resolution anyway, and upscaling them adds size without adding detail.

Can this fix interlacing or convert HDR while it re-encodes?

No, and neither is a setting you have overlooked. There is no deinterlacing filter in this pipeline, so interlaced source material keeps its combing baked into the encoded frames. There is no HDR tone-mapping stage either, so high-dynamic-range footage is colour-converted plainly and can look washed out on a standard-range display. Both belong in a desktop tool before you upload.

How are my files handled after conversion?

Your .ogv is uploaded over an encrypted connection, transcoded on our servers, and the files are deleted automatically a few hours afterwards — no sign-up, no watermark, never shared or made public. Transport-stream conversions of long video are large jobs, so the practical constraint is upload size and time rather than anything on your own machine; trimming the source first with the video cutter shortens both halves.