What is an MTS File?
An MTS file is an MPEG transport stream commonly produced by AVCHD cameras. 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. 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 probes both wrapper and codecs, then preserves, remuxes, or transcodes according to editor support.
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.
A format may describe a container, a bitstream, or both, and the filename extension can be misleading. Evaluate decoding support, metadata, transparency, color, timing, patents, and archival needs before choosing an output.
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.
- 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 at scale
Guidance that holds across every file formats term in this glossary, not just MTS Files.
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.
Answer these 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.
How Transloadit helps with MTS Files
When MTS Files are relevant to your workflow, you can hand the surrounding file formats work to Transloadit instead of maintaining the processing stack yourself. Transloadit detects file and MIME information, filters inputs, and converts images, audio, video, and documents into formats suited to browsers, applications, archives, and downstream services.
Support for a specific codec, container, parameter, or combination can vary by Robot and processing stack. Check the linked documentation for the exact inputs and outputs available for your use case.