If you've started digging through old camcorder footage, you've probably seen both extensions: .MTS on the SD card directly, .M2TS on the version your camcorder's import software made. Same content, two extensions. So what's the actual difference?
The short answer: not much you'll notice in playback, but enough to explain why one shows up before you've imported the footage and the other shows up after.
The longer answer is a small but interesting story about how AVCHD evolved alongside Blu-ray, and why old Sony software renamed your files.
Both are MPEG-2 Transport Streams
At the binary level, MTS and M2TS files are the same format: an MPEG-2 Transport Stream (MPEG-TS), a container designed in the 1990s for broadcasting digital video over flaky channels. It chops the video into small fixed-size packets that can be reassembled even if some are dropped — useful for satellite TV, cable, and ATSC broadcast.
When AVCHD was being standardized in 2006, Sony and Panasonic picked MPEG-TS as the container because:
- It handled H.264 video natively
- It was robust to interruption (handy when a camcorder battery dies mid-recording)
- It was already the foundation for Blu-ray's video layer (BDAV)
So at the bytes level, an .MTS file and an .M2TS file are both MPEG-TS containers wrapping H.264 video and AC-3 or PCM audio. If you opened both in a hex editor, the first few hundred bytes would look essentially identical.
The difference is what's around the file.
Where MTS shows up
.MTS is what AVCHD camcorders write directly to their storage. If you pop an SD card from a Sony Handycam, Panasonic HDC, or Canon Vixia into a card reader and navigate to PRIVATE/AVCHD/BDMV/STREAM/, every video file in there has the .MTS extension. Filenames look like 00001.MTS, 00002.MTS, with the camcorder using the AVCHD metadata folders to keep track of which clips were recorded when.
So .MTS is the camcorder-native extension. If you're looking at raw camcorder output, that's what you're seeing.
Where M2TS shows up
.M2TS shows up in two places, mostly:
1. After you import AVCHD footage into the camcorder's bundled software. Sony PMB / PlayMemories Home, Panasonic HD Writer, and similar utilities all rewrite the .MTS files to .M2TS during import — same content, new extension. (Why? See the next section.)
2. On Blu-ray Discs. Inside a Blu-ray's BDMV/STREAM/ folder, every video clip is a .m2ts file. If you've ripped a Blu-ray with MakeMKV or similar, you've got .m2ts files. AVCHD inherited a lot of its structure from Blu-ray's BDAV format, so this overlap is by design — the formats are sister specs.
So .M2TS is the post-import / Blu-ray extension. If you're looking at files that have been touched by software, or that came off a disc, you're likely seeing .m2ts.
Why two extensions for the same data
This is where it gets a little petty. The AVCHD specification mandates .MTS on the camcorder's media — three letters, all uppercase, period. That was a constraint dating back to old FAT filesystem conventions that limited extensions to three characters.
When AVCHD import software grew up around the format, it ran into a problem: lots of editing tools (Premiere, Final Cut, etc.) keyed off file extensions to figure out how to handle a clip. .MTS wasn't well-recognized — those tools knew how to deal with .M2TS because Blu-ray ripping had been around for years and the extension was already in their parser tables, but .MTS was the new kid.
So the import software did what software always does: it renamed the files. .MTS → .M2TS, no actual data conversion, just an extension change. That made the imported clips magically work in editors that couldn't handle .MTS directly.
The downstream effect is that on any computer where AVCHD footage has passed through bundled import software, the extension is .M2TS. On any computer that just copy-pasted from the SD card directly, it's .MTS. Same files, different histories.
Does any of this matter for playback?
Not really. The reason your Mac, your phone, and your browser refuse to play either extension is that they don't ship with an MPEG-TS demuxer for consumer playback. The container is the problem, not the extension on top of it.
If you renamed an .MTS to .M2TS, or vice versa, you'd get the same "this file can't be played" error from the same software. Apple removed the demuxer; the extension is just labeling the door it's no longer behind.
Does it matter for conversion?
A little. For the conversion itself: no — both files re-encode the same way to MP4, with the same settings, producing the same output quality. CamcorderRescue's converter accepts both MTS and M2TS and treats them as the same format under the hood.
But for finding the file on your computer, the extension difference matters. If you're looking at an SD card or external drive expecting to see .M2TS files because that's what your old import software produced, and instead you see .MTS, you might think you're missing something. You're not — those are the same files, in their pre-import state.
A practical implication: if you have both .MTS and .M2TS versions of the same footage (because you imported once, kept the originals on the SD card, and copied both to a backup drive), pick one to convert. They're the same content. Don't waste credits doing both.
A quick recap
| MTS | M2TS | |
|---|---|---|
| Container | MPEG-2 Transport Stream | MPEG-2 Transport Stream |
| Video codec | H.264 | H.264 |
| Audio codec | AC-3 / PCM | AC-3 / PCM |
| Where you find it | Directly on AVCHD camcorder media | After import software, or on Blu-ray |
| Plays on modern macOS / iOS / browsers | No | No |
| Plays on Premiere / Final Cut | Sometimes | Yes |
| Convertible to MP4 | Yes | Yes |
| Quality after conversion | Identical | Identical |
If your goal is to actually watch the footage, the answer for both is the same: convert to MP4. Drop in an MTS or drop in an M2TS — either is a 30-second job. The MP4 you get back will play on every device made in the last fifteen years, which is the whole point.
What's on the file is what matters. The extension is just the door it came in through.
