Google Chrome has been reported to download a roughly 4GB local AI model file in the background without explicit user permission, sparking debate about privacy, storage usage, and environmental impact.
The files are related to Gemini Nano and are mainly used for Chrome’s local AI features. The dispute is not simply that the browser supports local AI, but whether the download process is transparent enough, whether users should be informed in advance, and whether system resources are being used reasonably.
What happened
The model file being discussed is named weights.bin and is located in Chrome’s OptGuideOnDeviceModel directory. It is believed to be a localized version of Gemini Nano, used to perform some AI inference directly on the device.
Chrome decides in the background whether to download it based on hardware capability, especially RAM and VRAM. Users generally do not need to start the download themselves, and they may not see a clear prompt before it happens.
The more frustrating part is that manually deleting the model file usually does not stop it from coming back. As long as the related feature remains enabled, Chrome may download the model again after a restart or a later update.
The platforms mentioned in the discussion include Windows 11, macOS, and Ubuntu desktop systems. Based on Chrome’s desktop install base, the number of potentially affected devices could reach hundreds of millions.
Google’s explanation
Google says these files support local AI features such as “Help me write” and scam detection. Running the model locally can reduce some data uploads and improve privacy protection.
Google also says that if device storage is low, Chrome will automatically remove the related model to free up space. In other words, the model does not necessarily occupy disk space permanently.
At the same time, Google says users have been able to disable the related feature in Chrome settings since February 2024. Once disabled, the model will no longer continue downloading or updating.
How to check and disable it
If you do not want Chrome to keep the Gemini Nano model locally, start by checking a few places.
First, open Chrome settings and look for options related to “on-device AI”, local AI, writing assistance, or optimization suggestions, then disable the features you do not need.
Second, enter this in the address bar:
|
|
Then search for and disable:
|
|
Finally, check Chrome’s user data directory for the OptGuideOnDeviceModel folder and delete the model files inside it. Keep in mind that deleting the file alone is usually not enough. It is better to disable the related flag or setting first, otherwise Chrome may download it again later.
Possible paths on different systems
OptGuideOnDeviceModel is usually under Chrome’s user data directory. The exact location can vary depending on the operating system and installation method, but these are good places to check first:
- Windows:
%LOCALAPPDATA%\Google\Chrome\User Data\ - macOS:
~/Library/Application Support/Google/Chrome/ - Linux:
~/.config/google-chrome/ - Chromium:
~/.config/chromium/
After opening the relevant directory, search for OptGuideOnDeviceModel or weights.bin. If you use Chrome Beta, Dev, or Canary, the directory name may include the corresponding release channel.
How to tell whether weights.bin has been downloaded
The simplest method is to search Chrome’s user data directory for:
|
|
If it has been downloaded, it will usually appear inside OptGuideOnDeviceModel, and the file size may be close to several GB. You can also check the modified time to see whether Chrome recently created or updated it in the background.
If you cannot find weights.bin, that does not necessarily mean the device will never download it. Chrome may decide whether to fetch the model based on hardware conditions, region, version, feature flags, and experiment configuration.
Which Chrome AI features may be affected
After disabling the related local AI or optimization features, some on-device capabilities that depend on Gemini Nano may be affected, such as “Help me write”, local scam detection, and future browser AI features that do not go through the cloud.
For users who do not use these features, everyday browsing is usually not affected much. For users who frequently use Chrome’s built-in writing assistance, page understanding, or experimental safety detection features, the experience may fall back to cloud processing, become unavailable, or use another browser-provided alternative.
Where the controversy lies
The central question is whether a browser should download several GB of model files for AI features before the user has clearly agreed.
Supporters argue that local AI can reduce cloud processing, improve privacy, and make responses faster. Critics argue that users should at least see a clear prompt before the download, especially when the file is close to 4GB and may affect storage space and network traffic.
Privacy experts also point out that this kind of insufficiently disclosed background download may raise compliance questions under the EU ePrivacy Directive and GDPR. Whether it constitutes a violation depends on Google’s notice mechanism, default settings, data processing path, and user controls.
Summary
Chrome’s adoption of Gemini Nano shows that browsers are moving more AI capabilities onto the local device. But it also creates a new product boundary problem: local models still consume disk space and bandwidth, and they can affect the user’s sense of control over their own device.
For ordinary users, the most direct step is to check Chrome’s local AI and optimization settings. If you do not need these features, disable the related options and then delete the model files in the OptGuideOnDeviceModel directory.