This is really a two part question, since I don’t fully understand how these things work just yet:
My situation: I’m writing a web app which lets the user upload an image. My app then resizes to something displayable (eg: 640×480-ish) and saves the file for use later.
My questions:
- Given an arbitrary JPEG file, is it possible to tell what the quality level is, so that I can use that same quality when saving the resized image?
- Does this even matter?? Should I be saving all the images at a decent level (eg: 75-80), regardless of the original quality?
I’m not so sure about this because, as I figure it: (let’s take an extreme example), if someone had a 5 megapixel image saved at quality 0, it would be blocky as anything. Reducing the image size to 640×480, the blockiness would be smoothed out and barely less noticeable… until I saved it with quality 0 again…
On the other end of the spectrum, if there was an image which was 800×600 with q=0, resizing to 640×480 isn’t going to change the fact that it looks like utter crap, so saving with q=80 would be redundant.
Am I even close?
I’m using GD2 library on PHP if that is of any use
JPEG is a lossy format. Every time you save a JPEG same image, regardless of quality level, you will reduce the actual image quality. Therefore even if you did obtain a quality level from the file, you could not maintain that same quality when you save a JPEG again (even at quality=100).
You should save your JPEG at as high a quality as you can afford in terms of file size. Or use a loss-less format such as PNG.
Low quality JPEG files do not simply become more blocky. Instead colour depth is reduced and the detail of sections of the image are removed. You can’t rely on lower quality images being blocky and looking ok at smaller sizes.
According to the JFIF spec. the quality number (0-100) is not stored in the image header, although the horizontal and vertical pixel density is stored.