JPG vs JPEG: Is There Really a Difference?

jpeg jpg: two spellings for one identical file format. There is no difference in quality, compression, or features between a .jpg and a .jpeg, both follow the exact standard the Joint Photographic Experts Group published in 1992. Rename one to the other and every byte in the file stays exactly where it was, only the label changes.

I get asked this jpg vs jpeg question more than almost any other format question, usually by someone staring at two files that look identical because they are. The short answer above is the whole story, and if you want the format itself explained end to end, compression, converting, choosing when to use it, that lives in the JPEG guide. This page covers just the one-letter difference: why it exists, when it can ever matter, and the proof that renaming touches nothing.

Why Do Both .jpg and .jpeg Exist?

Both extensions exist because of a computing limit that stopped applying three decades ago, not because the format itself changed. JPEG is four letters, and early Windows and MS-DOS could not save a file extension longer than three characters, so software of the era cut ".jpeg" down to ".jpg," and the habit never left. The formal standard the committee produced carries the dry name ISO/IEC 10918, though nobody outside a standards document ever calls it that, everyone just says JPEG.

The DOS Three-Letter Limit

MS-DOS and Windows before Windows 95 used the 8.3 filename convention: at most eight characters for the name, then a period, then at most three characters for the extension (Wikipedia, 8.3 filename). ".jpeg" needed a fourth letter the file system would not allow, so it got trimmed to ".jpg," and every program saving a JPEG on those systems followed suit. When Windows 95 added support for long filenames, the restriction disappeared, but by then ".jpg" was the default in enough software, and enough cameras, that switching back never had a reason to happen.

Why Mac and Unix Never Needed To Shorten It

Unix and early Mac systems never had an 8.3 filename limit, so they kept the full four-letter ".jpeg" from day one (Adobe Community). That is the entire origin story: one operating system family had a hard character cap, the other did not, and thirty years after the cap stopped mattering, both spellings are still floating around because nobody had a reason to standardize on just one.

What Does JPEG Actually Stand For?

JPEG stands for Joint Photographic Experts Group, the committee that standardized the format in 1992. Part of the confusion is that one word is doing three jobs at once. JPEG is the name of the committee that wrote the standard, the name of the lossy compression method the standard describes, and the name of the file format that method produces. When someone asks whether jpg or jpeg is the right one, they are usually asking about the format, and the format is one thing with two file name spellings, not two competing things.

The compression itself works by slicing the image into small blocks of pixels, transforming each block's color information with the discrete cosine transform, the same kind of math used in most video codecs, then discarding the transformed values a viewer's eye is least likely to notice. That is why JPEG is lossy: the discarded values are gone for good, which is also why our own compressor's quality 80 default targets the point where the discarding is invisible at normal zoom, not the point where the file is merely small. Push the quality dial too low and the same math starts throwing away values a viewer does notice, which shows up as blocky squares along edges, the visible fingerprint of DCT compression pushed past what a photo can absorb.

How Do Computers Actually Identify a JPEG?

Not by the extension. Every JPEG file opens with the same two-byte marker, hex FF D8, followed by an application marker, and every decoder checks those bytes before it looks at the file name at all (Wikipedia, JPEG).

The extension is a hint for humans and for the operating system's file-type icon, nothing more. Rename a plain text file to photo.jpg and no image viewer will open it, because the first bytes are not FF D8, they are the ordinary text of the file. Rename a real JPEG the other way, from .jpg to .jpeg or the reverse, and every decoder opens it instantly, because those first bytes never moved. This is also why a JPEG saved under either extension displays identically in every browser, on every operating system, and in every photo app: they are all reading the same marker structure at the start of the file, never the file name. That same marker structure is also where EXIF metadata lives, the camera model, GPS coordinates, and capture timestamp a camera writes right after the opening marker. It rides along in the container regardless of whether the file is named .jpg or .jpeg, which is why our own tool strips it by default when you compress a photo here, that data has nothing to do with how the image looks, it just travels with the file until something removes it.

JPEG JPG: Are They Really Identical?

Yes, completely, and that settles the jpeg jpg debate before it starts: a .jpg and its .jpeg twin holding the same image are byte-for-byte the same file. Only the characters after the dot change, and even those are two accepted spellings of the same standard.

The Rename Proof

Take any JPEG on your computer, duplicate it, and rename the copy from .jpg to .jpeg, or the reverse. Run a checksum on both files and they match exactly. I did this with a 50,000-byte test file: the SHA256 hash came back as 45fe22162beb09011f6d7720b9421bec2bace86ee20843e95315ec1f2a1fff68 for the original .jpg, and the identical 45fe22162beb09011f6d7720b9421bec2bace86ee20843e95315ec1f2a1fff68 for the renamed .jpeg copy. Renaming a file changes the operating system's label for it, not one byte of what is inside. That is the whole mechanism. There is no hidden re-encode, no quality step, nothing to lose. You can reproduce this yourself in about thirty seconds: a single sha256sum command on Linux or Mac, or any free checksum utility on Windows, will show the same string for both files every time.

One Real Exception: Case-Sensitive Servers

