Initializing... drag & drop files here
Supports: MPG, MPEG
.mpg videos. Both .mpg and .mpeg are accepted, and batch conversion is supported..mpeg extension..mpg and .mpeg are two file extensions for the same MPEG program-stream container defined by ISO/IEC 11172 (MPEG-1) and ISO/IEC 13818-1 (MPEG-2). The shorter .mpg form exists because DOS and Windows 3.1 enforced 8.3 filenames — three-character extensions only — while macOS and modern Windows allow the full .mpeg. The codec, the container, the muxing, and the data inside are byte-identical. A simple rename is technically valid in the vast majority of cases.
That said, "rename" doesn't always solve real-world problems, and a true conversion pass through XConvert does:
.mpeg specifically — Some video editors, content management systems, school upload portals, and corporate ingest pipelines whitelist .mpeg and reject .mpg (or vice versa). A rename works locally but won't survive an upload form that validates extensions server-side after MIME sniffing — converting produces a file the server will accept on first try..mpg and .mpeg filenames in the same library breaks alphabetical sorting and confuses some media managers (Plex, Jellyfin, Kodi). Converting everything to one extension keeps the library clean.| Property | .mpg |
.mpeg |
|---|---|---|
| Underlying format | MPEG-1 / MPEG-2 program stream | MPEG-1 / MPEG-2 program stream |
| Standards body | ISO/IEC 11172 / 13818 | ISO/IEC 11172 / 13818 |
| MIME type | video/mpeg |
video/mpeg |
| Codec | Identical (MPEG-1 Video, MPEG-2 Video) | Identical |
| Audio | MP1 / MP2 / MP3 (Layer I/II/III) | MP1 / MP2 / MP3 |
| Origin of name | DOS 8.3 three-char limit | Full MPEG name |
| Player support | Universal (VLC, WMP, QuickTime, ffplay) | Universal |
| Practical difference | None at the data level — only the filename suffix | None at the data level — only the filename suffix |
The honest answer: at the byte level, none. A conversion is worthwhile when you also need re-encoding, trimming, resizing, or a guaranteed-clean program stream — not when you just want a different suffix.
| Aspect | MPEG-1 (ISO/IEC 11172) | MPEG-2 (ISO/IEC 13818) |
|---|---|---|
| Released | 1993 | 1995 |
| Designed for | VCD, CD-ROM video | DVD-Video, DVB broadcast, HDV |
| Typical bitrate | ~1.15 Mbit/s (VCD) | 4-9.8 Mbit/s (DVD) |
| Max resolution | 352×288 (Constrained Parameters) | Up to 1920×1152 |
| Interlacing | Progressive only | Progressive + interlaced |
| Audio | Layer I, II, III (MP1/MP2/MP3) | Layer I, II, III + AAC + AC-3 |
| Patent status | Expired | Expired worldwide (Malaysia exception until ~2035) |
Both are stored under .mpg or .mpeg. XConvert handles both transparently — drop in a 1996 VCD rip or a 2005 DVD rip and the converter detects the profile.
Yes. Both are MPEG program-stream containers defined by ISO/IEC 11172 (MPEG-1) and ISO/IEC 13818-1 (MPEG-2). The codec, container syntax, and data layout are identical. The only difference is the three-letter .mpg suffix (a holdover from DOS's 8.3 filename limit) versus the four-letter .mpeg suffix used on systems without that constraint.
Usually yes — and most desktop players (VLC, Windows Media Player, QuickTime) won't notice. But a rename fails when the receiving software validates extensions server-side, sniffs MIME types after upload, or expects a clean program stream that your file may not have. Converting through XConvert produces a file that passes those checks, with the bonus of optional re-encoding, trimming, and resizing in the same pass.
Only if you choose to re-encode at a lower bitrate. Pick Quality Preset: Very High to minimize visible loss, or use Constant Quality with a low quantizer for near-transparent re-encoding. If you want absolutely no loss and only need the extension to change, a local rename is technically equivalent — XConvert is the better choice when you also want a clean re-mux or trim.
MPEG-1 (1993, ISO/IEC 11172) was designed for Video CD at 352×240/352×288 around 1.15 Mbit/s, progressive only. MPEG-2 (1995, ISO/IEC 13818) added interlacing, higher resolutions up to 1920×1152, and the 4-9.8 Mbit/s bitrate range used by DVD-Video and DVB broadcast TV. Both share the same .mpg/.mpeg extension and the same program-stream container.
Re-encoding through any compression mode other than a one-to-one Constant Bitrate match produces a different file size. Specific file size explicitly resizes to a target. Constant Quality keeps visual fidelity steady but lets bitrate (and therefore size) float with scene complexity. Quality Preset picks reasonable defaults. If you want a near-1:1 size, set Constant Bitrate to match the source's original bitrate (visible in MediaInfo or VLC's Codec Information).
Yes. Switch the Trim option from Unchanged to Time Range, then enter the start and end timestamps. The output is just that segment, re-encoded as MPEG. This is common for pulling a 30-second highlight from a 2-hour camcorder dump or extracting a single chapter from an MPEG-2 DVD rip.
A generic MPEG-2 file isn't automatically DVD-compliant. DVD-Video has strict requirements on resolution (720×480 NTSC / 720×576 PAL), GOP structure, audio (AC-3 or MP2 at specific bitrates), and a VIDEO_TS folder layout — converting only produces the underlying video stream, not the disc structure. For DVD playback, author the converted MPEG with a tool like DVDStyler or burn it as a data disc your player can read. For modern smart TVs and streaming sticks, a plain .mpeg file usually plays straight from USB.
If long-term compatibility matters, yes — convert MPG to MP4 gives you H.264 video and AAC audio in an MP4 container, which streams natively in every modern browser, mobile app, and smart TV. MPEG-2 inside .mpg/.mpeg is fine for editing, archiving, and DVD workflows but isn't a web-streaming format. Reverse direction needed? See MPEG to MPG. Just shrinking without changing format? Try Compress MPG or Trim MPG.
Often, yes. Many legacy MPG captures (especially TV tuner recordings and TiVo extracts) have inconsistent or missing PTS/DTS timestamps that cause audio drift over long playback. A full re-encode through XConvert rebuilds timestamps from scratch, which usually resolves drift. If sync is already broken in the source by a fixed offset, you'll need a tool that lets you nudge audio delay (FFmpeg's -itsoffset or Audacity) — XConvert's pipeline assumes the source is internally consistent.