⚡ Verified — May 21, 2026. If you use Google Chrome, there is a very high chance your computer has a hidden 4GB AI file on it right now. Not might have. Has. You never saw a prompt. You never clicked agree. You were never told it was happening. The file is called weights.bin. It lives inside an intentionally obscure folder named OptGuideOnDeviceModel buried inside your Chrome profile. It powers Google's on-device Gemini Nano AI. Chrome installs it automatically when your hardware qualifies. If you delete it, Chrome downloads it again. Privacy researcher Alexander Hanff proved this forensically on May 4, 2026 using macOS kernel logs on a Chrome profile that was never touched by human hands. At Chrome's scale of 3.45 billion users, the carbon cost of this planetary-scale silent push falls between 6,000 and 60,000 tonnes of CO2. Google confirmed the file exists and defended the practice. This article tells you exactly where it is, what it is actually doing, whether you should be alarmed, and — most importantly — how to stop it permanently. Sources: Alexander Hanff, thatprivacyguy.com, May 4, 2026; Tom's Hardware, May 5, 2026; Malwarebytes, May 6, 2026; Snopes, May 8, 2026; TechRadar, May 8, 2026.
Your computer is yours. The hard drive is yours. The storage is yours. You paid for every gigabyte of it. So here is the question: when did you agree to let Google use 4 of those gigabytes for an AI model you did not choose, cannot easily find, and — until someone published forensic proof — had no way of knowing was there? You didn't. And that is the story that has been building quietly since 2024, before it broke in early May 2026 when security researcher Alexander Hanff published the proof. Not as a rumour. Not as speculation. As a forensic log showing the exact second a 4GB AI model arrived on a machine that no human had ever touched.
The story became mainstream on May 4, 2026 when Hanff — a privacy researcher and lawyer who runs ThatPrivacyGuy.com — published a detailed technical analysis of what Chrome had done to a fresh user profile he had created specifically for an automated privacy audit. His methodology made the finding impossible to dismiss: he created the Chrome profile on April 23, 2026. He let an automated script — running entirely through Chrome DevTools Protocol — load 100 webpages. No human ever opened the settings menu. No human ever typed a character. No human ever clicked an AI feature. By April 24, macOS kernel logs recorded the precise moment a 4GB AI model had finished writing itself to the Chrome data directory. Chrome had not asked. Chrome had not notified. Chrome had simply decided your machine qualified and taken the storage. Sources: Alexander Hanff, thatprivacyguy.com, May 4, 2026; TechSpot, May 5, 2026; Cybernews, May 5, 2026.
Within 48 hours, Tom's Hardware, Malwarebytes, Cybernews, TechSpot, Gizmodo, TechRadar, and Snopes had all independently confirmed the behavior. Snopes tested it specifically on machines belonging to their own staff — two Chrome users on macOS, one on Windows — and found the file on all three. The gHacks report confirmed it on Windows 11, Apple Silicon Macs, and Ubuntu Linux. Community forum posts show the same weights.bin file appearing in user reports dating back over a year. This is not a newly introduced behavior that emerged in May 2026. What emerged in May 2026 was the forensic proof, the media attention, and — for the first time — a widespread public awareness that it was happening at all. Sources: Snopes, May 8, 2026; gHacks, May 6, 2026; TechRadar, May 8, 2026.
What Exactly Is weights.bin — And Why Is Chrome Allowed to Put It There?
The file is called weights.bin. It contains the binary model weights for Gemini Nano — Google's lightweight on-device large language model, the same family that powers AI features on Pixel phones. Chrome stores it in a folder called OptGuideOnDeviceModel inside your Chrome user data directory. That folder name is not an accident. OptGuideOnDeviceModel is Chrome's internal jargon for 'Optimization Guide on-device model storage.' If Google had named it GeminiNanoAI, any user doing a storage cleanup would know exactly what it was. The deliberately opaque name means the vast majority of users who encounter it — perhaps during a disk cleanup or storage audit — will not recognise what they are looking at without researching it. The path on each platform: Windows: %LOCALAPPDATA%\Google\Chrome\User Data\OptGuideOnDeviceModel. macOS: ~/Library/Application Support/Google/Chrome/. Linux: ~/.config/google-chrome/. Sources: gHacks, May 6, 2026; HackingPassion.com, May 7, 2026; ppc.land, May 8, 2026.
Gemini Nano is designed to perform AI inference locally on your device — processing text without sending it to Google's servers. Chrome uses it to power three features that are enabled by default in recent versions: the 'Help me write' text assistant that appears in right-click menus across the web, an on-device scam detection system inside Chrome's enhanced protection mode, and a Summarizer API that websites and extensions can call to summarise page content without a network round-trip. These features can activate without you ever deliberately choosing to engage with an AI feature. If you have right-clicked inside a text box in Chrome 120 or later — which is any Chrome released in 2024 or 2025 — Gemini Nano running on your local storage may have already processed your text. Sources: Malwarebytes, May 6, 2026; Google spokesperson via Gizmodo, May 6, 2026.
Multiple independent reports — including gHacks — also found that Chrome does not consistently clean up older model versions when downloading updates. Some users discovered multiple version directories stacked inside the OptGuideOnDeviceModel folder, with combined sizes totalling 12GB or more. Not one installation. Multiple. On a device with a 128GB SSD — the standard in mid-range laptops — 12GB is nearly 10% of total storage consumed by a feature most users did not know they had. Source: gHacks, May 6, 2026; Medium, Sathish Raju, May 6, 2026.
Is It on Your Computer Right Now? The Two-Minute Check for Every Platform
Before deciding what to do, confirm whether the file is actually present on your machine. The folder name — OptGuideOnDeviceModel — is consistent across all three desktop platforms. This check takes under two minutes regardless of your operating system.
- Windows: Press Win+R, type %LOCALAPPDATA%\Google\Chrome\User Data and press Enter. Look for a folder named OptGuideOnDeviceModel. Right-click it and choose Properties to see the size. Anything approaching 4GB confirms Gemini Nano is installed. You can also type chrome://on-device-internals directly into Chrome's address bar for a real-time status readout showing whether the model is loaded and which version is present. If you find multiple numbered subdirectories inside OptGuideOnDeviceModel, add their sizes — the total may significantly exceed 4GB. Sources: TechSpot, May 5, 2026; Hackread.com, May 8, 2026.
- macOS: Open Finder, press Cmd+Shift+G, paste ~/Library/Application Support/Google/Chrome and press Enter. Look for the OptGuideOnDeviceModel folder and right-click it to choose Get Info. For a precise terminal measurement, run: du -sh ~/Library/Application\ Support/Google/Chrome/Default/OptGuideOnDeviceModel/. Apple Silicon and Intel Macs have both been confirmed to receive the file — there is no hardware-family exemption. Source: Alexander Hanff, thatprivacyguy.com, May 4, 2026; Snopes, May 8, 2026.
- Linux: Open a terminal and run: du -sh ~/.config/google-chrome/OptGuideOnDeviceModel. A result near 4G or higher confirms the model is present. The Ubuntu confirmation — alongside Windows and macOS confirmations from independent reports — means the download is cross-platform on all three major desktop systems Chrome supports. Source: Alexander Hanff, thatprivacyguy.com, May 4, 2026; gHacks, May 6, 2026.
- Not finding the folder? Google states the download only occurs on devices that meet specific hardware requirements — sufficient RAM, available storage, and adequate GPU memory. Chrome internally evaluates a 'performance class' score for each device before deciding whether to deploy the model. If your machine does not qualify, the file may not be present yet. This does not mean Chrome asked before installing it on machines that did qualify — only that yours did not cross the threshold for automatic deployment. Source: HackingPassion.com, May 7, 2026.
The Consent Problem: Google's Explanation Versus What Actually Happened
Google's official response — delivered by a spokesperson to Gizmodo and Yahoo Tech on May 6, 2026 — is this: 'We've offered Gemini Nano for Chrome since 2024 as a lightweight, on-device model. It powers important security capabilities like scam detection and developer APIs without sending your data to the cloud.' The spokesperson also confirmed that in February 2026, Google began rolling out a setting allowing users to disable the download directly in Chrome Settings, adding: 'Once disabled, the model will no longer download or update.' From Google's perspective, the deployment is covered by Chrome's existing terms of service, was described on a Chrome help page, and is a privacy benefit — keeping your data local rather than sending it to a server. Source: Google spokesperson via Gizmodo and Yahoo Tech, May 6, 2026.
Here is where Hanff's analysis becomes legally precise in a way Google's response does not fully address. Under Article 5(3) of the EU's ePrivacy Directive — which has been in force since 2002 — storing information on a user's device requires prior, freely given, specific, informed, and unambiguous consent, except where that storage is strictly necessary for a service the user explicitly requested. Gemini Nano powers features that are default-on and that the user never specifically requested. Chrome functions fully without it. The 'strictly necessary' exception does not clearly apply. There was no opt-in prompt, no notification at the point of download, and no opt-out accessible in Chrome's primary settings before February 2026. Even the February 2026 setting requires a user to know it exists and navigate to it — a disclosure architecture designed around invisibility rather than meaningful choice. Hanff has formally signalled he may pursue enforcement action. Sources: Alexander Hanff, thatprivacyguy.com, May 4, 2026; ConductAtlas, May 5, 2026.
For American users, the EU legal framework does not apply directly — but the principle does. The California Consumer Privacy Act requires disclosure of data practices and gives California residents specific rights around data stored on their behalf. Beyond jurisdictional law, there is a simpler question: should software installed on your hardware be permitted to permanently write 4 to 12 gigabytes to your storage without asking? On a budget laptop with a 64GB SSD — which represents a substantial portion of the global laptop market, particularly in emerging economies — a 4GB hidden install consumes more than 6% of all available storage. Without asking. Without notifying. On hardware the user bought and owns. That is the claim at the center of this story — and it is not a legal abstraction. It is the experience of a user who opens disk cleanup software, finds a folder they don't recognise eating 4 to 12GB, and has to research whether it is safe to delete. Source: Cybernews, May 5, 2026; ppc.land, May 8, 2026.
60,000 Tonnes of CO2: The Environmental Cost Nobody Is Covering
There is a number in Hanff's analysis that has received almost no coverage relative to the consent story — and it is the most staggering figure in the entire report. Chrome has approximately 3.45 billion users worldwide, confirmed by StatCounter data cited in the research, making it by far the most widely deployed software application on earth. A large but unspecified proportion of those users own devices that meet the hardware threshold for automatic Gemini Nano deployment. Even at a conservative estimate of the eligible fraction, the cumulative data transfer required to push a 4GB file across hundreds of millions of machines represents between 6,000 and 60,000 tonnes of CO2-equivalent emissions. Sources: Alexander Hanff, thatprivacyguy.com, May 4, 2026; Cybernews, May 5, 2026; StatCounter data cited in Hanff analysis.
To contextualise those numbers: 6,000 tonnes of CO2-equivalent is the approximate annual emissions of 1,300 passenger cars driving for a full year. The upper bound — 60,000 tonnes — represents approximately 13,000 cars. This is the atmospheric cost that every person on earth absorbs for a product decision that none of them were consulted about. Google has made significant public commitments to carbon neutrality and environmental sustainability across its product lines. Hanff's argument is direct: a company that takes those commitments seriously would disclose large-scale data transfers at the point they occur and give users a meaningful choice about whether to participate. A silent planetary push of billions of gigabytes sits in uncomfortable tension with public sustainability pledges — regardless of whether any individual user notices the bandwidth cost. Source: Alexander Hanff, thatprivacyguy.com, May 4, 2026.
How to Remove It and Stop It Coming Back — Four Options, Ranked by Permanence
You have real, tested options for removing this file and preventing Chrome from reinstalling it. They are not equally difficult or equally durable. Here is every method, starting from the fastest and working toward the most permanent — with an honest assessment of what each does and does not accomplish.
- Option 1 — Chrome Settings toggle (easiest, 2 minutes, works for most users). Open Chrome and go to Settings > System. Look for a toggle labelled 'On-device AI' or 'Gemini Nano.' Turn it off. Per Google's spokesperson, once disabled, 'the model will no longer download or update.' After disabling the toggle, navigate to the OptGuideOnDeviceModel folder and delete it to immediately reclaim the storage. This is the cleanest and most user-accessible fix. If you do not see the toggle, your Chrome version may predate the February 2026 rollout — update Chrome to the latest version through Settings > About Chrome and then check again. Sources: Google spokesperson via Gizmodo, May 6, 2026; Hackread.com, May 8, 2026.
- Option 2 — Disable via chrome://flags (5 minutes, works on all platforms). Type chrome://flags into Chrome's address bar. Search for 'optimization guide on device' and set it to Disabled. Also search for 'prompt-api-for-gemini-nano' and set that to Disabled. Relaunch Chrome when prompted. After relaunching, manually delete the OptGuideOnDeviceModel folder — it should not redownload with flags disabled. Important caveat: Chrome flags can reset after a major version update. Worth rechecking after any major Chrome release. Sources: aifromthefield.substack.com, May 7, 2026; Neowin, May 6, 2026.
- Option 3 — Windows Registry enterprise policy (10 minutes, most durable fix for Windows). Open Registry Editor via Win+R > regedit. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome. Create a new DWORD (32-bit) value named GenAILocalFoundationalModelSettings and set it to 0. This uses Chrome's enterprise policy layer — the same layer corporate IT teams use to manage Chrome across thousands of machines — to block the model download at a level that survives Chrome version updates, flag resets, and settings changes. It is the most durable fix available on Windows. Only attempt this if you are comfortable with Registry editing — incorrect edits can cause system instability. Sources: aifromthefield.substack.com, May 7, 2026; TechSpot, May 5, 2026.
- Option 4 — Delete the file only (2 minutes, temporary). Navigate to the OptGuideOnDeviceModel folder and delete it to immediately recover the storage. Chrome will redownload the model the next time it checks your hardware eligibility unless you have completed one of the options above first. Choose this if you need the space back immediately and plan to implement a permanent fix separately. Sources: Malwarebytes, May 6, 2026; Neowin, May 6, 2026.
The Part That Is Actually Misleading — And It Is Worse Than the Privacy Story
The honest assessment on the core privacy question: Gemini Nano, for the specific features it powers, is less alarming than the headlines imply. The 'Help me write' feature processes your text locally. The scam detection runs on-device. For those features, on-device AI is a genuine privacy improvement over an equivalent cloud-connected implementation — your text goes to the local model, not to Google's servers. Google's defense that the model 'powers important security capabilities without sending your data to the cloud' is accurate for those specific use cases. If you only evaluate Gemini Nano on the data transmission question, it is actually more privacy-protective than alternatives. Sources: Malwarebytes, May 6, 2026; Google spokesperson via Gizmodo, May 6, 2026.
Here is the genuinely misleading part — and this is the finding from Hanff's analysis that deserves far more attention than the 4GB install story alone. Chrome 147 added a highly visible 'AI Mode' pill directly in the browser's address bar — the most valuable real estate in any browser, the place where your eyes go before anything else when you open a new tab. Any user who discovers that Chrome has silently installed a 4GB local AI model, and who then sees an 'AI Mode' button sitting prominently in that same browser's address bar, will draw a completely natural inference: the local model and the address bar button are connected. Queries typed into AI Mode stay on your device. That is the obvious interpretation given the context. Every part of that inference is wrong. The AI Mode button is a cloud-connected Search Generative Experience surface — every query goes over the network to Google's servers. The local 4GB model does not power the AI Mode button at all. Chrome installed a privacy-protecting local AI on your storage. Then it placed a cloud-connected AI button in your address bar. Two completely separate systems — designed to look like one. Source: Alexander Hanff, thatprivacyguy.com, May 4, 2026; Malwarebytes, May 6, 2026; gHacks, May 6, 2026.
Chrome Is Not Alone: The Broader 2026 Pattern of Silent AI Deployments
Here is what most coverage of this story leaves out: the consent architecture is not a bug or an oversight. It is a deliberate product decision. Google did not accidentally forget to ask you. Asking introduces friction. Friction reduces adoption rates. Reduced adoption means fewer users experiencing Gemini Nano, which slows the feedback loop Google needs to improve the model and justify continued infrastructure investment. The silent deployment is not carelessness — it is a calculated trade-off between user autonomy and product velocity. Google's response confirms this reading: they are not apologising for a mistake. They are defending a strategic decision. Your computer is the product's distribution channel. You were not consulted.
The Chrome case did not emerge in isolation. Two and a half weeks before Hanff published the Chrome analysis on May 4, he published a separate report on April 18, 2026: Anthropic's Claude Desktop application had been quietly installing a browser integration bridge across multiple Chromium-based browsers on users' systems — including browsers the user had never opened during the Claude installation process. The bridge would reinstall itself if removed. Hanff argued this violated the same EU ePrivacy Directive framework. Anthropic updated Claude Desktop in response. Then, two and a half weeks later, the Chrome story broke. The same researcher. The same framework. Two of the highest-profile AI companies in the world — within the same month — deploying software to user machines without meaningful prior disclosure. Sources: Alexander Hanff, thatprivacyguy.com, April 18 and May 4, 2026; Malwarebytes, May 6, 2026.
The structural pattern is consistent across the industry: AI features are being integrated into existing trusted software — browsers, operating systems, productivity suites — in ways that inherit the trust users have already extended to the host application. Nobody consciously installs 'Google's on-device AI assistant.' But virtually everyone uses Chrome. The AI feature arrives inside software people already trust, at a moment they are not expecting it, without any deliberate choice, and the disclosure exists — if at all — in a developer help page or a tech article the user will never read. Reports of the weights.bin file had been appearing in community forums and Reddit threads for over a year before Hanff's May 2026 analysis made it a mainstream story. The behavior is not new. The forensic proof, the mainstream coverage, and the widespread public awareness are. You are now part of that awareness.
Browser Comparison: Which Browsers Ask Before Deploying On-Device AI
| Browser | On-Device AI Model | Consent Flow | Local or Cloud? |
|---|---|---|---|
| Google Chrome | Gemini Nano (~4GB), deployed automatically since 2024 on qualifying devices. Multiple version directories have accumulated to 12GB+ on some machines. | No prior prompt or notification. A toggle was added in Chrome Settings in February 2026 — disabled after installation, not before. Deleting the file triggers automatic redownload until disabled through Settings, flags, or Registry policy. | On-device features (Help me write, scam detection, Summarizer API) process locally. The AI Mode button in the address bar is cloud-connected — queries go to Google's servers, not the local model. |
| Microsoft Edge | Microsoft Phi-3 and other models deployed selectively via Windows AI features. Less publicly documented than Chrome's approach. | AI features prompted during some Edge setup flows. Copilot integration is cloud-connected. Less independent forensic documentation as of May 2026. | Copilot is primarily cloud-connected. On-device model behavior varies by feature. |
| Mozilla Firefox | No on-device LLM deployed automatically. AI features use external APIs via user-chosen extensions. | Any AI extension requires explicit user installation. No automatic background model downloads documented as of May 2026. | Entirely dependent on which AI service the user voluntarily adds. Firefox manages none of this layer. |
| Brave | Optional Leo AI assistant with downloadable on-device models. User-initiated, not automatic. | User must explicitly enable Leo and choose which model to download. No automatic background deployment without user action. | On-device model options available. User controls routing between local and cloud processing on a per-query basis. |
| Apple Safari | Apple Intelligence models integrated at the macOS/iOS level on Apple Silicon devices. | Apple Intelligence requires explicit user opt-in during macOS Sequoia or iOS 18 setup — a clearly presented consent moment before any model is deployed to the device. | On-device processing for most Apple Intelligence tasks. Private Cloud Compute for tasks exceeding on-device capability uses hardware attestation and Apple's stated policy of no server-side logging of user requests. |
Frequently Asked Questions
01Is Chrome using this AI to spy on my browsing history?
No — and this distinction matters. Gemini Nano processes data locally on your device for the specific features it powers: Help me write, on-device scam detection, and page summarisation. It does not transmit your browsing history or text inputs to Google for these functions. The local processing is actually a privacy improvement over equivalent cloud-based features. The legitimate concerns here are consent, storage consumption, and the misleading visual design around the AI Mode button — not covert surveillance of your browsing. What does send data to Google's servers is the AI Mode button in Chrome's address bar, which is a separate cloud-connected system. If you use that button under the assumption your local model handles it, that assumption is incorrect. Sources: Malwarebytes, May 6, 2026; Google spokesperson via Gizmodo, May 6, 2026.
02Will deleting weights.bin break Chrome or affect my bookmarks and settings?
No. Chrome operates completely normally without the file. The features it powers — Help me write in right-click menus, on-device scam detection, the Summarizer API for websites — will stop working, and most users who delete it report noticing no difference in day-to-day browsing. Your bookmarks, passwords, history, extensions, and all settings are completely unaffected. Chrome will attempt to redownload the model unless you disable it via Chrome Settings (Settings > System > On-device AI), the chrome://flags method, or — on Windows — the Registry enterprise policy. Sources: TechSpot, May 5, 2026; Neowin, May 6, 2026.
03Does this affect Chrome on Android or iPhone?
This specific issue — the OptGuideOnDeviceModel desktop download — is confirmed on Windows 11, macOS (both Apple Silicon and Intel), and Ubuntu Linux. Chrome on Android integrates Gemini Nano differently: it operates at the Android system level on qualifying Pixel and Samsung devices rather than as a Chrome-specific user profile directory download. Chrome on iOS operates under Apple's browser engine restrictions and the desktop behavior does not apply. If you primarily use Chrome on a Windows or Mac desktop, this article's findings apply directly to your machine. Sources: Alexander Hanff, thatprivacyguy.com, May 4, 2026; Medium, Sathish Raju, May 6, 2026.
04Can Google face legal consequences for this in the US and EU?
In the EU, Hanff's analysis argues yes — Article 5(3) of the ePrivacy Directive requires prior informed consent before writing data to users' devices, with a narrow exception only for storage strictly necessary to deliver a service the user explicitly requested. Chrome functions without Gemini Nano, so the exception does not clearly apply. A maximum GDPR fine of 4% of Alphabet's 2025 annual revenue of approximately $350 billion would exceed €14 billion. In the US, California's CCPA requires disclosure of data storage practices. Whether EU data protection authorities choose to act is a separate question from whether legal exposure exists. As of May 21, 2026, no formal enforcement action has been filed or announced. Sources: ConductAtlas, May 5, 2026; HackingPassion.com, May 7, 2026.
05What did Google officially say about this?
A Google spokesperson told Gizmodo and Yahoo Tech on May 6, 2026: 'We've offered Gemini Nano for Chrome since 2024 as a lightweight, on-device model. It powers important security capabilities like scam detection and developer APIs without sending your data to the cloud.' Google confirmed that in February 2026, a settings toggle was added allowing users to turn the model off and remove it, stating: 'Once disabled, the model will no longer download or update.' Google has not announced a change to the initial consent flow, has not committed to an opt-in model for future AI deployments, and has not explained why the default-on setting was not accompanied by a notification or prompt at the point the file was first written to user storage. Source: Google spokesperson via Yahoo Tech and Gizmodo, May 6, 2026.
06I switched to Firefox or Brave. Should I be concerned about similar behavior?
Based on current documentation: no. Firefox does not deploy any on-device LLM automatically — AI features require explicit user installation of extensions. Brave's Leo AI assistant is entirely user-initiated: you must explicitly enable it and choose which model to download. Neither browser has documented automatic background model deployments comparable to Chrome's Gemini Nano rollout. If this issue drove you to a different browser, both Firefox and Brave represent meaningfully different default consent postures on on-device AI deployment. Sources: gHacks analysis, May 6, 2026; Brave documentation.
The fastest fix for most people — verified by Aditya Kumar Jha, May 21, 2026: Open Chrome, go to Settings > System, and find the 'On-device AI' or 'Gemini Nano' toggle added in February 2026. Disable it, then navigate to the OptGuideOnDeviceModel folder and delete it to immediately reclaim 4 to 12GB of storage. If the toggle is missing, update Chrome to its latest version first. For Windows users who want the most durable solution — one that survives Chrome version updates — the Registry enterprise policy using GenAILocalFoundationalModelSettings = 0 under HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome is the recommended approach. And regardless of which fix you choose: the AI Mode button in Chrome's address bar is cloud-connected and sends your queries to Google's servers — a completely separate system from the local model. Do not assume otherwise based on visual proximity. You're now one of a small fraction of Chrome's 3.45 billion users who knows exactly what's in that folder — and exactly how to deal with it. Sources: Google spokesperson via Gizmodo, May 6, 2026; aifromthefield.substack.com, May 7, 2026; Malwarebytes, May 6, 2026.
