M4V to MTS Converter

Converting M4V to MTS: What This Tutorial Covers

This is a niche conversion, so the honest summary first: M4V is Apple's MPEG-4 video container (the format iTunes movies and Apple exports use), and MTS is the .mts extension of AVCHD — the camcorder format Sony and Panasonic introduced in 2006, which packs H.264 video into an MPEG-2 transport stream. You would convert M4V to MTS only for a specific reason: feeding footage into AVCHD-era editing software, a camcorder-ecosystem tool, or a transport-stream pipeline that expects a .mts file. Before you start, two things to know — iTunes-purchased M4V files are usually DRM-locked and cannot be converted, and because the two containers use different stream packaging this is a re-encode, so quality can stay the same or drop but never improve. If you are not specifically targeting an AVCHD workflow, you almost certainly want M4V to MP4 instead.

How to Convert M4V to MTS

1. Upload Your M4V File: Drag and drop your .m4v (or .mp4) file onto the page, or click "+ Add Files" to browse. Several files queue and convert with the same settings.
2. Pick a Quality Preset or Bitrate Mode: The default is the "Very High (Recommended)" Quality Preset. To stay inside AVCHD's bitrate ceiling, switch to Constant Bitrate or Constraint Quality and cap it at 24 Mbps (or use Constant Quality / CRF, where a lower number means higher quality).
3. Set Resolution or Trim (Optional): Under Video resolution, keep original or pick a Preset Resolution such as 1080p or 720p to match AVCHD targets; under Trim, choose Time Range to export only part of the clip.
4. Convert and Download: Click "Convert" and download your .mts file. No sign-up, no watermark.

Walk-through: Hitting an AVCHD-Compatible Output

AVCHD is not just "H.264 in a transport stream" — it is H.264 inside an MPEG transport stream with constraints that real camcorders and older editors expect, most notably a total bitrate that tops out around 24 Mbit/s for the original spec (28 Mbit/s for AVCHD version 2.0). A generic high-bitrate .mts will still carry the .mts extension, but a strict AVCHD device or NLE may reject it. To stay close to what those tools expect:

• If your editor expects standard AVCHD: set Constant Bitrate or Constraint Quality and keep the ceiling at or below 24 Mbps, and pick a Preset Resolution of 1080p or 720p rather than an unusual custom size.
• If you only need a .mts file a transport-stream pipeline can ingest: the "Very High" Quality Preset at original resolution is usually fine — you are after the container and stream type, not strict AVCHD compliance.
• If file size matters more than spec compliance: use Variable Bitrate or raise the CRF value; the output stays a valid transport stream but gets smaller.

The audio is re-encoded too. AVCHD itself uses Dolby AC-3 or linear PCM, while your M4V almost certainly carries AAC, so the soundtrack is decoded and re-compressed during the convert step rather than copied across untouched.

Common Errors and How to Fix Them

• "Conversion fails immediately on an iTunes movie" — The file is FairPlay DRM-protected. Purchased or rented iTunes content cannot be decoded by any converter; only DRM-free M4V (your own exports, recordings, or downloads that were never encrypted) will convert. This is a limit of the file, not the tool.
• "My AVCHD camcorder or editor won't read the .mts" — The output is likely a valid transport stream but outside AVCHD's bitrate or resolution constraints. Re-run with Constant Bitrate capped at 24 Mbps and a 1080p or 720p Preset Resolution.
• "The MTS looks softer than the original M4V" — This is a re-encode, not a copy, so some detail is lost on every pass. Use the "Very High" preset or a low CRF value and match the source resolution to keep the loss minimal; quality can never exceed the source.
• "The file is huge" — Transport streams carry overhead and AVCHD targets high bitrates, so .mts output is often larger than the M4V you started with. Lower the bitrate ceiling or switch to Variable Bitrate if size is the priority.

When This Doesn't Work

If the M4V is a protected iTunes purchase, no online or desktop converter can process it — the encryption has to be absent in the first place. And if your real goal is simply to play the video on phones, browsers, or non-Apple devices, MTS is the wrong target entirely: AVCHD is built for camcorders and Blu-ray-style playback, not general sharing. In that case convert to a widely supported container with M4V to MP4, or if you only need the soundtrack use M4V to MP3. Coming the other way — moving camcorder footage off .mts into an Apple-friendly format — use the reverse tool, MTS to M4V.

Frequently Asked Questions

Can I convert a DRM-protected iTunes M4V to MTS?

No. Movies and TV shows purchased or rented from the iTunes Store are usually wrapped in Apple's FairPlay copy protection, which restricts playback to devices authorized with the purchasing Apple account. A FairPlay-protected M4V cannot be decoded by a converter, so the conversion will fail. Only DRM-free M4V files — your own screen recordings, exports, camera footage, or downloads that were never encrypted — can be converted to MTS. This is a limitation of the protection on the file, not of the tool.

Why would anyone convert M4V to MTS instead of MP4?

For most people, MP4 is the better target, so this conversion is genuinely niche. The honest reasons to choose MTS are narrow: you are importing footage into AVCHD-era editing software or a camcorder-ecosystem utility that specifically expects .mts, or you are feeding a transport-stream pipeline (broadcast-style or capture workflows) built around MPEG transport streams rather than MP4. If none of that describes your situation, M4V to MP4 plays on far more devices and editors and is almost always the right choice.

Will converting M4V to MTS lose quality?

Yes, to some degree — this is a re-encode, not a container copy. M4V and MTS use different stream packaging (MP4 versus an MPEG transport stream), so the H.264 video is decoded and re-encoded rather than remuxed across untouched, and the AAC audio is re-compressed to fit AVCHD's audio formats. Each encode discards a little detail and cannot rebuild what an earlier pass removed, so quality can stay close to the source or drop, but never improve. Using the "Very High" Quality Preset or a low CRF value and keeping the original resolution keeps the loss small.

Is MTS the same as M2TS or AVCHD?

They are closely related. AVCHD is the format; .mts is the extension cameras write to the memory card, and .m2ts is typically what you get after importing the same footage to a computer or what appears on Blu-ray discs. Both carry an MPEG transport stream with H.264 video. This tool outputs .mts; if your workflow specifically needs the .m2ts extension, use M4V to M2TS instead — the underlying stream is the same family.

What bitrate and resolution should I target for AVCHD?

Standard AVCHD tops out at a total bitrate around 24 Mbit/s (AVCHD version 2.0 raised this to 28 Mbit/s) and is built around 1080i, 1080p, and 720p. In our testing, capping Constant Bitrate at 24 Mbps with a 1080p Preset Resolution produced a .mts that imported cleanly into transport-stream-aware editors; pushing the bitrate much higher or using an unusual custom resolution is what most often causes a strict AVCHD device or NLE to reject the file. If you are not targeting a strict AVCHD device, the default preset at original resolution is fine.

How are my files handled, and is there a size limit?

Your M4V is uploaded over an encrypted connection, processed on our servers, and the files are deleted automatically a few hours after the conversion — no sign-up, no watermark, never shared or made public. The main practical limit is upload size and time: M4V files carry full video, and .mts output is often larger than the source because transport streams target high bitrates, so a long clip may take a while to upload and download.