MilikMilik

Chrome’s Hidden 4GB Gemini Nano: How to Find It, Delete It, and Stop It Coming Back

Chrome’s Hidden 4GB Gemini Nano: How to Find It, Delete It, and Stop It Coming Back

What Gemini Nano Is and Why It’s Using 4GB of Chrome Storage Space

Chrome has quietly bundled a local large language model called Gemini Nano that sits inside your browser folders as a file typically named weights.bin, taking up around 4GB of disk space. This on‑device AI powers features like scam detection, autofill improvements, writing assistance, tab organization, and other smart helpers that use Chrome’s on‑device Gemini API instead of calling cloud models. Running AI locally can be better for privacy because data does not need to leave your machine, but the trade‑off is significant storage usage that many users were never explicitly warned about or asked to approve. A clean Chrome install already consumes several gigabytes, and over time profiles, cache, and extensions grow even larger, so this extra 4GB chunk can go unnoticed until your drive starts to feel cramped. Understanding what the model does is the first step before deciding whether Gemini Nano removal is right for you.

Chrome’s Hidden 4GB Gemini Nano: How to Find It, Delete It, and Stop It Coming Back

How Chrome Ended Up Installing a 4GB AI Model Without You Noticing

Chrome’s local AI model has not suddenly appeared; reports indicate it has been downloading to eligible machines since 2024. Whether it lands on your system depends on hardware capabilities, your Google account features, and whether sites you visit request the on‑device Gemini API. That staggered rollout explains why some people only recently noticed a 4GB hit to their Chrome storage space. Early configurations required digging into experimental flags, and many users never realized that enabling or leaving AI helpers on by default allowed Chrome to fetch weights.bin in the background. Even if you thought you had opted out of AI features, toggles were scattered and their wording has evolved across Chrome versions, causing confusion about what is actually disabled. Because the model is treated as a core optimization component rather than a typical download, there is no conventional installer prompt, so the AI model arrives silently inside Chrome local storage instead of a visible app.

Step 1: Confirm Whether the Gemini Nano AI Model Is Installed

Before attempting AI model deletion, you should verify whether Chrome has already pulled the Gemini Nano package. Close Chrome, then open your file manager or terminal and navigate to your user profile’s Chrome data directory. Look for a folder named OptGuideOnDeviceModel; inside it, search for a weights.bin file around 4GB in size. On some systems, a quick way to locate it is to search within the Chrome profile directory for files larger than 1GB and review the results. If you do not see OptGuideOnDeviceModel or a large weights.bin file, Chrome may not have installed the local model yet, or you might have successfully avoided or previously disabled on‑device AI. If the file is present, note its location but do not delete it yet; removing it without changing settings will usually cause Chrome to quietly re‑download the model the next time its AI features are triggered.

Step 2: Disable Chrome’s On‑Device AI So the Model Stops Reinstalling

To permanently stop Gemini Nano from returning, you must disable Chrome’s on‑device AI before deleting the model. Open Chrome and go to the internal settings page for experimental features by entering chrome://flags in the address bar. In the search box on that page, look for an entry called optimization-guide-on-device-model. Change its setting from Default or Enabled to Disabled, then restart Chrome so the new configuration takes effect. In some newer versions, there is also a dedicated toggle in Chrome’s System or AI settings that turns local AI off completely; switching it off should prevent future downloads and may trigger automatic removal when storage is low. These controls can vary slightly across operating systems and Chrome versions, so check both flags and regular settings. Once you have disabled on‑device AI everywhere it appears, Chrome should stop treating the weights.bin file as required and will no longer silently restore it.

Step 3: Safely Delete the 4GB Weights.bin File and Verify Cleanup

After disabling on‑device AI, you can manually reclaim Chrome storage space by deleting the Gemini Nano model. Close all Chrome windows, return to the OptGuideOnDeviceModel directory in your Chrome local storage, and delete the weights.bin file. If your system sends deleted files to a recycle bin or trash folder, empty it to free the full 4GB. Next, reopen Chrome and use it normally for a while, especially on sites you frequent, then close the browser and recheck the directory. If the file has not reappeared, your Gemini Nano removal was successful and Chrome AI model deletion is complete. Should weights.bin return, revisit chrome://flags and any AI or system settings to ensure every on‑device option is disabled. Periodically re‑scanning your Chrome profile for large files is a simple way to confirm that Chrome local storage is not being quietly repopulated with a new copy of the model.

Comments
Say Something...
No comments yet. Be the first to share your thoughts!