This looks like Google is separating “on-device GenAI” from the rest of Chrome’s Safe Browsing so users can remove the local model and opt out of AI-powered (local) scam/download analysis without fully disabling browser security.
What the toggle actually changes
Based on the UI text shown in your screenshot and the article, the “On-device GenAI” switch is meant to:
- Disable features that rely on the local GenAI model (example given: scam detection locally)
- Delete the downloaded on-device GenAI model(s) from the device
That’s important because it suggests the “AI layer” is additive on top of existing protections, not a replacement for them.
Security impact (practical take)
If you turn it OFF, expect some reduction in protection depth for the specific features that used the local model (e.g., scam heuristics and “in-depth scan” style checks mentioned). You should still keep normal baseline protections enabled, especially:
- Chrome Safe Browsing (Standard or Enhanced Protection) under Chrome Settings -> Privacy and security -> Security
- “Warn you if passwords are exposed in a data breach” / password safety checks (if you use Chrome’s manager)
- Your OS/endpoint AV/EDR real-time protection
In other words: disabling the local model likely reduces one detection method, but it does not automatically mean “no protection.”
Privacy / resource angle
Reasons some users may want it OFF:
- Disk usage (local models can be sizable)
- Reducing local “AI features” footprint
- Avoiding potential future expansion of local model usage into other browser features (as the article hints)
Reasons to leave it ON:
- Extra on-device analysis can catch some scams/unsafe patterns earlier or with different signals than cloud-only checks
- Potentially faster decisions for some detections (local inference)
How to disable it (as shown)
- Chrome -> Settings -> System
- Toggle OFF “On-device GenAI”
If/when this reaches Stable, it should be the cleanest “official” way to remove the model rather than hunting files manually.
Bottom line
For most users, leaving it enabled is the safer default. If you disable it for footprint/privacy reasons, compensate by keeping Safe Browsing (preferably Enhanced Protection) and your endpoint security fully enabled.
Sources