M2V to FLV Converter

Converting M2V to FLV: What This Tutorial Covers

You have an .m2v — a raw MPEG-2 video elementary stream, the video-only intermediate that DVD and broadcast authoring tools produce — and you need it as an .flv for a legacy player, an old CMS, or a media server that only ingests Flash Video. This walk-through covers the codec choice that decides whether the result is watchable, the rate-control setting that behaves differently here than on most pages, and the handful of errors that DVD-era MPEG-2 reliably produces.

How to Convert M2V to FLV

1. Upload Your M2V File: Drag the .m2v onto the page or click "Add Files". Several files can be queued and converted in one batch.
2. Pick the Video Codec: Open Advanced Options. "Video Codec" offers FLV, H.264, Flash Video and Flash Video (v2), and starts on FLV — Sorenson Spark, the H.263-derived codec that Flash Player has decoded since version 6. Choose H.264 instead if whatever plays the file is newer than about 2008.
3. Set the Rate Control (Optional): "File Compression" opens on Quality Preset. On this page, Constant Quality (a quantiser field labelled CRF that starts at 5), Constant Bitrate, Constraint Quality and Specific file size all give you more predictable results — the reason is in the walk-through below. "Video resolution" is on Keep original, and "Trim" is on Unchanged until you switch it to Time Range.
4. Convert and Download: Click Convert. Files upload over an encrypted connection, are processed on our servers, and are deleted automatically after a few hours. No sign-up, no watermark.

Walk-through: Which of the Four Codecs to Choose

The Flash Video container was defined by Adobe's Flash Video File Format Specification (version 10.1, 2010, the last public revision), which assigns a numeric codec ID to each payload it can carry. The four this page exposes are four different entries in that table, and two of them are not general-purpose video codecs at all.

The two screen-video entries are lossless-oriented codecs designed for screen recordings, so the encoder skips bitrate controls entirely for them. Point them at DVD footage and you get an enormous file that looks no better than the source. For real-world video, the choice is between Sorenson Spark for maximum compatibility with ancient players and H.264 for anything else.

Why the Quality Preset Behaves Differently Here

Quality Preset works one of two ways depending on the codec. For codecs with constant-quality encoding, it computes a quality target from your preset and the output resolution. Sorenson Spark has no such mode, so the preset falls back to scaling the source video's bitrate — and this is where .m2v is unusual:

• A raw MPEG-2 elementary stream stores no bitrate. ffprobe reports bit_rate=N/A at both stream and file level, because there is no container header to hold it.
• With nothing to read, the pipeline substitutes a fixed fallback assumption rather than your file's real bitrate, so the preset scales a number that has nothing to do with your footage.
• The practical effect: a high preset does not reliably mean "close to source quality" on this page, and a low one does not reliably mean "much smaller".

If output size or quality matters, do not rely on the preset. Set Constant Bitrate and name a figure in Kbps or Mbps, or use Constant Quality — for Sorenson Spark, the value in that field acts as a quantiser on a 1-31 scale where lower means better quality, and it starts at 5. If you have a hard size ceiling, Specific file size divides your target by the running time instead.

Common Errors and How to Fix Them

• "My browser won't play the FLV." Adobe Flash Player reached end of life on 31 December 2020 and no current browser can play FLV natively. This is expected, not a broken conversion — open the file in VLC or mpv, which decode FLV without any Flash component.
• "The output has no sound." An .m2v has no audio track to begin with; the format cannot store one. The Audio Codec dropdown still renders (AAC, ADPCM, MP3), but there is nothing for it to encode, so every output from this page is silent.
• "The file is enormous." You almost certainly selected Flash Video or Flash Video (v2). Those are screencast codecs that ignore rate control; switch to FLV or H.264.
• "The picture is squashed horizontally." DVD material is anamorphic — a 16:9 NTSC title is 720x480 pixels with a 32:27 sample aspect ratio. Any resize normalises the output to square pixels and loses that ratio. Resize with Width x Height and type display dimensions such as 854x480 (16:9) or 640x480 (4:3).
• "Moving objects have comb lines." The source is interlaced, and nothing in this pipeline deinterlaces. Deinterlace in a desktop tool before uploading if the combing matters.
• "It looks blocky even on the highest preset." Sorenson Spark is an H.263-era codec and simply cannot hold much detail. Re-run with H.264 selected, or accept the limit of the format.

