Mozilla is set to launch a universal toggle in Firefox 148 that enables users to disable all generative AI features, marking a significant step towards enhancing user choice amid rising AI integration in browsers.
Mozilla is adding a single, browser‑level control that can turn off every generative AI capability in Firefox, a setting the organisation says will arrive with Firefox 148 on 24 February 2026. According to Mozilla’s blog post, the new AI controls section in desktop settings will provide “a single place to block current and future generative AI features in Firefox.” [4],[6],[2]
The control is designed as an all‑in‑one switch that blocks AI features globally while also allowing users to manage individual AI tools if they prefer. Mozilla says the settings will cover items such as in‑browser translations, AI‑generated alt text for PDFs, AI tab grouping, link previews and the sidebar chatbot, and will stop feature prompts from reappearing once disabled. [4],[6]
The effort follows earlier controversy around Mozilla’s decision to add on‑device AI to Firefox; the company framed the move as a balance between offering useful tools and respecting users who want no part of AI. Industry reporting notes Mozilla will make AI features opt‑in and emphasises user choice as central to the rollout. [3],[2]
Senior Firefox developers have described the control internally as an “AI kill switch.” As developer Jake Archibald put it, “Something that hasn’t been made clear: Firefox will have an option to disable all AI features completely. We’ve been calling it the AI kill switch internally.” That phrasing underscores Mozilla’s intention to reassure long‑standing users who are wary of AI in the browser. Mozilla’s public messaging likewise reflected the division in user preferences: “AI is changing the web, and people want very different things from it. We’ve heard from many who want nothing to do with AI.” [3],[4]
Some technical and rollout details remain unresolved. Commentators have pointed out Mozilla has not published the precise UI design for AI controls, whether the master toggle will automatically reverse previously enabled AI settings, or the exact scope of “future generative AI features” the switch will block. Enterprise deployment implications and any measurable performance effects from disabling AI are likewise not yet clarified. Organisations managing Firefox across fleets will need to review policies once the feature ships. [5],[6]
Mozilla’s move sets it apart from major rivals that are embedding AI more deeply into their browsers. Microsoft has been steering Edge toward an AI‑centric “agentic” experience and does not currently offer a single‑click global disable, while Google continues to layer AI into Chrome. Privacy‑focused alternatives such as Brave and DuckDuckGo already provide ways to limit AI‑style features, but Mozilla’s central toggle may widen expectations for clearer user controls across the browser market. [2],[1],[5]
Source Reference Map
Inspired by headline at: [1]
Sources by paragraph:
Source: Noah Wire Services
Noah Fact Check Pro
The draft above was created using the information available at the time the story first
emerged. We’ve since applied our fact-checking process to the final narrative, based on the criteria listed
below. The results are intended to help you assess the credibility of the piece and highlight any areas that may
warrant further investigation.
Freshness check
Score:
10
Notes:
The article reports on Mozilla’s announcement of an AI kill switch in Firefox 148, scheduled for release on 24 February 2026. This is the earliest known publication date for this specific information, indicating high freshness. The content does not appear to be recycled or republished from low-quality sites or clickbait networks. The narrative is based on a press release from Mozilla, which typically warrants a high freshness score. No discrepancies in figures, dates, or quotes were found between this and earlier versions. The article includes updated data and does not recycle older material.
Quotes check
Score:
10
Notes:
The article includes direct quotes from Mozilla developer Jake Archibald and CEO Anthony Enzor-DeMeo. Searches for the earliest known usage of these quotes indicate that they originate from Mozilla’s official communications and have not appeared in earlier material. The wording of the quotes is consistent across sources, with no variations found. No online matches were found for the quotes, but they can be independently verified through Mozilla’s official channels. Therefore, the quotes are considered reliable and verifiable.
Source reliability
Score:
8
Notes:
The article originates from TechRadar, a major news organisation known for its technology coverage. This is a strength in terms of source reliability. However, TechRadar is not as established as some other major news outlets, which slightly reduces the score. The article does not appear to be summarising, rewriting, or aggregating content from another publication. The lead source is independent and provides original reporting on the topic.
Plausibility check
Score:
10
Notes:
The claims made in the article are plausible and align with industry trends. Mozilla’s introduction of an AI kill switch in Firefox 148 is consistent with the company’s previous statements and actions regarding user control over AI features. The article provides specific factual anchors, including names, institutions, and dates, which support the plausibility of the claims. The language and tone are consistent with typical corporate communications from Mozilla, and there is no excessive or off-topic detail unrelated to the claim. The tone is professional and appropriate for the subject matter.
Overall assessment
Verdict (FAIL, OPEN, PASS): PASS
Confidence (LOW, MEDIUM, HIGH): HIGH
Summary:
The article meets our verification standards with high confidence. It is based on original reporting from a reputable source, includes verifiable quotes, and provides specific factual anchors. The content is fresh, with no signs of being recycled or republished from low-quality sites. The claims are plausible and supported by independent verification sources. There are no concerns regarding paywalls or content type. Therefore, the article passes our fact-checking criteria.