The one place the letters actually matter has nothing to do with JPEG itself: some web servers are case-sensitive and will fail to serve an uppercase .JPG file where a lowercase .jpg was requested. It is a server configuration quirk, not a format difference, but it is the actual bug people hit while chasing what they assume is a jpg versus jpeg problem. Save web images in lowercase and the issue never comes up.

The Difference Between JPG and JPEG: A Side-by-Side Look

Nothing about the image changes, only the label. The table below lists every property side by side, and every row on the .jpg side matches the .jpeg side exactly.

The format also answers to more than two spellings. Adobe's own list includes .jpg, .jpeg, .jpe, .jif, .jfif, and .jfi (Adobe, JPEG file), and browsers add .pjpeg and .pjp for a progressive-specific variant on top of that. .jpg and .jpeg are just the two spellings anyone actually sees day to day, because photo editors default to one of them. I have saved thousands of these over the years, and Photoshop and GIMP both write .jpg on Windows and on Mac, which is a large part of why the three-letter form still dominates even though the DOS limit that created it stopped applying in 1995.

Is JPEG 2000 or JPEG XL the Same Format?

No, despite the similar name, JPEG 2000 and JPEG XL are different, mostly incompatible image formats, not additional extensions for the same JPEG standard.

JPEG 2000, saved as .jp2, uses wavelet-based compression instead of the block-based DCT compression the original format uses, and it never picked up meaningful browser support outside specialized medical and archival software. JPEG XL is a newer, separately standardized format built for both lossy and lossless compression at better ratios than the original, and browser support for it is still limited and inconsistent as of this writing. Neither one opens as a normal .jpg or .jpeg file, and neither is what people mean when they ask whether jpg or jpeg is different, that question is always about the one 1992 standard with two spellings, never about these newer, separately named formats. If a tool or a camera ever hands you a .jp2 or a .jxl file, treat it as its own format needing its own converter, not a third spelling to add to the .jpg and .jpeg list.

Do You Ever Need to Convert Between JPG and JPEG?

No conversion step exists because none is needed, only a rename, and a rename is not the same operation as compression.

Compression is a different operation entirely, and it is the one that actually changes bytes. Feed a JPEG through real compression, for example the JPG compressor on this site set to quality 80, and the file gets smaller because the pixel data is re-encoded, not because a letter changed. Our homepage demo file goes from 497 KB to 214 KB as a WebP at that same quality setting, a real 56.9 percent smaller, because that step touches the actual image data. Renaming changes a label. Compressing changes bytes. Those are not the same operation, and confusing them is the root of most jpg vs jpeg questions that turn out to actually be about file size.

Some of that confusion comes from apps that silently do both at once. A messaging app or a social platform can re-encode a JPEG on upload, often keeping the same .jpg extension the whole time, so the file looks unchanged by name while the actual bytes shrank considerably. That is a real compression step happening behind the scenes, not a jpg-versus-jpeg effect, and it is why two .jpg files with the same name can still be very different sizes. If a photo looks softer after you post it somewhere, the platform's own compression is almost always the reason, not the extension it arrived with.

When Should You Use JPEG At All?

JPEG, saved as jpg or jpeg, it does not matter which, is built for photographs: continuous tone, lots of color variation, no hard edges that need to stay sharp.

Line art, logos, screenshots with flat color, and anything with text goes through the same lossy pipeline and comes out worse, with visible ringing and smudging along sharp edges, because JPEG's compression math assumes photographic noise, not flat color and clean lines (MDN, choosing an image format). For that kind of image, a lossless format like PNG is the right call instead, since PNG keeps every pixel exact and handles transparency, which JPEG cannot do under either extension. For a photo you are emailing, uploading, or publishing to the web, JPEG under either extension is still the right default.

Common Mistakes About JPG and JPEG

The extension does not define the file, the header does, and neither extension is higher quality or compresses better than the other. Three specific claims come up often enough that they are worth naming and closing off one at a time.

The Extension Defines the File

False. A JPEG is identified by the actual bytes in its header, the marker structure covered above, not by whatever three or four letters follow the dot. Renaming a PNG to .jpg does not turn it into a JPEG, most software still reads the real format from the file header and either displays it correctly or refuses to open it, sometimes with a confusing error that blames the wrong thing.

Neither Extension Is Higher Quality

Also false, and it is the myth I see argued most often, including in the occasional forum thread that gets it backward and insists one extension compresses better. A .jpg saved at quality 80 and a .jpeg saved at quality 80 from the same source produce the same result, down to the byte, because they are the same compression standard applying the same math to the same pixels. There is no version of JPEG that is secretly the good one. Whatever quality difference someone thinks they see almost always traces back to a different quality setting, a different source photo, or a second re-save, never the three versus four letters after the dot.

Re-Saving Does Not Restore Quality

Also false, and it applies equally to both extensions. JPEG is a lossy format, so once detail is discarded during a save, a later re-save at a higher quality setting cannot bring it back. It only re-compresses whatever is left, which is why repeatedly opening and re-saving the same JPEG, in either extension, degrades it a little more each time, an effect sometimes called generation loss.