Summary: Firefox 148 begins reaching users on February 24, 2026, adding AI Controls that manage current generative AI features and can block future ones from one desktop settings surface. A master switch covers translations, PDF alt text, tab grouping, link previews, and the AI chatbot sidebar, while also suppressing promotional reminders. Preferences persist across browser updates.
Firefox 148 starts reaching users on February 24, 2026, and tucked inside is something that has grown rare by 2026: an official way to say no to AI. Desktop settings gain an AI Controls section — one surface where every generative AI feature in the browser can be managed, or the entire category blocked, including anything Mozilla has yet to ship. Ajit Varma wrote the announcement, which went live on the official blog on February 2; TechCrunch’s headline skipped the decoration: Firefox will soon let you block all of its generative AI features.
Why it matters: most software in 2026 shows up with AI switched on and an opt-out that is fragmented, fuzzy, or wiped by the next update. Mozilla inverts the setup, promoting “no AI, please” to a first-class product state.
Every AI Feature Under One Page
Mozilla is frank about user sentiment to a degree few companies match. “We’ve heard from many who want nothing to do with AI,” the post concedes, while another cohort “want AI tools that are genuinely useful.” The principle Mozilla commits to: “What matters to us is giving people control, no matter how they feel about AI.”
The mechanics run on two layers: each AI feature carries its own toggle, and a master switch sits above the whole set. Preferences survive browser updates, so an opt-out holds through release cycles instead of being quietly requested again.
What Falls Under the Controls
At launch, the features governed by AI Controls include:
- Translations — reading any page in the language you prefer
- Alt text in PDFs — accessibility descriptions for images, generated automatically
- AI tab grouping — suggested related tabs and names for the groups
- Link previews — the key points, shown before you open a link
- The AI chatbot sidebar — bots chosen by the user, including Claude, ChatGPT, Copilot, Gemini, and Le Chat Mistral
The final entry earns a second look. The sidebar was a choose-your-own-model design from day one, and it now coexists with the kill switch: one user walks away from AI entirely; another hand-picks which AI to keep. User choice governs both routes.
Inside the Kill Switch
Cybersecurity News named the feature an “AI kill switch,” and the details hold the name up. Flip the Block AI enhancements toggle and every current AI feature goes dark — and so does every upcoming one. Features that do not exist yet arrive already blocked. Promotional pop-ups and reminders for AI features are suppressed as well, so users who opted out are not nagged back into the funnel. Everything lands in Firefox Nightly first, with feedback gathered through Mozilla Connect.
The decisions stack on each other: one location, coverage of future features, persistence across updates, no re-prompting. Out in the wild, most AI rollouts break all four at once.
Making Opt-Out the Strategy
The industry default in 2026 runs the other way: AI laced into core flows, off-switches scattered across settings, preferences occasionally wiped by redesigns. Mozilla’s calculus reads easily — in a market where every competitor is bolting on AI, “you can have none of it” is a differentiator on its own, especially for the users and enterprises that prize predictability. For IT teams, one switch covering present and future features is a far better policy surface than ten scattered settings.
The tradeoff is stated plainly, not hidden: blocking translations and PDF alt text discards genuine utility. Mozilla’s bet is that the goodwill earned by honoring a “no” outweighs the lost convenience — and that enough users feel strongly enough for that respect to turn into a market position.
Notes for Web Teams
For a start, do not build on browser AI. If alt text and translations can be switched off, your site’s accessibility and localization remain your own burden; browser features are a bonus layer, never the foundation. Beyond that, the pattern deserves copying by any team shipping AI features: put the opt-out in one place, extend it to features you have not built yet, carry the choice through updates, and stop promoting at people who said no. And plan for opt-out rates as a real metric: build on the assumption that everyone accepts AI features, and your analytics will eventually call the bluff.