MyMediaTools

Convert MTS to M4V — Free Online Tool

Convert MTS files from Sony or Panasonic AVCHD camcorders into Apple-compatible M4V format, re-encoding the H.264 video and AC-3/AAC audio into an MPEG-4 container optimized for iTunes, iOS devices, and Apple TV. The output includes the +faststart flag so M4V files begin playing immediately in web and Apple ecosystem players without buffering.

FFmpeg Command

Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg

Free — no uploads, no signups. Your files never leave your browser.

Estimated output:

Conversion Complete!

Download

How It Works

MTS files use the MPEG-2 Transport Stream container, which was designed for broadcast and camcorder recording — not for Apple ecosystem playback. Even though MTS often contains H.264 video (the same codec used in M4V), the Transport Stream wrapper is incompatible with iTunes and most Apple devices, so a simple remux is not sufficient. This tool re-encodes the video using libx264 with a CRF of 23 (visually near-lossless for typical camcorder footage) and transcodes the audio — whether it was originally AC-3 Dolby Digital or AAC — into standard AAC at 128k, which is natively supported across all Apple platforms. The resulting M4V file also has its metadata index moved to the beginning of the file via -movflags +faststart, enabling progressive playback in Safari and Apple-compatible web players.

What Each Flag Does

Flag What it does
ffmpeg Invokes the FFmpeg program, which handles all demuxing of the MPEG-2 Transport Stream container, decoding of the AVCHD H.264 video and AC-3/AAC audio, re-encoding, and writing the M4V output.
-i input.mts Specifies the input MTS file from the AVCHD camcorder. FFmpeg reads and parses the MPEG-2 Transport Stream wrapper to extract the contained video and audio elementary streams.
-c:v libx264 Re-encodes the video stream using the libx264 H.264 encoder. Although MTS already contains H.264, it must be decoded and re-encoded because the Transport Stream container structure is incompatible with the MPEG-4 container used by M4V.
-c:a aac Transcodes the audio to AAC using FFmpeg's native AAC encoder. This is necessary whether the MTS source contains AC-3 Dolby Digital (common in Panasonic AVCHD) or AAC, as the output must conform to standard AAC framing expected by Apple devices and iTunes.
-crf 23 Sets the Constant Rate Factor for libx264 to 23, which is the default balance between quality and file size for H.264 encoding. For typical camcorder footage this produces visually clean results; lower values like 18 yield higher quality at larger file sizes.
-b:a 128k Sets the AAC audio output bitrate to 128 kilobits per second, which is sufficient for stereo camcorder audio including dialogue, ambient sound, and music recorded in the field.
-movflags +faststart Relocates the M4V file's metadata index to the start of the file after encoding completes. This is required for streaming and web delivery — Safari and Apple players can begin playback immediately without downloading the entire file first.
output.m4v The output filename with the .m4v extension, which signals to both FFmpeg and downstream Apple applications that this is an MPEG-4 container formatted for iTunes and iOS compatibility.

Common Use Cases

  • Importing camcorder footage shot on a Sony Handycam or Panasonic HC-series into iTunes or the Apple TV app for home library playback
  • Preparing AVCHD wedding or event footage for delivery to clients who use iPhones or MacBooks as their primary viewing devices
  • Uploading camcorder MTS clips to an iOS editing workflow in iMovie, which does not natively recognize the AVCHD .mts container
  • Archiving AVCHD vacation footage in a format that can be AirPlayed to Apple TV without transcoding delays or compatibility errors
  • Converting MTS clips for embedding in a website that targets Safari users, where the +faststart M4V loads without waiting for the full file to download
  • Batch-converting a memory card full of MTS segments from a multi-camera AVCHD rig into a consistent Apple-compatible format before editorial assembly

Frequently Asked Questions

MTS files use the MPEG-2 Transport Stream container, which Apple's software does not natively support, even when the video inside is H.264. iTunes and iMovie expect video wrapped in MPEG-4-based containers like MP4 or M4V. Converting to M4V rewraps the video and transcodes the audio into formats these applications fully recognize, without significant quality loss at the default CRF 23 setting.
Yes — if your AVCHD camcorder recorded AC-3 Dolby Digital audio (common on Panasonic models), this conversion will transcode it to AAC at 128k. AAC at 128k is perceptually transparent for most speech and ambient camcorder audio, but it is a different codec, so there is a generational quality step involved. If you need higher fidelity, you can increase the audio bitrate in the FFmpeg command to 192k or 256k using the -b:a flag.
The M4V container format supports chapters, unlike MTS which does not. However, AVCHD camcorders do not embed chapter metadata in MTS files in a form that FFmpeg can automatically extract and carry over. If you want chapters in the M4V output, you would need to add them manually using a tool like HandBrake or MP4Box after the conversion.
The +faststart flag moves the MP4/M4V metadata index (the 'moov' atom) from the end of the file to the beginning. For local playback on an Apple device this makes little difference, but it is essential if you plan to stream or share the file via a web server — without it, a browser or player must download the entire file before it can begin playing. It adds no overhead and is always worth including.
The -crf 23 value controls quality using H.264's Constant Rate Factor scale, where lower numbers mean higher quality and larger files, and higher numbers mean smaller files with more compression. For higher-quality output suitable for archiving camcorder footage, try -crf 18. For a smaller file where some quality loss is acceptable — for example, a web preview — try -crf 28. You can change this value directly in the command and run it on your desktop for files over 1GB.
Yes. On Linux or macOS, you can loop over all MTS files in a directory with: for f in *.mts; do ffmpeg -i "$f" -c:v libx264 -c:a aac -crf 23 -b:a 128k -movflags +faststart "${f%.mts}.m4v"; done. On Windows Command Prompt, use: for %f in (*.mts) do ffmpeg -i "%f" -c:v libx264 -c:a aac -crf 23 -b:a 128k -movflags +faststart "%~nf.m4v". This is particularly useful for processing a full AVCHD memory card of segmented MTS clips.

Technical Notes

AVCHD MTS files frequently contain multiple audio tracks — for instance, a stereo track plus a surround mix — and this FFmpeg command will by default select only the first audio track for output. If you need to preserve multiple audio tracks in the M4V (which the container supports), add -map 0:v -map 0:a to map all streams explicitly. The libx264 encoder used here is not the same as Apple's hardware H.264 encoder, so the output will be software-encoded; on a slow machine, processing long MTS files may take significant time. The M4V container is functionally identical to MP4 with the exception of optional Apple FairPlay DRM support — if DRM is not required, the files are interchangeable and renaming .m4v to .mp4 will not break playback. One known limitation is that AVCHD's broadcast-oriented MPEG-2 TS structure sometimes causes FFmpeg to probe the input longer than usual; if you experience audio/video sync issues on MTS files recorded across segment boundaries (AVCHD splits recordings into 2–4GB chunks), consider using -fflags +genpts in the command to regenerate presentation timestamps.

Related Tools

Convert MTS to AIFC Convert MTS to CAF Convert MTS to ALAC Convert MOD to M4V Convert MXF to M4V Convert WebM to M4V Compress MTS Extract Audio MTS to MP3