Initializing... drag & drop files here
Supports: FLV
FLV (Adobe Flash Video) is a dead format: Adobe ended support for Flash Player on December 31, 2020, and no current browser will play an FLV file. MKV (Matroska) is the opposite — an open, royalty-free container that holds almost any video and audio codec plus subtitles and chapters, and it's the format media servers like Plex and Jellyfin expect. Converting rescues your Flash-era clip into a container that desktop players and home-media libraries actually read. One thing to set expectations: the picture can't end up sharper than the original — early FLV is often low-resolution, and the conversion re-encodes that source, it never adds detail.
| Property | FLV (source) | MKV (output) |
|---|---|---|
| Full name | Flash Video | Matroska Video |
| Developer | Macromedia (2003), then Adobe | Matroska non-profit (open project, ~2002) |
| Standard | Proprietary | Open, royalty-free container spec |
| Typical video codecs | Sorenson Spark, On2 VP6, H.264 | Any — H.264, H.265, VP9, AV1, MPEG-4 |
| Typical audio codecs | MP3, AAC, Nellymoser, ADPCM | Any — AAC, AC-3, FLAC, Opus, DTS |
| Multiple audio tracks | One track | Many tracks in one file |
| Subtitles / chapters | None native | Soft subtitles, chapters, attachments |
| Browser playback | None (Flash EOL Dec 31, 2020) | Not native in Chrome/Safari; Firefox only began adding it in 2025 |
| Plays in | Legacy Flash players only | VLC, MPV, Plex, Jellyfin, Kodi, many modern TVs |
| Best for | (legacy web streaming) | Archiving and media-server libraries |
.flv file onto the page or click "+ Add Files." You can queue several clips and convert them all in one batch.FLV was in service for about fifteen years, so "an FLV file" could hold any of several generations of codec. What it holds decides how much the picture changes, because every conversion here decodes the source and encodes fresh output — there is no stream-copy shortcut, even when the codec on both sides is the same.
| Stream in the FLV | Era it came from | What the MKV gets |
|---|---|---|
| Sorenson Spark video (an H.263 variant) | Flash Player 6-7, roughly 2002-2005 | Re-encoded to H.264 — the biggest visible jump in codec, and the source is usually low resolution |
| On2 VP6 video | Flash Player 8 onward, roughly 2005-2008 | Re-encoded to H.264 — noticeably better source than Spark, still SD in most cases |
| Screen Video (FLASHSV) | Flash screencasts and tutorials | Re-encoded to H.264 — sharp-edged screen content softens slightly; keep the quality preset high |
| H.264 / AVC video | Flash Player 9 Update 3 (2007) onward | Re-encoded to H.264 again — same codec, one fresh generation, so use Very High to keep it invisible |
| MP3 audio | The classic Flash pairing | Re-encoded to AAC |
| AAC audio | Later, H.264-era FLV files | Re-encoded to AAC |
| Nellymoser audio | Flash microphone / voice-chat captures | Re-encoded to AAC — narrowband speech stays narrowband |
| ADPCM or raw PCM audio | Early Flash authoring exports | Re-encoded to AAC |
Pick MKV if the destination is a media server (Plex, Jellyfin, Kodi) or a long-term archive, or if you want subtitles and multiple audio tracks in one file — Matroska is an open, royalty-free container built for that. Pick MP4 if the file has to play in a browser, on a phone, or get uploaded to a social platform, because MKV is not natively supported by Chrome, Safari, iOS, or QuickTime. Both rescue the content out of the dead FLV container; they differ only in where the result will play.
It depends on what's inside the FLV. If the source already uses H.264 video, MKV keeps that codec and the re-encode stays at near-source quality — the "Very High" preset keeps any loss invisible. If the FLV uses an older codec like Sorenson Spark or On2 VP6, the video is re-encoded to H.264, a bigger lossy pass; the same "Very High" preset keeps that loss visually small. Either way the result can't look better than the source, so a low-resolution Flash clip stays low-resolution.
FLV depended on Adobe Flash Player, which Adobe stopped supporting on December 31, 2020, and began blocking from running on January 12, 2021. No mainstream browser ships a Flash runtime today, so the container is effectively dead for playback. The video and audio inside are usually intact — re-encoding them into MKV (or MP4) is how you get the content playing again.
MKV can carry soft subtitles, chapters, and many audio tracks — that flexibility is one of the main reasons to choose it. But FLV itself is limited to a single audio track and has no native subtitle support, so there usually isn't a second track or subtitle stream in the source to preserve. The benefit is forward-looking: once it's an MKV, you can add external subtitle files or extra audio tracks to your media-server copy.
MKV plays in VLC, MPV, Kodi, Plex, Jellyfin, and many modern smart TVs and media-streaming boxes, which is why it's the standard for home-media libraries. It does not play natively in most web browsers, on iPhones, or in Apple QuickTime. In our testing, an MKV produced here with the default H.264 + AAC codecs opened cleanly in VLC and played through a Plex server; if you need it on an iPhone or in Safari, convert to MP4 instead.
No. Matroska could technically hold the FLV's existing stream, but this page has no stream-copy path — the video is always decoded and re-encoded to the codec you choose, so even an FLV that already carries H.264 comes out with a fresh H.264 encode. In practice that costs one generation of loss, which the "Very High (Recommended)" preset keeps hard to see, and produces a file that is usually a little larger than a straight remux would have been. The upside is a predictable, standards-clean MKV that media servers will direct-play rather than trip over.
H.264, the default. Every Plex, Jellyfin, and Kodi client and effectively every direct-play smart TV decodes it in hardware, so the server hands the file over untouched instead of burning CPU transcoding it. The page also offers H.265/HEVC, AV1, VP9, VP8, MPEG-2, MPEG-4, Xvid, Theora and several legacy codecs inside the MKV — H.265 will make a smaller file but forces older clients to transcode, and the rest mostly narrow where the file will play. Given that a Flash-era source is low resolution to begin with, the space you would save with a newer codec is small; the compatibility you would lose is not.
Yes. Your file is uploaded over an encrypted connection, processed on our servers, and deleted automatically a few hours after conversion — no sign-up, no watermark, never shared or made public. The main practical limit on a very large FLV is upload time, not your device.