Why JPG Has Survived as the Internet's Most Dominant Image Format

The internet is a visual place, and most of those visuals are JPGs. Not PNGs, not WebPs, not GIFs. JPGs. Even after more than three decades of competition from newer formats, JPEG compression remains the engine behind the majority of photographs shared, published, and stored online. That staying power is not an accident. It is the result of genuinely clever engineering, a critical moment in internet history, and a set of trade-offs that still make sense for most photography today.

Key Facts:
- JPG was standardized in 1992 by the Joint Photographic Experts Group, a committee of imaging and communications experts
- Lossy compression works by discarding visual data the human eye cannot reliably detect
- A JPG file can be 10 to 20 times smaller than the same image saved uncompressed
- The format still accounts for a large majority of photographic images on the web
- Image dimensions directly multiply file size, making output resolution a critical decision before exporting

The Group Behind a Three-Letter Name

The name JPEG is an acronym, standing for the Joint Photographic Experts Group, the standards body that developed and published the format in 1992. The group was a collaboration between the International Organization for Standardization and what was then called the CCITT, now known as the ITU-T. Their goal was straightforward: create a compressed file format for continuous-tone photographic images that could be transmitted and stored efficiently.

At the time, digital cameras barely existed outside of expensive professional equipment. But the committee could see where things were heading. Computers were getting faster. Storage was getting cheaper but was still painfully limited. Networks were coming. If you were going to move photographic images around electronically, you needed a format that could survive the constraints of the era.

The 1992 standard they produced turned out to be remarkably future-proof.

How Lossy Compression Discards What You Cannot See

The central mechanism behind JPG is lossy compression, which means the algorithm permanently removes some data from the image during encoding. This is the part that makes people nervous. Permanently remove data? That sounds destructive.

But here is the key insight. Not all data in a photographic image is equally visible to the human eye. The visual system is much more sensitive to brightness changes than to color changes. It is better at detecting gradual shifts in tone than sharp transitions in certain hues. It notices contrast differences in some parts of the visual field more readily than others.

JPG compression exploits these biological facts. The algorithm converts image data from the standard RGB color space into a format that separates brightness information from color information. It then applies what is called the Discrete Cosine Transform, breaking the image into 8x8 pixel blocks and expressing the color information in each block as a sum of frequencies, from low-frequency gradual changes to high-frequency fine detail.

The compression step discards the high-frequency components that are hardest to see, keeping the low-frequency information that contributes most to perceived image quality. The result is a file that looks nearly identical to the original at moderate compression settings, while occupying a fraction of the storage space.

At typical web compression levels, the difference between the original and the JPG is genuinely hard to see. The file, however, might be fifteen times smaller.

Why This Mattered So Much in the 1990s

To understand why JPG took over the web so completely, you have to remember the context in which it arrived. In the early days of the web, bandwidth was measured in kilobits per second, not gigabits. Downloading a single uncompressed photograph over a dial-up connection would have taken minutes. Web pages needed to be light enough to load before users gave up and disconnected.

JPG arrived at exactly the right moment. A photograph that might have been a multi-megabyte TIFF file could now be reduced to a manageable size without losing the visual character that made photography worth sharing. Browsers built in support for the format. Cameras began outputting JPGs directly. The cycle reinforced itself.

By the time broadband arrived and file sizes became less critical, JPG was already embedded deeply in software, hardware, and human habit. Every camera, every phone, every image editing application spoke JPG natively. Switching the entire ecosystem to something new is a significant undertaking, and for photography, JPG was doing the job well enough that the urgency was never quite there.

The Practical Difference Between a Good JPG and a Bad One

The format supports a quality scale, typically presented as a number from 1 to 100 in editing software. Higher numbers preserve more detail and discard less data. Lower numbers produce smaller files with more visible compression artifacts, the blocky patterns and color smearing that become obvious when a JPG is saved at very low quality.

For web use, a quality setting somewhere between 70 and 85 hits the sweet spot for most photographs. The files are small enough to load fast, and the image looks clean enough that viewers do not notice the compression.

Getting the most out of that range means starting with the right source. You want to compress JPG files after you have already made your editing decisions, not before. Re-compressing an already-compressed JPG stacks the losses. The first compression removes data you cannot see. Subsequent compressions start removing data you can see.

This is why photographers typically work in a lossless format during editing and export to JPG only as a final step for web delivery.

The Dimension Problem Most People Overlook

There is another factor that shapes how large a JPG file ends up being, and it has nothing to do with the compression algorithm itself. It is the number of pixels in the image.

A photograph shot at full resolution on a modern smartphone might be 4000 pixels wide and 3000 pixels tall. That is 12 million pixels. Compress it at quality 80, and you still get a file that is significantly larger than what most web pages actually need. The compression has done its job, but you are compressing a much bigger canvas than necessary.

Web images are usually displayed at much lower resolutions than the original capture. A hero image on a blog might need to be 1200 pixels wide at most. A thumbnail might need 400 pixels. Exporting at the native camera resolution and then relying on the browser to scale it down wastes bandwidth and slows load times.

The decision about output dimensions also connects to the shape of the image. Choosing the right aspect ratio before you export prevents unnecessary cropping, stretching, or empty space that increases file size without adding visual value. A 16:9 image forced into a square container does not serve the layout, and a square image that should be widescreen creates problems for the reader. Matching the ratio to the display context before exporting is a step that saves storage and improves the experience.

Why Newer Formats Have Not Replaced It

WebP, AVIF, and HEIF all offer better compression than JPG at equivalent visual quality. In some tests, AVIF files are about half the size of equivalent JPGs. That is a genuinely meaningful improvement.

And yet JPG persists. The reason is support. JPG works everywhere. Every browser, every operating system, every image viewer, every photo printing service, every social media platform accepts it without hesitation. WebP had spotty support for years before it became universal. AVIF is still gaining ground. HEIF, the format Apple uses natively on iPhones, still does not open in Windows without additional software.

For developers and photographers who need a format that will work without any compatibility concern, JPG remains the safe, reliable choice. The file size disadvantage is real but often acceptable given the zero-friction compatibility.

The Format That Redefined What Photos Could Do Online

JPG did not survive three decades by accident. It survived because it solved a genuine problem with an elegant approach, arrived at the moment the web needed it most, and embedded itself so deeply in the infrastructure of digital photography that replacing it requires overcoming enormous inertia.

The psychovisual tricks behind the Discrete Cosine Transform are still as mathematically sound as they were in 1992. The trade-off between file size and image quality is still one of the most important decisions in web publishing. And the format that pioneered this trade-off is still the one most photographers, developers, and content creators reach for by default.

Knowing how JPG works, where its limits are, and how to get the most out of it makes you better at working with images on the web. The format is old. But the thinking behind it is as relevant as ever.