Initializing... drag & drop files here
Supports: MP4, M4V
If you just want a video that plays everywhere, you don't want AVCHD — keep M4V or convert to MP4. Convert M4V to AVCHD only when a specific device or workflow demands it: re-importing edited footage into a Sony or Panasonic camcorder, authoring an AVCHD disc that plays on a Blu-ray player or PS4/PS5, or feeding a legacy NLE that rejects MP4-family files. M4V and AVCHD both carry H.264 video, so this conversion keeps that codec family — re-encoding the video at a visually-lossless default into the rigid AVCHD transport-stream structure and swapping the audio to AC-3 — rather than gaining quality.
| Property | M4V | AVCHD |
|---|---|---|
| Origin | Apple, 2005 (iTunes / QuickTime variant of MP4) | Sony + Panasonic, 2006 (HD camcorder spec) |
| Container | ISO BMFF / MPEG-4 Part 14 (.m4v) |
MPEG-2 Transport Stream, 192-byte packets (.mts / .m2ts) |
| Video codec | H.264 (AVC) | H.264 only (Main / High profile) |
| Audio codec | AAC (default) | AC-3 (default) or LPCM |
| Resolution | Any, up to 4K and beyond | 1080p / 1080i / 720p (HD only — no 4K) |
| Max video bitrate | No format-level cap | 24 Mbit/s (AVCHD 1.0), 28 Mbit/s (AVCHD 2.0 progressive) |
| DRM | May carry Apple FairPlay (purchased iTunes content) | None |
| Folder structure | Single file | BDMV/ directory (STREAM/, PLAYLIST/, index files) |
| Plays on | Apple TV, iTunes, QuickTime, most modern players | Sony / Panasonic camcorders, Blu-ray players, PS4 / PS5 |
| Best for | Apple-ecosystem playback, web-adjacent delivery | Camcorder ingest, AVCHD discs, legacy HD NLEs |
Both formats already use H.264, so the conversion re-encodes your video into the AVCHD MPEG-2 transport stream — keeping the same H.264 codec at a visually-lossless default rather than doing a cross-codec transcode — and re-encodes AAC audio to AC-3. The catch is that AVCHD is a strict spec: a 4K M4V is downscaled to 1080p, and an M4V whose bitrate exceeds the AVCHD ceiling is constrained to fit playback hardware.
.m4v wrapper..mts / .m2ts stream that consumer camcorder and disc hardware expect.AVCHD is a strict specification, so the converter has to make your M4V conform — downscaling above-1080p sources and holding the bitrate within the ceiling. These are the boundaries the output must fit.
| Property | AVCHD requirement |
|---|---|
| Container | MPEG-2 Transport Stream (.mts / .m2ts) |
| Video codec | H.264 / AVC, High Profile (Level 4.0, or 4.2 for 1080p50/60) |
| Maximum resolution | 1920×1080 — no 4K mode |
| Scan / frame rates | 1080p (24/25/30/50/60), 1080i, 720p |
| Maximum video bitrate | 24 Mbit/s (AVCHD 1.0) · 28 Mbit/s (AVCHD 2.0, 1080p50/60) |
| Audio codec | Dolby AC-3 (default) or uncompressed LPCM |
| Best for | Camcorder ingest, AVCHD discs, legacy HD editors |
.mp4 sources. DRM-protected M4V (FairPlay-locked iTunes purchases) cannot be converted — only DRM-free files.The video stream may be identical, but the container and audio aren't. AVCHD requires an MPEG-2 Transport Stream wrapper (.mts / .m2ts) and AC-3 audio; M4V uses an ISO BMFF wrapper and AAC audio. Sony / Panasonic camcorders and AVCHD-only NLEs parse the container, not just the video, so even an H.264 M4V is rejected as-is. The converter re-encodes the H.264 video into the AVCHD transport stream — keeping the same H.264 codec at a visually-lossless default — and converts the AAC audio to AC-3.
No. M4V files bought or rented from the iTunes Store are locked with Apple's FairPlay DRM, and that protection blocks any format conversion — by us or any other converter. Only DRM-free M4V files (your own exports, home recordings, or unprotected downloads) can be converted. If you're unsure, an M4V that plays only on your own Apple devices and refuses to open elsewhere is almost certainly FairPlay-protected.
Usually not noticeably. Both use H.264, so the conversion keeps that codec at a visually-lossless default and adds no cross-codec generation loss; the AAC audio is re-encoded to AC-3. Quality drops further only when the source must also be downscaled or bitrate-constrained to comply — for example a 4K M4V downscaled to 1080p, or a high-bitrate M4V constrained below 24 Mbit/s. In our testing, a compliant 1080p H.264 M4V re-encoded to AVCHD stayed visually indistinguishable from the source; only the AAC track changed codec, to AC-3.
No. AVCHD caps at 1080p (1920×1080 progressive, 1440×1080 interlaced). The converter downscales 4K M4V sources to 1080p when AVCHD is selected. If you need to keep 4K, convert to M4V → MKV or M4V → MP4 instead — both keep the full resolution.
They're closely related. MTS is the raw extension AVCHD camcorders write directly to SD card. M2TS is the same content used inside the AVCHD BDMV/STREAM/ folder on a disc. AVCHD is the overall spec — the folder structure plus the stream format. Our converter outputs the stream both extensions wrap; pick M4V → MTS or M4V → M2TS if you need a specific extension, or stick with AVCHD for the folder-ready file.
If the camcorder supports AVCHD ingest (most Sony Handycam, HDR-CX/PJ, FX, and Panasonic HC-V / HC-X models do), yes — copy the converted MTS into the PRIVATE/AVCHD/BDMV/STREAM/ folder on the SD card and the camcorder will see it. Older bodies may need the index files refreshed; some manufacturer utilities rebuild them automatically. Note that AVCHD's strict bitrate and level rules mean a non-conforming source is constrained to fit the playback hardware.
Aim for 24 Mbit/s unless you specifically need AVCHD 2.0. The original AVCHD 1.0 spec caps video at 24 Mbit/s, and that ceiling is what the widest range of camcorders, standalone Blu-ray players, and older editors expect. The 28 Mbit/s ceiling exists only in AVCHD 2.0 for 1080p50/60 footage, and not every device that reads AVCHD 1.0 will accept a 2.0 stream. When in doubt keep the peak at or below 24 Mbit/s for the safest playback, and only reach for 28 when the target is a confirmed AVCHD 2.0 device handling 50/60p.
The converter outputs the stream file (the .mts content). The surrounding BDMV/INDEX.BDM, MOVIEOBJ.BDM, and PLAYLIST/00000.MPL index files are generated by your disc-authoring app (multiAVCHD, tsMuxeR, ImgBurn with an AVCHD template, or built-in tools in Vegas / EDIUS). Drop the converted .mts into the authoring app's input list and it builds the folder structure for you. To go the other direction — pulling AVCHD footage back into an Apple workflow — use AVCHD → M4V.