`f_auto` is not giving webp format even on Chrome.
Hi,
Our app is requesting images with `f_auto` parameter and some of the images are transformed to webp format on Chrome, but others are still served as jpeg.
How to solve this problem?
-
Hi,
Thank you for contacting us.
Can you please share with us some examples so that we can further investigate this?
Looking forward to your reply.
Thanks,
Raya0 -
Hi, I am having the same issues.

<img height="112" src="https://res.cloudinary.com/XXXX/image/upload/c_fill,dpr_auto,f_auto,g_auto,h_112,q_auto,w_380/Nikolassee.jpg" width="380">
I am using react and adding the images with componentDidUpdate to have them responsive.
componentDidUpdate() {
data.map((shop) => {
const {district} = shop
const element = this.refs[`img-${district.toLowerCase()}`]
const transformations = {
dpr: "auto",
width: element.clientWidth,
height: element.clientHeight,
gravity: "auto",
crop: "fill",
quality: "auto",
fetch_format: "auto",
}
const imgTag = cloudinaryCore.imageTag(`${district}.jpg`, transformations).toHtml()
element.innerHTML = imgTag
})
}Thx & Best Adrian
0 -
Hi Adrina,
Please check the Response Headers, there you should see the image actual format.
Please let me know if it helps you.
Best,
Yakir
0 -
thx for the tip, I looked it up and the response header has image/jpg in it
0 -
ok ... I just refreshed and now I got the WebP format. Does Cloudinary need some time to figure out the right format for an image?
Because I was clearing the cache and did a hard reloads before, too.
0 -
Hi Aricma,
I'm sorry for my late response.
Well, this feature should work immediately according to browser user-agent.
If you want us to deeply investigate this, please reach us at support@cloudinary.com.
Best,
Yakir
0 -
I had the same issue so I came here. When I checked the header, it was a WEBP as hoped.
So on windows when I right-click the image and save to run my tests I was been made believe it was a PNG (Says Windows) but in fact is was a WEBP.
Hope this adds
Daniel0
Post is closed for comments.
Comments
7 comments