MPEG to FLV Converter

How to Convert MPEG to FLV Online

1. Upload Your MPEG File: Drag and drop, or click "Add Files" to select a.mpg or.mpeg video. Both extensions are accepted, and batch conversion is supported — queue multiple files and convert them in a single session without re-uploading.
2. Pick Video Codec and Audio Codec: The default Video Codec for FLV is FLV1 (Sorenson Spark / H.263). Switch to H.264 if your RTMP server or player supports it — H.264 produces noticeably smaller files at the same quality. The default Audio Codec is AAC; MP3 is also a safe FLV-container choice for older Flash players.
3. Set Quality Preset, Bitrate, or Target File Size (Optional): Under File Compression, choose a Quality Preset (Highest, Very High, High, Medium, Low, Lowest), set a Specific file size in MB/KB, or fine-tune with Constant Bitrate, Variable Bitrate, Constant Quality, or Constraint Quality. Adjust Video resolution with Preset Resolutions (2160p, 1440p, 1080p, 720p, 480p, 360p, 240p, 144p), a Resolution Percentage, or custom Width × Height. Use Trim (Time Range) with a Start Time and Duration if you only need a clip.
4. Convert and Download: Click Convert. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — no sign-up, no watermark, never shared.

Why Convert MPEG to FLV?

MPEG (.mpg /.mpeg) is a Program Stream container built around MPEG-1 or MPEG-2 video and MP2 audio — the format that powered Video CDs, DVDs, and digital broadcast TV. FLV (Flash Video) was introduced by Macromedia in the early 2000s (Flash Player 6/7 era) and became the dominant web video container until HTML5 video and Adobe's Flash Player end-of-life on December 31, 2020. FLV is now a niche-but-still-needed format — primarily for RTMP ingest into live-streaming pipelines and for legacy systems that were built before HTML5 existed.

• RTMP live-stream ingest — RTMP (Real-Time Messaging Protocol) carries FLV-formatted streams from broadcasters into media servers. OBS Studio, Wirecast, vMix, Wowza Streaming Engine, NGINX-RTMP, and SRS all speak RTMP/FLV, even when delivering HLS or DASH to viewers. Converting an MPEG file to FLV lets you replay archive footage through an RTMP "stream-from-file" pipeline.
• Legacy CMS and LMS uploaders — Older content management systems, learning management systems, and e-commerce product-video uploaders built between 2005 and 2015 often hard-require.flv as the input format. Re-encoding from MPEG-2 keeps those systems working without re-engineering the back end.
• Digital signage and kiosks running embedded Flash runtimes — Some industrial kiosks, in-store displays, and museum installations still run embedded Flash projector binaries that loop FLV content. They cannot be retrofitted to MP4 without hardware replacement.
• Smaller files than MPEG-2 — MPEG-2 is an inefficient codec by modern standards (typical 4-9 Mbps for SD content). Re-encoding to H.264-in-FLV usually shrinks the file 3-5x at equivalent perceptual quality, useful for transferring legacy archives.
• Stream-replay testing — Engineers testing RTMP servers, transcoders, or low-latency CDN endpoints often need a steady supply of FLV test files at known resolutions and bitrates. Converting a known-good MPEG clip is the simplest way to generate them.

MPEG vs FLV — Format Comparison

Codec Choice Inside the FLV Container

Frequently Asked Questions

Which video codec should I pick inside the FLV container — FLV1 or H.264?

Pick H.264 if your downstream RTMP server, Flash projector, or player accepts it — every modern RTMP server (Wowza, NGINX-RTMP, SRS, Ant Media, OBS-as-relay) does, and you'll get roughly 3-5x better compression than FLV1 at equivalent perceptual quality. Pick FLV1 (Sorenson Spark / H.263) only when you're feeding a very old Flash Player runtime (FP 6-8) that predates the December 2007 H.264 update.

Why would I still need FLV in 2026 when Flash is dead?

The FLV file format and the Adobe Flash Player runtime are different things. Flash Player playback in browsers ended December 31, 2020, but FLV remains the standard ingest container for RTMP — and RTMP is still the most common way live broadcasters (Twitch, YouTube Live, Facebook Live, custom origins) get video into their CDN. OBS, Wirecast, vMix, and Wowza all still produce and consume FLV-wrapped streams. Legacy LMS, kiosks, and signage hardware add to the list.

Will the converted FLV play in Chrome, Firefox, Safari, or Edge?

No. No major browser has supported Flash or FLV playback since 2020-2021. To play an FLV locally, use VLC, MPC-HC, MPV, or PotPlayer — all of these handle FLV natively without Flash. For web playback, convert to MP4 instead with MPEG to MP4 (or FLV to MP4 if you already have an FLV).

My MPEG file is 4 GB — can I still convert it?

Yes, conversion happens on our servers so there's no fixed server-side cap. Very large MPEG-2 files (DVD-VOB rips, long broadcasts) benefit most from picking H.264 in the codec dropdown plus a Quality Preset of Medium or High — output will often be 3-5x smaller than the source. If you need a hard size target instead, use Specific file size and enter a value in MB.

How do I extract just one segment from a longer MPEG into FLV?

Expand Trim, switch from Unchanged to Time Range, then enter Start Time and Duration in either seconds or HH:MM:SS.sss format. Only the selected segment is encoded — useful for pulling a 30-second highlight out of a 2-hour MPEG-2 broadcast capture. For audio-only segments, see Audio Cutter; for trim-only with no codec change, see Trim MPEG.

What audio codec should I use — AAC, MP3, or something else?

AAC is the default and the best choice for new RTMP ingest — every modern Flash-era and post-Flash player supports AAC-in-FLV. MP3 is a safe fallback for very old Flash Player versions (FP 6-7) or for systems built specifically around MP3 audio. Avoid Nellymoser and Speex unless you have a specific legacy requirement; they're low-bitrate codecs designed for voice chat, not general audio.

Why does the converted FLV look softer than the original MPEG?

MPEG-2 typically encodes at 4-9 Mbps for SD content. If you select a Lowest or Low Quality Preset, or a small Specific file size, the encoder will drop bitrate well below that and you'll see softness and macroblocking — especially on motion-heavy footage. Bump the preset to Very High or High, or set a Constant Bitrate of 2-4 Mbps for SD and 4-8 Mbps for 720p, and the output will match the source perceptually.

Does the FLV container support 1080p or higher resolutions?

Yes when using H.264 — there's no hard resolution cap in the FLV file format itself, and H.264-in-FLV will encode 1080p, 1440p, even 4K cleanly. The original FLV1 (Sorenson Spark) codec was practically limited to standard-definition resolutions and looks poor above 720p. Pick H.264 from the Video Codec dropdown before increasing Preset Resolution to 1080p or higher.

Are uploaded files private?

Yes. files are processed on our servers and deleted automatically after a few hours and are not used for any purpose beyond converting them. There's no account requirement, no watermark, and no email harvesting.