If you go to the Options for the add-on (click the "gear" wheel icon on the button bar), "Save Path Options" section, you can change to saving directly in the Downloads folder. Due to limitations on where add-ons can auto-save, I can't offer very much flexibility on this. If you prefer to choose where to save each time, the setting above that lets you select your preferred approach.

For converting to PNG and JPEG, the add-on doesn't need to use external services unless Firefox restricts the page. To convert animated WebP to animated GIF, you need to use an external service (Firefox doesn't have a function add-ons can call for that).

Hi, do you mean the one assigned CVE-2023-4863? Mozilla issued Firefox 117.0.2 and 115.2.1 to address the problem. See: https://www.mozilla.org/security/advisories/mfsa2023-40/

The reason for mentioning that patch is: this extension uses features Firefox makes available to add-ons and web page scripts; the extension does not have its own image conversion libraries.

Unfortunately, add-ons are restricted to starting in either the Downloads folder and or in a sub-folder of the Downloads folder. If you don't want to save in the Save_webP folder, you can place a shortcut in that folder to double-click over to your preferred location.

Hi, could you open an issue at https://github.com/jscher2000/Save-webP-as-extension/issues or send me an email at jscher2000@outlook.com for personal assistance? Until then, if the menu item is no longer appearing on the right-click context menu, you might want to remove and reinstall it, and if you notice a problem in private windows (Ctrl+Shift+P or "Never Remember History") make sure it is enabled for private windows when you reinstall.

(Update: version 1.5.1 pops up a little panel with some more options when the script is denied permission to read the page. Previously that just caused silent failure.)

I know, it's inconvenient and demands a lot of trust. This add-on only reads data when you call it up, and it does not read data in pages other than the image it's operating on. Either way, it doesn't send info to me -- I have no interest what is happening in anyone else's browser.

For what it's worth, I did *try* to write this extension *without* that permission. If the image is hosted on the same server as the page (both the same server as listed in the address bar), then the fact that you right-clicked the image could grant one-time permission automatically (so called activeTab permission).

But a large proportion of images are hosted on a different server, so that method failed frequently in real world testing. Maybe there is a new solution to this four years down the road? I'll update this reply if I find one and rewrite the add-on.