V2.0.0-alpha.22 — Cached images double in file size of original

[whollyjordan]

If I upload a 100 KB image, the cached version served on live page will be ~200 KB.

[marcantondahmen]

Is it a JPG? Then you should change the AM_IMG_JPG_QUALITY setting in the config. You can find more about the config file in the docs.

[whollyjordan]

Ooh. I am one of those "optimise my own images before uploading" types, so sounds like I need to turn off post-compression trickery. I'll go read the docs right now... thanks!

[whollyjordan]

As my own compression approach is superior, can compression in Automad be disabled?

[whollyjordan]

Update: "Is it a JPG?" — It is both PNG and JPG.

Even with compression set to 50, I have an example 60 KB image that Automad turned into a 200 KB file!

[whollyjordan]

Just to confirm this is how it is designed to work, here's an example:

I upload a PNG image (file size 60 KB).

I open the web page, and the image is now a JPG, and file size is 380 KB.

(Default settings.)

If I set compression to 50, it is still a big file size.

Thanks in advance for confirming (or otherwise) this behaviour!

[marcantondahmen]

No, if the source image is a png, the cached and resized version is also a png of course.

[whollyjordan]

Okay, thanks. What's happening for me is, when I add an image block, and enter the URL of an external PNG image, it converts to JPG.

If I UPLOAD the image instead, and select it, then it remains a PNG.

[marcantondahmen]

That's not really possible. Images are always cached in the same format that is given in the mime type of the original image. If you just provide an image url, the image is downloaded automatically and the mime type is checked. Is it possible that the mime type in your remote image is wrong?

[whollyjordan]

Re: wrong mime type —maybe! It isn't happening with all PNG files. So, clearly something about the one I tested is different.