Understanding Image Transformations report
My team has inherited internal processes that utilize Cloudinary from a time when we lacked sufficient guidance and standards for the platform. As we research older code and gain a clearer understanding of our existing implementation, I'm trying to identify the sources of the prevalent transformations, and why they are being used.
In Programmable Media UI, under "Reports/Delivery Reports" there is a section for "Top Image Transformations." When I examine these transformations, I've noticed that some of them appear to not make much sense. Any insight into how these are presented would be appreciated.
Here is an example of a report for one of our product environments.
- It seems that for #1 and #2 we are doing basic format transformations (which doesn't seem to be best practice for optimization); does setting a format imply a
- #3 is really strange to me as it seems we are using
f_autobut also setting the format to
webpat the end of the chain. Is that correct, or is the declaration of
webpjust stating that that was the format determined to be best by the auto fetch format?
- #3 is also strange because it has flags for progressive and sanitize. Since sanitize is only used for SVG it doesn't seem relevant, and progressive is only used for PNG and JPG so that seems unneeded as well. It seems like the proper transformation for this entry should be
f_auto,q_autowithout anything else? Maybe those flags are present in case one of those applicable formats are uploaded? (Can flags be stringed together using a period, for some reason I thought it would need to be
I know we have some improper practices currently, but would like to identify my misunderstands first before addressing improvements.