I have this png header image with transparency that is quite large 2500x1236, but only 343KB. I don't need or want it that big, so I throw it in PS and crop it down to 1666x444 and save for web, png24 tranparency, and the new, much smaller image, comes out of Ps at 585KB. WTH? How could the file size nearly double when it should be cut nearly in half?

Is this a Ps quirk? Should I just always use a png optimizer like pngOut?


When you resize an image with only a few colors, the resulting file, whether it has larger or smaller dimensions, is likely to have more colors (due to interpolation) and therefore be less compressible. Also if you started with binary transparency the result will likely have full alpha, which is also less compressible. Finally, your "bit depth" (actually "sample depth") might have increased. To regain the high compressibility you'll need to reduce the colors, number of different alpha values, and sample depth to be like those in your original image.

  • oh yeah, you're right. the bit depth went from 8 to 32! I don't know if the original transparency is binary. Let me see what I can do with this new info and report back. ty. – Chris M May 17 '14 at 22:59
  • ok. got it. Using indexed colors with the web palette the file size is down to 234KB, however, this is closer to png8 and the drop shadows and gradients are quite degraded. and I had to merge all the layers to use indexed color. :-( – Chris M May 17 '14 at 23:10

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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