4 ms·

chrome keeps changing downloaded images to webP which is annoyin af. can't even find a way to disable it

acdha 6y ago
Are you sure that’s Chrome and not a website which selects the format based on the client’s advertised capabilities? I know Facebook did that and it confused a lot of people when a .jpg wasn’t a JPEG.
- unnouinceput 6y ago
  For me was the same problem on Chrome. Switched to Firefox, same sites are happy to let me save their images as .jpeg instead of .webp
  - anonymoushn 6y ago
    I thought this might have been caused by a difference in whether image/webp is included in the Accept header on requests for web pages (not requests for images), since some people who run web sites prefer to serve different html to UAs that support and do not support webp rather than serving different image formats at the same URL. But when I looked at the Accept header Firefox sends for pages, it included image/webp. So I'm not sure what these sites are doing.
crazygringo 6y ago
It's not and you can't. The website is service up the images as webP. Chrome is just giving you what the website gives you, there's nothing to "disable".
- bzb3 6y ago
  You could remove webp from the Accept header so the web server thinks your browser can't interpret webp. Not guaranteed to work, obviously.
- slipheen 6y ago
  There's an extension you can use to save it as a different format, but it's transcoding. https://chrome.google.com/webstore/detail/save-image-as-type/gabfmnliflodkdafenbcpjdlppllnemd https://chrome.google.com/webstore/detail/save-image-as-type... In theory, you could probably do some combination of altering the user agent, and/or blocking .onload for webp images (which is often used to detect webp support). If you changed both, most sites would probably serve you a jpg/png version.
LinuxBender 6y ago
Perhaps a site is giving you a different version of a file based on your user-agent? Try changing your user-agent and see if that changes. Or contact the website and ask them.
anonymoushn 6y ago
Chrome sends "Accept: image/webp" by default when requesting images. Some CDNs send webps to clients who send this header and original-format images to clients who do not.
tracker1 6y ago
Use the developer tools, right click on the image's request and from there copy as curl... paste in an editor and remove all the headers, etc and you should get a more compatible version.

Are you sure that’s Chrome and not a website which selects the format based on the client’s advertised capabilities? I know Facebook did that and it confused a lot of people when a .jpg wasn’t a JPEG.

unnouinceput 6y ago
For me was the same problem on Chrome. Switched to Firefox, same sites are happy to let me save their images as .jpeg instead of .webp
- anonymoushn 6y ago
  I thought this might have been caused by a difference in whether image/webp is included in the Accept header on requests for web pages (not requests for images), since some people who run web sites prefer to serve different html to UAs that support and do not support webp rather than serving different image formats at the same URL. But when I looked at the Accept header Firefox sends for pages, it included image/webp. So I'm not sure what these sites are doing.

crazygringo 6y ago

It's not and you can't. The website is service up the images as webP. Chrome is just giving you what the website gives you, there's nothing to "disable".

bzb3 6y ago
You could remove webp from the Accept header so the web server thinks your browser can't interpret webp. Not guaranteed to work, obviously.
slipheen 6y ago
There's an extension you can use to save it as a different format, but it's transcoding. https://chrome.google.com/webstore/detail/save-image-as-type/gabfmnliflodkdafenbcpjdlppllnemd https://chrome.google.com/webstore/detail/save-image-as-type... In theory, you could probably do some combination of altering the user agent, and/or blocking .onload for webp images (which is often used to detect webp support). If you changed both, most sites would probably serve you a jpg/png version.

LinuxBender 6y ago

Perhaps a site is giving you a different version of a file based on your user-agent? Try changing your user-agent and see if that changes. Or contact the website and ask them.

anonymoushn 6y ago

Chrome sends "Accept: image/webp" by default when requesting images. Some CDNs send webps to clients who send this header and original-format images to clients who do not.

tracker1 6y ago

Use the developer tools, right click on the image's request and from there copy as curl... paste in an editor and remove all the headers, etc and you should get a more compatible version.