0

I have a bunch of jpegs taken with a Nikon D3200 at 6016 x 4000. They weigh between 9M and 12M each.

To try and reduce space a bit, I compressed copies with the default Windows utility, and the new images are 3411 x 2268 and weigh between 0.4M and 0.5M. That is, there's been a 20:1 reduction in file size, while pixelwise the reduction is 3:1.

I look at the images in my screen, even zooming several times, and I struggle to see a difference in quality; I'm aware than I'm no expert, though.

So my questions are, what is a more normal rate for jpeg compression: 6016 x 4000 at 10M, or 3411x 2268 at 0.5M? Is there anything I should be worried that I'm losing from the original files?

3

The fact that should be realized is that your 6016 x 4000 pixel images are 72,192,000 bytes size before compression. That is roughly 69 MB, and is 3 bytes of R,G,B image data per pixel. That is simply the size of your RGB image data, 69 MB (uncompressed). That is 6016 x 4000 x 3 bytes per = 72,192,000 bytes of image data in every image. That is simply the size of your image data.

Then JPG is drastic compression, not lossless, meaning, the images do not decompress to be the same quality as before compression. The more compression, the worse they get. Here is an idea at my own site about that problem: https://www.scantips.com/basics09b.html

Your 9 to 12 MB compression is the "normal" reasonable size you ask about. That is already perhaps around 1/8 of the actual data size, which is already a tremendous reduction. That would be the cameras highest quality choice called Fine (Fine JPG Quality, as opposed to less quality). Your camera manual says 11.9 MB is the D3200 average typical file size. (different scenes can compress a little different, but in this ballpark.)

It would not seem reasonable to Not want high quality. Just use your cell phone if you don't want the best. :)

You can make image files smaller by resampling to fewer pixels, but still Fine JPG quality. That is camera Large, Medium, Small, which is just resampling. Resampling to 1/3 size in pixel dimensions is 1/9 size in area, and in bytes. That could be about right for your 1920x1080 video monitor, unless you needed to crop it substantially. Nothing really wrong with that except for printing prints larger than 6x4. But when you end up with the photo of your lifetime, you might wish it larger.

Or you can use extreme JPG compression, and pretty much ruin your images. Both resampling and JPG compresion are irrecoverable, other than going back to retake the picture.

Your 0.5 MB images should show their own faults. I hope you just made copies, and kept the original files too.

  • That stated goal was in fact the 1/9 bytes, more suitable for small uses like the HD monitor size.. But for myself, I think the archive should be left at original camera Large Fine size, for best quality for any future purpose. It is already compressed, and is simply the size of the image data, and disk storage space is inexpensive. Then make a copy for any smaller use. – WayneF Dec 3 '17 at 15:58
1

Jpeg is a compression-based image algorithm. Very roughly, instead of storing full color information for each pixel, it saves space by saying "hey, the next six pixels are all the same color". Bumping up the compression level makes this happen more often, despite the pixel colors not quite matching.

How much is too much? That depends on your needs (are you putting it on a website?), but mostly, when it no longer looks good - you've gone too far.


Separately, though, jpegs are lossy (when you make modifications, the image quality inherently degrades), so if you are concerned about keeping image quality, you should store the raw photo and use a raw image editor, like Lightroom.

  • Thanks for your answer. My question arose because I have family pictures from an event last week, and they take 1.5GB. That's why I tried shrinking them a bit, and I was surprised by the reduction in size. On my screen, even zooming substantially I cannot tell one version from the other. But before I erase the originals, I wanted to make sure I'm not missing anything. – Martin Argerami Dec 2 '17 at 20:27
  • 2
    Your casual description of "the next six pixels are all the same color" is somewhat similar to how e.g. GIF image compression works, but it isn't even in the same ballpark as how JPEG compression works. JPEG is a lot more complex and is based on a complex analysis of the colors and tonal patterns of pixels in each 8x8 block of the image. – twalberg Dec 2 '17 at 22:02
  • 1
    GIF and PNG are both lossless compression, both easily decompress to return EXACTLY the same image pixels. JPG is lossy compresson, no such guarantee or result, allowing it to take much more liberty with your data integrity, but then it can compress smaller, and you get back JPG artifacts. – WayneF Dec 2 '17 at 22:08
  • JPEG = This block of 16x16 pixels are all the same color. (JK) – xiota Aug 23 '18 at 10:00
  • @twalberg Hence "very roughly". The actual details of the compression algorithm are irrelevant to this question, only the idea of lossy compression, and going into the full description of how jpeg works would likely just lose people in the woods and obscure the answer to the actual question. – Xiong Chiamiov Aug 24 '18 at 17:55

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.