"Firefox already supports a strong ecosystem of ad-blocking and privacy extensions," Mozilla explained.
Mozilla rolls ad blocking into Firefox for iOS
After weeks in an experimental phase, Mozilla has begun a gradual rollout of a native ad-blocking feature in the iOS version of Firefox. The feature is off by default and — according to Mozilla’s communication with The Register — the timetable for general availability depends on how well the initial rollout performs.
Apple’s WebKit Content Blocking requirement
Mozilla says it had to change course for iOS because Apple forces all iOS browsers to use WebKit for rendering. That constraint meant Firefox could not rely on extension-based blockers the way it does on other platforms; instead, Mozilla implemented ad blocking using Apple’s WebKit Content Blockers. Apple has described app extensions as “essentially little sandboxed applications that are launched on demand to extend some specific piece of functionality,” and warned that “JavaScript-based content blocking extensions … have significant performance drawbacks.” Apple frames WebKit Content Blocking as “describing content blocking rules in a structured format ahead-of-time, declaratively,” and notes that Web Content Blockers execute in bytecode for each resource request, modifying requests or injecting CSS changes while pages load.
Audit-ready is a season. It shouldn't be.
Evidence in spreadsheets, controls drifting between audits, frameworks multiplying on flat headcount. Nubivance runs continuous compliance on Rapid7 Cyber GRC - SOC 2, HIPAA, ISO 27001, PCI, CMMC.
End the scrambleHow Firefox for iOS implements blocking — EasyList, JSON and bytecode
Under the hood, Mozilla’s approach is straightforward: it adapted the EasyList filter — a list originally designed for the classic Adblock blocker — by dropping it into a JSON file and handing that data to WebKit. In practical terms, Firefox for iOS uses the platform’s declarative content-blocking mechanism rather than running JavaScript-based extensions on demand.
User controls, rollout mechanics and explicit limits
Users can enable the feature from inside Firefox for iOS by opening the in‑app Settings, tapping Browsing, and toggling the Ad Blocker field on. Mozilla also requires Remote Improvements to be turned on so it can push fixes and feature changes between full releases; historically, toggling Remote Improvements also meant enabling telemetry, but Mozilla changed that linkage in February with the release of Firefox 148 and the two features are now decoupled.
Even when enabled, the new iOS ad blocker has clear exceptions. It will block ad-related trackers, third‑party advertising network ads, third‑party ads served by websites, and popups/overlays. It will not remove ads on search result pages, nor sponsored content on Firefox’s home or new tab page — “after all, you wouldn’t want Mozilla to lose those precious ad bucks, would you?” the source dryly noted — and it will not eliminate ads served directly by websites. Mozilla also cautions that the blocker “still might not work in all places,” a common limitation for content-blocking tools.
What this means for end users, extension developers, and technologists
- End users: Those seeking cross-platform consistency now have a native ad-block option on iOS that mirrors Firefox’s stance on privacy extensions elsewhere, but they should expect certain site-level and Mozilla-owned ad placements (new tab/home) to remain visible.
- Extension developers: Mozilla says it will continue to support the existing ecosystem of ad‑blocking and privacy extensions and has no plans to expand built-in adblocking outside iOS, preserving market space for third-party blockers on desktop and Android.
- Technologists and performance-minded teams: The use of WebKit’s declarative, ahead‑of‑time rule format follows Apple’s stated goals to reduce energy use, page load time, and memory impact compared with JavaScript-based blockers, and it reflects a platform-driven tradeoff between extension flexibility and runtime performance.
Mozilla’s iOS ad-blocking rollout is a compact case study in platform constraints shaping product design: Apple’s WebKit rules forced a rework of Firefox’s typical extension strategy, producing a baked-in blocker that leaves certain ads intact and preserves the extension economy elsewhere. Mozilla’s lack of a firm release date and its explicit decision not to expand built-in adblocking beyond iOS leave two clear near-term facts: users on iOS can opt into a new, limited blocker now as it rolls out, and extension developers retain their role on other platforms.
