Get it!
Latest stable
- Get NoScript for Firefox NoScript for Firefox (desktop and mobile!), Tor Browser and other Mozilla-based browsers from Mozilla Add-ons
- Get NoScript for Chromium NoScript for Chrome and other Chromium-based browsers (eg. Edge, Brave, Vivaldi...) from the Chrome Web Store
Direct download for Firefox
You can get the latest stable version for Firefox desktop only also using this direct NoScript 11.5.2 download link. To install, just drag and drop it onto your address bar.
v 11.5.2
============================================================
x [tor-browser#43257] More efficient, flexible and
race-resistant placeholder styling
v 11.5.1
============================================================
x [nscl] Panic abort on buggy pages (like
https://github.com/) going in infinite loops when webgl is
disabled
x Refactoring to use DocRewriter
x [tor-browser#43258] Remove content script crypto.subtle
dependency
x Synchronize Sites.onionSecure on any settings update
x [tor-browser#32668] More reliable Security Level Reset on
Tor / Mullvad Browser
v 11.5.0
============================================================
x [tor-browser#32668] Use the Security Level as the default
policy for Options Reset on Tor Browser
x [tor] Stateless-compatible Tor Browser integration
x [L10n] Updated pt_BR
x Stateless-compatible temporary permissions
x Switch from deferWebTraffic to Wakening
x Stateless-compatibile TabGuard
x Switch to non-persistent background page
x [xss] Refactor for non-persistence
x Removed Fennec-specific code
x Bump min Gecko compatibility to 115.0 (stateless
background script support)
Development build
NoScript development happens very fast to keep up with emerging web threats. If you're brave enough and you need a specific feature or fix not released yet, or you simply want to provide feedback before official release, you may want to try the latest release candidate.
RC for Firefox
Install NoScript 11.5.3rc2 on Firefox Desktop by simply clicking here.
On Firefox for Android, unfortunately, a pre-release can only be downloaded (same link as above) and temporarily installed on Nightly by using the web-ext tool, which is only suitable for hardcore developers and contributors.
Non-store versions for Chromium
On Chromium based browsers you can download either:
- NoScript 12.0.8 (MV3) - experimental, supporting the Google-mandated but limiting, unproven and unstable latest extensions technology. Requires Chromium version 128 or above (latest stable version recommended).
- NoScript 11.4.44 (MV2) - legacy, unsupported by Google but proven and stable. Best option for browsers based on Chromium 127 and below.
In order to install next MV3 version until it reaches the Chrome Store, or the MV2 version if you're affected by some MV3-caused bug which could not have been fixed yet, you need to unzip the downloaded noscript-$VERSION-chrome.zip
file and load its content as an unpacked extension in developer mode.
Please follow these steps:
- Open the Extension Management page by navigating to chrome://extensions. Alternatively, open this page by clicking on the Extensions menu button and selecting Manage Extensions at the bottom of the menu. Alternatively, open this page by clicking on the Chrome menu, hovering over More Tools then selecting Extensions
- Enable Developer Mode by clicking the toggle switch next to Developer mode.
- Unzip the zipped "noscript-11.5.3rc2-chrome.zip" package to a directory of your choice.
- Click the [Load unpacked] button and select the extension directory you've unzipped the extension to (the one containing the "manifest.json" file)
You're done. Happy testing!
Recent development history
v 11.5.3rc2
============================================================
x [nscl] Several performance and reliability enhancements
from NSCL
x [nscl] Updated to latest NoScript Commons Library
x Fixed offscreen placeholder container preventing user
interaction on the left of placeholders
(tor-browser#43282)
x Fix localization-related console spam when opening options
panel (tor-browser#43269)
v 12.0.8
============================================================
x Filter out tabs with no accessible url from context
matching routine
x [nscl] Remove RuleCondition.responseHeaders usage breaking
Chromium older than 128 (e.g. Kiwi Browser, issue #398)
v 12.0.7
============================================================
x Boostrap from REQUIRED.js (created at build time by
manifest.js)
v 12.0.6
============================================================
x [nscl] Better SyncMessage recovery from DNR/XHR
interaction browser bugs
x More reliable implementation of DNR-based unrestricted
tabs
x Make debugging DNR a bit easier
x Workaround for current tab on current window not always
available to UI popup on Vivaldi
v 12.0.5
============================================================
x Fixed contextual policies MV3 implementation (issue #394).
v 12.0.4
============================================================
x [nscl] MV3 work-around for Permissions-Policy breaking
SyncMessage
v 12.0.3
============================================================
x Improved startup behavior
x Do not retry failed synchronous policy retrievals if
document is not loading
x Coalesce activity reports by origin
x More robust initialization sequence
x Fix DNRPolicy matching for entries including explicit
protocol
v 12.0.2
============================================================
x Make "Temporarily set top-level sites to TRUSTED" work on
Manifest V3 (issue #388)
x Fix UI reporting noise from requests of uninteresting
types (e.g. images)
x Fixes naked domains with no HTTPS lock and explicit port
numbers not correctly matched in mapped MV3 DNR rules
(issue #387)
v 12.0.1
============================================================
x Restructure inclusion of file/ftp protocol-specific
content scripts
x Fixed TabTies session (de)serialization bugs
x [nscl] Fixed media blocking regresssion affecting Youtube
(issue #386)
v 12.0.0
============================================================
x [nscl] Switch all the Chromium usages of patchWindow() to
the new Worlds API
x [nscl] Switch patchWorkers.js implementation from
patchWindow.js to Worlds.js
x [nscl] Switch WebGLHook implementation from patchWindow.js
to Worlds.js
x Optimized fall-back reporting for non-HTTP documents and
included script type
x Remove uuid from DNR reporting CSP to prevent it from
being abused for tracking
x Import versioning module just once
x Infrastructure to replace patchWindow.js with MAIN world
content scripts
x MV3 compatibility
x DeclarativeNetRequest-backed policy enforcement
x Fixed theming race condition and other bugs
x Require explicit call to run tests
x fixup! Gecko strict compatibility versionining to prevent
Chromium-only NoScript 12.x from being accidentally
installed on Firefox
x Simplified Wakening
x Gecko strict compatibility versionining to prevent
Chromium-only NoScript 12.x from being accidentally
installed on Firefox
v 11.5.3rc1
============================================================
x Fixed offscreen placeholder container preventing user
interaction on the left of placeholders
(tor-browser#43282)
x Fix localization-related console spam when opening options
panel (tor-browser#43269)
v 11.5.2rc1
============================================================
x [tor-browser#43257] More efficient, flexible and
race-resistant placeholder styling
v 11.5.1rc4
============================================================
x [tor-browser#43258] Fixed LifeCycle error on update
v 11.5.1rc3
============================================================
x [nscl] Panic abort on buggy pages (like
https://github.com/) going in infinite loops when webgl is
disabled
x Refactoring to use DocRewriter
v 11.5.1rc2
============================================================
x [tor-browser#43258] Remove content script crypto.subtle
dependency
x Synchronize Sites.onionSecure on any settings update
v 11.5.1rc1
============================================================
x [tor-browser#32668] More reliable Security Level Reset on
Tor / Mullvad Browser
v 11.5.0rc1
============================================================
x [tor-browser#32668] Use the Security Level as the default
policy for Options Reset on Tor Browser
x [tor] Stateless-compatible Tor Browser integration
x [L10n] Updated pt_BR
x Stateless-compatible temporary permissions
x Switch from deferWebTraffic to Wakening
x Stateless-compatibile TabGuard
x Switch to non-persistent background page
x [xss] Refactor for non-persistence
x Removed Fennec-specific code
x Bump min Gecko compatibility to 115.0 (stateless
background script support)
Browser compatibility and obsolete versions
NoScript 11.5.2 is compatible with Gecko versions 115 and above, and it's currently the most full-featured and reliable NoScript even if the version number is less than 12 (Chromium-only, see below).
NoScript 12.0.8 is Manifest V3 and Chrome/Chromium compatible out of the box, but NOT compatible with Firefox yet. Convergence between Firefox and Chrome version is planned for NoScript 13, to be released in 2025.
NoScript 11.4.44rc2 is compatible with Gecko versions 59-114.
You can still download NoScript "Classic" (5.1.9) (SHA256) for Seamonkey, Palemoon, Waterfox Classic and possibly other "vintage" (pre-Gecko 57) Firefox forks here.
Notice: you may need to open about:config and set your xpinstall.signatures.required preference to false in order to install NoScript 5.x, since Mozilla doesn't support signatures for legacy add-ons anymore. If you're using a non ESR Firefox, you may also need this hack.
Users of Firefox 58 and below are urged to upgrade their very unsafe browser. For those few who can't,
- latest NoScript version compatible with Gecko 57 - Gecko 58 is 10.1.7.3;
- latest NoScript version compatible with Gecko 46 - Gecko 56 is 5.1.9 (SHA256);
- latest NoScript version compatible with Gecko 13 - Gecko 45 is 2.9.0.14 (SHA256);
- latest NoScript version compatible with Gecko 1.9 - Gecko 12 is 2.9.0.1rc1 (SHA256);
- latest NoScript version compatible with Gecko < 1.9 is 1.10 (SHA256).
Disclaimer
We cannot update nor support NoScript 5.x and below anymore, because it was based on a completely different and now obsolete technology. However you can still find usage information and a FAQ section for those ancient versions in the NoScript Classic archived website.