Initializing... drag & drop files here
Supports: MOV
.mov is Apple's QuickTime container — what iPhones, DSLRs and macOS screen recorders write. .m2ts is the BDAV MPEG-2 Transport Stream used by Blu-ray discs and AVCHD camcorders, and it exists for a completely different reason: it is a broadcast-style stream designed to be played back from a disc or a card in a fixed-function device, not a file designed to be copied around. This page re-encodes a MOV into that stream format, and the rest of the page is about the difference between "an .m2ts file" and "an AVCHD- or Blu-ray-compliant stream", because they are not the same thing.
| Property | Value |
|---|---|
| Full name | BDAV MPEG-2 Transport Stream |
| Defined by | The Blu-ray Disc Association; the AVCHD variant by the AVCHD Format Co-Promoters, from 2006 |
| Packet layout | 192 bytes per packet — a 4-byte arrival-timestamp prefix followed by a standard 188-byte transport packet |
| System format | MPEG-2 Transport Stream |
| Video codec (AVCHD spec) | MPEG-4 AVC/H.264, or MPEG-4 MVC/H.264 for stereoscopic |
| Audio codec (AVCHD spec) | Dolby Digital AC-3 at 64–640 kbps, or Linear PCM at 1.5 Mbps stereo |
| Bitrate ceiling (AVCHD spec) | ≤24 Mbps, or ≤18 Mbps when the target media is a DVD |
| Where you normally find it | BDMV/STREAM/ on a Blu-ray, and on AVCHD camcorder media, where the same streams are usually named .MTS |
| Our video default here | H.264 — AVCHD-compliant |
| Our audio default here | AAC — not an AVCHD or Blu-ray audio codec; switch to AC3 |
| Native browser support | None. .m2ts is a disc and device format, not a web format |
We checked the bytes our converter writes: the .m2ts output really is BDAV-framed, with 192-byte packets and the sync byte sitting at offset 4 behind the timestamp prefix, rather than the plain 188-byte packets that a generic .ts file carries. That framing follows the output extension, which is why MOV to TS and MOV to MTS produce plain transport packets from the same source.
.mov onto the page or click "+ Add Files". Several clips can be queued and converted in one batch with the same settings..m2ts but not a compliant one.| Setting | What this page opens with | What the AVCHD specification calls for | Action |
|---|---|---|---|
| Video codec | H.264 | MPEG-4 AVC/H.264 | Leave it alone |
| Audio codec | AAC | Dolby Digital AC-3 (64–640 kbps) or Linear PCM | Change to AC3 |
| Video bitrate | Derived from the Quality Preset | ≤24 Mbps (≤18 Mbps for DVD media) | Use Constant or Variable Bitrate and cap it |
| Packet framing | 192-byte BDAV packets | 192-byte BDAV packets | Already correct for .m2ts |
| Container structure | One standalone stream file | BDMV folder tree with clip info and playlists |
Build it in an authoring tool |
The audio row is the one that catches people. An .m2ts with AAC inside will play in VLC, in most PC software and on a lot of smart TVs, and will be rejected outright by disc-authoring software and by camcorder-facing tools that validate against the spec. If your next step is a piece of software that says "AVCHD" or "Blu-ray" anywhere in its documentation, set AC3 before you convert rather than re-encoding twice.
It is not a disc. A Blu-ray or AVCHD volume is a directory structure — a BDMV root containing STREAM for the .m2ts payload, CLIPINF for the per-clip .clpi metadata, and PLAYLIST for the .mpls playlists that tell a player what order to present things in. Our output is the stream file only. Authoring software (multiAVCHD, tsMuxeR, DVDStyler-class tools, or your camcorder's own utility) takes that stream and generates the surrounding structure; you cannot create it by copying a file into a folder and renaming things.
It is also not a rewrap. Even when your MOV already contains H.264 at a compliant bitrate, this conversion decodes and re-encodes the video rather than copying the stream through, so plan the quality settings accordingly. And two source-side behaviours carry over unchanged: interlaced camcorder footage is not deinterlaced, and HDR footage from a recent iPhone gets a plain colour conversion with no tone-mapping, which typically looks flat or washed out. Export an SDR version upstream if colour accuracy matters.
It is genuinely BDAV-framed. Each packet is 192 bytes — the 4-byte arrival-timestamp prefix that BDAV adds, then the 188-byte MPEG-2 transport packet — which is the actual structural difference between .m2ts and a plain .ts. What makes it non-compliant out of the box is the audio codec, not the framing.
No. A disc needs the BDMV structure — STREAM, CLIPINF and PLAYLIST — and a camcorder card needs its own index files, none of which a single stream file contains. Convert here to get a compliant stream, then feed that stream to authoring software, which builds the folder tree and the playlists around it.
AC3 for anything that will be validated against the AVCHD or Blu-ray specification; the official AVCHD format allows Dolby Digital AC-3 between 64 and 640 kbps, or Linear PCM at 1.5 Mbps for stereo. AAC — this page's default — is not in that list, even though it plays fine in software players. DTS and E-AC-3 appear in the dropdown and exist in the wider Blu-ray world but are not part of the AVCHD audio set.
.m2ts and .MTS hold the same BDAV stream; AVCHD camcorders write .MTS on their own media and the files usually become .m2ts once imported to a computer. .ts is the plain broadcast transport stream with 188-byte packets and no arrival-timestamp prefix. Our converter follows the extension you pick: .m2ts gets the 192-byte BDAV framing, while .ts and .mts get plain 188-byte packets, so choose based on what the receiving system expects.
Transport streams carry overhead a file container does not: every 188 bytes of payload gets a header, .m2ts adds four more bytes per packet on top, and the program tables are repeated continuously so a player can join the stream at any point. Add the fact that the default Quality Preset targets a generous bitrate and a modest size increase is normal. Cap it with Constant Bitrate if the exact number matters — which for AVCHD work it does.
H.264, the default. It is the codec the AVCHD specification mandates, it is what Blu-ray players and camcorder-facing software expect, and it is what your MOV most likely already contains. H.265 will produce a smaller file that a strict AVCHD tool will refuse; MPEG-2 is the older Blu-ray-era option and much less efficient; MPEG-4, Xvid and DivX inside a transport stream are unusual enough that support is unpredictable.
Software players handle it easily — VLC, MPC-HC and anything ffmpeg-based read .m2ts including the AAC variant. Hardware is stricter and varies: many smart TVs and consoles play .m2ts from USB, but the ones that reject it usually reject it because of the audio codec rather than the container. If a device refuses the file, re-converting with AC3 audio is the first thing to try.
No — the video is decoded and re-encoded every time, so there is always a generation of loss even when the input and output codecs match. Set Quality Preset to Highest, or use Constant Bitrate near the source's own rate, if you want that loss to be negligible. If you need to shorten the clip as part of the same job, use Trim with a start time and duration rather than converting and then cutting.
It is uploaded over an encrypted connection, converted on our servers, and deleted automatically after a few hours. Nothing is shared, published or made searchable, there is no sign-up, and no watermark is added to the output.