JPEG vs JPG: Are They the Same Thing?

JPEG and JPG. Same letters in the same order, except one has an extra E. Some files end in .jpg. Some end in .jpeg. Photoshop saves one way. Your phone saves another. Are they the same?

Yes. They’re identical. Same format, same files, same everything. The “missing E” is purely a historical filename quirk.

Here’s the full story.

Why two file extensions for the same format

In the early days of personal computing, MS-DOS and early Windows could only handle file extensions up to 3 characters long. So when the JPEG format was finalized in 1992 and people started saving JPEG images, they had to pick a 3-letter extension. They chose .jpg.

Meanwhile, on Mac, Unix, and Linux systems — which didn’t have the 3-letter limit — files were saved as .jpeg. The full 4-letter version of the abbreviation.

The result: the same exact file format ended up with two different file extensions on different systems. By the time Windows added support for longer extensions (Windows 95 and later), the .jpg convention was deeply embedded in everyone’s workflows.

Today, both extensions still exist, and both work identically.

What JPEG actually stands for

JPEG = Joint Photographic Experts Group. That’s the name of the committee that developed the image compression standard in the late 1980s and finalized it in 1992.

The committee was “joint” because it was a collaboration between two existing standards bodies: the ISO (International Organization for Standardization) and the ITU (International Telecommunication Union). They came together specifically to develop a standardized way to compress photographic images for digital storage and transmission.

The standard is technically called “ISO/IEC 10918.” Nobody calls it that. Everyone calls it JPEG.

Are the files truly identical?

Yes, in every meaningful way:

Same internal format: a .jpg and a .jpeg file with the same content are bit-for-bit identical
Same compression algorithm: same DCT (Discrete Cosine Transform), same quantization tables, same Huffman coding
Same software handles both: every image viewer, editor, browser, and operating system treats .jpg and .jpeg files identically
Same metadata structure: EXIF data, color profiles, embedded thumbnails — all stored identically

If you renamed a .jpg file to .jpeg, nothing about the file would change except its filename. It would open and display identically.

Why some tools save one way vs the other

Different software has different defaults:

Adobe Photoshop: defaults to .jpg when saving
GIMP: defaults to .jpg when exporting
Phone cameras (iPhone, Android): typically .jpg for the camera roll, sometimes .jpeg for screenshots and edited copies
macOS Preview: .jpg
Older Windows software: almost always .jpg
Some web exports: .jpeg (more semantically “correct” but historically less common)
Some scanning software: .jpeg

There’s no functional reason for any particular choice. It’s pure convention based on the software author’s preference. You can usually change the default in the export settings if you care.

When to use `.jpg` vs `.jpeg`

For 99% of users: just use .jpg. It’s the most common, works everywhere, and is what people expect.

The handful of cases where .jpeg might matter:

Filename-sensitive systems: a few automated systems are configured to look specifically for one extension. If a system isn’t accepting your .jpg uploads, try renaming to .jpeg (or vice versa).

Filename pattern matching: web servers or scripts that use file extensions to determine behavior might be configured for one or the other. Renaming usually fixes it.

Personal preference: some people just like .jpeg better because it’s the proper abbreviation. No functional impact.

For uploading to most websites, sending via email, or just saving photos: either works. The first one your software offers is fine.

What’s actually inside a JPG file

Regardless of which extension, JPGs contain:

Header bytes identifying the file as JPEG (starts with FF D8 FF in hex)
JFIF or EXIF metadata block with technical details and (often) camera/edit info
Quantization tables — settings for how aggressively the image was compressed
Huffman tables — settings for the entropy coding step
Compressed image data — the actual pixels, divided into 8×8 blocks
Optional embedded thumbnail — a small version for fast preview
End-of-image marker (FF D9)

The same structure regardless of .jpg or .jpeg extension. Software reads the file by examining the header bytes, not the filename.

Renaming files between extensions

If you have a folder of .jpeg files and want them all as .jpg (or vice versa), this is a pure rename operation — no actual file content changes.

On Windows:

Open the folder in File Explorer
View → File name extensions (turn on)
Select all files
Right-click → Rename
Type the new name with new extension

For bulk renames, the command prompt works: ren *.jpeg *.jpg in a folder renames all .jpeg files to .jpg.

On Mac:

Open the folder in Finder
Select all files
Right-click → Rename
Choose “Replace Text” → replace .jpeg with .jpg

On Linux/macOS terminal:

for f in *.jpeg; do mv "$f" "${f%.jpeg}.jpg"; done

Note: renaming the extension doesn’t change the file’s actual format. A misnamed file (like a .jpg that’s actually a renamed .png) won’t work properly. But for true JPEG files, renaming between .jpg and .jpeg is safe and immediate.

JPEG vs JPG vs JPEG 2000 vs JPEG XL

Just to make things slightly more confusing: there are newer “JPEG” formats that are not the same thing:

JPEG 2000 (extension .jp2 or .j2k): a different compression format developed in 2000. Better quality than original JPEG at similar file sizes. Never caught on widely; mostly used in specific industries (medical imaging, archival).

JPEG XL (extension .jxl): a newer format from 2021 that’s significantly better than original JPEG. Slowly being adopted; some browsers support it, many don’t yet. Promising long-term replacement for JPG.

When people say “JPEG” or “JPG” they almost always mean the original 1992 format, not these newer variants. The newer formats are explicitly named with their version numbers.

When NOT to use JPEG

JPEG is great for photographs. It’s bad for:

Text-heavy images (screenshots, scans of text): JPG compression artifacts make text edges fuzzy. Use PNG instead.
Graphics with sharp edges (logos, icons, diagrams): same problem. PNG handles these better.
Images with transparency: JPG doesn’t support transparency at all. Anything transparent becomes white when saved as JPG.
Images you’ll edit repeatedly: each JPG save loses a little more quality. Lossless formats (PNG, TIFF) keep quality across edits.

For “photo of something”: JPG is the right choice. For anything else: probably not.

File size comparison

For a typical 12-megapixel photograph:

JPG at quality 90: ~3.5 MB
JPG at quality 80: ~2 MB
JPG at quality 70: ~1.2 MB
PNG: ~25 MB (lossless, much larger)
TIFF uncompressed: ~36 MB
WebP at equivalent quality: ~30% smaller than JPG

JPG’s compression efficiency is part of why it took over: at “quality 85,” files are 10-20× smaller than uncompressed source, with no visible loss to most viewers.

TL;DR

JPEG and JPG are the same format — identical files, different filename extensions
.jpg exists because of old Windows 3-character filename limits
For new files, .jpg is the most common choice; .jpeg works equally well
Renaming between the two is safe — the actual file content doesn’t change
JPEG 2000 and JPEG XL are different (newer) formats — when people say “JPEG” they mean the 1992 original
For converting other formats to JPG: PNG to JPG, HEIC to JPG, WebP to JPG
For making JPGs smaller: Image Compressor