Convert MTS Files Online for Free
Understand an MTS camera or Blu-ray transport stream before selecting a compatible delivery format, preserving tracks, timing, and source evidence.
- Add a file Choose or drop it here
- Pick the format Change it whenever needed
- Download the result After conversion completes
MTS Usually Means a Blu-ray-Style Transport Stream, Not One Video Codec
Files named .mts or .m2ts are commonly BDAV MPEG-2 Transport Stream files used by Blu-ray, AVCHD cameras, and related workflows. The name does not tell you whether picture data is MPEG-2 video, AVC/H.264, or VC-1, nor which audio, subtitles, language tracks, or metadata are present. Treat MTS as a container family first and inspect its streams before choosing a converter setting.
This is different from an MPG Program Stream. Transport Streams packetize data for robust, timed delivery, and one file can carry multiple independently identified streams. A conversion that chooses only visible video can silently drop an alternate soundtrack, subtitle, or camera audio channel. Keep the MTS original: a new delivery file cannot recreate discarded tracks or source detail.
First play the file at an opening landmark, a middle landmark, and the ending. Record video codec, dimensions, frame rate, interlace/HDR information if reported, every audio stream, language/name, channels, and any source warning. That is the baseline for every later conversion choice.
M2TS Adds Four Bytes to Each 188-Byte MPEG Transport Packet
Normal MPEG-2 Transport Stream packets are 188 bytes. BDAV M2TS prefixes each with a 4-byte TP_extra_header, producing 192-byte source packets. The National Archives describes this distinction directly, and the Library of Congress describes BDAV aligned units of 6,144 bytes made from 192-byte source packets. That four-byte prefix is why a tool that expects ordinary 188-byte TS can misread an MTS file unless it recognizes the BDAV form.
The extra header carries arrival-time information; technical BDAV discussion describes a 30-bit arrival timestamp based on a 27 MHz counter. It is not video picture quality information. It supports reconstruction of a compliant constant-rate transport stream behavior. Removing or inventing it by a filename change is not a valid conversion.
A correct conversion first identifies the 192-byte framing, then interprets the embedded transport packets and their selected media streams. If the reader begins on the wrong byte boundary, every following packet can appear damaged even when the original file is sound.
PAT, PMT, PIDs, and PES Explain Where Picture and Sound Actually Live
Inside each 188-byte transport packet, a 13-bit Packet Identifier, or PID, identifies its purpose. PID 0 carries the Program Association Table, or PAT. PAT entries point to Program Map Table PIDs; the PMT then lists the elementary streams belonging to that programme, including video, audio, subtitles, and the PCR reference. PES packets carry the compressed elementary stream data after that mapping is known.
This is why “take the first stream” is not a safe conversion policy. An MTS may contain multiple audio PIDs, alternate languages, commentary, and subtitles. Inventory them, audition the intended audio, and record both PID/stream index and language/name. If a result has wrong sound, the underlying cause is usually a mapping choice, not the destination filename.
- PAT: points from programme number to its PMT.
- PMT: identifies the programme’s component stream PIDs.
- PID: labels a particular transport-stream packet flow.
- PES: carries encoded audio/video data for a selected stream.
- PCR/PTS: help the decoder maintain programme timing.
Timing and Continuity Counters Reveal Real MTS Damage
Transport Stream presentation uses programme clock and presentation-time information. The PMT identifies the PCR PID, and PTS aligns a component for display. Continuity counters run per PID through values 0 to 15 for payload packets. A discontinuity or missing packet can break decoding, create a visible glitch, remove sound, or cause a timestamp jump. A conversion cannot honestly recreate media that was never read.
Compare a start event, a middle event, and ending event in source and output. A fixed sound shift points to trim or offset. Drift that grows points to rate/timestamp mapping or source continuity trouble. If the original fails at the same time, preserve the warning. Do not call a shorter export a repaired master simply because it plays to its own end.
A camera or Blu-ray title may be spread across several clips or controlled by a playlist. One physical .mts segment may not equal the logical feature. Check the source folder/playlist context where it exists before deciding that one file is the complete programme.
Compatibility Depends on Actual Codecs, Not the MTS Extension
M2TS can carry different permitted video and audio combinations. A player may recognize BDAV framing yet reject an audio codec, an AVC/VC-1 profile, high bit depth, HDR metadata, subtitles, or an unusual channel layout. AVCHD and Blu-ray workflows add their own profile restrictions. Test the named destination: a desktop inspection player’s success does not prove that an editor, television, upload service, or disc-authoring tool accepts the same streams.
Stream copy is valuable only when source codecs and target container/receiver actually match. If a new codec is required, encode once from the inspected source. Higher bitrate cannot restore source loss; enlarging dimensions cannot create detail; a downmix changes the source mix. Record the reason for conversion and exact receiver requirement.
For a current web delivery, choose a documented web target rather than assuming MTS will play in browsers. For preservation, retain the MTS file and accompanying playlist/disc context alongside any access copy.
MTS Inspection Findings and Conversion Consequences Compared
| Finding | What it means | Conversion consequence |
|---|---|---|
| 192-byte packets | BDAV adds four bytes before each TS packet. | Use an M2TS-aware reader; do not parse as ordinary TS blindly. |
| PAT/PMT | Programme tables map component stream PIDs. | Inventory tracks before selecting output. |
| PCR/PTS | Programme/component timing references. | Check source/output landmarks for sync. |
| Continuity gap | Possible missing payload packet in a PID. | Document source damage; do not claim recovery. |
| Multiple clips | One segment may be part of a logical playlist. | Check playlist/disc context before exporting a full title. |
| Codec mismatch | Container opens but a payload is unsupported. | Choose supported delivery codec or another target. |
MTS Questions to Answer Before You Convert or Delete Anything
Is MTS just an MPEG file?
No. It is commonly BDAV M2TS: a transport-stream form with 192-byte packets, programme tables, PIDs, and timing data.
Why does a tool report damaged packets?
It may be reading 192-byte M2TS as 188-byte TS, or the source may have continuity/timestamp damage. Verify framing first.
Why is the wrong language in my export?
An unintended audio PID was selected. Inspect and audition tracks, then record the chosen stream.
Why is duration different from the disc title?
A logical title can span playlist-controlled segments; one MTS file may be only part of it.
Should I delete original MTS after converting?
No. Keep it, its playlist/folder context, and notes on stream selection and warnings.
Use an evidence-first final audit for any MTS-derived delivery copy. Reopen the completed output after the writer has closed it. Confirm selected video/audio streams, duration, picture shape, expected language, channel layout, and source/output landmarks. Test a seek where the target supports it, then play the final seconds. If conversion uses a service, test the service’s delivered derivative as well; it can transcode or strip streams independently of the local conversion.
Record the original file name/path, associated playlist or disc context, source packet/stream report, selected PIDs, exact output settings, destination version, and observed warnings. This makes later review possible without inferring facts from an extension. It also prevents a repeated lossy conversion when another recipient requests a new format or needs a different audio language.