How do I re-encode MPG to WebM without losing video quality?
+
Upload your MPG file and the converter runs a CRF-based re-encode targeting visually-lossless WebM output (CRF 18 by default, lower values = larger file / higher quality). The codec is chosen to match the WebM container — H.264 for broad-compat MP4, H.265 for size-efficient MKV, VP9 for WebM, AV1 for newer pipelines.
Which video codec does the WebM output use?
+
It depends on the WebM container. MP4 defaults to H.264 for the broadest playback support across phones, browsers, and Smart TVs. MKV defaults to H.265 / HEVC for roughly half the file size at equivalent quality. WebM defaults to VP9. The advanced options expose explicit codec choice if you need to override.
Will my audio track survive MPG to WebM conversion?
+
Yes. When MPG and WebM share an audio codec (e.g. both carry AAC), audio is re-muxed with no re-encode — bit-identical. When the codecs differ, audio is transcoded to AAC / Opus / Vorbis depending on what the WebM container supports. Multi-track audio (commentary, alternate languages) is preserved.
Can I keep the original framerate when converting MPG to WebM?
+
By default yes — a 24fps MPG stays 24fps in WebM; a 60fps MPG stays 60fps. If you need to change rate (e.g. interlaced 29.97 → progressive 30, or 60 → 30 for upload limits), the framerate option handles 3:2 pulldown, deinterlacing, and frame-blending in the same encode pass.
How much will the file size change going from MPG to WebM?
+
Same-codec re-mux (MPG H.264 → WebM H.264 just changing container): nearly identical size. Codec change can swing dramatically: H.264 → H.265 typically halves the file at the same visual quality; VP9 is roughly comparable; AV1 cuts another 20-30% but is slower to encode.
Will the WebM file play on iPhone, Android, and Smart TVs?
+
MP4 / H.264 plays natively on every modern device. MOV / H.264 plays on Apple devices and most TVs but not always on older Android. MKV needs VLC on iOS. WebM is browser-first. The advanced options include a "device compatibility" preset that picks the safest WebM codec / container for your target.
How long does converting a 1-hour MPG video to WebM take?
+
Same-codec re-mux is near-instant — 30 to 60 seconds for a 1-hour file. A full codec re-encode runs at roughly 0.3-0.7x source duration on our GPU pipeline, so a 1-hour MPG → WebM finishes in 18-40 minutes depending on resolution and target codec.
What is the maximum resolution supported for MPG to WebM?
+
Up to 8K (7680×4320) on Premium plans. Free conversions are capped at 4K (3840×2160) by the per-file size limit. HDR metadata (HDR10, HDR10+, Dolby Vision when present) is carried through where both MPG and WebM containers support it.
Is my MPG video private during conversion to WebM?
+
Yes. Uploaded video files are processed in isolated workers, never viewed by a human, never indexed, and deleted within minutes of completion. The retention window is documented at /privacy/ and we publish no training corpus from user uploads.
Can I crop, trim, or rotate during the MPG to WebM conversion?
+
Not in the same step — use /video-trim/ or /video-cutter/ to clip first, then run the MPG → WebM conversion. Chaining trim and convert is faster than re-encoding the entire MPG just to drop unused footage.
Why is the WebM file blurry compared to the MPG source?
+
Almost always a bitrate-too-low setting. Re-encoding from a high-bitrate MPG into a default-CRF WebM compresses heavily on motion-rich scenes. Push CRF down to 16-18, or set an explicit target bitrate matched to the MPG source, and the WebM regains its clarity.
Does the MPG to WebM converter handle subtitles?
+
Yes — embedded subtitle tracks (mov_text in MP4, SRT/ASS in MKV) are preserved when both MPG and WebM containers support them. Burned-in (hardsub) subtitles transfer automatically because they live in the video frame itself.