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 MPG files.
FLV to MPG Conversion FAQ
How do I convert FLV to MPG without re-encoding the video stream?
+
When the FLV and MPG containers can both carry the same codec (H.264, H.265, VP9, AV1), the converter falls back to a remux: the elementary streams are copied byte-for-byte into the MPG container and only the wrapper changes. A remux of a 1 GB FLV into MPG typically finishes in 5-15 seconds with zero quality loss. FLV typically holds Sorenson Spark or H.264 video with MP3 or AAC audio, wrapped in a stream format designed for RTMP delivery. Contents are MPEG-1 or MPEG-2 video with MP2 audio; the muxing and the GOP structure are identical to a .mpeg file.
Can the MPG hold more than one audio track?
+
Yes, and it is a real upgrade over FLV. MPG treats every audio stream as a first-class track, so an original-language mix, a dub and a director commentary can live in one file with the player switching between them on demand. MPG is the extension DVD authoring software, older camcorders and broadcast ingest tools recognise, so it stays useful for those pipelines.
Is there any point converting between two legacy formats like FLV and MPG?
+
Only if a specific piece of equipment demands the target. Both formats come from the same pre-H.264 era, so neither conversion buys efficiency, quality or future-proofing — it buys compatibility with one particular device. If the goal is to keep the footage usable long-term, convert to a current container instead of sideways. No current browser, phone or TV can play FLV — anything still in this container has to be moved out of it to remain watchable. MPG inherits every MPEG-2 limitation — heavy bitrate, interlacing, no soft subtitles — plus the confusion of two extensions for one format.
Will multi-track audio survive FLV to MPG conversion?
+
Yes — every audio track in the FLV (director commentary, alternate languages, descriptive audio) is preserved in the MPG when the target container supports multi-stream audio. MKV and MOV handle unlimited audio tracks; MP4 supports many but some hardware players only see track 1; WebM is capped at one Opus / Vorbis track. MPG is the same MPEG program stream as .mpeg — the three-letter extension is a DOS-era truncation, not a different format.
Are subtitle tracks preserved when converting FLV to MPG?
+
Soft subtitles (selectable tracks) survive when MPG can carry them: MKV holds SRT, ASS, SSA, PGS, VobSub natively; MP4 only holds mov_text (a stripped-down format). Converting an MKV with ASS styled subs to MP4 will typically downgrade them to mov_text or burn them in. Hardsubs (burned into the video) carry over regardless.
Does FLV to MPG keep chapter markers / DVD-style navigation?
+
Chapter metadata transfers between FLV and MPG whenever both containers support a chapter atom (MKV, MP4, MOV). WebM stores chapters in a Matroska-compatible block, so MKV <-> WebM chapters round-trip cleanly. AVI has no chapter spec at all, so an AVI source arrives with no chapters to carry across and an AVI target cannot store the ones it was handed; add markers manually afterwards if you need them.
What about MKV attachments (fonts, cover art) when going FLV to MPG?
+
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 MPG drops these attachments when MPG 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 MPG output use by default?
+
The default codec is chosen to match the MPG container conservatively: MKV defaults to H.265 (HEVC) for better compression; MP4 defaults to H.264 for the widest device support; WebM defaults to VP9; AVI uses MPEG-4 ASP (DivX/Xvid lineage). Override via the advanced codec dropdown — AV1 is available for MKV / WebM where you want maximum compression and can wait through the encode.
How does HDR (HDR10, Dolby Vision) survive FLV to MPG?
+
HDR static metadata (HDR10 mastering display values, max content light level) carries through to MPG when both containers and the chosen codec support it (HEVC, AV1 in MKV / MP4). Dolby Vision is more fragile — DV profile 5 / 7 / 8.1 in FLV commonly survives only into MKV with HEVC; converting to an MPG container that does not carry the DV layer flattens to HDR10.
Will the FLV to MPG converter keep variable framerate (VFR)?
+
MKV and WebM record real per-frame timestamps and handle VFR natively, so FLV VFR survives into an MPG of those formats with no resampling. MP4 nominally stores timestamps too but some players assume CFR; the converter exposes a "force CFR" toggle that resamples VFR FLV to 24 / 30 / 60 fps MPG for problematic targets.
Why is my MPG file smaller / larger than the FLV after conversion?
+
Same-codec remux produces a near-identical size (container overhead differs by 0.1-2%). A codec change can swing the size by 50% or more: H.264 to H.265 typically halves the file at the same visual quality; H.264 to AV1 halves it again on a slow preset. Going from a high-bitrate FLV (Blu-ray rip) to a low-bitrate MPG (web upload) is the most common reason for a dramatic drop.
Does the FLV to MPG converter handle 4K / 8K / 60fps content?
+
Yes up to 8K (7680x4320) on Premium. Free tier handles 4K (3840x2160) up to the 1 GB file cap. Pure remuxes (same-codec passthrough) of large FLV into MPG are limited by disk I/O, not CPU — a 30 GB FLV typically remuxes to MPG in under a minute regardless of resolution. Re-encodes scale with pixel count.
