You've got two photos. One ends in .jpeg. One ends in .jpg.

Somewhere in your head, a quiet voice asks: is one of these better? Higher quality? More compatible? Should I convert one to the other?

No. Stop. They are the same thing.

Not similar. Not related. Identical. Same format, same compression, same bytes. The only difference is one letter in the filename — and that letter exists because of a limitation in an operating system from the 1980s that hasn't mattered since Windows 95.

That's the whole answer. But the story behind that missing letter is genuinely good, and knowing it will save you from ever paying attention to this "difference" again. It'll also tell you the few weird cases where the extension does trip things up — and what to do about them.

The format: one standard, one committee

JPEG stands for Joint Photographic Experts Group — the committee that built the standard. Their work became ISO/IEC 10918, created in 1992, also published as ITU-T Recommendation T.81, after a process that started back in 1986.

The committee's own site calls it one of the most successful multimedia standards ever defined, and it's hard to argue. Three decades later, JPEG is still the most dominant still image format around. Every camera, every browser, every phone, every image tool on earth reads it.

Notice what the standard defines: how the image data is compressed and stored. Not what the file is called. The bytes inside a .jpeg file and a .jpg file follow the exact same specification. The extension is a label on the box. The box contents don't change when you relabel it.

The missing letter: blame DOS

So why do two spellings exist?

Because early PC filesystems physically couldn't store the fourth letter.

MS-DOS used the FAT filesystem, which allowed a maximum of eight characters for the filename and three characters for the extension — the famous "8.3 filename," documented to this day in Microsoft's own filesystem naming conventions. Eight for the name, a dot, three for the extension. That was the hard ceiling.

JPEG has four letters. DOS allowed three. So on PCs, .jpeg became .jpg. Nothing philosophical about it — the letter simply didn't fit.

Meanwhile, Unix and Mac systems never had the three-letter restriction, so their users kept the full .jpeg extension while the DOS and Windows world standardized on .jpg.

Then Windows 95 arrived with long filename support, and the 8.3 limit stopped mattering. But by then, millions of PCs, programs, and habits had settled on .jpg. Extensions are sticky. The workaround outlived the problem — by three decades and counting.

That's the entire "JPEG vs JPG" debate. A 1980s storage constraint, fossilized into a filename.

If you want to see the fossil for yourself, it's still in Windows. The 8.3 system lives on as "short names" — Microsoft's docs describe how long filenames get an auto-generated 8.3 alias, the tilde names like PROGRA~1 you've seen in old file paths. Modern Windows keeps generating them for backward compatibility. The constraint that renamed JPEG is not just history; it's still running quietly under your C: drive.

And JPEG wasn't the lone victim. The same squeeze gave the world .htm for HTML, .mpg for MPEG, and .tif for TIFF. Every one of those pairs is the same story: one format, two spellings, three-letter ceiling. JPEG's case just became the most famous because photos are the files normal people actually touch.

So which should you use?

Whichever you want. Truly.

If you need a tiebreaker: use .jpg. It's shorter, it's what most cameras and phones write, and it's what most people expect to see. Some picky web forms were coded by someone who only imagined one spelling, and that spelling is usually .jpg.

But there is no quality argument, no compatibility argument, no technical argument between them. Any software that reads one reads the other. A "JPG to JPEG converter" website is selling you a rename — the digital equivalent of charging you to rotate your hat.

Renaming is free and safe

Because the extension is just a label, changing .jpeg to .jpg (or back) is a rename, not a conversion. Zero risk, zero quality change, instant.

  • Mac: click the filename in Finder, edit the extension, confirm the change when asked.
  • Windows: enable file name extensions in Explorer's View menu, then rename.
  • Command line: mv photo.jpeg photo.jpg. Done.
  • A whole folder on Mac/Linux: for f in *.jpeg; do mv "$f" "${f%.jpeg}.jpg"; done

The pixels don't move. The compression doesn't change. You changed the sticker on the box.

One caution flowing the other direction: renaming only works between the two JPEG spellings, because the underlying file already is a JPEG. Renaming photo.png to photo.jpg does not make it a JPEG — it makes it a PNG wearing a name tag that lies. Some software will open it anyway by sniffing the actual bytes; other software will choke. Format changes need real conversion, not renaming.

And when a form demands JPG and what you're holding is a HEIC from your iPhone or a WebP saved from a browser, that's a real conversion. Do it on your own device. ConvertApps handles exactly this — HEIC, PNG, and WebP to JPG, in batches, entirely offline. Your photos never touch anyone's server just because a government portal was built in 2009. I've written before about why uploading files to random converter sites is a habit worth killing.

When the extension actually matters

Ninety-nine percent of the time: never. Here's the one percent.

Picky upload validators. Some web forms check the filename instead of the file contents. If the checklist says .jpg and you hand it .jpeg — or the reverse — a lazily coded validator rejects a perfectly valid file. Fix: rename and resubmit. Thirty seconds.

