After some years of stability, FoxyProxy has been updated to support Manifest Version 3 which is required by Chrome in order for extensions to be compatible with Chrome in 2024. We took advantage of this forced update to implement many feature requests and other changes that were requested over the years.
FoxyProxy has been owned and developed consistently by the same team since 2006.
The repository has the source code for version 8.0+ for Firefox, Chrome, and other Chromium-based browsers like Chromium, Brave and Edge. Source code for older versions.
Permissions
downloads: Used to save/export user preferences to file, for backup or sharing
notifications: Used to inform users (e.g. for errors)
proxy: Used to set proxies (core function of the extension)
storage: Used to store user preferences
tabs: Used to get tab details (e.g. for “Quick Add”, “Tab Proxy”, & “Incognito/Container Proxy”)
webRequest: Used to provide proxy authentication
webRequestAuthProvider: Used to provide proxy authentication
host permission: Used to provide proxy authentication (to any URL "<all_urls>")
Optional Permissions
browsingData: Used for “Delete Browsing Data” button to delete cookies, indexedDB, and localStorage, only if requested by the user
privacy: Used for “Limit WebRTC” button to toggle browser.privacy.network.webRTCIPHandlingPolicy, only if requested by the user
Mini FAQ
Why is there a CryptoJS library in lib?
The CryptoJS library was already included in FoxyProxy 3.x to encrypt user credentials. It is needed to migrate encrypted settings from the old version (which had no updates for many years, as you mentioned). It is not used to encrypt anything; only to decrypt old data when upgrading from version 3.x to 8.x.
The library is not used in Firefox, and will be removed once users migrate to v8+.
Remote Code
No remote code is used in this extension.
The target is built in foxyproxy-XXX-YYY.zip; e.g. foxyproxy-chrome-standard.zip.
Without grunt:
copy the appropriate manifest-xxx.json file to manifest.json; e.g. mv manifest-chrome.json manifest.json
zip the src directory into the top of an archive. The src/ directory should not be in the zip archive.
FAQ
💻 Settings disappeared after the upgrade to v8
Using Firefox and you’ve lost all FoxyProxy settings?
FoxyProxy Basic 8.0 was first released in Sep 2023 as a trial run since it had fewer users (26k on Chrome & Firefox).
We waited for 2 months for any feedback & bug reports before releasing FoxyProxy Standard.
Unfortunately, we didn’t get any bug report about the data migration sync issue, otherwise we would have fixed it before releasing the standard version.
FoxyProxy 8.2 went online on Dec 6th.
Due to a bug in version 8.2, previous settings of some users were not migrated after the upgrade.
Versions 8.3-8.6 created with fixes for the bugs immediately, but due to the AMO approval waiting time, version 8.6 came online on Dec 12th.
Previous settings were not deleted and are recoverable. The following options are available if FoxyProxy updated from 7.* and you have encountered the update bug.
Click the file; firefox will ask you to install that addon. Confirm
Go to Firefox settings, addons (about:addons), FoxyProxy, check that it shows version 7.*
Important: On that same page, set “Allow automatic updates” to off
The settings bug is expected to be fixed in the latest release.
Check About for more information.
📱 Firefox for Android
Firefox for Android ignored disabling extensions.update.enabled (due to a bug). Therefore, installation of an older version from AMO will get updated. The bug is fixed in Firefox 123.
FoxyProxy Browser Extension
About/Changelog | Help | Issues
After some years of stability, FoxyProxy has been updated to support Manifest Version 3 which is required by Chrome in order for extensions to be compatible with Chrome in 2024. We took advantage of this forced update to implement many feature requests and other changes that were requested over the years.
FoxyProxy has been owned and developed consistently by the same team since 2006.
The repository has the source code for version 8.0+ for Firefox, Chrome, and other Chromium-based browsers like Chromium, Brave and Edge. Source code for older versions.
Permissions
"<all_urls>"
)Optional Permissions
browser.privacy.network.webRTCIPHandlingPolicy
, only if requested by the userMini FAQ
Why is there a CryptoJS library in lib?
The CryptoJS library was already included in FoxyProxy 3.x to encrypt user credentials. It is needed to migrate encrypted settings from the old version (which had no updates for many years, as you mentioned). It is not used to encrypt anything; only to decrypt old data when upgrading from version 3.x to 8.x.
The library is not used in Firefox, and will be removed once users migrate to v8+.
Remote Code
No remote code is used in this extension.
Screenshots
Dark Theme
Light Theme
Releases
Browser Minimum
(released 2022-11-29)
(released 2021-10-05)
(API minimum 102)
Beta Installation Guide
Backup your FoxyProxy settings
Download repo (or use
git
)Chrome
manifest-chrome.json
insrc
folder tomanifest.json
chrome://extensions/
manifest.json
(orsrc
folder)Firefox (Nightly/Beta/Developer Edition)
manifest-firefox.json
insrc
folder tomanifest.json
about:debugging#/runtime/this-firefox
manifest.json
Firefox for Android
about:config
xpinstall.signatures.required
false
src
for Firefox as mentioned abovesrc
Building for Distribution
With grunt:
npm i -D grunt-cli
grunt --target=chrome-standard
grunt --target=chrome-basic
grunt --target=firefox-standard
grunt --target=firefox-basic
The target is built in
foxyproxy-XXX-YYY.zip
; e.g.foxyproxy-chrome-standard.zip
.Without grunt:
mv manifest-chrome.json manifest.json
src
directory into the top of an archive. Thesrc/
directory should not be in the zip archive.FAQ
💻 Settings disappeared after the upgrade to v8
Using Firefox and you’ve lost all FoxyProxy settings?
FoxyProxy Basic 8.0 was first released in Sep 2023 as a trial run since it had fewer users (26k on Chrome & Firefox). We waited for 2 months for any feedback & bug reports before releasing FoxyProxy Standard. Unfortunately, we didn’t get any bug report about the data migration sync issue, otherwise we would have fixed it before releasing the standard version. FoxyProxy 8.2 went online on Dec 6th. Due to a bug in version 8.2, previous settings of some users were not migrated after the upgrade. Versions 8.3-8.6 created with fixes for the bugs immediately, but due to the AMO approval waiting time, version 8.6 came online on Dec 12th.
Previous settings were not deleted and are recoverable. The following options are available if FoxyProxy updated from 7.* and you have encountered the update bug.
Retrieve Settings and Keep version 8.2
From this comment:
Look for old data
With Sync
If above has some data, then in the Console tab, type the following and hit ENTER
Without Sync
If above has some data, then in the Console tab, type the following and hit ENTER
Import data
FoxyProxy_sync.json
orFoxyProxy_local.json
file that you have savedDowngrade to 7.*
Downgrade may retrieve old settings.
The settings bug is expected to be fixed in the latest release. Check About for more information.
📱 Firefox for Android
Firefox for Android ignored disabling
extensions.update.enabled
(due to a bug). Therefore, installation of an older version from AMO will get updated. The bug is fixed in Firefox 123.Downgrade or Beta Installation
menu -> Settings -> About Firefox Nightly
about:config
xpinstall.signatures.required
false
extensions.update.enabled
false
menu -> Settings -> Advanced -> Install add-on from file
and select the.zip
file you transferred to the android deviceSee also: