If your laptop has felt a little fuller lately, here’s one possible reason: recent versions of Google Chrome quietly download a large on‑device AI model — often several gigabytes, sometimes landing as a file like weights.bin — usually without asking you first. Let’s unpack what it is, whether it should worry you, and exactly how to switch it off. 🤖
🤖 What is weights.bin, really?
It’s the brain for Chrome’s built‑in AI. Google ships a compact version of its Gemini Nano model so the browser can do AI tasks — summarising pages, “help me write”, smart suggestions — on your device rather than in the cloud. Chrome pulls it down in the background through its component updater (you may see it in chrome://components as Optimization Guide On Device Model), and the model files can run to a few gigabytes.
Here’s the genuinely fair part — and we want to be balanced: running AI locally is, in principle, more private than the cloud. Your text doesn’t leave your machine for those features. That’s a real privacy positive. ✅
The problem isn’t that the AI runs on your device. It’s that nobody clearly asked you — and a few gigabytes showed up anyway.
⚠️ So what’s the issue?
Three things rub people the wrong way, and reasonably so:
- Consent: a multi‑gigabyte download arrives by default, with no clear, up‑front opt‑in.
- Transparency: most people have no idea it happened, what the model can do, or how to remove it.
- Your resources, their infrastructure: it’s your disk space, your bandwidth and your battery powering a feature you may never use.
🛑 How to forbid Chrome from doing this
You have a few options, from quick to bulletproof. (Chrome’s menus shift between versions, so treat these as a map, not GPS.)
1️⃣ Turn off the AI features (quick)
Open chrome://settings/ai and switch off the on‑device / built‑in AI options. With the features off, Chrome has no reason to keep the model.
2️⃣ Disable the flags (thorough)
Go to chrome://flags, search for “on device model” and “Gemini Nano”, and set entries such as Optimization Guide On Device Model and Prompt API for Gemini Nano to Disabled. Restart Chrome.
3️⃣ Block it for good with a policy (bulletproof)
The most reliable method is an enterprise policy — it works on one machine too. Set GenAILocalFoundationalModelSettings to “Do not download the model”, and disable the related AI policies. Apply it via the Windows Registry, a macOS configuration profile, or a policies.json file on Linux. Chrome will stop fetching the model entirely.
Already downloaded? Deleting the model folder from your Chrome profile reclaims the space — but unless you also do step 2 or 3, Chrome will simply fetch it again.
🔐 Or switch to a browser that doesn’t phone home
This whole episode is specific to Google Chrome. If you’d rather not play whack‑a‑mole with Google’s defaults, here are solid privacy‑respecting alternatives — the ones built on Firefox’s engine are fully independent of Google’s browser entirely:
⚖️ Is what Google is doing GDPR‑compliant — and morally OK?
We’re a digital agency, not your lawyers — so take this as an informed opinion, not legal advice. On the strict letter of GDPR, on‑device processing is actually a point in Google’s favour: keeping data local is exactly the kind of data minimisation the regulation encourages. The harder questions are about consent and transparency: GDPR (and the ePrivacy rules around storing things on your device) lean heavily on people being clearly informed and able to choose. A multi‑gigabyte model arriving silently, on by default, with the off‑switch buried in chrome://flags, sits uncomfortably with that spirit.
Morally? Our take: the technology is fine — admirable, even. The pattern is not. “Default‑on, opt‑out‑if‑you‑can‑find‑it” treats your device as Google’s infrastructure and your consent as an afterthought. The honest fix is a one‑liner: make it opt‑in. Ask first. Most people would happily say yes — and the ones who say no deserve to be heard. 🤝
🇪🇺 Don’t agree with it? You can do something about it
If you believe a company is mishandling your data or your consent under EU rules, you have the right to complain to a Data Protection Authority — for free. Find your country’s regulator on the official European Data Protection Board list:
Find your EU Data Protection Authority ↗
Because Google’s European HQ is in Ireland, its lead regulator is the Irish Data Protection Commission, which also accepts concerns.
🧭 The bottom line
On‑device AI is a genuinely good idea, and likely the future. But the future shouldn’t install itself on your hard drive without asking. Turn it off if you want to, switch browser if you’d prefer, and — if it bothers you on principle — tell the regulator. Consent isn’t a formality. It’s the whole point.
On the hardware side of the same coin, we also looked at Jolla’s new European privacy phone — and whether privacy beats raw power. 📱
CWA Europe advises businesses on digital privacy, consent strategy and navigating the ever-shifting landscape of data regulation — including building websites that earn user trust by design. Get in touch to discuss your data and compliance strategy.
References & further reading
- Google Chrome Developers — official documentation on Built-in AI APIs and Gemini Nano integration in Chrome. developer.chrome.com/docs/ai
- Chromium Blog — announcements covering Chrome’s on-device model rollouts and the Prompt API origin trial. blog.chromium.org
- European Data Protection Board — guidance on data minimisation, on-device processing, and consent requirements under GDPR. edpb.europa.eu
Photo: Jeremy Waterhouse · Pexels.
Frequently asked questions
What exactly is the weights.bin file Chrome downloaded to my computer?
It is the model file for Gemini Nano, Google's compact on-device large language model. Chrome downloads it through its component updater system — the same mechanism that pushes security patches and codec updates — so it arrives silently in the background. The file typically sits inside your Chrome profile directory under a path containing 'OptimizationGuide' or similar, and can run to several gigabytes depending on the version.
Does Chrome's on-device AI model access my personal files or browsing history?
The model itself is just a set of numerical weights — it has no ability to read your disk or send data anywhere on its own. The risk is not the model file but the features that use it: when you invoke Chrome's AI tools (summarisation, 'help me write', smart autocomplete), that text is processed locally by the model. Google states this data stays on-device for those features. However, separate telemetry settings may still send usage signals to Google regardless — check chrome://settings/syncSetup and chrome://settings/privacySandbox.
If I disable the AI features in Chrome, will the downloaded model files be deleted?
Turning off AI features in chrome://settings/ai tells Chrome it no longer needs the model, which should prompt the component updater to remove it — but this can take time and is not always immediate. The most reliable approach is to also disable the relevant flags in chrome://flags and, if you want certainty, manually delete the model folder from your Chrome profile directory. On Windows it is typically found under %LOCALAPPDATA%GoogleChromeUser DataOptimizationGuide; on macOS under ~/Library/Application Support/Google/Chrome/OptimizationGuide.
Is it legal under GDPR for Chrome to download a multi-gigabyte file without asking?
This sits in a legal grey area. GDPR's ePrivacy rules require clear consent before storing data on a user's device — and a multi-gigabyte model file is unambiguously stored on your device. Google's defence is that on-device processing serves a legitimate interest (privacy-preserving AI) and that the model is a functional component, not personal data. Whether that reasoning satisfies the consent requirement is a matter regulators have not yet definitively ruled on. If you believe your rights have been infringed, you can raise a concern with your national Data Protection Authority — in the EU, find yours at edpb.europa.eu.