MPG is the same MPEG-1 or MPEG-2 video as .mpeg, just the shortened extension DOS-era software required.
Common Uses
Video distribution
Broadcast media
DVD video
MPG Transformation FAQ
What is an MPG file?
+
MPG (MPEG) is a family of standards for coding audio-visual information.
What is an MPEG program stream, and why is my file one?
+
It is a multiplex designed to be decoded by fixed-function hardware in real time, not to be edited on a computer. Audio and video packets are interleaved with timing markers so a set-top box can start playing from anywhere in the stream, without an index and without buffering the whole file. That design is why MPG content plays on old equipment flawlessly and confuses modern software regularly. Contents are MPEG-1 or MPEG-2 video with MP2 audio; the muxing and the GOP structure are identical to a .mpeg file.
Why does broadcast and authoring software insist on MPG?
+
Because the whole chain was built on it. Playout servers, DVD authoring tools and ingest systems were specified around this format when it was current, and equipment with a twenty-year service life does not get re-specified. Files coming out of those systems are the format the system was designed to emit, not a choice anyone made recently. MPG is the extension DVD authoring software, older camcorders and broadcast ingest tools recognise, so it stays useful for those pipelines.
Is MPG the same format as its other extension?
+
Yes. This extension and the longer or shorter name you see alongside it describe one underlying format, and anything that reads either reads both. The two names are historical: an eight-character filename limit from the DOS era, a vendor naming its application rather than its file format, or two programs that simply defaulted differently. Converting either produces the same result, so use whichever extension the software at the other end is expecting.
Why will my browser not play an MPG file?
+
Browsers ship decoders for a deliberately short list of formats, and MPG is not on it — the licensing, the codec variety it permits, or simply its age keeps it out. The file is not broken and a desktop player will open it, but nothing you do to the page will make a browser render it. Converting to a web-native container is the only reliable route to inline playback. MPG inherits every MPEG-2 limitation — heavy bitrate, interlacing, no soft subtitles — plus the confusion of two extensions for one format.
Will MPG play on a phone or TV without flattening the battery?
+
Usually yes, because the chips in phones, tablets and televisions decode this kind of payload in dedicated silicon rather than on the main processor. That is the difference between a video that plays cool for two hours and one that heats the device and drains it in forty minutes. Where the format falls down is app support rather than decoding — the codec is fine, the wrapper is what a gallery app may refuse.
Should I still be saving new files as MPG?
+
Only if something downstream demands it. The format still opens, and there is no urgency about converting an archive that is not causing trouble, but it is no longer where the tooling or the efficiency is going. For anything new, a current format costs nothing extra and avoids the next round of this question a few years from now.
Where do subtitles go for an MPG file?
+
Beside it, or into the picture. MPG has no subtitle stream of its own, so the two options are a sidecar .srt file the player loads alongside the video, or burning the text into the frames during a re-encode. The sidecar keeps the subtitles editable and switchable but travels as a second file that is easy to lose; burning in survives any transfer but cannot be turned off afterwards.
Does it matter that MPG is over thirty years old?
+
Age itself is not the problem — several formats from that era are still perfectly good, precisely because everything has had decades to implement them. What matters is what the era assumed: small files, modest processors, no network, and features nobody needed yet. Where those assumptions still fit, the format is fine. Where they do not, that is the reason to convert. MPG is the same MPEG program stream as .mpeg — the three-letter extension is a DOS-era truncation, not a different format.
Does using MPG require a patent licence?
+
Not for you. The codecs involved are covered by patent pools, and the licensing is settled by the people who ship decoders — the phone, the browser, the operating system — long before a file reaches you. It is why the format is everywhere in hardware and why royalty-free alternatives exist at all, and it changes nothing about converting a file you already have.
Can I just rename the extension instead of converting MPG?
+
Almost never, and it is worth understanding why: the extension is a label, while the bytes inside are structured for one specific format. Renaming produces a file whose name promises something its contents do not deliver, and whatever opens it either refuses the file or misreads it. The one narrow exception is two formats that are genuinely the same container under different names — and even then a proper rewrap is safer than a rename.
What happens to my MPG file after the conversion?
+
It is deleted automatically. The upload and the converted result stay on our servers for about 24 hours, which leaves time to download the result, and are then removed by an automatic cleanup. The transfer runs over HTTPS in both directions. Nobody reads the contents, nothing is indexed, and nothing is passed to anyone else.
