Add your MP4 file
Drop one or more .mp4 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 .mp4 video into .m2ts 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 .mp4 video into .m2ts audio keeps what you can hear and drops the picture entirely. An .mp4 file is a multimedia container that bundles compressed video, audio, subtitles, and chapter data into a single stream-friendly package. It is the default delivery format for nearly every phone, camera, and video platform, which makes .mp4 the safest target when a clip has to play everywhere.
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. For this route the practical draw is preserves full disc quality, including lossless audio tracks and seekable and damage-tolerant like every transport stream — balanced against file sizes are very large, often tens of gigabytes per title, which is worth knowing before you commit a large batch.
The usual reason to take .m2ts audio out of a .mp4 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, fewer track, attachment, and chapter features than Matroska; on the target side, the payoff is preserves full disc quality, including lossless audio tracks, which is exactly what you want for archiving personal Blu-ray projects and camcorder discs.
| Aspect | MP4 video (.mp4) | Blu-ray transport stream (.m2ts) |
|---|---|---|
| Format type | Container — quality depends on the codecs and settings inside | Container — quality depends on the codecs and settings inside |
| How it stores data | typically carries H.264/AVC or H.265/HEVC video with AAC audio, though the box structure also accepts AV1, MP3, and timed-text tracks | 192-byte packets whose arrival timestamps enable the precise buffer control disc players require |
| Strongest at | publishing video to the web, social media, or a client who has not specified a format | archiving personal Blu-ray projects and camcorder discs |
| Weak spot | fewer track, attachment, and chapter features than Matroska | file sizes are very large, often tens of gigabytes per title |
| Metadata | iTunes-style metadata atoms (title, artist, cover art) plus XMP and per-track language tags; ID3 is not native to the container | chapter and playlist information lives in separate CLPI and MPLS files on the disc, not inside the .m2ts stream |
Drop one or more .mp4 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 .m2ts in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if M2TS 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 M2TS file. Outputs keep the original filename with the .m2ts extension.
Since mp4 is container-oriented and m2ts is container-oriented, the conversion preserves the source content exactly as stored; no additional compression pass is applied beyond what .m2ts itself requires.
Yes — the .mp4 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 such as VLC and MPC-HC play .m2ts smoothly and editing software imports it, but no browser or mobile OS supports the container. Converting to MKV keeps every track, while converting to MP4 favors device compatibility.
Much smaller — the video stream is usually 80–95% of a .mp4 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, iTunes-style metadata atoms (title, artist, cover art) plus XMP and per-track language tags; ID3 is not native to the container; 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 .mp4 → .m2ts → .mp4 is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.