Chrome silently installs 4GB Gemini Nano AI model

The core legal accusation is not that Gemini Nano is dangerous, but that Chrome wrote it to disk without ever asking. Alexander Hanff's audit, reproduced by gHacks, Cybernews and Tom's Hardware, found a fresh Chrome profile materialize a 4GB weights.bin inside OptGuideOnDeviceModel in roughly fourteen and a half minutes, with no dialog, no toast, and no entry in the new-tab UI. Under the EU ePrivacy Directive's Article 5(3), storing or accessing information on a user's terminal equipment requires prior informed consent unless strictly necessary to deliver a service the user explicitly requested. Hanff's argument is that no Chrome user ever asked for a local LLM, and the visible AI Mode pill in the address bar actually routes to Google's cloud — meaning the local 4GB file is not strictly necessary even for the AI feature most users notice.

Google's response, given to Decrypt and Gizmodo, sidesteps the consent question and reframes the model as infrastructure: a lightweight on-device engine for scam detection and developer APIs that keeps data off the cloud. That framing is plausible from a product viewpoint, but PCWorld's editorial captures the disconnect: even granting that on-device inference can be privacy-positive, depositing 4GB on someone's drive without a dialog 'and he has a point.' The February 2026 opt-out setting is real, but it is precisely an opt-out — under EU rules, the inversion of consent is the entire problem, not the fix.

What turned a niche storage gripe into a viral story is the persistence. Hanff and PCWorld both documented that deleting weights.bin does not stick: Chrome's optimization-guide component classifies the missing file as a transient error and queues a fresh 4GB download on the next eligible window. The user-visible result is a browser that appears to override an explicit action — dragging a file to the trash — by silently undoing it minutes or hours later. Hanff's blog post puts it bluntly: 'If the user deletes it, Chrome re-downloads it.'

This design exposes how Chrome's component-update pipeline differs from a normal software install. Optimization-guide-on-device-model is treated as a managed component whose presence is enforced by policy, not a user choice. That is also why the only durable fixes route through chrome://flags or the new Settings > System > On-device AI toggle: the flag and the setting tell the policy engine to stop wanting the file, which is a different operation from removing the file. For users who think of their disk as their property, that subtle inversion — where the cloud-controlled policy outranks the local file system — is the part that feels least like a browser and most like a managed endpoint.

The under-discussed angle in Hanff's audit is environmental. He puts the per-device install at roughly 0.06 kg CO2-equivalent, dominated by network transport and the embodied energy of provisioned storage. Multiplied across Chrome's footprint — Conduct Atlas cites more than two billion users — the math becomes uncomfortable: 6,000 tonnes of CO2e at 100 million devices, 30,000 tonnes at 500 million, and up to 60,000 tonnes at one billion. TechRadar's framing makes the figure tangible: 30,000 tonnes is roughly the annual emissions of 6,500 passenger vehicles, paid out for a single model push.

That number compounds because the file is not static. The Register's reporting tracked the model growing from ~3GB in April 2025 to ~4GB by November 2025, and the re-download behavior means any user who tries to reclaim disk space pays the transfer cost a second time. For users on metered connections — common in much of Europe, Latin America and Southeast Asia — Chrome is silently consuming a meaningful fraction of a monthly data cap to ship a model that does not power the AI feature visible in the address bar. The climate critique is the rare tech-policy argument that hits storage hawks, sustainability advocates and EU regulators with the same data point.

The reaction map matters. Outrage concentrated on Reddit, where r/degoogle's top thread by u/BlokZNCR became the dominant venue for mass-migration sentiment toward Firefox, LibreWolf and Brave; r/whennews focused on the practical chrome://flags disable steps; r/tutanota fit the story into a broader Google pattern. YouTube tilted instructional — Tech Jarves and Automation Avenue both led with how to find and stop the install — while X surfaced the EU angle most aggressively, with posts from Marius Fanu, Hedgie and Pirat_Nation foregrounding the consent and re-download behavior.

The more interesting signal is the contrarian undercurrent inside the same threads. Reddit's u/Solonotix called local inference a privacy step forward over cloud calls, u/krizzalicious49 pushed back on the 'no consent' framing by arguing there is no strong evidence Chrome is installing the model on every device without warning, and u/Smitellos pointed out that Firefox also ships a local AI component. None of these dissolve the core complaint — none dispute that Chrome writes the file or that it re-downloads after deletion — but together they map the real seam in the debate: the disagreement is not whether the file exists, it is whether shipping it by default counts as a privacy upgrade (because nothing leaves the device) or a privacy violation (because nothing was asked). EU law sides with the latter framing; Google's product narrative sides with the former.

The reason the story has legs beyond a single news cycle is the comparison set. Coverage from XDA Developers and the verified research record both note that Firefox and Apple require opt-in for analogous on-device AI features, putting Chrome's silent default in sharp relief. Chrome is now the outlier among major consumer software vendors in writing a multi-gigabyte AI model to disk as a default behavior, while peers gate equivalent functionality behind an explicit user choice.

That asymmetry reframes Google's February 2026 opt-out as a partial concession rather than a resolution. The opt-out exists, but the default did not change — every new Chrome install, on every eligible machine, still starts from the same 4GB write. For EU regulators applying Article 5(3), that distinction is decisive: opt-out collection of any kind on terminal equipment has been the consistent legal flashpoint of the last decade, from cookie banners to fingerprinting to now AI weights. For users who care more about disk than law, the comparison with Firefox and Apple is what converts a technical complaint into a switching argument — which is why the dominant sentiment in the r/degoogle thread is not 'fix Chrome' but 'leave Chrome.'