HTML publish delivers bigger PNG's

[Jbarrigon]

When publish to HTML the result PNG files in the image folder are bigger than the originals (example a 100kb files result in a 400kb file) i have check all the parameters and dont find where the problem could be.

[Colin Holgate]

It could be the PNG was optimized in some way. Try taking your published PNGs to tinyng.com, that should reduce their size a lot.

[cybertimeDev]

I have the same problem and yes, it was optimized by tinypng in my case but it's laborious if I have to adapt/overwrite my png's after every export. It should exist an option like "leave unprocessed" in the bitmap properties. In Adobe Flash Professional CC my optimized png's was unprocessed if I choosed the compression option "Photo (JPEG)" in the bitmap properties. Why was this changed? -.-

[Colin Holgate]

PNGs are lossless, but it's possible to have ones that are not 32 bit. Animate only knows how to export the 32 bit kind.

There is an option in Publish Settings where you can tell it not to overwrite the images folder. That way you could do one export, optimize the external PNGs, then publish updates without doing the images.

I would leave the optimizing until near the end. Also, tiny png do have a Photoshop plugin, which I sometimes use:

https://tinypng.com/photoshop

[cybertimeDev]

Thank you but all of this is not a good workaround.

Often I have to overwrite an image in my FLA, so the solution with no overwriting won't help here. If this option would exist in the bitmap properties of each item, it would be a solution.

The optimizing at the end is also not the best way, because I have to check the filesize before I send a preview to my client. Then the client sends me feedback which I have to incorporate. After exporting the new version I have to overwrite my PNG's again.

Further I don't understand why I can't choose 8, 24 and 32 bit at the bitmap properties, the only option is "Lossless". In the Publish Settings at tab Spritesheet I have the option. Why not at bitmap properties?

I really hope that Adobe will fix that in the next update.

[Colin Holgate · Accepted solution]

It's been years since we've been requesting customized 8 bit PNGs, but you could add a request too:

Feature Request/Bug Report Form

The way I really work is slightly different to the ways I've described so far, but maybe knowing how I do that will give you a work around that isn't too terrible:

At a point where, like you, I want to know what the size is of the final folder, and I'm showing the client, I will tiny png optimize what I have, and put that set of images on the server. I continue to work on it locally without optimizing, and generally speaking I do know if I have added some new bitmaps to the project. If I have, I optimize those ones and add them to the server folder.

If at some point I've done a lot of additions, or gotten confused, I will batch optimized the whole folder of images again. It doesn't take much time to do that.