Block Third-Party
JavaScript by Default

By default, APIVoid Script Stop blocks every JavaScript file loaded from a domain different from the website you're visiting. So if you visit example.com and the page tries to load a script from tracker.io, that script is blocked before it reaches the browser. First-party scripts (those served from the same domain as the website) are allowed by default, but you can also block those with one toggle in the settings.

Open the popup on the broken page. You'll see every script the page tried to load, with the blocked ones marked in red. Click the Allow once checkbox next to a script host to allow it for the current session, or check Whitelist to allow it permanently. If you can't easily identify which script is breaking the website, you can toggle off the per-site switch to disable Script Stop on that website entirely while keeping it active everywhere else. This action is recommended on websites you trust.

Yes, in most cases. The extension applies new rules immediately, but scripts that already loaded on the current page have already executed in the browser and can't be retroactively removed. Similarly, a script you just allowed wasn't downloaded by the browser when the page first loaded, so a refresh is needed to actually request and run it. The popup includes a Refresh Page button that gently pulses after any change, as a reminder. New tabs and future navigations always use the latest rules automatically, so a refresh is only needed for the page you're currently looking at.

Allow Once allows a script host for the current browsing session only, and is removed when you close the browser. Whitelist allows it permanently across all browser restarts. Block Once and Blacklist work the same way on the block side. Allow Once is useful when you want to temporarily test if a script is causing a website breakage, while Whitelist is useful for hosts you've verified are safe and want to keep allowed long-term.

Yes. Matching is subdomain-inclusive everywhere: whitelisting example.com also allows cdn.example.com, api.example.com, and any deeper subdomain. The same applies to the blacklist, the exclusions list, and the built-in trusted and blocklists. If you want to allow a parent domain but block a specific subdomain of it (for example, allow example.com but block ads.example.com), add the parent to the whitelist and the specific subdomain to the blacklist: the more specific block rule takes priority.

It's a curated list of well-known and safe script providers (such as js.stripe.com, googleapis.com, paypal.com, and many more) that's allowed out of the box, so most websites continue to work without manual setup. You can disable the trusted list entirely from the settings page if you want stricter blocking, or you can blacklist any specific entry to override it.

No. All blocking logic runs entirely inside your browser. The extension does not collect, transmit, or log any browsing data, visited URLs, or personal information. Your whitelist, blacklist, exclusions, settings, and history are stored locally on your device only.

No, in fact most users notice pages load faster. Blocking happens at the browser's native network layer, so there's no JavaScript running on every page to slow things down. Pages typically load faster because they're not downloading and executing dozens of third-party scripts for ads, tracking, and analytics.