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 .divx 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 .divx 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.
A .divx file is video packaged for the DivX ecosystem: an AVI-derived container carrying MPEG-4 Part 2 video compressed with the DivX codec. The extension appeared on rips and downloads throughout the 2000s, when DivX certification logos on DVD players promised these files would play from burned discs. For this route the practical draw is decodes with any MPEG-4 Part 2 decoder, including ffmpeg and VLC and considerably better compression than the DVD MPEG-2 it typically replaced — balanced against obsolete next to H.264 and H.265, needing more bits for the same quality, which is worth knowing before you commit a large batch.
The usual reason to take .divx 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 decodes with any MPEG-4 Part 2 decoder, including ffmpeg and VLC, which is exactly what you want for playing movie archives from the 2000s downloading era.
| Aspect | AVCHD video (.mts) | DivX video (.divx) |
|---|---|---|
| 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 | aVI-compatible RIFF layout extended by the DivX Media Format with menus, chapters, and XSUB bitmap subtitles |
| Strongest at | importing camcorder footage into Premiere, Resolve, or Final Cut | playing movie archives from the 2000s downloading era |
| Weak spot | transport-stream packet overhead makes files larger than the same video in MP4 | obsolete next to H.264 and H.265, needing more bits for the same quality |
| 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 | inherits RIFF INFO tags from AVI, plus DivX-specific chapter and menu structures in Media Format files |
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 .divx in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if DIVX 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 DIVX file. Outputs keep the original filename with the .divx extension.
Since mts is container-oriented and divx is container-oriented, the conversion preserves the source content exactly as stored; no additional compression pass is applied beyond what .divx 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.
VLC, MPC-HC, and ffmpeg open .divx files as readily as AVI, and renaming to .avi works whenever the menu features go unused. No browser or mobile platform supports the format, and DivX-certified DVD hardware was the only native device support that ever existed.
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 → .divx → .mts is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.