Images won't save correctly after update
So I noticed this recently (sometime after the latest update) where now if I try to save an image it'll either 1) not add the right extension (like .png or .jpg) or will try to save it as a html document. I'm not able to add the extension in the name itself as then my programs just complain about it being an incorrect image format, and it's not any of my add-ons as I did try in safe mode as well and another browser (the other browser worked fine).
I already found this thread recently (https://support.mozilla.org/en-US/questions/1248840) where they were having the exact same issue. However, this didn't fix my problem because it either made some images suddenly disappear (no thumbnails at all) or continued to try and save the image as an invalid format. Any ideas how to fix this? Or just have to wait until update fixes it?
Chosen solution
Firefox 65 supports WebP images, so websites do not need to fallback to JPG images.
- https://www.ghacks.net/2018/11/02/firefox-65-supports-googles-webp-image-format/
- https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/65#Other
There are specific prefs present on the about:config page to control this new feature. You can remove "image/webp," from the accept prefs to prevent getting WebP images send by the server.
- image.http.accept = image/webp,*/* => */*
- network.http.accept.default = text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8 => text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
The image.webp.enabled pref controls internal support for WebP, but doesn't affect the behavior of websites. You can leave this pref set to true to be able to open locally saved WebP images or make web pages that only support WebP images work.
Read this answer in context 👍 2All Replies (9)
Where are you saving from?
From practically everywhere. I was first trying to save some pictures from Rooster Teeth, then from Wikia, then general google search images (by that point I was trying every single image I came across and none of them were working).
If an image wants to be save as an HTML file then this can mean that you do not g the actual image when you use context menu, but are send to an other (html) page where the image is located. In such a case you can left-click the image or try to open the link in a new tab via the right-click context menu.
If you have the correct image, but the file extension is wrong or missing then try to rename/modify the file extension to the correct value for this image (.jpg or .png).
Ok not to sound annoyed but just want to make it clear where my skills are: I've saved countless images before both the normal way of saving as well as using developer tools and html source to grab images and know how to fix extensions (if it helps I was a graphic/web designer for awhile).
I've done the exact same method on another browser using the exact same link to a problem image and it works fine on them, just not Firefox (even when in safe mode). Firefox tries to insist on either an html page (as a webp extension) or not at all. Even when I try to manually fix the extension, the file is then treated as invalid and won't appear correctly. Other browser save it as normal (whether it's png, jpg, svg, etc.). I only recently noticed this after a recent Firefox update :(
Modified by Mechemik
Chosen Solution
Firefox 65 supports WebP images, so websites do not need to fallback to JPG images.
- https://www.ghacks.net/2018/11/02/firefox-65-supports-googles-webp-image-format/
- https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/65#Other
There are specific prefs present on the about:config page to control this new feature. You can remove "image/webp," from the accept prefs to prevent getting WebP images send by the server.
- image.http.accept = image/webp,*/* => */*
- network.http.accept.default = text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8 => text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
The image.webp.enabled pref controls internal support for WebP, but doesn't affect the behavior of websites. You can leave this pref set to true to be able to open locally saved WebP images or make web pages that only support WebP images work.
Thanks that fixed it! It appears it was the "network.http.accept.default" that needed to be fixed (removing the "image/webp" part) :)
I also did a quick test with default for" image.http.accept" and with the edited version and it appears that one is needed for png files (otherwise Firefox goes back to trying html format)
Modified by Mechemik
You're welcome and thanks for reporting back on what worked for you.
cor-el said
Firefox 65 supports WebP images, so websites do not need to fallback to JPG images.There are specific prefs present on the about:config page to control this new feature. You can remove "image/webp," from the accept prefs to prevent getting WebP images send by the server.
- https://www.ghacks.net/2018/11/02/firefox-65-supports-googles-webp-image-format/
- https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/65#Other
The image.webp.enabled pref controls internal support for WebP, but doesn't affect the behavior of websites. You can leave this pref set to true to be able to open locally saved WebP images or make web pages that only support WebP images work.
- image.http.accept = image/webp,*/* => */*
- network.http.accept.default = text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8 => text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
This is not a solution but a work around for a poorly implemented new feature breaking expected behaviors.
It is up to website to serve content in a specific format. New formats will keep appearing like SPDY and Brotli (br) encoding for files send via a secure connection that caused issues with security software that didn't support these new features. Current Firefox releases started to support the WebP format for images and servers that already supported this format, but didn't send it to Firefox users will now send it to Firefox. WebP images usually have a smaller file size, so that can be considered as an improvement (less traffic and faster page loading). In a long past compressed formats like JPG and PNG were new formats when BMP was still widely used. There are other image formats that haven't made it. The same for media files where are a lot of formats, but only a few formats are used.