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 .flv 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 .flv 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.
An .flv file is a Flash Video container, the format that powered most web video during the 2000s. YouTube, news sites, and early streaming platforms delivered .flv streams into the Flash Player plugin before HTML5 video replaced the whole stack. For this route the practical draw is very small container overhead and h.264/AAC content re-wraps to MP4 without any re-encoding — balanced against no mainstream player ships FLV support anymore, which is worth knowing before you commit a large batch.
The usual reason to take .flv 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 very small container overhead, which is exactly what you want for recovering clips downloaded during the Flash era.
| Aspect | AVCHD video (.mts) | Flash video (.flv) |
|---|---|---|
| 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 | a simple sequence of tagged audio, video, and script packets designed for progressive download and RTMP streaming |
| Strongest at | importing camcorder footage into Premiere, Resolve, or Final Cut | recovering clips downloaded during the Flash era |
| Weak spot | transport-stream packet overhead makes files larger than the same video in MP4 | no mainstream player ships FLV support anymore |
| 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 | an onMetaData script tag embeds duration, dimensions, and encoder details; there is no standard field set for titles or authorship |
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 .flv in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if FLV 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 FLV file. Outputs keep the original filename with the .flv extension.
Since mts is container-oriented and flv is container-oriented, the conversion preserves the source content exactly as stored; no additional compression pass is applied beyond what .flv 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.
No current browser can play .flv, since the plugin that decoded it was removed from Chrome, Firefox, and Edge at the end of 2020. VLC and ffmpeg-based tools still read the format reliably, which is how old files get rescued into MP4.
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 → .flv → .mts is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.