Initializing... drag & drop files here
Supports: MKV
.MTS is the name AVCHD camcorders write to their memory cards — Sony and Panasonic introduced the format in 2006, and its 8.3 filename convention is why the extension is three letters rather than four. Converting a Matroska file to MTS produces the MPEG transport stream those workflows are built around, under the name they expect. This is a re-encode rather than a rewrap, and there are two things worth being precise about before you start: what the file we write actually is, and what an AVCHD device expects it to be. They are not quite the same thing.
.mkv onto the page or click "+ Add Files". Several clips can be queued and converted with one set of settings..mts. No sign-up, no watermark.In the AVCHD world these two extensions describe the same recording at different points in its life: camcorders write .MTS to the card using legacy 8.3 filenames, and importing to a computer produces the long-filename .m2ts. The underlying content is the same transport stream. Where it stops being a pure naming question is packet framing — Blu-ray's BDAV variant prefixes every 188-byte transport packet with a 4-byte header, and our two output paths differ on exactly that point.
| MTS (this page) | M2TS (that page) | |
|---|---|---|
| Where the name comes from | AVCHD camcorder memory cards, 8.3 filenames | Blu-ray discs and computer imports |
| Packet framing we write | Plain 188-byte transport packets, sync byte 0x47 |
BDAV framing — 192 bytes, a 4-byte header then the 188-byte packet |
| Base standard | MPEG-2 transport stream (ITU-T H.222.0 / ISO/IEC 13818-1) | The same, modified for random-access media |
| Video codec here | H.264 by default | H.264 by default |
| Audio codec here | AAC by default | AAC by default |
| Choose it when | Something asks for .mts, or a tool wants a plain transport stream |
Something expects Blu-ray-style BDAV framing |
If you are unsure which the receiving software wants, the extension it advertises is the best clue — and since neither output is a disc, you can convert to the other and compare without losing anything.
| Property | MKV (Matroska) | MTS (AVCHD transport stream) |
|---|---|---|
| Container | Matroska — open and codec-agnostic | MPEG transport stream |
| Video codec | Anything: H.264, HEVC, VP9, AV1 and more | H.264/MPEG-4 AVC in the AVCHD spec |
| Audio | Anything: AAC, AC-3, FLAC, Opus, DTS | Dolby Digital (AC-3), or linear PCM on some professional models |
| Multiple audio and subtitle tracks | Yes, effectively unlimited | Not carried through this conversion |
| Chapters and attachments | Yes | No |
| Developed by | The open Matroska project | Sony and Panasonic, 2006 |
| Best for | Archiving, any-codec storage, subtitles | Camcorder footage, AVCHD players, disc-authoring input |
| Native browser playback | No | No |
AVCHD is a tighter specification than Matroska in every direction, and three of its constraints are worth knowing. Video is H.264/MPEG-4 AVC — that is not a preference, it is the format. Audio is Dolby Digital (AC-3), running from 64 to 640 kbit/s in stereo or multichannel, with uncompressed linear PCM permitted on some professional models at up to 7.1 channels; AAC is not part of that set, which is why our AAC default plays fine on a computer but can produce silence on a TV or a camcorder-oriented player. And the bitrate ceiling is roughly 24 Mbit/s, rising to about 28 Mbit/s for AVCHD Progressive, so there is no point requesting a rate above that if a strict player is on the other end.
The last constraint is structural rather than technical. AVCHD footage lives inside a BDMV directory alongside index and playlist files; a single .mts file lifted out of that structure is the raw footage, not the recording the camcorder navigates. Copying one back onto a card rarely makes a camera or player recognise it.
.mts is not an AVCHD volume. Without the BDMV folder structure and its index and playlist files, most devices ignore it. Import the file into editing or authoring software instead.MTS is a narrow target and it is worth being honest about when it is the wrong one. If you simply want the video to play — on a phone, a browser, a smart TV app, a messaging thread — MKV to MP4 is smaller, better supported and less trouble in every respect. If your goal is a finished AVCHD or Blu-ray disc, you need authoring software: this page produces the stream that software ingests, not the folder structure it builds. If the receiving tool specifically wants Blu-ray-style BDAV framing, use MKV to M2TS instead. And DRM-protected or truncated sources cannot be converted here at all — repair or re-export them in a desktop tool first.
In the AVCHD world, yes — camcorders write .MTS to the memory card using legacy 8.3 filenames, and the same recording becomes .m2ts when imported to a computer. On this site there is one concrete difference: the .mts output is written as plain 188-byte transport packets, while MKV to M2TS writes the Blu-ray BDAV variant, which prefixes each of those packets with a 4-byte header for a 192-byte unit. Pick the one your receiving software expects rather than assuming the extension is cosmetic.
AC3 if anything resembling AVCHD hardware is involved. Dolby Digital is the audio format the specification is built around — 64 to 640 kbit/s, stereo or multichannel — with linear PCM allowed on some professional models for up to 7.1 channels. AAC is our default because it is compact and universally decoded by software, but it is outside the AVCHD audio set, and "picture plays, no sound" on a TV is almost always this exact mismatch.
No. What you get is one video stream, not a volume. A complete AVCHD or Blu-ray structure is a BDMV directory holding the media alongside index, clip-information and playlist files that tell a player how to navigate the recording. Authoring software builds that around your clips. Treat the .mts from this page as the footage you feed into that project, or into your editor.
Some — this is always a re-encode, never a lossless rewrap, so the video is decoded and compressed again for one generation of loss. Leaving "Quality Preset" on "Very High (Recommended)" and "Video resolution" on "Keep original" keeps that close to invisible on typical 1080p footage. Bear in mind too that AVCHD tops out around 24 Mbit/s, or about 28 Mbit/s for AVCHD Progressive, so a strict player will not benefit from anything you encode above that.
Because transport streams were designed for broadcast and disc hardware rather than general-purpose playback. VLC and most full desktop players handle .mts without complaint; browsers, phones and lightweight players frequently do not, and some refuse the extension outright regardless of what is inside. If you need something that opens anywhere, MKV to MP4 gives you the same H.264 video in a container nothing rejects.
They do not survive. Matroska is unusually generous about extra tracks — many languages, many subtitle formats, chapters, attachments and metadata — and the transport stream written here carries one video stream and one audio stream. Choose the audio track you want before converting, burn subtitles into the picture if they need to be visible, and keep the original MKV as the copy that still holds everything else.
Yes, but not through the preset list. The "Preset" values under "Video resolution" set a height and let the width follow your source's aspect ratio, so a preset alone will not guarantee an exact pixel pair. Use "Width x Height" when a specific frame size is required. Note that there is no pixel-aspect correction here either, so anamorphic or non-square-pixel sources should be given explicit width and height values rather than left to scale on their own.
No. There is no deinterlacing filter anywhere in the pipeline, so interlaced source material — which is common in AVCHD-era recordings — keeps its comb lines baked into the encoded frames. If your footage is interlaced and you want progressive output, deinterlace it in a desktop tool such as HandBrake before uploading, then convert the cleaned-up file here.
Your MKV is uploaded over an encrypted connection, transcoded on our servers, and the files are deleted automatically a few hours later. There is no sign-up, no watermark, and nothing is shared or made public. Full-length camcorder footage is large, so the practical constraint is upload size and time rather than the conversion itself; trimming the source with the video cutter first shortens the wait considerably.