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 .avi 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 .avi 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 .avi file is Microsoft's Audio Video Interleave container, one of the oldest video wrappers still in circulation. It stores video and audio in alternating chunks inside a RIFF structure, and the extension remains common on older camcorder captures and DivX-era rips. For this route the practical draw is simple, thoroughly reverse-engineered structure and virtually every desktop player and converter opens it — balanced against no streaming support of any kind, which is worth knowing before you commit a large batch.
The usual reason to take .avi 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 simple, thoroughly reverse-engineered structure, which is exactly what you want for playing back footage digitized from DV and Hi8 tapes.
| Aspect | Blu-ray transport stream (.m2ts) | AVI video (.avi) |
|---|---|---|
| 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 | interleaves audio and video chunks inside a RIFF file, with the codec identified by a four-character FourCC code |
| Strongest at | archiving personal Blu-ray projects and camcorder discs | playing back footage digitized from DV and Hi8 tapes |
| Weak spot | file sizes are very large, often tens of gigabytes per title | no streaming support of any kind |
| Metadata | chapter and playlist information lives in separate CLPI and MPLS files on the disc, not inside the .m2ts stream | rIFF INFO chunks store basic fields such as title, artist, and encoding software, but nothing comparable to ID3 or MP4 atoms exists |
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 .avi in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if AVI 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 AVI file. Outputs keep the original filename with the .avi extension.
Since m2ts is container-oriented and avi is container-oriented, the conversion preserves the source content exactly as stored; no additional compression pass is applied beyond what .avi 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.
Windows still opens .avi natively and macOS handles common variants through third-party players, though browsers never adopted the container. Whether a specific file plays depends entirely on the codec inside, so an old Indeo or Cinepak recording may need VLC even on Windows.
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 → .avi → .m2ts is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.