Firefox quietly adopts Brave’s Rust adblocker in experimental release

Firefox has slipped Brave’s Rust-based adblock-rust engine into version 149, but left it disabled by default, turning a high-profile privacy tool into an experiment rather than a finished rollout. That matters because this is not just another browser tweak: it is one of the clearest signs yet that Rust is moving from developer talking point to code that could affect how millions of people browse every day.

Firefox 149 was released on March 24, 2026, and the new blocker fits Mozilla’s usual pattern for features that are present but not yet exposed to users. When a feature ships disabled, it can still be activated through internal preferences in about:config, which makes the move notable for developers watching Firefox’s privacy stack and for users who prefer browser-level protections over extension-heavy setups.

The cross-browser angle is the bigger story. Firefox runs on Gecko and Quantum, while Brave is built on Chromium, so the reuse of Brave’s blocker inside Firefox is an unusual handoff between two very different browser families. Brave says adblock-rust powers its native ad blocker and handles network blocking, cosmetic filtering, resource replacements, hosts syntax, uBlock Origin syntax extensions, iOS content-blocking syntax conversion, and builds to either native code or WebAssembly. In practice, that means Firefox is borrowing a privacy engine that was designed to work deep inside the browser, not as a patchwork add-on.

That design choice lines up with long-standing advice from privacy-focused projects: keep browser extensions to a minimum. Extensions have privileged access and can widen the attack surface, so a built-in blocker can be a cleaner answer than piling on more add-ons. For Firefox users, the payoff could be less overhead, tighter integration, and fewer moving parts in the extension layer.

Brave has been aggressively refining the engine as well. In early 2026, the company said a redesign cut memory use by 75 percent, saving roughly 45 MB per browser instance across desktop, Android, and iOS. Those gains shipped in Brave v1.85, with more optimization work planned for v1.86. That kind of improvement is exactly the sort of user-visible win that makes a feature attractive beyond its home browser.

Mozilla’s own Rust infrastructure helps explain why this was possible at all. Firefox source documentation already includes a dedicated process for adding, building, linking, and vendoring Rust crates, and Mozilla’s Rust update policy says official Firefox builds ship with stable Rust. Rust is already part of Firefox’s engineering base. With adblock-rust now in the mix, it is also edging closer to the browser’s everyday user experience.