Add your M2TS file
Drop one or more .m2ts 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 .m2ts video into .mpeg 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 .m2ts video into .mpeg audio keeps what you can hear and drops the picture entirely. An .m2ts file is a BDAV transport stream, the container Blu-ray discs and AVCHD software use for high-definition video. Open a Blu-ray's BDMV/STREAM folder and every title is an .m2ts file pairing H.264, VC-1, or HEVC video with multichannel audio.
An .mpeg file holds an MPEG program stream: video and audio multiplexed together using the original MPEG-1 or MPEG-2 standards. These files come from Video CDs, DVD-authoring workflows, and older capture hardware, and they remain readable by virtually every conversion tool. For this route the practical draw is universally decodable, with all underlying patents expired and simple, robust structure that tools have parsed for thirty years — balanced against mPEG-1 and MPEG-2 need roughly twice the bitrate of H.264 for comparable quality, which is worth knowing before you commit a large batch.
The usual reason to take .mpeg audio out of a .m2ts 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, file sizes are very large, often tens of gigabytes per title; on the target side, the payoff is universally decodable, with all underlying patents expired, which is exactly what you want for handling digitized VHS or Video CD content.
| Aspect | Blu-ray transport stream (.m2ts) | MPEG video (.mpeg) |
|---|---|---|
| Format type | Container — quality depends on the codecs and settings inside | Container — quality depends on the codecs and settings inside |
| How it stores data | 192-byte packets whose arrival timestamps enable the precise buffer control disc players require | program streams were engineered for reliable storage media, in contrast to the error-hardened transport stream used for broadcast |
| Strongest at | archiving personal Blu-ray projects and camcorder discs | handling digitized VHS or Video CD content |
| Weak spot | file sizes are very large, often tens of gigabytes per title | mPEG-1 and MPEG-2 need roughly twice the bitrate of H.264 for comparable quality |
| Metadata | chapter and playlist information lives in separate CLPI and MPLS files on the disc, not inside the .m2ts stream | the program stream carries essentially no descriptive metadata; the specification predates any notion of embedded titles or tags |
Drop one or more .m2ts 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 .mpeg in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if MPEG 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 MPEG file. Outputs keep the original filename with the .mpeg extension.
Since m2ts is container-oriented and mpeg is container-oriented, the conversion preserves the source content exactly as stored; no additional compression pass is applied beyond what .mpeg itself requires.
Yes — the .m2ts 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.
Desktop players on every operating system decode MPEG-1 and MPEG-2 program streams, and no licensing barriers remain. Browsers never adopted the format for the HTML5 video element, so web delivery requires conversion first.
Much smaller — the video stream is usually 80–95% of a .m2ts 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, chapter and playlist information lives in separate CLPI and MPLS files on the disc, not inside the .m2ts stream; 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 .m2ts → .mpeg → .m2ts is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.