Convert M2TS to MXF — Free Online Tool
Convert M2TS Blu-ray and AVCHD files to MXF for professional broadcast and post-production workflows. This tool re-encodes the video using H.264 and transcodes the audio to uncompressed PCM — the standard lossless audio format required by most broadcast and NLE ingest pipelines.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your M2TS file here
or click to browse
Free — no uploads, no signups. Your files never leave your browser.
Settings
Note: Browser-based encoding uses approximate quality targets. For precise CRF compression, copy the FFmpeg command above and run it on your desktop.
Estimated output:
Conversion Complete!
DownloadHow It Works
M2TS carries video (typically H.264 or MPEG-2) and audio (often AC-3, DTS, or AAC) inside a BDAV MPEG-2 Transport Stream wrapper designed for Blu-ray and AVCHD camcorders. MXF, by contrast, is a professional wrapper built for broadcast ingest, timecode support, and rich metadata embedding. Because the two containers have fundamentally different internal structures and metadata models, a straight remux is not possible — the file must be fully re-encoded. The video stream is encoded to H.264 using libx264 at CRF 23 (a visually near-transparent quality level), while the audio — which may have been compressed AC-3 or DTS in the source — is decoded and re-encoded as 16-bit PCM (pcm_s16le) at 192k, producing uncompressed broadcast-ready audio. Subtitle tracks present in the M2TS are not carried into MXF, as the output format does not support embedded subtitles.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg media processing tool. In the browser-based version of this tool, FFmpeg runs entirely via WebAssembly (FFmpeg.wasm) with no server upload; the same command can be run locally on your desktop with a standard FFmpeg installation. |
-i input.m2ts
|
Specifies the input file — in this case an M2TS file, the BDAV MPEG-2 Transport Stream container used by Blu-ray discs and AVCHD camcorders. FFmpeg will automatically detect and demux the video, audio, and subtitle streams contained within. |
-c:v libx264
|
Encodes the output video stream using the libx264 H.264 encoder. Since MXF does not share the same internal stream structure as M2TS, the video must be fully re-encoded rather than copied, and H.264 is the most widely compatible professional codec for MXF in broadcast environments. |
-c:a pcm_s16le
|
Transcodes the audio to 16-bit little-endian uncompressed PCM — the broadcast-standard audio format for MXF. This decodes whatever compressed audio was in the M2TS (typically AC-3 or DTS) and outputs it as fully uncompressed audio, which is required by most professional broadcast ingest and NLE workflows. |
-crf 23
|
Sets the Constant Rate Factor for the libx264 video encoder to 23, which is the default quality level and produces visually near-transparent results for most HD source material from Blu-ray or AVCHD. Lower values (e.g., 18) increase quality and file size; higher values (e.g., 28) reduce file size with some quality tradeoff. |
-b:a 192k
|
Specifies a 192kbps audio bitrate target. Note that for PCM audio (pcm_s16le), this parameter has no practical effect — PCM is uncompressed and its bitrate is determined entirely by sample rate and bit depth, not a bitrate ceiling. It is included here for command consistency and has no negative impact on output quality. |
output.mxf
|
Defines the output filename and signals to FFmpeg that the container format should be MXF (Material Exchange Format). FFmpeg infers the MXF muxer from the .mxf file extension, wrapping the H.264 video and PCM audio streams into a professional KLV-structured MXF file suitable for broadcast ingest. |
Common Use Cases
- Ingesting Blu-ray rips or AVCHD camcorder footage into a broadcast NLE like Avid Media Composer or Adobe Premiere in a format those systems natively accept for professional editing
- Delivering finished high-definition content to a broadcast facility or playout server that mandates MXF with uncompressed PCM audio rather than compressed formats like AC-3 or AAC
- Archiving AVCHD event recordings (weddings, concerts, corporate shoots) in an MXF container with uncompressed audio for long-term post-production asset management
- Preparing Blu-ray source material for color grading or VFX pipelines that require MXF-wrapped H.264 with frame-accurate timecode support
- Converting AVCHD camcorder M2TS clips to MXF so they can be ingested into newsroom automation systems that require broadcast-standard containers
- Stripping Blu-ray transport stream overhead and repackaging content as MXF with clean PCM audio tracks for dubbing, re-scoring, or audio post-production workflows
Frequently Asked Questions
The audio in M2TS files is commonly stored as compressed AC-3 (Dolby Digital) or DTS, both of which involve lossy compression. During this conversion, that compressed audio is fully decoded and re-encoded as 16-bit PCM (pcm_s16le), which is entirely uncompressed. The resulting MXF audio is technically lossless in format, but any quality loss already introduced by the original AC-3 or DTS encoding in the M2TS cannot be recovered. If the source M2TS already used AAC audio, the same decoding-then-PCM-encoding process applies.
MXF in broadcast and post-production contexts almost universally requires uncompressed PCM audio (either 16-bit or 24-bit) because it guarantees frame-accurate sync, eliminates decoder dependencies on playout systems, and meets the technical specifications of most broadcast standards. Compressed audio formats like AC-3 or AAC, which are standard in M2TS, introduce decoder latency and are not accepted by many broadcast ingest and QC workflows. The pcm_s16le codec used here produces standard 16-bit little-endian PCM, which is universally compatible with professional editing and broadcast equipment.
No. MXF does not support embedded subtitle streams, so any subtitle or closed caption tracks present in the source M2TS file will be dropped during conversion. If subtitles are critical to your workflow, you should extract them separately from the M2TS file before conversion — for example, as a SRT or SUP file — and handle them as a sidecar asset in your post-production system.
The video portion will be roughly similar in size depending on the complexity of the source content, since both use H.264 at CRF 23. However, the audio will almost certainly be significantly larger in the MXF output — uncompressed PCM audio consumes far more space than the AC-3 or DTS tracks typical in M2TS files. For a two-hour Blu-ray rip with multiple audio channels, the audio size difference alone can add several gigabytes to the output file.
Yes. Replace -c:a pcm_s16le with -c:a pcm_s24le in the command to output 24-bit PCM audio instead of 16-bit. This provides greater dynamic range headroom, which is particularly useful if the MXF file will undergo further audio processing or mixing in post-production. Most professional broadcast and DAW systems accept both 16-bit and 24-bit PCM in MXF, but check your specific ingest system's specifications before switching.
To adjust video quality, change the -crf value in the command: lower numbers (e.g., 18) produce higher quality at larger file sizes, while higher numbers (e.g., 28) reduce file size at some quality cost. For batch processing multiple M2TS files on your desktop, you can use a shell loop — for example, in bash: for f in *.m2ts; do ffmpeg -i "$f" -c:v libx264 -c:a pcm_s16le -crf 23 -b:a 192k "${f%.m2ts}.mxf"; done. This is especially useful for large collections of AVCHD clips that exceed the 1GB browser limit.
Technical Notes
M2TS and MXF share no structural compatibility at the container level — M2TS is a packetized MPEG-2 Transport Stream designed for disc media and real-time broadcast delivery, while MXF uses a KLV (Key-Length-Value) metadata architecture optimized for professional production asset management, including timecode, descriptive metadata, and operational patterns. This means every conversion between these formats requires a full transcode rather than a simple remux. One important limitation is that M2TS often carries multiple audio tracks (e.g., a primary language and director's commentary) and the MXF output will include multiple audio tracks as well, but mapping should be verified if a specific track selection is needed. The libx264 encoder at CRF 23 produces visually lossless results for most Blu-ray and AVCHD source material; however, if the source was already highly compressed (e.g., from a consumer AVCHD camcorder at low bitrates), some generation loss is unavoidable. The -b:a 192k flag is provided for completeness but has no practical effect on PCM audio output, which is uncompressed by definition — it does not use a bitrate target. Timecode metadata embedded in the MXF output will depend on FFmpeg's ability to extract timing information from the M2TS transport stream headers, and complex multi-program M2TS files may require explicit stream selection using -map flags to ensure the correct video and audio programs are targeted.