Edit: I am basically having to rewrite some of this question because I have discovered something else that throws a wrench into my findings.
This is most likely a Chromium issue as I also experience this with Chrome, but I thought I’d ask here since the support staff is active and perhaps able to implement a fix in Brave.
I don’t understand how Chromium decides when to save a jpg as webp or jpg. When I am collecting images from a Google search, I like to click/drag the image from the browser to my desktop and organize later. Most of the time, the image saves as a jpg, but it’s becoming more common for it to save a webp. This befuddles me because the image in the URL is actually a jpg, but Chromium somehow decides to save it as webp. An example is this image:
Taking the below image URL as an example, if you open that in a new tab or window and click/drag the image directly to a folder, it will be dropped as a webp:
In case of link rot, just go a Google search and click/drag images until you find a webp. Don’t worry, you’ll find one before you know it.
However, if you right-click the image in the browser and Save image as, you only have the option to save as a jpg:
Now for the aforementioned wrench: If you remove the entire query string from that URL like so:
…now it will drag/drop as a jpg (and save as a jpg as well). What is the source of this inconsistency?
Is there a fix that can be implemented in Brave to disable webp altogether? I understand that it’s a new image format on the rise, but it’s not merging into the mainstream lane very elegantly. Lots of people despise this format because of the lack of support for it.