When FLV Is the Wrong Answer

FLV survives in two places: old archives, and RTMP — live encoders such as OBS still push RTMP, which wraps its payload in FLV-style tags before the platform repackages it as HLS. Neither of those is a file you upload. If your actual goal is a video that plays on a phone, a browser, or a modern TV, FLV is a dead end and you should target a current container instead.

Frequently Asked Questions

Why is the converted FLV silent?

Because the source has no audio. .m2v is an MPEG-2 elementary video stream: a video-only bitstream with no container, which is exactly why DVD authoring uses it — the picture is encoded separately from the .ac3 or .mp2 soundtrack and the two are muxed at the end. Nothing is dropped in conversion; there was never an audio track in the file. To end up with sound, mux the audio back in with a desktop tool, or convert to a container-based target such as M2V to MP4 and add the audio there.

What can still play an FLV file in 2026?

Desktop players, not browsers. VLC, mpv and MPC-HC all decode FLV directly, and ffmpeg-based tools handle it fine. What no longer exists is in-browser playback: Flash Player was discontinued at the end of 2020 and every mainstream browser removed the plugin, so an .flv embedded in a web page will not play for anyone. If you need something a visitor can watch, convert FLV to MP4 afterwards or target MP4 in the first place.

Should I pick FLV or H.264 in the codec dropdown?

H.264 unless you have a specific reason not to. Both are legal FLV payloads — the format's codec table lists Sorenson H.263 as ID 2 and AVC as ID 7 — but H.264 arrived with Flash Player 9 and delivers dramatically better quality per bit. Sorenson Spark only makes sense when the software that has to read the file predates that: some Flash Player 6/7-era projectors, old Flash Media Server workflows and certain embedded devices really do only understand codec ID 2.

Does converting to FLV make the file smaller than the M2V?

Usually yes, sometimes dramatically, because MPEG-2 is extremely inefficient by modern standards and DVD video runs up to 9.8 Mbit/s. But the amount depends entirely on the rate control you choose, and the default preset is unreliable on this page because .m2v carries no source bitrate for it to scale. Set Constant Bitrate or Specific file size if size is the point of the exercise.

Can I convert only part of the clip?

Yes. The "Trim" section starts on Unchanged; switch it to Time Range and give a start time plus a duration, and only that section is encoded. This is worth doing on DVD rips, which often carry the whole title in one long stream. For frame-accurate work on the source instead, video cutter handles trimming as its own operation.

Why does the same clip look worse as FLV than as MP4?

Because you are usually comparing two different codec generations. With FLV selected, the payload is Sorenson Spark, an H.263 derivative from the early 2000s with no B-frames worth speaking of, coarse motion compensation and a small toolset. H.264 in an MP4 has two decades of coding tools on top. Selecting H.264 inside the FLV container closes most of that gap — the container is not what limits quality, the codec is.

Will interlaced DVD footage be fixed automatically?

No. There is no deinterlacing step anywhere in this pipeline, so 480i or 576i fields are encoded as-is and the combing stays in the picture. That is deliberate: automatic deinterlacing damages progressive footage that was wrongly flagged, and a bad guess is worse than none. Run a proper deinterlace filter locally first if your source is interlaced and the output is for viewing rather than archiving.

Is my file kept private during conversion?

Yes. The .m2v is uploaded over an encrypted connection, converted on our servers, and deleted automatically after a few hours, along with the FLV output. There is no sign-up, no watermark, and files are never shared or made public. We checked the claims on this page against a real MPEG-2 elementary stream: ffprobe identifies it as mpegvideo with no duration and no bitrate, which is exactly why the rate-control advice above matters more here than on a container-based source.