Convert MOV to M2TS — Free Online Tool
Convert MOV files to M2TS format for Blu-ray disc authoring and AVCHD camcorder compatibility, re-encoding video with H.264 and audio with AAC inside a MPEG-2 Transport Stream container. This is ideal when you need to move Apple QuickTime footage into a broadcast or disc-ready BDAV structure.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your MOV 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
MOV is Apple's QuickTime container, often used in professional editing with codecs like ProRes or H.264. M2TS is a MPEG-2 Transport Stream wrapper used on Blu-ray discs and AVCHD cameras. Because M2TS requires a transport stream container structure that MOV cannot share directly, full re-encoding is performed: the video stream is encoded to H.264 (libx264) with a CRF of 23, and the audio is encoded to AAC at 128k bitrate. The output is a .m2ts file whose packet structure is compatible with Blu-ray authoring software and AVCHD-capable players. Note that MOV-specific metadata such as chapter markers and transparency channels will not survive this conversion, as M2TS does not support those features.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg program, the open-source multimedia processing engine that handles all the decoding, re-encoding, and container remuxing in this MOV-to-M2TS conversion. |
-i input.mov
|
Specifies the input file in Apple QuickTime MOV format. FFmpeg will probe this file to detect its video codec (e.g., H.264, ProRes, MJPEG), audio codec, and container metadata before beginning the conversion. |
-c:v libx264
|
Encodes the video stream using the H.264 codec via libx264. This is required because M2TS in the BDAV specification is designed around H.264 and H.265 for HD content, and the MOV source codec may not be directly compatible with the M2TS transport stream structure. |
-c:a aac
|
Encodes the audio stream to AAC, which is widely supported within M2TS and Blu-ray players. Even if the source MOV already contains AAC audio, re-encoding is necessary due to the repackaging into the MPEG-2 Transport Stream container. |
-crf 23
|
Sets the Constant Rate Factor for H.264 video quality at 23, FFmpeg's default. This produces a good balance of visual quality and file size for HD content destined for Blu-ray authoring or AVCHD playback — lower values like 18 are preferable for disc mastering where quality is critical. |
-b:a 128k
|
Sets the AAC audio bitrate to 128 kilobits per second, sufficient for stereo dialogue and music in a Blu-ray or AVCHD context. For surround sound or high-fidelity music content, increasing this to 192k or 256k would be appropriate. |
output.m2ts
|
Defines the output filename with the .m2ts extension, signaling FFmpeg to write a BDAV MPEG-2 Transport Stream with the 192-byte packet structure expected by Blu-ray authoring tools and AVCHD-compatible devices. |
Common Use Cases
- Authoring a Blu-ray disc from footage captured or exported as MOV from Final Cut Pro or DaVinci Resolve
- Making Apple QuickTime footage compatible with Sony or Panasonic AVCHD camcorder libraries and players
- Preparing H.264 video content for broadcast workflows that ingest MPEG-2 Transport Stream files
- Archiving high-definition MOV recordings in a format playable on standalone Blu-ray disc players via USB or disc
- Converting iPhone or GoPro MOV exports into M2TS for use in Blu-ray authoring tools like DVDFab or Nero
- Standardizing a mixed library of MOV files into a single M2TS format for a broadcast or streaming playout system
Frequently Asked Questions
No. The M2TS container format does not support chapter markers, so any chapters embedded in your MOV file will be lost during this conversion. If chapter navigation is important to you, you may want to document your chapter timestamps before converting. Blu-ray chapter points are typically defined separately within the disc authoring software rather than inside the M2TS stream itself.
Yes, this conversion involves re-encoding both the video and audio streams, which introduces some generational quality loss. The video is encoded using H.264 with a CRF of 23, which is a visually good default but not lossless. If your source MOV uses a high-quality codec like Apple ProRes, you will notice some reduction in quality. To minimize loss, you can lower the CRF value — for example, CRF 18 produces near-lossless H.264 output at the cost of a larger file size.
M2TS does support multiple audio tracks, so it is technically possible to carry them through. However, this tool's default FFmpeg command maps a single audio stream. If your MOV file contains multiple audio tracks and you need them all in the output, you would need to add explicit stream mapping flags like '-map 0:a:0 -map 0:a:1' to the FFmpeg command and run it locally on your desktop.
No. M2TS does not support transparency or alpha channels. H.264, the video codec used in this conversion, also does not carry transparency data in standard implementations. If your MOV source contains an alpha channel (for example, exported from Motion or After Effects), the alpha information will be discarded and the transparent areas will typically be rendered as black in the output.
The '-crf 23' flag controls quality in H.264 encoding. Lower values produce higher quality and larger files — for example, '-crf 18' is near-lossless and suitable for archival or Blu-ray mastering. Higher values like '-crf 28' or '-crf 30' reduce file size but introduce visible compression artifacts. For Blu-ray authoring, values between 16 and 20 are generally recommended to ensure the output meets the visual quality expectations of HD disc content.
Yes. On Linux or macOS you can use a shell loop: 'for f in *.mov; do ffmpeg -i "$f" -c:v libx264 -c:a aac -crf 23 -b:a 128k "${f%.mov}.m2ts"; done'. On Windows Command Prompt you can use 'for %f in (*.mov) do ffmpeg -i "%f" -c:v libx264 -c:a aac -crf 23 -b:a 128k "%~nf.m2ts"'. This is particularly useful for larger files over 1GB, which exceed the browser tool's limit and must be processed locally.
Technical Notes
M2TS uses a 192-byte packet structure (a 4-byte timestamp header prepended to each 188-byte MPEG-2 TS packet), which is specific to the BDAV (Blu-ray Disc Audio-Video) specification and distinguishes it from plain .ts transport stream files. When encoding from MOV, the absence of the '-movflags +faststart' flag that MOV benefits from is intentional — M2TS has its own transport stream packet structure for streaming and does not use the same kind of moov atom optimization. MOV files sourced from Apple devices or professional editing software may contain ProRes, MJPEG, or even PNG-based video streams; all of these will be transcoded to H.264 in this conversion, so the resulting M2TS will always use libx264 regardless of the source codec. Audio from AAC-encoded MOV files will still be re-encoded rather than stream-copied because the container switch requires repackaging at the transport stream level. Subtitles embedded in MOV files can survive in M2TS if explicitly mapped, but this requires manual FFmpeg stream mapping beyond the default command. Chapter markers, transparency data, and Apple-specific metadata atoms (such as color profile tags common in iPhone footage) will be stripped in the output.