Uppercase extensions. Cameras love writing IMG_2041.JPG. Case-sensitive systems — many web servers, most Linux boxes — treat .JPG and .jpg as different strings. A web page pointing at photo.jpg while the server holds photo.JPG serves a broken image. Fix: lowercase your extensions before uploading anything to a server.

Ancient or rigid software. Old tools and inflexible corporate systems sometimes expect one spelling. Same fix as always: rename.

The MIME type, for the developers. On the web, the official media type is image/jpeg — regardless of which extension the file uses. There is no image/jpg in the standards. Browsers forgive it, validators don't. If you're setting headers, it's image/jpeg, always.

That's the complete list. Notice every fix is a rename.

What JPEG actually is (and its one real weakness)

Since we're here, it's worth understanding the format you use ten thousand times a year.

JPEG is a Huffman-coded, DCT-based lossy compression standard. Translation: it shrinks photos by throwing away visual detail your eye is least likely to miss — typically hitting compression ratios of 10:1 to 20:1 while looking nearly identical to the original. That efficiency on photographs is why it conquered the world.

"Lossy" is the key word, and it carries JPEG's one real gotcha: generation loss. Every time you edit a JPEG and re-save it as a JPEG, the compression runs again and quality degrades a little more. Save-edit-save-edit enough times and the smearing becomes visible. The quality slider in your export dialog controls how much detail each save throws away — higher quality, bigger file.

The practical rule: edit from originals, export a JPEG once at the end. Don't use a JPEG as a working file you repeatedly re-save.

Which format when: the 20-second table

The real question hiding under "jpeg vs jpg" is usually "which format should this file be?" Here's the answer:

You have... Use Why
Photos for the web, email, forms JPEG (.jpg) Universal, small, made for photographs
Screenshots, logos, diagrams, text PNG Lossless — hard edges and text stay crisp
Anything needing transparency PNG JPEG has no transparency at all
iPhone photos staying in Apple's world HEIC Smaller files, no compatibility pain inside the walls
iPhone photos leaving Apple's world Convert to JPEG HEIC still confuses non-Apple software and forms
Images for a website you control WebP Smaller than JPEG at similar quality, all modern browsers
Masters you'll edit repeatedly PNG or the RAW/original No generation loss while you work

Two takeaways from that table. JPEG remains the universal donor — when in doubt, when sharing, when uploading, JPEG works everywhere. And the formats that beat it technically keep losing on compatibility, which is why a 1992 standard still runs your camera roll.

This is also where format friction actually bites people: not jpeg-versus-jpg, but modern-format-versus-old-form. Your phone shoots HEIC, the insurance portal wants JPG, and suddenly you're googling converters at 11 pm. Keep the fix local — ConvertApps turns a batch of HEICs or WebPs into JPGs on-device, nothing uploaded, and the portal never knows the difference. The same logic applies to every file conversion you'd otherwise do on a website.

How to check what a file really is

Extensions can lie — anyone can rename anything. When an upload keeps failing or an image won't open, stop trusting the filename and check the actual contents.

  • Mac: select the file, press Command-I for Get Info, and read the "Kind" field. Or open Terminal and run file photo.jpg — it inspects the bytes and reports the true format, whatever the name claims.
  • Linux: same file command, same result.
  • Windows: open the image in any viewer and check its properties, or right-click > Properties > Details for the format information.

Two seconds of checking beats twenty minutes of fighting a form that keeps rejecting a "JPG" that's secretly a PNG. Mystery attachments from other people are the usual culprits — their tool saved one thing and named it another. And if the check reveals the file genuinely is the wrong format, convert it properly on-device instead of renaming it and hoping.

FAQ

Is JPEG or JPG higher quality?

Neither. They are the same format with the same compression — the extension has zero effect on quality. A .jpeg file renamed to .jpg is byte-for-byte identical. Quality in JPEG files is set by the compression level chosen when the image was saved, not by the filename.

Why do some files say .jpeg and others .jpg?

History. MS-DOS limited file extensions to three letters, so PCs shortened .jpeg to .jpg, while Mac and Unix systems kept the full spelling. The limit died with Windows 95, but both spellings survive. Which one you see depends on which tool saved the file.

Can I just rename .jpeg to .jpg?

Yes — it's completely safe in both directions. The extension is only a label; renaming changes nothing about the image data. What you cannot do is rename a different format (like PNG or HEIC) to .jpg and expect a real JPEG. Changing formats requires actual conversion.

Is JPG still the best format for photos?

For sharing and uploading, it's still the safest. HEIC and WebP compress better, but JPEG's universal support means it works on every device, form, and program without surprises. Best practice: keep originals in whatever your camera shoots, and export JPEGs for anything leaving your device.

Does converting HEIC or PNG to JPG lose quality?

Converting to JPEG applies lossy compression, so technically yes — a small amount of detail is discarded. At high quality settings the difference is invisible for normal photos. The bigger risk is repeated re-saving: convert once from the original and the loss is negligible; re-save the same JPEG over and over and it compounds.

The takeaway

JPEG and JPG are one format with two spellings, split by a three-letter DOS limit that died in 1995 — rename freely, convert locally, and never think about it again.

— Dolce