Step 1: Provide your FLV files using the button above or by toss and let go.
Step 2: Click the 'Convert' button to start the conversion.
Step 3: Fetch your converted WebM files.
FLV to WebM Conversion FAQ
How do I convert FLV to WebM without re-encoding the video stream?
+
There is no stream-copy switch on this page. A few pairs copy a compatible video stream into the WebM container without re-encoding it, MKV to MP4 among them, which is quick and loses no quality. Most pairs re-encode the video. FLV typically holds Sorenson Spark or H.264 video with MP3 or AAC audio, wrapped in a stream format designed for RTMP delivery. WebM is deliberately narrow: VP8 or VP9 video (AV1 more recently) with Vorbis or Opus audio, and nothing else.
Can I add selectable subtitles once the file is WebM?
+
Yes. FLV has no usable soft-subtitle track, so subtitles for FLV content had to be burned into the picture or shipped as a separate sidecar file. WebM carries subtitles as their own selectable stream, so after conversion you can attach an SRT track the viewer can switch on, switch off or restyle.
Will the WebM play in a browser when the FLV would not?
+
Yes, and that is usually the whole reason for the conversion. An FLV embedded in a web page either shows a broken player or forces a download, because browsers ship no decoder for it. WebM plays inline through the native HTML5 video element with no plugin and no external application. WebM plays natively in every modern browser with no plugin, no licence fee and no patent exposure, which makes it the default for web-embedded video.
Is it worth converting old FLV recordings to WebM at all?
+
For anything you intend to keep, yes. FLV belongs to an earlier generation of video tooling and the software that reads it is steadily disappearing from phones, browsers and operating systems. Moving the footage to WebM now, while a clean decoder still exists, is the difference between an archive you can open in ten years and one you cannot. No current browser, phone or TV can play FLV — anything still in this container has to be moved out of it to remain watchable.
Will multi-track audio survive FLV to WebM conversion?
+
Usually not. Most conversions keep one audio track, the one with the most channels (normally the main mix), re-encoded for the WebM container, so commentary and alternate-language tracks are dropped. AVI, WMV, MPEG, FLV, VOB and M4V to MKV keep every track, and so does MP4 to MOV. To keep a different track, remux the FLV with that track first (VLC or ffmpeg can do this), then convert it. WebM is a strict subset of Matroska that Google published in 2010 specifically to give HTML5 video a royalty-free container.
Are subtitle tracks preserved when converting FLV to WebM?
+
On some pairs. MP4 to MOV keeps every text subtitle track. AVI, WMV, MPEG, FLV, VOB and M4V to MKV keep every subtitle track: text subtitles are copied or converted to SRT, and picture-based subtitles such as DVD or Blu-ray ones are copied as they are. MP4, MOV and WebM to MKV keep only the first subtitle track (as ASS), and MP4 to WebM keeps the first one as WebVTT. Other pairs, including MKV to MP4 or MOV and WebM to MP4, drop subtitle tracks, and the converter does not burn them into the picture. Subtitles that are already burned in stay, because they are part of the video frames.
What about MKV attachments (fonts, cover art) when going FLV to WebM?
+
MKV is the only mainstream container that stores arbitrary attached files (TTF fonts for ASS subs, JPG cover art, fan-translated PDF inserts). Going from FLV to WebM drops these attachments when WebM is not MKV — the elementary streams convert, but the attached payload stays in the source. Keep FLV as a backup if you depend on attached fonts.
Which codec does the WebM output use by default?
+
It depends on the WebM container. MP4, MOV and MKV output use H.264, which plays on practically every phone, browser and TV. WebM output uses VP9. AVI, WMV and MPEG output use the older codecs those formats were designed for. WebM is a poor fit anywhere outside a browser — video editors, phones’ native galleries and Smart TVs largely ignore it.
How does HDR (HDR10, Dolby Vision) survive FLV to WebM?
+
There is no HDR processing or tone mapping. When the video stream is copied (MKV to MP4 or MOV with the default settings), HDR10 passes through as it is. When the video is re-encoded, the HDR10 mastering metadata is dropped and Dolby Vision or HDR10+ data is not kept, and with a Quality, Resolution or Frame Rate setting some pairs also reduce the video to 8-bit colour, so an HDR FLV can look washed out in the WebM.
Why is my WebM file smaller / larger than the FLV after conversion?
+
It depends on what happens to the video. MKV to MP4 or MOV with the default settings copies the video stream unchanged, so the size stays close to the source. Most other pairs re-encode it: a high-bitrate FLV usually comes out smaller, while an already heavily compressed one can grow. Smaller File under Quality gives the smallest output, and H.265 in the Codec setting (MP4, MOV and MKV) is usually smaller than H.264 at similar quality but plays on fewer devices.
