Update May 15, 2025: Please note that JPEGmini functionality is planned to be deprecated in the near future. Any URLs that include q_jpegmini should be changed to use some form of q_auto instead (e.g. q_auto, q_auto:best, q_auto:low, etc.). For more information on these features, refer to the Cloudinary quality optimization documentation.
Yes. When using both q_jpegmini and f_auto:
- A WebP image will be delivered for supported browsers (i.e., Chrome) at a default quality of 100%.
- JPEG-XR will be delivered for supported browsers (i.e., IE) at a default quality of 70%.
- And JPG will be delivered (with the JPEGmini quality) for all other browsers, at JPEGmini's detected optimized quality.
For example:
http://res.cloudinary.com/demo/image/upload/s--GvV9jraa--/f_auto,q_jpegmini/v1334156373/brown_sheep.jpg
Please note that the JPEGmini Image Optimization add-on is no longer available for new registrations. If you are an existing subscriber to this add-on, we encourage you to use the automatic quality transformation (q_auto) instead.
For more information on JPEGmini, please see here:
https://cloudinary.com/documentation/image_optimization#how_to_optimize_image_quality
Comments
5 comments
I would like to know this as well :)
So, how can we achieve this?
It's "only" been a year and still no answer...
Hi Joacim,
While the question is in the title, the body of this KB article is actually the answer and the solution to the question. I'm sorry if this isn't clear.
Please let us know if you still need any assistance?
I got an error when added `q_jpegmini`. The imaged didn't load. Why would that happen?
Hi Tamarindo,
Can you please raise a support ticket here: https://support.cloudinary.com/hc/en-us/requests/new and include the URL of the image which threw the error and we can check the issue.
Please sign in to leave a comment.