Add your MTS file
Drop one or more .mts files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
Pulling the soundtrack out of a .mts video into .mpg audio keeps what you can hear and drops the picture entirely. Free, private, and validated — the file never leaves your browser.
Batch files can each use a different output. Nothing uploads for local conversions.
Working inputs include camera RAW, browser-local audio/video, PDF, CBZ/CBR comics, office documents, ebooks, markup, 3D models, structured text, images, and archives.Pulling the soundtrack out of a .mts video into .mpg audio keeps what you can hear and drops the picture entirely. An .mts file is AVCHD footage as written to a camcorder's memory card, containing H.264 video inside an MPEG transport stream. Sony and Panasonic camcorders from the late 2000s onward filled SD cards with .mts clips, so the extension is familiar to anyone importing family or event video.
The .mpg extension is the three-letter spelling of .mpeg, applied to identical MPEG-1 or MPEG-2 program stream data. Files named .mpg and .mpeg are interchangeable at the byte level, so players and converters treat them the same and differ only in the label they display. For this route the practical draw is opens in everything from Windows Media Player to ffmpeg and decades of tooling make its behavior thoroughly predictable — balanced against dated compression wastes space compared with any modern codec, which is worth knowing before you commit a large batch.
The usual reason to take .mpg audio out of a .mts file is that only the sound matters — a talk, interview, song, or podcast segment. Keeping the video stream would waste storage, and a dedicated audio file is easier to trim, tag, and play. On the source side, transport-stream packet overhead makes files larger than the same video in MP4; on the target side, the payoff is opens in everything from Windows Media Player to ffmpeg, which is exactly what you want for working with recordings from PC TV capture cards.
| Aspect | AVCHD video (.mts) | MPEG video (.mpg) |
|---|---|---|
| Format type | Container — quality depends on the codecs and settings inside | Container — quality depends on the codecs and settings inside |
| How it stores data | uses 192-byte transport packets, standard 188-byte packets plus a 4-byte arrival timestamp, matching Blu-ray's BDAV layout | byte-for-byte the same program stream format standardized in ISO/IEC 11172 and ISO/IEC 13818 |
| Strongest at | importing camcorder footage into Premiere, Resolve, or Final Cut | working with recordings from PC TV capture cards |
| Weak spot | transport-stream packet overhead makes files larger than the same video in MP4 | dated compression wastes space compared with any modern codec |
| Metadata | recording date, camera settings, and GPS coordinates on some models are stored in the AVCHD folder's clip-info files rather than in the .mts stream itself | nothing beyond the raw stream itself, so titles and descriptions live only in the filename |
Drop one or more .mts files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
Select .mpg in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if MPG is selectable, the route is real and validated.
Press Convert. A WebAssembly FFmpeg build demuxes the audio track and re-encodes it locally; the video stream is simply discarded.
Each result is signature-checked before the download unlocks, so a failed encode can never masquerade as a valid MPG file. Outputs keep the original filename with the .mpg extension.
Since mts is container-oriented and mpg is container-oriented, the conversion preserves the source content exactly as stored; no additional compression pass is applied beyond what .mpg itself requires.
Yes — the .mts file is processed inside your browser tab and never uploaded. A WebAssembly FFmpeg build demuxes the audio track and re-encodes it locally; the video stream is simply discarded. Close the tab and the file is gone from memory.
Any application that accepts .mpeg files accepts .mpg without complaint, since the difference is purely historical. That covers VLC, Windows Media Player, and QuickTime Player, but not the HTML5 video element in any browser.
Much smaller — the video stream is usually 80–95% of a .mts file's weight, and it is discarded entirely. The remaining audio is re-encoded at the bitrate implied by your quality setting.
This converter strips container metadata deliberately (the FFmpeg command runs with metadata mapping disabled) so exported files do not leak recording details. In the source, recording date, camera settings, and GPS coordinates on some models are stored in the AVCHD folder's clip-info files rather than in the .mts stream itself; none of it is transmitted anywhere because the file never leaves your browser.
Yes — the reverse route exists as a separate tool. Bear in mind that round-tripping .mts → .mpg → .mts is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.