Step 1: Provide your MPG 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 M4V files.
MPG to M4V Conversion FAQ
How do I convert MPG to M4V without re-encoding the video stream?
+
When the MPG and M4V 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 M4V container and only the wrapper changes. A remux of a 1 GB MPG into M4V typically finishes in 5-15 seconds with zero quality loss.
Will multi-track audio survive MPG to M4V conversion?
+
Yes — every audio track in the MPG (director commentary, alternate languages, descriptive audio) is preserved in the M4V 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.
Are subtitle tracks preserved when converting MPG to M4V?
+
Soft subtitles (selectable tracks) survive when M4V 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 MPG to M4V keep chapter markers / DVD-style navigation?
+
Chapter metadata transfers between MPG and M4V 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, so converting AVI to M4V produces an unchaptered file unless you add markers manually.
What about MKV attachments (fonts, cover art) when going MPG to M4V?
+
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 MPG to M4V drops these attachments when M4V is not MKV — the elementary streams convert, but the attached payload stays in the source. Keep MPG as a backup if you depend on attached fonts.
Which codec does the M4V output use by default?
+
The default codec is chosen to match the M4V 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 MPG to M4V?
+
HDR static metadata (HDR10 mastering display values, max content light level) carries through to M4V 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 MPG commonly survives only into MKV with HEVC; converting to a M4V container that does not carry the DV layer flattens to HDR10.
Will the MPG to M4V converter keep variable framerate (VFR)?
+
MKV and WebM record real per-frame timestamps and handle VFR natively, so MPG VFR survives into a M4V 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 MPG to 24 / 30 / 60 fps M4V for problematic targets.
Why is my M4V file smaller / larger than the MPG 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 MPG (Blu-ray rip) to a low-bitrate M4V (web upload) is the most common reason for a dramatic drop.
Does the MPG to M4V 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 MPG into M4V are limited by disk I/O, not CPU — a 30 GB MPG typically remuxes to M4V in under a minute regardless of resolution. Re-encodes scale with pixel count.
Is my MPG file private during M4V conversion?
+
Yes — uploaded MPG files are processed in isolated workers and deleted within minutes of completion. We never view, store, retain, or share the content. See /privacy/ for the data retention window. The conversion pipeline runs on hardware we control end-to-end; no third-party APIs receive your file.
Can I trim, crop, or join MPG files during the M4V conversion?
+
Not in the same job — keep conversion focused on container / codec. Use /trim/ to clip the MPG first, then queue the MPG -> M4V step. For joining several clips into one M4V, the /merge/ tool stitches them on a per-codec basis (it remuxes when the inputs share a codec, re-encodes otherwise) and emits a single M4V file at the end.