What is an MTS File?
An MTS file is an MPEG transport stream commonly produced by AVCHD cameras, using the Blu-ray-derived variant whose 192-byte source packets add a four-byte timestamp header to each standard 188-byte packet. It stores compressed video, audio, timing information, and related stream data in a transmission-oriented container.
How MTS Files work
Files ending in .mts are typically camera-recorded transport streams inside an AVCHD directory structure. The same 192-byte packet structure also appears under the .m2ts extension on Blu-ray media and after some import tools rename clips, so the two extensions do not indicate different containers. They packetize compressed picture and sound with clock references, timestamps, and stream tables designed for continuous capture and playback. The same recording may also have playlist, clip-information, and thumbnail files elsewhere in the card hierarchy, so the standalone stream is not the whole camera package. In post-production, ingest software first detects the packet size because parsers that assume standard 188-byte packets lose sync on 192-byte source packets. It then probes the wrapper and codecs before preserving, remuxing, or transcoding according to editor support.
Key facts
- 1AVCHD commonly places MTS clips under a BDMV/STREAM directory; copying only those clips can discard playlist and clip metadata used by camera-aware tools.
- 2An MTS wrapper may carry AVC video with AC-3 or linear PCM audio, but the extension alone does not guarantee any particular payload combination.
- 3Transport-stream timestamps can wrap, jump, or reset across camera clips, so concatenating packet bytes may produce discontinuities even when playback seems continuous.
When MTS Files matter
Inspect MTS codecs before moving camera footage into editing or web-delivery workflows. Remux compatible streams to avoid quality loss, or transcode when the target editor or player lacks support.
Common use cases for file formats & compression
These examples cover file formats & compression broadly, not specifically MTS Files.
- Accepting heterogeneous uploads while producing a controlled set of delivery formats.
- Moving assets between cameras, editors, browsers, archives, and downstream APIs.
- Separating long-lived source files from compact derivatives optimized for a particular channel.
Working with file formats & compression
This guidance covers file formats & compression broadly, not just MTS Files.
A parser reads the file structure, identifies contained streams and metadata, and exposes them to a decoder or application. Conversion usually decodes the source representation and writes compatible information into a different structure or encoding.
This category covers file and bitstream formats, their structures, and the compression methods they use. A filename extension can be misleading, so evaluate the detected format, decoding support, metadata, transparency, color, timing, patents, and archival needs before choosing an output.
What you gain
- A suitable format preserves the properties a workflow actually needs.
- Standardized structures allow files to move between compatible tools and systems.
- Format conversion can improve delivery size, editability, or long-term accessibility.
What it costs
- Modern formats can save bandwidth but may need fallbacks for older clients and production tools.
- Converting to a simpler format can discard transparency, animation, metadata, color precision, or editability.
- Archival suitability, browser support, and editing support often favor different choices.
Before production
- 1Inspect the detected container, codec, MIME type, and magic bytes instead of trusting a suffix.
- 2Verify decoder support and preserve metadata, color, transparency, or timing when required.
- 3Retain the source when the chosen delivery format is lossy or tied to current software.