Initializing... drag & drop files here
Supports: M2TS
M2TS is the transport stream that Blu-ray discs and AVCHD camcorders write — each 188-byte MPEG-2 transport packet carries an extra 4-byte header, giving the 192-byte BDAV packets stored in a BDMV/STREAM folder. MKV is Matroska, the open container the IETF published as RFC 9559 in October 2024. This tutorial covers the conversion itself and then the question everyone actually searches for — whether you can do it "without losing quality" — because the honest answer has a catch that changes which settings you should pick.
.m2ts clip onto the page or click "+ Add Files". Batch is supported, so a folder of camcorder clips can go through in one run with identical settings..mkv file. No sign-up, no watermark.Most people arrive at this conversion expecting a remux — lifting the H.264 video out of the transport stream and dropping it into Matroska untouched, byte for byte, in a few seconds. That is not what happens here. Our pipeline decodes and re-encodes the video on every conversion; there is no stream-copy path, even when the output codec is the same H.264 the source already used. The result is one generation removed from the original: at Very High the difference is hard to see, but the output can only match the source or fall slightly short, never improve on it.
That distinction changes how you should drive the settings:
| Source audio | Leave on AAC | Set to AC3 | Set to FLAC or PCM |
|---|---|---|---|
| Dolby Digital (AC-3), 64–640 kbit/s | Lossy to lossy — a second generation | Stays in the Dolby family; MKV carries it natively | Bit-exact copy of the decoded audio; large files, no fidelity recovered |
| Linear PCM (AVCHD pro models, Blu-ray) | Clean single-generation encode, small file | Unnecessary detour | The right choice — keeps the master lossless |
| DTS / Dolby Digital Plus (Blu-ray) | Lossy to lossy from a higher rate | Re-encoded into AC-3 | Large but stable for archiving |
| 5.1 surround, any codec | Carries up to 8 channels | Carries 5.1 | Carries multichannel |
| Property | M2TS (BDAV transport stream) | MKV (Matroska) |
|---|---|---|
| Standardised by | Blu-ray Disc Association / ITU-T H.222.0 systems layer | IETF, RFC 9559 (October 2024) |
| Packet structure | 192-byte packets: 188-byte TS packet plus a 4-byte header | Variable-length EBML elements |
| Designed for | Broadcast and disc playback, error resilience | File storage, archiving, streaming servers |
| Depends on sidecar files | Yes — playlist and clip-info files hold the disc structure | No, a single self-contained file |
| Multiple audio tracks and subtitles | Supported on disc, spread across the folder tree | Supported inside the one file |
| Typical players | Blu-ray players, VLC, media-centre software | VLC, mpv, Kodi, Plex, Jellyfin, most editors |
| Awkward part | A lone .m2ts outside its folder loses menus and chapters |
Some smart TVs and older hardware won't open it |
The hard stop is copy protection: retail Blu-ray discs are encrypted with AACS and frequently BD+, and an encrypted stream cannot be decoded by a conversion tool. This page works on M2TS files you can already open — your own AVCHD footage, unprotected recordings, or discs decrypted separately with software you own. Two softer failure modes are worth knowing. A clip copied off a camera card mid-write can have a damaged stream index that scrubs partially in a player but fails to convert cleanly; re-copy it from the source. And camcorders that split a long recording into sequential clips give you several files that need joining in a video editor first — converting them one at a time produces several MKVs, not one continuous archive. If your files carry the camcorder spelling, MTS to MKV is the identical conversion, and the M2TS converter hub lists the other output formats this footage can go to.
A re-encode. Our pipeline decodes the video and encodes it again on every conversion, so even an H.264 source going to an H.264 MKV is one generation removed from the original rather than a byte-for-byte copy. At the Very High preset that generation is very hard to spot in normal viewing. If you need the original bitstream preserved exactly, use a stream-copy remuxer such as MKVToolNix instead — that is a different operation from what any transcoding service does.
By default it becomes AAC, which is a second lossy generation. Setting Audio Codec to AC3 avoids the codec change and keeps a Dolby track in Dolby form, including its 5.1 channel layout, which Matroska carries natively and VLC, Kodi and Plex all decode. DTS is also selectable, as are FLAC and the PCM variants if you want the audio stored losslessly — worth it when the source was Linear PCM, less useful when it was already compressed.
Matroska itself supports chapters, multiple audio tracks and soft subtitles — that is much of why it is the archival favourite. What survives depends on the source, and a lone .m2ts clip is a weak starting point: on a disc the chapter marks and playlist structure live in sidecar files next to the stream rather than inside it, so converting one clip in isolation cannot recover them. A single AVCHD camcorder clip normally has one audio track and no subtitles anyway. The advantage of MKV is headroom — you can add subtitle or audio tracks to the archived file later without converting it again.
Because a .m2ts is only half a file in practice. It expects the BDMV/AVCHD folder tree around it — playlist and clip-info sidecars that many backup routines quietly drop — and plenty of editors and players refuse the bare stream. One self-contained .mkv per clip is easy to name, store, verify and migrate, and Matroska is a published open specification rather than a disc-authoring convention.
H.264 is the default and the safest answer: it is what the camcorder recorded, so the encoder is working with material its own compression model suits, and every player handles it. Choose H.265 when storage matters more than compatibility — it typically reaches similar quality at a lower bitrate, at the cost of slower encoding and patchier support on older hardware. The legacy options in the list (MPEG-2, MPEG-4, Xvid, WMV) exist for specific device targets and will produce larger files at lower quality.
No. No deinterlacing is performed anywhere in the pipeline, so if the source fields were combed the output keeps them combed. That is fine for archiving, since the field information is preserved rather than guessed at, and a player or editor can deinterlace on playback. If you need progressive frames baked in, deinterlace in a desktop editor before or after this conversion.
Choose MKV for archiving, media servers such as Plex and Jellyfin, multiple audio tracks and subtitles. Choose M2TS to MP4 for phones, smart TVs, browsers and social uploads, where MP4 support is close to universal and MKV is hit-and-miss. Both wrap the same re-encoded H.264 video, so the decision is entirely about where the file has to play.
It is uploaded over an encrypted connection, processed on our servers and deleted automatically after a few hours along with the MKV — no sign-up, no watermark, never shared or made public. The practical constraint is upload size and time rather than the conversion: Blu-ray-rate M2TS files are large, so trimming first keeps the transfer manageable.