Tuesday, May 12, 2026
English edition

Development

Chrome's 4GB AI model isn't new, but you're not wrong for being confused

May 8, 2026 Development Source: Ars Technica

Chrome's 4GB AI model isn't new, but you're not wrong for being confused

Share this article

So Google has not suddenly decided to gobble up 4GB of your storage space—it did that two years ago, and nobody thought to get upset. But should you? A fresh Chrome install with no extensions eats up 6–8GB of storage, and it will grow considerably with cache and extension data. In a few months, Chrome can occupy 10 times more space than the AI model consumes. Maybe that’s not ideal, either, but that’s just the state of browsers today. Google says Chrome will delete the model if your machine runs low on storage, and you can turn off local AI features in the Chrome settings with a toggle under the System tab. Flip that off, and Chrome will remove the model and not redownload it. This is a fixable problem, but it shouldn’t be a problem in the first place. Running AI models locally is generally a good thing—that data stays on your machine rather than feeding a cloud-based model. It’s a positive for privacy and security, and users should have that choice. But “choice” is the operative word, and Google isn’t actually giving you one because AI is Google’s new default. Maybe you don’t want any of these AI features. If that’s the case, Chrome should not consume 4GB of space for something you don’t use without asking. Google users were more willing to excuse AI in 2024, but the backlash is real in 2026. People are increasingly looking to avoid AI features, which makes this 4GB stealth download all the more questionable. Google’s obsession with AI has led to numerous stumbles, even when the company has ostensibly good intentions, because we are all (rightly!) hyper-focused on how this technology is impacting our lives. Some of those “good intentions” seem to have made the Chrome situation worse. As users sought ways to remove this AI model, many looked for the settings toggle. This happened to coincide with the wide release of Chrome 148, and the label for this toggle included a pretty suspicious change versus v147.