The one-line truth
.jpeg and .jpg are the
exact same format. Converting one to the other is really just a
rename: zero quality loss, zero data change.
If you have ever downloaded a photo as image.jpeg and then hit an upload
form that only accepts .jpg, you have run into one of the most
confusing non-problems in computing. The good news: there is nothing wrong with your
file. Both extensions point at the same underlying JPEG image
standard, created by the Joint Photographic Experts Group.
So why do two extensions exist?
Blame early Windows. The FAT and FAT32 filesystems used by MS-DOS and early Windows
enforced an 8.3 filename rule — at most eight characters for the
name and three for the extension. "JPEG" is four letters, one too many, so it was
trimmed to JPG. Unix-like systems (and, later, the web) never had that
restriction, so .jpeg survived there. Today both work everywhere; the
split is purely historical baggage.
When the rename actually matters
Because the data is identical, 99% of the time you can swap the extension freely. The exceptions are software that is stricter than it should be:
- Legacy upload forms that match on the literal string
.jpg. - Old desktop apps with hard-coded file filters.
- Automated pipelines that route files by extension.
In every one of those cases, changing .jpeg to .jpg makes
the identical image sail straight through.
Convert it the safe way
A plain rename works almost always. When you want to be certain the file is a clean, standard JPEG — for example after editing or when metadata is acting up — a true re-save is the belt-and-braces option. The change-extension guide covers both routes on Windows, Mac, mobile and the command line.
Want the deeper story? Read JPEG vs JPG: what's the difference for the full, myth-busting explanation.