Initializing... drag & drop files here
Supports: MXF
MXF is the SMPTE broadcast container that Sony XDCAM, Panasonic P2, Canon XF, and ARRI cameras record to; MTS is the AVCHD file that Sony, Panasonic, and Canon HD camcorders write to their SD cards. This converter decodes your MXF essence and re-encodes it into an H.264 transport stream so it drops into an AVCHD-style camcorder or editor workflow — uploaded over an encrypted connection, processed on our servers, no sign-up and no watermark. Be honest with yourself about the target first: this is a rare, professional-to-consumer downconversion, and for general playback or sharing almost everyone is better served by converting MXF to MP4. Pick MTS only when a specific AVCHD device, importer, or disc-authoring tool insists on the .mts file.
| Property | Value |
|---|---|
| Full name | Material Exchange Format |
| Standard | SMPTE ST 377-1 (originally SMPTE 377M, 2004); application/mxf media type registered in RFC 4539 |
| Type | Professional broadcast / post-production container — a wrapper, not a codec |
| Operational patterns | OP1a (one self-contained file); OP-Atom (one file per track — Panasonic P2 and Avid) |
| Typical video essence | MPEG-2 Long-GOP (Sony XDCAM), AVC-Intra (Panasonic P2), DNxHD/DNxHR (Avid), XAVC / XF-AVC (H.264) |
| Audio | Uncompressed PCM, frequently several discrete mono tracks |
| Metadata / timecode | KLV-wrapped descriptive metadata plus SMPTE 12M timecode |
| Recorded by | Sony XDCAM, Panasonic P2, Canon XF, ARRI, Avid systems |
| Best for | Editing, archiving, broadcast exchange and playout |
| Property | Value |
|---|---|
| Full name | MPEG Transport Stream (AVCHD camcorder video) |
| Standard | AVCHD, introduced 2006 by Sony and Panasonic; later adopted by Canon and JVC |
| Container | MPEG transport stream (BDAV-style) |
| Video codec | MPEG-4 AVC / H.264 |
| Audio codec | Dolby Digital (AC-3) or Linear PCM per the AVCHD spec |
| Typical bitrate | Roughly 17–24 Mbps (AVCHD 1.0); up to 28 Mbps for progressive/3D modes (AVCHD 2.0) |
| Typical resolution | 1080i, 1080p, and 720p — up to 1920×1080 |
| Disc twin | .m2ts — the same stream, renamed when authored to a Blu-ray or AVCHD disc |
| Native playback | VLC, MPC-HC, and most non-linear editors; not most phones or browsers |
| Best for | Sony/Panasonic camcorder import paths, AVCHD-only editors, AVCHD disc authoring |
For almost everyone, MP4 is the right target — it plays on phones, browsers, smart TVs, and every editor, so convert MXF to MP4 unless you specifically need .mts. Choose MTS only when a tool or device expects AVCHD: some Sony and Panasonic camcorder import paths, certain AVCHD-only editors, or a Blu-ray/AVCHD disc-authoring workflow that ingests transport streams. MTS is a delivery-side format that tops out at 1080p, so it is a poor home for a 4K or high-bitrate broadcast master — keep those in MXF, or use MP4 for review copies.
The most likely cause is an OP-Atom MXF that holds only video. Broadcast workflows — Avid is the classic example — split each clip into separate companion files, one for video and one (or more) per audio track. If you upload the video-only file on its own, there is no audio stream to carry into the MTS, so the output is silent. Upload the matching audio MXF alongside it, or start from an OP1a (single-file) MXF that already muxes video and audio together.
It depends on the device, and audio is the usual sticking point. This converter produces H.264 video in a transport stream — which is the AVCHD video format — but it defaults the audio to AAC, while the AVCHD specification calls for Dolby AC-3 or Linear PCM. Many software editors and players accept AAC-in-TS without complaint, but a strict AVCHD camcorder re-import or disc authoring tool may reject it. If your target device is fussy, switch the Audio Codec to AC-3 before converting so the file matches the AVCHD audio spec.
Probably not as separate tracks. Broadcast MXF commonly carries several discrete mono channels — for example dialog, music, and effects on their own tracks. AVCHD/MTS is built around a single stereo or 5.1 program, so multiple mono tracks are typically folded down to one stereo mix rather than kept individually. If you need every track preserved for a mix, keep the file in MXF or convert MXF to MP4, which has broader multi-channel handling.
Some, because it is always a re-encode and MTS cannot recover detail. MXF essence such as XDCAM MPEG-2, AVC-Intra, or DNxHD has to be decoded and re-encoded into H.264 — there is no stream-copy or remux shortcut, since AVCHD requires H.264 in a transport stream. Keeping File Compression at the Very High preset holds the difference to something a normal 1080p display won't show. In our testing, a 50 Mbps XDCAM HD422 MXF re-encoded to an AVCHD-class H.264 MTS at roughly 24 Mbps came out about half the size and looked indistinguishable on a 1080p monitor — but a 4K master forced down to 1080p loses the extra resolution permanently.
Not reliably. Because the converter decodes and re-encodes the essence rather than copying it, the SMPTE 12M timecode track and the descriptive KLV metadata that MXF wraps around the video are not guaranteed to carry into the MTS. Basic timing such as frame rate is preserved, but frame-stamped timecode, ANC/caption data, and structured production metadata often are not. If your downstream workflow depends on them, keep the original MXF as the reference and re-apply that data in a dedicated broadcast tool.
They are the same transport stream with different file names. Camcorders write .mts into the AVCHD folder on the card; when that footage is authored onto a Blu-ray or AVCHD disc, the extension becomes .m2ts. If your device or authoring tool expects the disc form, the stream itself is identical — only the file name changes. For general playback neither one is ideal on phones or browsers, which is why MP4 remains the safer target for anything outside a dedicated AVCHD pipeline.
Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically a few hours after conversion — no sign-up, no watermark, never shared or made public. There is no file-count limit; the real constraint on a large master is upload size and connection speed, since MXF camera files can run to many gigabytes. If you need to bring an AVCHD clip back the other way into a broadcast container, use MTS to MXF.