Squashing Gemini Nano

 Close-up of a squashed, overripe yellow banana peel discarded on dark, textured asphalt. The fruit is partially mashed and oozing onto the pavement, creating a messy, flattened shape.
Banana image by PJ R on Flickr CC BY-NC 2.0

A colleague recently alerted me to the fact Google Chrome is silently downloading Gemini Nano onto our computers without a clear opt-in or notification. While the model is downloaded to our device, several AI features still route queries to Google's cloud servers, obfuscating what is actually being processed locally. For those who value digital self-reliance and owning one’s own processes, this "silent install" is a significant overreach.

So, I immediately went to Google’s Gemini to investigate. From the horse’s mouth, as it were:

This download, which can take up approximately 4GB of local storage, is intended to power on-device AI features like "Help me write," web page summarization, tab organization, and scam detection. If you want to reclaim your storage or prevent the download, you can generally manage these settings by:
  • Navigating to Chrome Settings.
  • Selecting AI Innovations (or Experimental AI).
  • Disabling features like "Help me write" or "History search".

After turning off all the “AI innovations”, I asked what remaining files to delete.

Since you've already toggled off the "AI Innovations" (or Experimental AI) settings, Chrome should theoretically stop using the model, but it often leaves the massive weights.bin file behind on your drive.
Copy and paste the following into your File Explorer address bar:
%LOCALAPPDATA%\Google\Chrome\User Data\Default\OptGuideOnDeviceModel\
Once you are in that folder, you are looking for:
A folder typically named with a version number (e.g., 125.0.0.0).
Inside that versioned folder, you will find weights.bin. This is the bulk of the 4GB download.
You can safely delete the entire OptGuideOnDeviceModel folder.

There was some searching and correcting Gemini, but I found that deleting the 4GB weights.bin file is only half the battle.

Beyond the AI model, the "ghost" data in Chrome often extends to the GPUCache.
Chrome builds a massive cache of "shaders" to speed up graphics rendering on your GPU. Over time, these can balloon into several gigabytes and they rarely clean themselves up.
Path: %LOCALAPPDATA%\Google\Chrome\User Data\Default\GPUCache
Action: You can safely delete everything inside the GPUCache folder. Chrome will just rebuild what it needs for the sites you actually visit.
Clearing these requires fully killing Chrome’s background processes via Task Manager before the files can be unlinked and deleted from your Default profile folder. Be sure to also check your System Tray (by the clock) and right-click "Exit" Chrome there, or the files will remain "in use."
Summary of Cleanup Paths:
AI Model: %LOCALAPPDATA%\Google\Chrome\User Data\OptGuideOnDeviceModel\
Shader Cache: %LOCALAPPDATA%\Google\Chrome\User Data\Default\GPUCache
Since you are on Windows 11, if you want to see exactly where the bloat is without clicking through a hundred folders, open PowerShell as Admin and run this command:
Get-ChildItem -Path "$env:LOCALAPPDATA\Google\Chrome\User Data" -Recurse | Where-Object { $_.Length -gt 100MB } | Select-Object FullName, @{Name="SizeGB";Expression={$_.Length / 1GB}}

Running that led me to the component_crx_cache, a 7GB (!) temporary storage zone for compressed extension and component files (CRX files).

This is a cache folder. This is where Chrome stages large updates. Deleting the contents of component_crx_cache is safe.
How to clear it:
Close Chrome (and check Task Manager for any lingering processes).
Navigate to: %LOCALAPPDATA%\Google\Chrome\User Data\component_crx_cache\
Delete everything inside that folder.

I waited a couple days to see if Chrome (or my 18 month old desktop) would crash or if it would just reinstall Gemini Nano. It did. Reinstall Gemini Nano, not crash my computer.

Gemini then sent me on a snipe hunt for “Hidden Download Flags.” I found one, “Enables optimization guide on device”, and disabled it. After reporting my ‘failure’ Gemini replied:

It appears Google has already begun "cleaning up" the flags menu as the May 2026 rollout progresses, likely to prevent users from easily toggling these features off. If you don't see those specific flags, it means your version of Chrome has moved these controls into the Enterprise Policy layer.
Since the flags are missing, you must use the policy override. This is the "Nuclear Option" that ensures Chrome doesn't even attempt to check for the model.
Close Chrome completely. (Check Task Manager to ensure no "Google Chrome" processes are lingering).
Open Registry Editor(Win + R, type regedit).
Navigate to:HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome
If you don't see "Google" or "Chrome," right-click the "Policies" folder > New > Key, and name them accordingly.
Create the Value:
Right-click in the right pane > New > DWORD (32-bit) Value.
Name it: GenAILocalFoundationalModelSettings
Double-click it and set the Value data to 1.
Confirming the change:
Reopen Chrome and type chrome://policy in the address bar.
Click Reload Policies.
Search for GenAILocalFoundationalModelSettings. It should show a status of "OK" with a value of 1.
Once the Registry policy is active, Chrome is essentially forbidden from talking to the model server.
Go to chrome://components.
Find Optimization Guide On Device Model.
Click Check for update.

I didn’t find the "Optimization Guide On Device Model" entry in components. Gemini replied:

Since the "Optimization Guide On Device Model" entry has completely disappeared from your chrome://components page after applying the policy, you have actually achieved the most complete form of "removal" possible.
In Chrome’s architecture, if a component is missing from that list entirely, it means the browser no longer recognizes it as a valid part of your installation. By setting the GenAILocalFoundationalModelSettings policy to 1, you effectively told Chrome: "This component is forbidden in this environment."

Always looking out for me, Gemini suggested:

Check chrome://policy one last time: Ensure GenAILocalFoundationalModelSettings is there with a status of "OK".
Look at your drive: Ensure the folder C:\Users\sawah\AppData\Local\Google\Chrome\User Data\OptGuideOnDeviceModel remains empty or deleted. To ensure the browser has fully cleared its internal state. You can trigger a reload that bypasses the cache by holding the Shift key while clicking the Refresh button in the browser toolbar.

Eureka! As we say here in California. Everything seems to be stable and I’ve cleared 11GB of Google slop from my computer. And a hat tip to Cory Doctorow for getting to "Google slop" first!

Stay tuned...

References

  • Arntz, P. (2026, May 6). Google Chrome’s silent 4GB AI download problem. Malwarebytes
  • Doctorow, C. (2025, July 15). The Inhuman Gigapede: Coprophagic AI. Medium
  • Joseph, J. (2026, May 7). Chrome is quietly downloading a 4GB AI model without your permission. PCMag
  • Thurrott.com. (2026, May 7). Google clarifies how Chrome’s built-in AI features use local storage. Thurrott
  • Tom’s Hardware. (2026, May 6). Google Chrome 'silently' downloads 4GB AI model to your device without permission. Tom's Hardware