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 .wmv 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 .wmv 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 .wmv file contains Windows Media Video, Microsoft's proprietary codec family, almost always wrapped in an ASF container. The extension was everywhere on Windows XP-era PCs, from downloaded clips to Movie Maker exports, but it has faded as MP4 became universal. For this route the practical draw is excellent support across legacy Windows software and vC-1 encodes hold up reasonably well for their age — balanced against effectively abandoned by Microsoft itself, which is worth knowing before you commit a large batch.
The usual reason to take .wmv 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 excellent support across legacy Windows software, which is exactly what you want for playing old Movie Maker projects and family archives.
| Aspect | AVCHD video (.mts) | Windows Media video (.wmv) |
|---|---|---|
| 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 | aSF container carrying WMV1, WMV2, or WMV3 (VC-1) video, typically with WMA audio |
| Strongest at | importing camcorder footage into Premiere, Resolve, or Final Cut | playing old Movie Maker projects and family archives |
| Weak spot | transport-stream packet overhead makes files larger than the same video in MP4 | effectively abandoned by Microsoft itself |
| 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 | aSF content-description attributes hold title, author, copyright, and rating fields, plus extended attributes used by Windows Media Player libraries |
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 .wmv in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if WMV 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 WMV file. Outputs keep the original filename with the .wmv extension.
Since mts is container-oriented and wmv is container-oriented, the conversion preserves the source content exactly as stored; no additional compression pass is applied beyond what .wmv 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.
Windows 10 and 11 still play .wmv out of the box, but macOS dropped support after the QuickTime plugin era ended, and no browser or mobile OS will touch it. Conversion to MP4 is required for web or cross-platform use.
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 → .wmv → .mts is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.