Initializing... drag & drop files here
Supports: MP4, M4V
MTS is the file extension AVCHD camcorders write to SD cards during recording, and AVCHD is the HD video standard Sony and Panasonic jointly introduced in 2006 for consumer and prosumer camcorders. MP4 and MTS often share the same underlying H.264 video — the difference is the container (MPEG transport stream vs MPEG-4 Part 14) and the audio codec convention (AC-3 vs AAC). Converting MP4 to MTS rebuilds the file so it lines up with the AVCHD folder structure and codec profile that camcorder-aware hardware and software expect.
| Property | MP4 (MPEG-4 Part 14) | MTS (AVCHD) |
|---|---|---|
| Container | ISO base media file format | MPEG-2 Transport Stream |
| Typical video codec | H.264, H.265, AV1 | H.264 (AVCHD Main or High Profile) |
| Typical audio codec | AAC | Dolby Digital AC-3 or linear PCM |
| Max bitrate (spec) | Container-agnostic | 24 Mbps interlaced / 28 Mbps 1080p50-60 |
| Resolution support | Any | 1920x1080, 1440x1080, 1280x720, SD |
| Error resilience | Index at end of file | Packet-level (PCR/PAT/PMT) |
| Recorded by | Phones, drones, action cams, DSLRs | Sony / Panasonic AVCHD camcorders |
| Native target | Streaming, web, mobile | Blu-ray, AVCHD recorders, camcorders |
| Browser playback | Yes (Chrome, Firefox, Edge, Safari) | No (must be transcoded) |
| Setting | Best for | Notes |
|---|---|---|
| H.264 + AC3 + 1920x1080 + 24 Mbps | Blu-ray / AVCHD recorder import | Matches AVCHD spec; safest default |
| H.264 + AC3 + 1920x1080 + 28 Mbps | 1080p50 / 1080p60 progressive footage | Upper limit of AVCHD 2.0 spec |
| H.264 + AAC + 1280x720 + 12-17 Mbps | Lightweight MTS for consumer camcorder reimport | Smaller files, broadly compatible |
| CRF 18-20 (Constant Quality) | Visually lossless archival | Bitrate varies with scene complexity |
| H.265/HEVC | Not recommended for MTS | Outside AVCHD spec; many AVCHD devices reject |
Both are MPEG-2 Transport Stream containers carrying AVCHD H.264 video. MTS is the extension cameras write to SD cards directly; M2TS is the extension files get after being imported into the AVCHD/BDMV folder structure on a computer or Blu-ray disc, where each 188-byte transport packet is prefixed with a 4-byte timestamp. The video and audio data are identical and the files are functionally interchangeable for most players; renaming .mts to .m2ts (or vice versa) is usually all that's needed. If you also need the M2TS variant, use MP4 to M2TS instead.
Pick AC-3 if the destination is a Sony or Panasonic Blu-ray recorder, an AVCHD camcorder, or a Blu-ray disc — AC-3 (Dolby Digital) is part of the AVCHD audio spec and what consumer playback hardware expects. AAC works for software-only MTS workflows and slightly smaller files, but Blu-ray players that strictly enforce the spec may refuse it. For maximum portability across hardware, AC-3 at 256 or 384 kbps stereo is the safe pick.
Maybe. VLC plays MTS files out of the box on Windows, macOS, and Linux. Windows Media Player on Windows 11 plays them when the HEVC/AVCHD codecs are present. macOS Finder previews work for many AVCHD files but not all. Web browsers (Chrome, Firefox, Edge, Safari) do not play.mts URLs natively — for browser playback, convert to MP4 instead via MTS to MP4.
Anything above the AVCHD spec ceiling (28 Mbps for 1080p50/60, 24 Mbps for everything else) risks rejection by AVCHD-strict hardware. Use Constant Bitrate set to 24 Mbps for 1080p30 source or 28 Mbps for 1080p60 source. The visible quality drop from 60 to 28 Mbps in H.264 is small for most camcorder-style footage; it becomes more visible with high-motion drone shots, so consider CRF 18 instead and let the encoder size the bitrate itself.
No — not within the AVCHD spec. AVCHD tops out at 1920x1080, so any AVCHD-strict device will reject a 4K MTS. The converter will still produce a 4K MPEG transport stream file if you set the resolution that way, but it won't be a valid AVCHD file. For 4K archival, leave the footage as MP4 or use a 4K-capable container like MXF or MOV.
Yes. Both NLEs ingest AVCHD MTS natively. Premiere Pro handles it through the AVCHD importer; Vegas Pro reads MTS directly. If your timeline is already built around AVCHD source media and you exported edits as MP4, converting back to MTS keeps codec settings, frame rates, and metadata consistent across the project.
No. Camcorder recording timestamps, GPS tags, and the AVCHD index sidecar files (INDEX.BDM, MOVIEOBJ.BDM) live in the AVCHD folder structure, not in the MTS stream itself. The converter rebuilds the video and audio streams cleanly but doesn't reconstruct the surrounding AVCHD folder — for that you'd use authoring software like multiAVCHD after conversion.
The MP4 container can hold codecs that the MTS / H.264 encoder doesn't accept as input — for example, ProRes, DNxHD, or HEVC 10-bit 4:2:2 from a high-end camera. If you hit this, transcode the source to H.264 8-bit 4:2:0 MP4 first (or accept that the converter will re-encode from whatever it can decode). MP4 files from phones, drones, and action cams are virtually always H.264 or H.265 and convert without issue.
Yes — either lower the Quality Preset, reduce Constant Bitrate, increase CRF (higher number = more compression), or set a Target File Size in MB. If you only need size reduction without changing the container, Compress MP4 is faster than full transcoding to MTS.