Initializing... drag & drop files here
Supports: M2TS
.mts — the same AVCHD data with the camcorder-side extension. Batch is supported, so you can drop in a whole folder of camcorder clips and each one converts in parallel.M2TS is the container Blu-ray discs and AVCHD camcorders use to store high-definition video. Technically it is a modification of the MPEG-2 Transport Stream specification (ITU-T H.222.0 / ISO/IEC 13818-1) adapted for random-access media — the same scheme broadcasters use, repackaged so a disc or memory card can seek instantly. The AVCHD format that puts these files on Sony and Panasonic camcorders was announced jointly by the two companies in May 2006, and it wraps H.264/AVC video with Dolby AC-3 or uncompressed LPCM audio at up to 24 Mbit/s (28 Mbit/s for AVCHD Progressive).
The catch is that almost nothing outside a Blu-ray player or dedicated camcorder software opens an .m2ts file comfortably. The streams inside are modern and high quality, but the transport-stream wrapper is the wrong shape for general playback and editing. Converting re-encodes those streams into a container the target actually speaks. The common reasons people convert away from M2TS:
.m2ts. Converting to MP4 produces a file that plays essentially everywhere with no extra software.| Property | Value |
|---|---|
| Container | BDAV — a modification of MPEG-2 Transport Stream (ITU-T H.222.0 / ISO/IEC 13818-1) |
| Extensions | .m2ts (Blu-ray / after computer import), .mts (on the camcorder) |
| Video codecs | H.264/AVC (AVCHD); plus MPEG-2, VC-1, and H.265 on Blu-ray |
| Audio codecs | Dolby AC-3 and LPCM (AVCHD); plus DTS on Blu-ray |
| Typical bitrate | Up to 24 Mbit/s (AVCHD), up to 28 Mbit/s (AVCHD Progressive) |
| Typical resolution | 1080i / 1080p / 720p (AVCHD 1.0 and Progressive) |
| Introduced | AVCHD announced by Sony and Panasonic, May 2006 |
| Native support | Blu-ray players, VLC, MPC-HC, camcorder software; not most browsers or default OS players |
| Best converted to | MP4 (playback), MOV (Mac editing), MKV (archival), MP3 (audio) |
| Format | Container / codec | Best for | Native support |
|---|---|---|---|
| M2TS (source) | MPEG-2 TS wrapper, H.264 + AC-3 | Blu-ray discs, AVCHD camcorders | Blu-ray players, VLC, camcorder software |
| MP4 | MP4, H.264/H.265 + AAC | Playback and sharing everywhere | Every browser, phone, TV, editor |
| MOV | QuickTime, H.264 + AAC | Mac editing (Final Cut, iMovie) | macOS/iOS and most editors |
| MKV | Matroska, any codec | Multiple audio/subtitle tracks, media servers | VLC, Plex, Jellyfin (not most browsers) |
| WebM | WebM, VP9/AV1 | Royalty-free HTML5 web embeds | Chrome, Firefox, Edge, Safari 14+ |
| MP3 | MP3 audio only | Extracting just the sound | Every player |
Not bit-for-bit — xconvert always re-encodes the video; there is no stream-copy pass. But AVCHD M2TS files already contain H.264/AVC video, which is exactly what an MP4 carries natively, and the converter keeps the source codec family by default, encoding at a visually lossless preset (CRF 18 for H.264) — so the output is indistinguishable from the source in normal viewing. Changing the codec, resolution, bitrate, or quality preset moves you further from the source. LPCM audio is typically re-encoded to AAC for MP4 compatibility.
They are the same AVCHD data; only the extension differs by source. According to Sony, a camcorder writes the recording as .mts, and the file is renamed to .m2ts when it is imported to a computer (or when it lives on a Blu-ray disc). You can rename one to the other and it still plays. This converter accepts both, so it makes no difference which one you upload.
VLC and MPC-HC play .m2ts directly on Windows, macOS, and Linux, and dedicated camcorder software (Sony PlayMemories Home, Panasonic's tools) handles them. Blu-ray player software opens disc-sourced M2TS. What generally won't open them are mobile photo apps, web browsers, and the stock Windows and macOS players — which is the usual reason to convert to MP4.
For MP4 and MOV the picture is preserved for practical purposes, because both containers natively hold the H.264 already inside an AVCHD file, so the converter keeps that codec family by default and re-encodes at a visually lossless preset — the output is indistinguishable from the source in normal viewing rather than a bit-for-bit copy. You move further from the source only if you deliberately change the codec (H.265), downscale the resolution, or hit a Specific file size target. In our testing, a 60-second 1080p AVCHD clip converted to MP4 in a couple of seconds and looked identical to the source in side-by-side viewing.
For a Mac, convert to MOV — Final Cut Pro and iMovie import it without the transport-stream stumble. For Windows and cross-platform editors, MP4 is the safest import. If your editor still struggles with long-GOP H.264 during scrubbing, transcode to a higher-bitrate intermediate, but for most assembly and trimming a standard conversion to MP4 or MOV is enough. If you only need to extract audio from a recording, target M2TS to MP3 instead.
AVCHD's high bitrate makes clips bulky, so you have two levers. Switch the mode to Specific file size and enter a target in MB to let the encoder auto-tune the bitrate, or combine downscaling (1080p to 720p) with the H.265 codec, which is roughly 40-50% smaller than H.264 at equal quality. Trimming dead footage first is the highest-leverage step on long recordings. To shrink without changing format, the dedicated video compressor is the most direct route.
MP4 for almost everyone — it plays on phones, browsers, smart TVs, and every editor, and it natively carries the H.264 already inside an AVCHD file, so the conversion is clean. Choose MKV only when you want to keep several audio tracks or subtitle streams together in one file, typically for a Plex or Jellyfin library; MKV is more flexible but won't play in most browsers or the stock OS players. If you just need the footage to play and share, MP4 is the safe default, and MOV is the better pick if you're editing on a Mac.
Yes — conversion runs on our servers, not in your browser. Your file is uploaded over an encrypted (TLS) connection, processed, and then deleted automatically after a few hours. There's no sign-up and no watermark, and files are never shared or made public. The practical limit on a very large AVCHD recording is upload time and connection speed, not a fixed per-file cap.