Yes — you can cut most of a JPG's weight without any visible quality loss. I tested it on three real photos: a single image dropped from 606 KB to 241 KB, a second squeezed to an exact 100 KB target came out at 79 KB, and a batch of four fell from 5.60 MB to 2.47 MB.

That is 60%, 87% and 56% saved — on the same photos, with no change you can see at normal viewing size. The trick is not a secret setting. It is checking the result at full zoom instead of trusting a number on a slider.

The three tests, with real numbers

I ran the tests on ordinary photos, not special test images. Each one went through the same tool, in the browser, with nothing uploaded. The point was to see what normal settings actually do, not what a marketing page claims.

One photo, quality mode

The first photo started at 606 KB. I compressed it once, at the default quality setting, and it came out at 241 KB. That is 60% of the file gone, and at normal viewing size the two versions look the same. I only saw a difference when I zoomed in close and hunted for it.

One photo, exact target size

The second test used target-size mode. I set the target to 100 KB because that was the budget for the page. The tool returned a file of 79 KB, which is 87% smaller than the original. Hitting an exact size matters when a platform caps uploads or a page has a strict weight budget.

Four photos, bulk mode

The third test was a batch of four photos, compressed together. They started at 5.60 MB combined and finished at 2.47 MB, saving 56%. Bulk mode matters because nobody compresses one image at a time on a real site. A product page or a blog post has a dozen images, and doing them one by one is how the job never gets done.

What actually loses quality

Three things change a JPG: quality, dimensions and format. Quality is the slider most tools show you. Dimensions are the pixel width and height. Format is JPG versus PNG versus WebP. Most of the damage people blame on compression actually comes from resizing badly or saving in the wrong format.

Lowering quality removes detail your eyes cannot see at normal size. That is why a file can shrink by more than half and still look identical. The loss only shows up when you push the slider too far, or when you zoom in past 100% and look for it. At the size readers actually see, it is not there.

Google's guide to compressing images makes the same point: the goal is the smallest file that still looks right, not the lowest number on a slider.

Dimensions are the bigger lever when a photo is displayed small. A photo far wider than its display size carries far more data than the page needs. Resizing it first, then compressing, beats compressing alone every time. Check the display size before you touch the quality slider.

Format is the third choice, and it is simple. Use JPG for photos. Use PNG only when you need transparency. WebP gives smaller files than JPG at the same visible quality, and most browsers support it now. If your audience includes very old browsers, keep a JPG as the fallback. MDN's image format guide lists which browsers support WebP and which still need a fallback.

The workflow I use now

After those three tests, I settled on a short workflow. It takes a few minutes for a batch, and it works for blog images, product photos and portfolio shots alike. Here it is, in order.

  1. Check the display size first. If the image shows smaller than its real size, resize it to the display width before anything else.
  2. Compress once, at a middle quality setting, and check the result at 100% zoom. If it looks clean, stop there.
  3. If you have a hard budget — say 100 KB for a page-speed target — use target-size mode and let the tool hit it exactly.
  4. Do the whole batch at once instead of one file at a time. That is the only way a backlog of images actually gets finished.
  5. Convert to WebP when the platform accepts it, and keep the JPG for anywhere that does not.

I ran all three tests with a free tool that can compress jpg images in the browser, with bulk mode and an exact target-size mode. Nothing is uploaded, so the photos never leave your device.

Mistakes that cost quality

The most common mistake is compressing the same file twice. Each pass throws away more detail, and the second pass has nothing good left to keep. Always compress from the original, never from an already compressed copy.

The second mistake is saving a photo as PNG because it feels safer. PNG is lossless, so it sounds better. For a photo, it usually means a file several times larger than the same image as a JPG, with no visible benefit. PNG is for graphics and transparency, not photos.

The third mistake is upscaling. If a photo is small, enlarging it will not add detail — it only makes the blur bigger, and then compression makes it worse. Use the photo at its real size, or pick a larger original.

The last mistake is skipping the zoom check. A thumbnail hides everything. Open the compressed file at 100% and look at faces, text and edges. If those are clean, the file is good. If they are not, raise the quality and try again.

What the numbers mean for a real page

A single photo at 241 KB instead of 606 KB loads faster on a slow connection, and it costs the reader less data. A batch that drops from 5.60 MB to 2.47 MB is the difference between a page that feels heavy and one that feels instant. The savings add up because a page rarely has one image.

The 79 KB result matters most for strict budgets. Some platforms cap uploads, and some pages have a weight target to meet. Target-size mode takes the guessing out of it: set the number, get a file under it, and move on. That is the feature I now reach for first when a limit is involved.

FAQ

How much can I compress a JPG without losing quality?

In my tests, between 56% and 87% came off with no visible difference at normal viewing size. The exact amount depends on the photo — busy, detailed photos compress less than simple ones — so always check the result at full zoom.

What quality setting should I use?

Start in the middle, around 80, and check the result at 100% zoom. If it looks clean, stop. If you can see damage, raise the setting and try again. There is no single right number — the photo decides.

Is 100 KB enough for a photo on the web?

Yes, for most web photos. My target-size test produced a 79 KB file that looked clean at full zoom. Large hero images shown full-screen may need more room, but for blog and product photos, 100 KB is a sensible budget.

Do I need to upload my photos to compress them?

No — not with a tool that runs in the browser. The photos I compressed never left my device, because the work happens locally. That also means there is no queue, no account and no waiting for an upload.

Does compressing a JPG twice make it smaller?

Yes, but it costs quality each time. Each pass throws away detail, and the second pass has less good data to work with. Compress once, from the original file, and keep the original safe in case you need it again.

The short version

The short version is simple: check the display size, resize first, compress once, and look at the result at full zoom. My three tests saved 60%, 87% and 56% — and none of the photos looked worse. Start with the biggest image on your slowest page. That is where the win is.