Mozilla announced that Firefox 148, scheduled for release on February 24, 2026, will include a single toggle to completely disable all generative AI features in the browser. The move responds to user feedback requesting explicit control over AI integration.
Release timeline
| Milestone | Date |
|---|
| Announcement | February 2, 2026 |
| Firefox Nightly availability | Available now |
| Firefox Beta availability | Available now |
| General release (Firefox 148) | February 24, 2026 |
| Mobile implementation | Future release (TBD) |
New AI controls
Firefox 148 introduces a new AI controls section within desktop browser settings, providing two levels of control.
Global kill switch
| Setting | Function |
|---|
| ”Block AI enhancements” toggle | Disables all AI features at once |
| Pop-up suppression | Hides reminders about AI capabilities |
| Future-proofing | New AI features automatically respect the setting |
Individual feature controls
| Feature | Description |
|---|
| Browser translations | On-device translation for web pages |
| Alt text generation | Automatic image descriptions |
| AI-enhanced tab grouping | Suggested tab organization |
| Link previews | Summarizes linked content |
| Sidebar chatbot access | Direct access to AI assistants |
Third-party AI assistant options
Users can choose which AI assistant powers certain features:
| Assistant | Provider |
|---|
| ChatGPT | OpenAI |
| Claude | Anthropic |
| Gemini | Google |
| Copilot | Microsoft |
| Le Chat Mistral | Mistral AI |
| None | Disable chatbot features entirely |
Default behavior
| Condition | Default state |
|---|
| ”Block AI enhancements” toggle | Off by default |
| Previously used features | Enabled |
| Previously disabled features | Blocked |
| Never-used features | Available (not enabled) |
Once preferences are set, they persist across browser updates. Users can change settings at any time.
Mozilla’s rationale
“We’ve heard from many who want nothing to do with AI. We’ve also heard from others who want AI tools that are genuinely useful. Listening to our community, alongside our ongoing commitment to offer choice, led us to build AI controls.”
— Ajit Varma, Firefox head
The announcement positions Mozilla as the privacy-focused alternative in an increasingly AI-saturated browser market.
Criticism of the framing
The feature’s labeling has drawn criticism from privacy advocates.
”Confirm shaming” concerns
| Issue | Criticism |
|---|
| ”Block AI enhancements” label | Frames AI-off as rejecting improvements |
| Implied value judgment | Suggests turning off AI is self-sabotage |
| Dark pattern classification | Some observers call it “confirm shaming” |
Users aren’t “disabling AI”—they’re “blocking enhancements.” The implication subtly pressures users toward the default behavior.
Alternative framings considered
| Option | Neutrality |
|---|
| ”Block AI enhancements” (chosen) | Implies negative choice |
| ”Disable AI features” | More neutral |
| ”AI features: On/Off” | Neutral |
| ”Use AI features” | Toggle implies positive choice |
Browser AI landscape comparison
| Browser | AI features | User control | Default |
|---|
| Firefox 148 | Translations, alt text, tab groups, previews, chatbots | Global disable + per-feature toggles | AI off-by-default available |
| Chrome | AI-powered search, writing, organization | Limited; features opt-out individually | AI features on |
| Edge | Copilot deeply integrated | Can hide sidebar; features scattered | Copilot prominent |
| Safari | Limited AI integration | Minimal AI to disable | Conservative integration |
| Brave | Brave Leo AI assistant | Can disable Leo | Optional |
Competitor approaches
| Browser | Challenge |
|---|
| Chrome | AI features enabled by default, scattered opt-out options |
| Edge | Copilot as core feature, deep integration across experience |
| Safari | Limited AI but no centralized control |
Both Microsoft and Google have faced criticism from users wanting traditional browser functionality without AI assistance.
Current AI features in Firefox
| Feature | Processing | Data sharing |
|---|
| Translation | On-device | No external servers |
| Alt text generation | On-device | No external servers |
| Tab grouping | On-device | No external servers |
| Link previews | Cloud-based | Depends on feature |
| Sidebar chatbots | External services | Sent to chosen provider |
Mozilla has emphasized that on-device features like translation don’t require sending data to external servers, distinguishing them from cloud-based AI integrations in competing browsers.
User impact by persona
Privacy-conscious users
| Benefit | Details |
|---|
| Centralized opt-out | Single toggle for all AI |
| Future-proofing | New features respect setting |
| No data sharing | On-device features don’t transmit data |
Power users
| Benefit | Details |
|---|
| Selective enablement | Use translation, disable chatbots |
| Per-feature control | Fine-grained preferences |
| Assistant choice | Pick preferred AI provider |
Enterprise administrators
| Benefit | Details |
|---|
| Consistent behavior | Same settings across organization |
| Policy enforcement | No need to chase feature flags |
| Simplified management | Single configuration point |
Technical implementation
| Aspect | Details |
|---|
| Settings location | about:preferences > AI Controls |
| Persistence | Survives browser updates |
| Sync | Unclear if synced via Firefox Account |
| Mobile | Desktop first; mobile in future release |
Privacy implications
On-device features
| Feature | Privacy assessment |
|---|
| Translation | Data stays local |
| Alt text | Data stays local |
| Tab grouping | Data stays local |
Cloud features
| Feature | Privacy assessment |
|---|
| Chatbot access | Data sent to third-party AI provider |
| Link previews | May involve external requests |
Users who enable sidebar chatbots should understand their queries go to the selected provider (OpenAI, Anthropic, Google, Microsoft, or Mistral) under that provider’s privacy policy.
Industry context
Firefox’s approach contrasts with the broader industry trend of embedding AI deeply and making it difficult to disable:
| Trend | Firefox response |
|---|
| AI-by-default | Explicit enable/disable |
| Fragmented opt-outs | Centralized control |
| Cloud-first processing | On-device where possible |
| Mandatory integration | User choice emphasized |
Recommendations
For privacy-focused users
| Action | Result |
|---|
| Enable “Block AI enhancements” | All AI features disabled |
| No further action needed | Future features auto-blocked |
For selective AI users
| Action | Result |
|---|
| Leave global toggle off | Features available |
| Enable desired features individually | Selective functionality |
| Choose preferred AI assistant | Control which provider receives data |
For enterprise IT
| Action | Consideration |
|---|
| Test in Firefox Nightly | Early access to controls |
| Plan policy configuration | Decide organization-wide defaults |
| Document approved features | Communicate to users |
Availability
Firefox 148 releases through Mozilla’s standard channels on February 24, 2026. Users running Firefox Nightly or Beta can access the feature earlier for testing.
The AI controls will be available in the desktop browser initially; mobile implementation may follow in a later release.
Context
Mozilla’s decision to provide explicit AI control reflects genuine user demand for browser simplicity and privacy. Whether the “Block AI enhancements” framing undermines that message is a matter of perspective—but the underlying functionality gives users more control than any major competitor currently offers.
