Millions of Chrome users may have an unexpected guest on their hard drives: a 4GB file called weights.bin. Google has been quietly storing this AI model file through its browser without explicit user permission.
What Is Weights.bin?
The file is part of Google's on-device AI system built into Chrome. It powers features like real-time translation and smart text suggestions. The company began rolling out this capability in recent months as part of its push to bring more AI processing directly to users' machines.
Unlike cloud-based AI services that process data on remote servers, this approach keeps computations local. That means faster response times and improved privacy since data never leaves the device. But the trade-off is significant storage consumption.
Why This Matters
This practice affects anyone using Chrome who did not explicitly agree to store large AI files locally. For users with limited storage space, especially those on laptops with small SSDs or older computers, a sudden 4GB file can be disruptive. The issue also raises questions about consent and transparency in how tech companies deploy AI features.
Users who never opted into this feature may find their available storage unexpectedly reduced. The file does not appear in standard downloads folders, making it harder to detect without manual inspection.
How to Check and Remove It
The weights.bin file is located in Chrome's application support folder. On Windows, users can find it under AppDataLocalGoogleChromeUser DataDefaultOptimization GuideOnDeviceHeadModel. Mac users should look in ~/Library/Application Support/Google/Chrome/OptimizationGuide/OnDeviceHeadModel.
Deleting the file will remove the local AI capabilities but will not harm Chrome's core functionality. Users who want these features back can re-enable them through Chrome settings later if desired.
A Broader Trend
Google is not alone in pushing AI processing to local devices. Apple, Microsoft and other major tech firms are developing similar on-device models for speed and privacy benefits. But the quiet deployment approach has drawn criticism from privacy advocates who argue users deserve clearer notifications before such changes occur.
The incident highlights growing tensions between convenience and transparency as artificial intelligence becomes deeply embedded in everyday software.



