Mozilla launches ad blocking for Firefox on iOS

What happened

Let me check the template file first. The template confirms the structure. The user's request uses custom section headings ("The announcement", "What actually changed", etc.) rather than the default news template headings — that's fine, the prompt overrides those. Here is the article:

Mozilla has switched on native ad blocking inside Firefox for iOS, ending a long-standing gap between the browser's desktop experience and its iPhone counterpart. The rollout follows a limited testing window over the past few weeks and is now available as an official, built-in option for all users.

How it works

This piece walks through exactly what Mozilla shipped, the technology underneath it, and what that means for developers, privacy-conscious iPhone owners, and anyone who has been waiting for a Firefox mobile experience that matches what the desktop version has offered for years.

Mozilla is launching built-in ad blocking for Firefox on iOS today, completing a testing phase that ran over the past several weeks. The feature is described as a new built-in option, meaning it arrives as a first-party toggle inside the browser rather than as a third-party extension or a separate download. Mozilla confirmed the feature blocks most third-party ads and trackers before they load, which is significant because preventing network requests entirely is different from hiding page elements after the fact. This distinction matters to both users who care about page load time and developers who want to understand what content is actually being fetched.

Why it matters

The underlying mechanism is Apple's WebKit Content Blocker API, which is the same content-blocking interface available to every browser on iOS. Mozilla is pairing that API with the EasyList filter list, an open, community-maintained catalog of ad and tracker domains that has been a standard in the browser privacy space for years. Because Apple's WebKit Content Blocker processes filter rules natively before network requests leave the device, the blocking happens at the platform level rather than inside the JavaScript engine. That architectural choice is what allows Firefox on iOS to reduce bandwidth consumption and strip clutter from mobile websites, since the ad requests are dropped before any data is transferred rather than simply hidden from view after loading.

Who is affected

iPhone users who have kept Firefox installed on their device primarily for its desktop sync or tab management features now have a concrete privacy reason to make it their primary mobile browser. Because third-party ads and trackers are stopped before they load, pages should render faster and consume less cellular data, which is a tangible benefit on metered connections. Developers who run ad-supported iOS web properties should note that Firefox's new behavior aligns with what browsers using WebKit Content Blockers — including Safari with its built-in Intelligent Tracking Prevention — already do. Advertisers and analytics vendors who rely on third-party scripts should verify that their measurement infrastructure accounts for Firefox on iOS as a blocking environment, not just a passive one.

The feature is available today inside the Firefox app on iOS. To test it, open Firefox on an iPhone, navigate to the browser's settings, and look for the content-blocking or tracking protection toggle. Because Mozilla used WebKit Content Blocker — the same API Apple exposes to Safari extensions — no additional download or profile installation is required. The EasyList filter list used by the feature is publicly accessible and updated by its maintainers on an ongoing basis, so the block list will evolve without requiring a separate app update each time a new ad domain is added. Users who want to verify the feature is active can load a page that serves third-party ads and check whether network requests to known ad domains are being suppressed in a tool like a packet capture.

What to watch next

Mozilla has not yet detailed whether the EasyList integration will be user-configurable — meaning whether Firefox on iOS will eventually let users swap in alternative filter lists such as uBlock Origin's lists or regional variants of EasyList. That flexibility exists in Firefox for desktop and is a common request from power users on mobile. The second thing to watch is how Apple's ongoing App Store and WebKit policy changes interact with this feature; Apple controls the Content Blocker API and could alter its behavior or rules in a future iOS release. Following Mozilla's release notes and the EasyList repository will give builders the earliest signal if the filter list source, the API layer, or the default toggle behavior changes in a future Firefox for iOS update.