Add your AVI file
Drop one or more .avi 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 .avi video into .mts 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 .avi video into .mts audio keeps what you can hear and drops the picture entirely. 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.
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. For this route the practical draw is the transport-stream base survives card errors and interrupted recordings well and h.264 essence is often modern enough to re-wrap without re-encoding — balanced against transport-stream packet overhead makes files larger than the same video in MP4, which is worth knowing before you commit a large batch.
The usual reason to take .mts audio out of a .avi 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, no streaming support of any kind; on the target side, the payoff is the transport-stream base survives card errors and interrupted recordings well, which is exactly what you want for importing camcorder footage into Premiere, Resolve, or Final Cut.
| Aspect | AVI video (.avi) | AVCHD video (.mts) |
|---|---|---|
| Format type | Container — quality depends on the codecs and settings inside | Container — quality depends on the codecs and settings inside |
| How it stores data | interleaves audio and video chunks inside a RIFF file, with the codec identified by a four-character FourCC code | uses 192-byte transport packets, standard 188-byte packets plus a 4-byte arrival timestamp, matching Blu-ray's BDAV layout |
| Strongest at | playing back footage digitized from DV and Hi8 tapes | importing camcorder footage into Premiere, Resolve, or Final Cut |
| Weak spot | no streaming support of any kind | transport-stream packet overhead makes files larger than the same video in MP4 |
| Metadata | rIFF INFO chunks store basic fields such as title, artist, and encoding software, but nothing comparable to ID3 or MP4 atoms exists | 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 |
Drop one or more .avi 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 .mts in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if MTS 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 MTS file. Outputs keep the original filename with the .mts extension.
Since avi is container-oriented and mts is container-oriented, the conversion preserves the source content exactly as stored; no additional compression pass is applied beyond what .mts itself requires.
Yes — the .avi 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.
Editing suites and VLC handle .mts directly, while browsers, phones, and many TVs fail to recognize the extension even though they could decode the H.264 inside. Re-wrapping to MP4 usually restores playback everywhere without touching quality.
Much smaller — the video stream is usually 80–95% of a .avi 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, rIFF INFO chunks store basic fields such as title, artist, and encoding software, but nothing comparable to ID3 or MP4 atoms exists; 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 .avi → .mts → .avi is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.