M4V to M2TS Converter

Convert M4V to M2TS: What This Tutorial Covers

This guide is for anyone who needs to turn an Apple M4V file into the .m2ts stream that Blu-ray authoring tools, AVCHD discs, and PS4/PS5-era players expect — and explains the catches (DRM, AC-3 audio, and the fact that a lone .m2ts isn't a finished disc) before you run the conversion. M4V and M2TS both carry H.264 video, so this is mostly a re-wrap into the Blu-ray transport-stream structure, not a quality-losing transcode.

How to Convert M4V to M2TS

1. Upload Your M4V File: Drag and drop or click "Add Files" to select your M4V — iTunes exports, QuickTime saves, or any DRM-free H.264 M4V. Batch is supported, and .mp4 sources are accepted too. FairPlay-protected iTunes purchases cannot be converted (see the DRM note below).
2. Pick the Video Codec and Quality: The Video Codec defaults to H.264 — the codec the BDAV/Blu-ray spec requires — with the Audio Codec set to AC3. Choose a Quality Preset (the Preset dropdown defaults to "Very High (Recommended)"), target a Specific file size, or switch File Compression to Constant or Variable Bitrate. Keep peak video bitrate at or below 24 Mbit/s for the widest player support.
3. Set Resolution and Trim (Optional): Under Preset Resolutions, pick 1920×1080 or 1280×720; a 4K M4V is downscaled to 1080p because M2TS/AVCHD is an HD-only container. Use the Trim "Time Range" control to enter a start time and duration if only one segment needs to land on disc.
4. Convert and Download: Click Convert. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically a few hours after conversion — no sign-up, no watermark, never shared.

Walk-through: Codec, Audio, and Bitrate Choices

M2TS is the BDAV MPEG-2 transport stream — 192-byte packets (a standard 188-byte MPEG-2 TS packet plus a 4-byte timestamp header) carrying H.264/AVC video and AC-3 (Dolby Digital) or LPCM audio. Because your M4V already uses H.264, the video re-wraps into that transport-stream structure rather than being transcoded to a different codec; the encoder only re-encodes the video when the source breaks the spec (for example, a 4K or above-cap-bitrate M4V). The AAC audio in an M4V is not valid BDAV audio, so it is re-encoded to AC-3.

Set the options to match where the file is going:

• Standard AVCHD disc or Blu-ray player playback — leave Video Codec on H.264 and Audio Codec on AC3. Keep peak bitrate at or below 24 Mbit/s (the AVCHD 1.0 ceiling) so older standalone players accept it.
• Newer AVCHD 2.0 authoring chain — you can push peak bitrate toward 28 Mbit/s, the AVCHD 2.0 limit, if the target player supports it.
• Very early Blu-ray authoring chain that wants MPEG-2 — switch Video Codec to MPEG-2. BDAV permits it, but H.264 gives the same quality at roughly half the bitrate, so only do this if the workflow explicitly requires MPEG-2.
• Source is 4K or HDR — M2TS/AVCHD has no 4K mode, so the file is downscaled to 1080p. To keep full resolution, convert to M4V to MP4 or M4V to MKV instead.

Common Errors and How to Fix Them

• "This M4V won't convert / conversion fails immediately" — The file is almost certainly FairPlay-DRM-protected (an iTunes Store purchase or rental). DRM blocks conversion entirely. Only DRM-free M4V files convert.
• "The Blu-ray player rejects the disc / file" — The peak bitrate likely exceeds the AVCHD ceiling, or the resolution isn't a supported AVCHD mode. Re-run with peak bitrate under 24 Mbit/s and a Preset Resolution of 1920×1080 or 1280×720.
• "There's no sound on playback" — A player that can't decode the source's original layout needs standard AC-3; the converter already targets AC3 by default, so re-run with Audio Codec on AC3 if you changed it.
• "I have the .m2ts but my player still won't see it as a disc" — A lone .m2ts is just the stream, not a finished disc. You need the surrounding BDMV/ folder structure (see "When This Doesn't Work").
• "My footage looks interlaced or combed on a flat-panel TV" — The source is likely 1080i; many AVCHD-only players expect 1080i/1080p/720p, so leave the resolution at a supported preset and let the display deinterlace, or pick a progressive preset.

When This Doesn't Work

The converter outputs the stream file — the .m2ts content — but a single .m2ts is not a playable Blu-ray or AVCHD disc on its own. A real disc needs the BDMV/ directory: the STREAM/ folder holding your .m2ts, plus PLAYLIST/ (.mpls), CLIPINF/ (.clpi), and the INDEX.BDM / MOVIEOBJ.BDM index files. Those index files are built by disc-authoring software — multiAVCHD, tsMuxeR, ImgBurn with an AVCHD template, or the built-in tools in Vegas and EDIUS. Drop the converted .m2ts into the authoring app's input list and it assembles the folder structure for you. Two other dead ends: FairPlay-protected M4V files can't be converted by any tool, and a truncated or corrupted M4V may need re-exporting from its source app first. If you only want a file that plays everywhere without disc authoring, M2TS is the wrong target — convert to M4V to MP4 instead. To go the other direction, see M2TS to M4V.

Frequently Asked Questions

My M4V is already H.264 — why does it need converting for M2TS?

The video stream may be identical, but the container and audio aren't. M4V wraps H.264 in an ISO BMFF (MPEG-4) container with AAC audio; M2TS wraps it in a BDAV MPEG-2 transport stream with AC-3 audio. Blu-ray players, AVCHD hardware, and disc-authoring apps parse the transport-stream container, not just the video codec, so even an H.264 M4V has to be re-wrapped. The converter rebuilds the H.264 video into the transport stream — re-encoding only when the source breaks the spec — and converts AAC audio to AC-3.

Can I convert a DRM-protected (iTunes-purchased) M4V to M2TS?

No. M4V files bought or rented from the iTunes Store carry Apple's FairPlay DRM, which blocks any format conversion — by us or any other tool. Only DRM-free M4V files (your own exports, home recordings, or unprotected downloads) convert. A quick test: an M4V that plays only on your own Apple devices and refuses to open in VLC or other players is almost certainly FairPlay-locked.

What's the difference between .m2ts and .mts?

They're the same stream with two filename conventions. .MTS is the legacy 8.3 form AVCHD camcorders write directly to SD card; .m2ts is the long-filename form used inside the BDMV/STREAM/ folder on a Blu-ray or AVCHD disc. The payload — H.264 video plus AC-3 audio in 192-byte transport packets — is identical. If you need the camcorder-style extension, use M4V to MTS instead.

Will I lose quality converting M4V to M2TS?

Usually not noticeably. Both use H.264, so when your M4V already fits the spec (1080p or below, bitrate under the AVCHD cap) the video is re-wrapped without a full re-encode and only the AAC audio is re-encoded to AC-3. Quality drops only when the source must be re-encoded to comply — a 4K M4V downscaled to 1080p, or a high-bitrate M4V constrained below the ceiling. In our testing, a compliant 1080p H.264 M4V converted to M2TS with the video stream re-wrapped and only the audio track re-encoded to AC-3.

Does the .m2ts include the BDMV folder I need to burn a disc?

No. The converter produces the stream file only. The surrounding BDMV/INDEX.BDM, MOVIEOBJ.BDM, PLAYLIST/, and CLIPINF/ files that make a playable disc are generated by your authoring app — multiAVCHD, tsMuxeR, ImgBurn's AVCHD template, or the tools in Vegas / EDIUS. Drop the converted .m2ts into the app's input list and it builds the folder structure, then burn to DVD-R (AVCHD) or BD-R.

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

Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically a few hours after conversion — no sign-up, no watermark, never shared or made public. XConvert handles large M4V files, including multi-GB HD captures; because conversion runs on our servers, the practical limit is upload size and connection speed rather than a fixed cap, and batch jobs aren't quantity-limited.