A progressive JPEG stores the whole image several times over in rising detail, so it can appear blurry at first and sharpen as the rest arrives. A baseline JPEG stores it once, top to bottom. Both decode to exactly the same pixels. On our 55 test images the progressive file was about 3% smaller by median, so it is worth using for photos, but it is not a speed trick for Core Web Vitals: Largest Contentful Paint waits for the image to finish loading either way. For tiny images under about 10 KB, baseline is usually smaller.
What is the difference between a baseline and a progressive JPEG?
A baseline JPEG is written in one pass, so a browser that has only part of the file can show only the top of the image. A progressive JPEG splits the same data into several passes, called scans. The manual for cjpeg, libjpeg-turbo's encoder (dated Mar 24, 2026), puts it this way: "the data is stored in multiple scans of increasing quality," so "the decoder can use the first scan to display a low-quality image very quickly" and "can then improve the display with each subsequent scan."
| Baseline | Progressive | |
|---|---|---|
| How it arrives | Top to bottom, at full detail | The whole image, blurry, then sharper |
| Final image | The same pixels | The same pixels |
| File size | A little larger for most photos | A little smaller for most photos |
| Tiny images, like icons | Usually smaller | Usually a little larger |
| Opens in every browser and app | Yes | Yes |
The quality you get is set by the quality setting, not by the mode. Progressive only changes the order the data is stored in.
Is a progressive JPEG smaller?
Usually, by a few percent. The cjpeg manual says "the total file size is about the same, often a little smaller." We checked that on Nov 18, 2026 with the 55 PNG originals in the wall's Made by AI tag that are not photographs of people: landscapes, interiors, logos and game screenshots, from 0.6 to 8.3 megapixels (1.5 by median). We also shrank each one to 320 pixels wide, the size of a thumbnail, to see the small case. Each image was saved at quality 85 with Pillow 12.1.1 and libjpeg-turbo 3.1.3 in three ways:
- Baseline, Pillow's default.
- Optimized baseline, with
optimize=True, which makes an extra pass to build Huffman tables (the last, lossless step of JPEG compression) that fit this one image. - Progressive, with
optimize=True, progressive=True.
| Images | Baseline, median | Optimized baseline, median | Progressive, median | All together, baseline to progressive |
|---|---|---|---|---|
| 55 at full size | 245 KB | 244 KB | 237 KB | 18.4 MB to 17.2 MB |
| 55 at 320 wide | 16.3 KB | 15.8 KB | 15.5 KB | 821 KB to 772 KB |
The fair comparison is progressive against optimized baseline, since progressive files always get optimized tables:
- Files of 10 KiB and up (95 of the 110): progressive was smaller in 88, by 3.0% at the median.
- Files under 10 KiB (15 of them, mostly logo thumbnails): progressive was larger in 14, by 1.7% at the median.
- Pixels: we decoded every optimized baseline and progressive pair, and all 110 were identical, pixel for pixel.
So a part of what people credit to "progressive" is really the optimized tables, which a baseline JPEG can have too. The rest is a small real saving for anything bigger than a thumbnail. These are one wall's images, many of them made by AI, so treat the percentages as a guide, not a law.
Does a progressive JPEG improve Largest Contentful Paint?
No. Largest Contentful Paint (LCP) is the Core Web Vitals measure of when the biggest thing on the screen appears, and for an image that means the finished image. web.dev's guide to LCP (updated Sep 4, 2025) says plainly: "Images that haven't yet loaded aren't considered "rendered"." A progressive JPEG that shows a blurry first scan early is still counted at the moment its last byte has loaded and been painted.
Counting the early scans has been proposed. The issue "Refine LCP to take progressive loading into account" was opened on Jan 4, 2021 and was still open on Nov 18, 2026; its last comment, from Dec 7, 2022, says "Progress here is dependent on getting hard data RE the benefits (or lack thereof) of progressive image rendering." Until that changes, progressive is about how the wait feels, not about the score.
What does move LCP for an image is making it arrive sooner: serve it no wider than it is shown (what size images should be), use a smaller format where you can (AVIF vs JPEG XL vs WebP), and never lazy load the main image at the top (should you lazy load images). A progressive JPEG's few percent help a little with the first of those.
When should you use progressive, and when baseline?
| If the image is | Use |
|---|---|
| A photo or large image on a web page | Progressive |
| The main image at the top of a page, on slow connections | Progressive, plus the steps above for LCP |
| An icon, logo or small thumbnail under about 10 KB | Baseline, optimized |
| A file you keep as your original | Whatever your camera or editor wrote; do not re-save it just to switch |
How do you make a JPEG progressive without losing quality?
Convert the file you already have losslessly, rather than opening it in an editor and saving it again, which would compress it a second time. libjpeg-turbo's jpegtran does this. Its manual (dated Oct 7, 2026) says it "works by rearranging the compressed data (DCT coefficients), without ever fully decoding the image. Therefore, its transformations are lossless":
jpegtran -copy all -progressive input.jpg > output.jpg
-copy all keeps the EXIF and other metadata. If you are making the JPEG in the first place:
- cjpeg: add
-progressive, which, the manual says, "implies -optimize". - Python's Pillow:
image.save("out.jpg", quality=85, optimize=True, progressive=True), as Pillow's format guide documents. - ImageMagick: add
-interlace Plane. Its option reference says to "UseLineorPlaneto create aninterlaced PNGorGIForprogressive JPEGimage."
How can you tell if a JPEG is progressive?
- ExifTool:
exiftool -EncodingProcess photo.jpgprints "Baseline DCT, Huffman coding" or "Progressive DCT, Huffman coding", two of the values in ExifTool's JPEG tag list. - Pillow: a progressive file has a
progressivekey inImage.open("photo.jpg").info; a baseline one does not. We checked both ways on our test files.
Frequently asked questions
Does a progressive JPEG have lower quality?
No. At the same quality setting it holds the same image data in a different order, and our 110 pairs decoded to identical pixels. The early scans are blurry only while the file is still arriving.
Is converting to progressive lossless?
With jpegtran, yes: it rearranges the compressed data without decoding it. Opening the JPEG in an editor and exporting it as progressive is not lossless, because the editor compresses it again. Our post on what JPEG quality to use measured what each re-save costs.
Do all browsers support progressive JPEGs?
Yes. Progressive mode is part of the JPEG standard, and every major browser opens these files. How a browser draws the early scans while it waits is up to the browser.
Are WebP and AVIF progressive?
MDN's guide to image formats (updated Nov 5, 2026) says "AVIF does not support progressive rendering, so files must be fully downloaded before they can be displayed," and that JPEG XL files can be: "Most browsers can progressively render them by displaying an initial version before the full image downloads." An AVIF is usually so much smaller than the JPEG that it finishes sooner anyway, as our AVIF vs JPEG XL vs WebP measurements showed.
Should thumbnails be progressive?
Usually not. Under about 10 KB, progressive was larger in 14 of our 15 small files, and there is little to gain from drawing so small an image in stages.
What Heart Photos does
Heart Photos serves the images on its pages as AVIF, in the sizes each screen needs, so a visitor downloads a file much smaller than the JPEG and does not need a progressive one. Your upload itself is never saved again: a JPEG original is kept losslessly as JPEG XL, and Download Original hands you back the very file you uploaded, byte for byte, baseline or progressive just as it was.
To see it on your own images, open Heart Photos and upload one. For more on how much each choice costs, read what JPEG quality to use and what size images should be for a website.