Convert M4V to MTS — Free Online Tool
Convert M4V files from iTunes or iOS devices into MTS (AVCHD) format compatible with Sony and Panasonic camcorder workflows. This tool re-encodes the H.264 video and AAC audio streams from the MPEG-4 container into an MPEG-2 Transport Stream, making your downloaded or recorded Apple content editable in broadcast and camcorder-oriented video software.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your M4V 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
M4V and MTS share H.264 as a common video codec, but because the two containers differ fundamentally — M4V is an MPEG-4 box-based container while MTS is an MPEG-2 Transport Stream — the video stream cannot simply be remuxed and must be re-encoded from scratch. The AAC audio is similarly re-encoded to ensure it conforms to the AVCHD transport stream framing. The -movflags +faststart optimization present in M4V output is irrelevant here and is dropped, since MTS uses a fixed transport stream packetization model rather than a web-streaming-oriented moov atom structure. The result is a file that camcorder editing software, non-linear editors with AVCHD ingest pipelines, and broadcast tools recognize as a native AVCHD recording.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg binary — the open-source multimedia processing engine that performs the actual M4V-to-MTS conversion. In the browser-based version of this tool, FFmpeg runs as a WebAssembly module (FFmpeg.wasm) without any server involvement. |
-i input.m4v
|
Specifies the input file, an M4V container typically sourced from iTunes downloads, iOS recordings, or Apple-ecosystem video exports. FFmpeg reads the H.264 video and AAC audio streams from inside this MPEG-4 box structure. |
-c:v libx264
|
Sets the video encoder to libx264, re-encoding the video stream into H.264 suitable for MPEG-2 Transport Stream packetization. Even though the source M4V likely already contains H.264, a full re-encode is required because the container framing and stream parameters must conform to the AVCHD/MTS transport stream format. |
-c:a aac
|
Encodes the audio stream using AAC, which is valid within the MTS/AVCHD container. Since the M4V source already carries AAC audio, this re-encodes it to ensure the audio packets are correctly framed for the MPEG-2 Transport Stream muxer rather than copied with M4V-specific framing. |
-crf 23
|
Sets the Constant Rate Factor for the libx264 video encode to 23, the default quality level that balances file size and visual fidelity. For iTunes M4V sources that are already lossy, consider using CRF 18-20 to minimize additional quality degradation during this second encode. |
-b:a 128k
|
Sets the AAC audio bitrate to 128 kilobits per second, a standard quality level suitable for dialogue, general video content, and iTunes-sourced audio. For music-heavy M4V content being preserved for broadcast or archival use in MTS, increasing this to 192k or 256k is advisable. |
output.mts
|
Specifies the output filename with the .mts extension, which signals FFmpeg to use the MPEG-2 Transport Stream muxer. The resulting file is an AVCHD-compatible transport stream that Sony/Panasonic editing software, AVCHD-aware NLEs, and broadcast ingest tools can recognize and import. |
Common Use Cases
- Importing iTunes-purchased or recorded M4V content into Sony Vegas Pro or Magix Video Pro, which prefer native AVCHD/MTS project formats for timeline editing
- Bringing iOS screen recordings or Apple Clips exports into a Panasonic AG-series camcorder editing workflow where the NLE expects MTS files on an SD card structure
- Archiving Apple TV+ or iTunes video downloads (DRM-free copies) alongside actual camcorder footage in a unified MTS-based media library for consistent ingest
- Preparing M4V training videos or instructional content for playout on broadcast systems or hardware encoders that accept AVCHD Transport Stream as input
- Converting M4V conference recordings to MTS so they can be ingested by legacy Blu-ray authoring tools that require AVCHD-compliant video streams
- Matching codec and container format of Apple-sourced video to existing MTS footage from a camcorder before editing in DaVinci Resolve with a native AVCHD timeline
Frequently Asked Questions
Yes, this conversion involves a full re-encode of both video and audio streams, so some generation loss is inevitable. The default CRF 23 for libx264 produces visually good results for most content, but if your M4V source was already heavily compressed (as iTunes downloads typically are), stacking another lossy encode can introduce minor artifacts in fast-motion or high-detail scenes. Using a lower CRF value like 18 in the FFmpeg command will preserve more quality at the cost of a larger output file.
No — MTS (MPEG-2 Transport Stream / AVCHD) does not support chapter metadata. M4V files can carry chapter markers natively, but these will be silently dropped during conversion to MTS. If chapter navigation is important to your workflow, you should export or document the chapter timestamps before converting, as there is no mechanism to embed them in the MTS container.
By default, FFmpeg selects only the best single audio stream for the output. MTS does technically support multiple audio tracks, but the default command shown here maps only the primary audio stream. To include additional audio tracks, you would need to add explicit -map flags to the FFmpeg command, for example adding '-map 0:a:1' for a second audio track alongside '-map 0:v:0 -map 0:a:0'.
Authentic AVCHD footage from Sony or Panasonic camcorders is recorded at specific frame rates (typically 60i, 50i, 30p, or 24p) and bitrates defined by the AVCHD specification, along with a precise directory structure on the recording media. Converting M4V content to MTS produces a valid transport stream file but does not replicate the full AVCHD folder structure (BDMV/STREAM) that some editing applications expect. If your NLE requires a proper AVCHD disc structure, you may need additional authoring steps beyond this conversion.
Adjust the -crf value in the command — lower numbers mean higher quality and larger files, while higher numbers reduce quality and file size. The scale runs from 0 (near-lossless) to 51 (very low quality), with 23 as the default balance point. For archival-quality conversion of an iTunes M4V, a CRF of 18 is a common choice. Simply replace '23' in the command with your preferred value: for example, 'ffmpeg -i input.m4v -c:v libx264 -c:a aac -crf 18 -b:a 128k output.mts'.
The single-file command shown targets one input and one output, but you can batch process on your desktop using a shell loop. On Linux or macOS, run: 'for f in *.m4v; do ffmpeg -i "$f" -c:v libx264 -c:a aac -crf 23 -b:a 128k "${f%.m4v}.mts"; done'. On Windows Command Prompt, use: 'for %f in (*.m4v) do ffmpeg -i "%f" -c:v libx264 -c:a aac -crf 23 -b:a 128k "%~nf.mts"'. The in-browser tool processes one file at a time, making the local FFmpeg command particularly valuable for large batch jobs.
Technical Notes
M4V is essentially an MPEG-4 Part 14 container (nearly identical to MP4) with an optional Apple DRM layer; DRM-protected M4V files cannot be processed by FFmpeg or any browser-based tool — only DRM-free M4V files will convert successfully. The output MTS format uses MPEG-2 Transport Stream packetization, which is fundamentally different from the box/atom structure of M4V, requiring a full remux rather than a simple container swap. Both formats share libx264 as a valid video codec, but the re-encode is still necessary due to container framing differences. Subtitle streams present in M4V (typically in tx3g or mov_text format) are not carried into MTS output by this command, as MPEG-2 Transport Streams use different subtitle encapsulation (DVB or SCTE standards) that require separate handling. Audio bitrate defaults to 128k AAC, which is appropriate for most speech and general content; music-heavy content may benefit from 192k or 256k. Because MTS lacks the -movflags +faststart optimization, the output file is not suited for progressive web streaming and is best used in local editing or broadcast ingest scenarios.