Google Chrome is facing criticism after users discovered that the browser can quietly place a multi-gigabyte local AI model on their computers. The issue has drawn attention because the file is large, the download may not be obvious to ordinary users, and deleting the file manually may not stop Chrome from downloading it again.

The concern is not simply that Chrome has AI features, but rather that browser-based AI is moving from optional cloud tools into local system storage, using disk space and bandwidth without the kind of clear, up-front warning many users would expect.

For people with large modern desktops, a 4GB file may not sound serious. But for laptops with smaller SSDs, metered connections, managed workstations, virtual machines, older systems, or business fleets with hundreds of endpoints, a silent 4GB browser component becomes a real administrative problem.

What Chrome is Reportedly Downloading

The file at the center of the controversy is tied to Google's on-device AI work in Chrome. Reports identify the model as Gemini Nano, a local AI model used by Chrome for features that can run directly on the user's computer instead of sending every request to the cloud.

That local approach has an upside. Running some AI tasks on the device can reduce cloud processing, improve responsiveness, and potentially protect privacy by keeping certain operations local. Google also documents built-in AI features for Chrome developers, including local model management, downloads, updates, and purging. (Source: chrome.com)

Why Users Are Upset

The rollout has angered users because of how the model appears to arrive. Reddit users in r/sysadmin and Chrome communities have been discussing reports that Chrome placed roughly 4GB of AI-related files on systems without a clear consent prompt. Some users say the files appear under Chrome's user data directories, including folders associated with on-device optimization or AI model storage. (Source: reddit.com)

The main complaint is control. Most users understand that modern browsers update themselves, download security components, refresh phishing lists, and cache data. But a multi-gigabyte AI model feels different. It is large enough to affect storage, backups, software inventory, endpoint monitoring, and network usage.

The problem becomes worse if deleting the file is not enough. Several reports say that manually removing the model may only be temporary if Chrome still has the related AI features enabled. In that case, Chrome may download the model again later.

That behavior makes the issue feel less like ordinary browser maintenance and more like a feature being pushed onto the machine. Even users who are not opposed to AI may object to a browser deciding to reserve several gigabytes of local storage without a plain-language prompt.

Why Google Wants Local AI in Chrome

Google's broader goal is easy to understand: the browser as well as the search engine is becoming an AI platform. Instead of relying only on websites or cloud tools, Chrome can expose AI capabilities to web apps and browser features. That could allow tasks such as writing assistance, summarization, translation, scam detection, and autofill improvements to happen locally.

From a technical standpoint, Google's move to push AI is not surprising. Microsoft is building AI into Windows and Edge, Apple is building Apple Intelligence into macOS and iOS, and Google is building Gemini into Android, Search, Workspace, and Chrome. Even PC hardware is being redesigned around AI, with AMD promoting Ryzen AI processors that include a dedicated neural processing unit, and Intel Core Ultra chips also shipping with built-in AI acceleration.

This matters because Chrome's local AI model is not an isolated browser experiment. It is part of a much larger shift toward on-device AI, where software companies and chipmakers both want AI workloads running directly on the user's machine. AMD describes Ryzen AI systems as combining an NPU, CPU, and GPU to accelerate AI workloads locally, while Intel says Core Ultra AI PCs can run AI directly on the PC. In other words, the browser, the operating system, and even the processor are all being pushed in the same direction: more AI processing on the device itself. (Source: amd.com)

How to Check for the Local AI Model

On Windows, users can look under Chrome's user data folders for directories associated with on-device models. Common areas to check include the Chrome profile data under the user's AppData folder. The exact path can vary depending on Chrome version, profile, and rollout status.

A practical starting point is:

%LOCALAPPDATA%\Google\Chrome\User Data\

From there, users can search for large files or folders related to on-device model storage. Reports have mentioned names such as weights.bin and folders related to OptGuideOnDeviceModel, though the exact names may change over time. One utility I suggest using is TreeSize Free which helps to spot large files in a directory tree with many folders.

On macOS, Chrome user data is generally stored under the user's Library application support folders. Users can search the Chrome profile directory for unusually large AI model files.

How to Disable Chrome's Local AI Model

For Windows users, the most reliable fix is to set Chrome's official policy value in the Registry. This is better than simply deleting the AI model files manually because Chrome may download them again if the feature remains enabled.

Google's Chrome Enterprise documentation says the GenAILocalFoundationalModelSettings policy controls how Chrome downloads and uses the local foundational GenAI model. If the policy is set to 0, or is not configured, Chrome is allowed to download the model automatically and use it locally. If the policy is set to 1, Chrome will not download the model, and any existing downloaded model should be deleted by Chrome. (Source: chromeenterprise.google)

There is one important caveat: this setting blocks Chrome's local foundational GenAI model. It does not necessarily disable every AI-related feature in Chrome, because Google may use separate policies for other AI features. In other words, this is the correct fix for the large local AI model download, but it should not be described as a universal "disable all Chrome AI" switch.

To apply the setting:

1. Click Start, type "cmd" (no quotes); wait for "CMD.EXE" or "Command Prompt" to appear, right click and select "Run as administrator".
    
2. Highlight the text below with your mouse:
   
   reg add "HKLM\SOFTWARE\Policies\Google\Chrome" /v GenAILocalFoundationalModelSettings /t REG_DWORD /d 1 /f
echo this is a dummy line
 
3. Right click over top of the highlighted text and select "Copy" from the dialogue menu.
    
4. Go to the command prompt you opened in Step #1 above and right click into the black window. The command you copied in Step #2 should be output to the command prompt and executed.

Google also documents that Chrome policies can be configured on Windows by modifying the Windows Registry, including under the machine-wide policy area used by this command. (Source: support.google.com)

After running the command, restart Chrome. Then type chrome://policy into Chrome's address bar, click Reload policies, and confirm that GenAILocalFoundationalModelSettings appears with a value of 1. If it does, Chrome should be blocked from downloading or using the local foundational AI model.

Conclusion

Chrome's local AI model is not automatically malware, and local AI is not automatically bad. On-device AI can offer privacy and performance benefits when it is implemented carefully. But, users have a legitimate complaint when a browser quietly downloads several gigabytes of AI files without a clear, up-front explanation. The issue is not just storage. It is consent, transparency, and control.

As AI becomes built into browsers, operating systems, office suites, phones, and search engines, users should expect a simple rule: ask first, explain clearly, and provide a real off switch.

What's Your Opinion?

Should Chrome be allowed to download local AI models automatically if the features improve privacy and security? Or should any multi-gigabyte AI component require clear user approval first? Have you found large AI model files inside your Chrome profile folder? If so, did disabling Chrome's AI features remove them permanently, or did they return after a browser update?