What Chrome’s Hidden 4GB Gemini Nano Model Actually Is
If your disk space has mysteriously shrunk, Chrome’s on-device Gemini Nano AI model may be the culprit. Since 2024, Chrome has been quietly downloading a roughly 4GB file called weights.bin into a folder named OptGuideOnDeviceModel when certain AI features are enabled. This local model powers features like scam detection, writing assistance, autofill suggestions, tab organization, and other Gemini-based helpers inside the browser. Running the model locally can be a privacy win because your data doesn’t have to be sent to cloud servers for every request. However, Chrome has been doing this without clearly explaining the storage cost or asking for explicit permission. The download doesn’t happen for everyone at the same time—Chrome considers your hardware, Google account features, and whether you visit sites that use the on-device Gemini API. That staggered rollout is why many users are only discovering the 4GB footprint now.
How to Check If Gemini Nano Is on Your System
You don’t need special tools to confirm whether Chrome’s local AI model is sitting on your drive. Start by locating Chrome’s profile or data directory on your system, then look for a folder called OptGuideOnDeviceModel. Inside, the main file to watch for is weights.bin, typically around 4GB in size. Its presence indicates that Chrome has installed the Gemini Nano model locally. On some systems, you can also search for large Chrome-related files by scanning for files over 1GB in the Chrome data path. If you’ve used Gemini-based features such as Help Me Write, scam detection, or enhanced autofill, there’s a good chance the model is already there. Users who disabled AI options early often find that the file never downloaded, which shows that the install is tied to feature usage and settings rather than being universally forced on every Chrome installation.
Step-by-Step: Safely Deleting the 4GB Gemini Nano Model
Once you’ve confirmed that weights.bin is on your system, you can reclaim that chunk of storage. First, close all Chrome windows to ensure the file isn’t in active use. Next, navigate to the OptGuideOnDeviceModel folder inside your Chrome data directory and delete the weights.bin file. This immediately frees up several gigabytes of space. However, deletion alone isn’t permanent. If Chrome still thinks on-device AI is allowed, it can silently redownload the model in the background the next time a Gemini-powered feature is triggered. That’s why you should pair manual removal with disabling the local AI setting inside Chrome (covered in the next section). Without that step, Chrome treats the missing file as a corrupted or incomplete model and simply restores it, undoing your efforts to reduce Chrome storage bloat.
How to Stop Chrome from Reinstalling Gemini Nano
To prevent Chrome from undoing your cleanup, you need to turn off its on-device AI model. Chrome provides a system-level toggle that disables local AI, deletes the model, and blocks future downloads. You can access Chrome’s internal settings by entering chrome://flags in the address bar. There, search for an entry named optimization-guide-on-device-model. Set this flag to Disabled, then restart Chrome. After the restart, Chrome should remove the weights.bin file automatically if it hasn’t already been deleted. With the flag off, Chrome will no longer fetch the Gemini Nano model even if you visit websites using the on-device Gemini API. This gives you practical control over AI model storage while still letting you decide later whether to re-enable specific AI features, rather than having a 4GB model silently reappear every time those features are triggered in the background.
What Changed in 2026—and How to Manage AI Going Forward
In 2026, many users assumed Chrome had suddenly pushed a new 4GB AI model onto every machine, but the underlying behavior hadn’t actually changed. The Gemini Nano model has been hovering around 4GB since it rolled out in 2024, and its installation still depends on your hardware, account configuration, and browsing patterns. The renewed attention came when more people discovered weights.bin and noticed a wording change around Chrome version 148, where a clear statement about not sending data to Google’s servers was removed from the local AI toggle description. Even though the file size and basic behavior remain the same, this raised concerns about transparency and default choices. Looking ahead, the safest strategy is to treat AI features as opt-in. Periodically review Chrome’s system and AI-related settings, ensure on-device AI is disabled if you don’t need it, and keep an eye on your browser’s disk footprint so you can reclaim disk space whenever hidden models appear.